Run Your Contract Playbook on Every Draft, Then Refine the Rules
A contract playbook only works if it runs on every draft and changes with the results. Here's what Word review flags and when to revise the rules.
A contract playbook is the rulebook for one contract type: the positions your team prefers, the fallbacks it will accept, and the point where a deviation goes to a lawyer. In-house legal teams usually own it and apply it to counterparty paper, and some call it a legal playbook. It pays off when the team runs it on every draft and revises it from what those drafts show.
Throughout the rest of this article, we'll follow one customer's services agreement, checked against a software company's Playbook, from the first clause to the changes the results send back to the Playbook. Need to pull terms out of hundreds of agreements at once instead? Start with AI contract analysis at scale.
Executed Contracts, Old Guidelines, or a Blank Page Can All Seed a Playbook
You don't have to start a contract negotiation playbook from a blank table of hypothetical positions. Harvey’s Playbook Builder converts an existing playbook into structured rules, builds rules from contracts that already hold language your team won, or helps you create them from scratch. Executed agreements are especially useful when your written policy and your negotiating history have drifted apart.
A good rule carries a preferred position, a fallback, guidance for the reviewer, and an escalation path. Playbook Builder also keeps citations to the source documents behind each rule, so you can check how a standard was built.
The hard cases sit between the standard and the fallback. Say your Playbook prefers payment within 30 days and accepts 60. Then "Net 75" lands on your desk. The reviewer needs enough guidance to see why it's out of range and what to do next. You can also mark a rule required, so missing standard language gets flagged. With the rules in place, run them on a live draft.
Every Covered Clause Comes Back Acceptable, Needs Review, or Unacceptable
Say the incoming draft is a customer's services agreement on the customer's paper. Playbook review in Word checks every covered clause against your rules and shows the result in the draft. Here's how it might come back (illustrative):
Clause | Incoming language | Playbook result | Next action |
|---|---|---|---|
Payment terms | Net 75 | Needs review | Fallback allows net 60, so counter at 60 |
Liability cap | Unlimited for data breach | Unacceptable | Negotiate to the capped position |
Governing law | Delaware | Acceptable | None |
Assignment | Consent not required for affiliate transfers | Needs review | Fallback allows affiliate transfers with notice |
"Acceptable" means the clause fits a position you've already approved. "Needs review" is your queue, and "unacceptable" is your negotiation list. You stay in control either way.
After reading Harvey's reasoning, you check the proposed language and accept edits as tracked changes inside Harvey for Word, right where you already draft. No copying clauses into another tool.
In Practice: For Carvana, scaling playbooks with Harvey reduced drafting and review time by 80%. Read how the Playbook Builder works.
Want to see it in action? Millie Lehmann, Strategic Business Development Lead at Harvey, builds a Playbook from existing guidelines and runs it against a live contract in Word.
See how a Playbook moves from existing guidance into a live contract review in Harvey for Word.
Provisions Nobody Wrote a Rule for Still Get Flagged for Review
Your Playbook only knows what your team has written down, and counterparty paper keeps wandering into positions nobody planned for. In our example, the customer's data-use clause matches no rule at all. Harvey flags it for manual review because no rule covers it, and the lawyer decides whether the clause is acceptable.
That decision can carry forward to the next draft. Playbook Builder can show where the Playbook has coverage gaps and suggest fallback language to fill them. Once your team agrees on a position, it becomes a new rule.
Contract Review Agents go further. They draw on executed contracts and negotiation guidelines alongside the Playbook, and precedent benchmarking shows how a proposal compares with positions your team accepted before. You can check the source agreements. The capability is available through an Early Access waitlist.
Once you've settled on a position, AI-assisted redlining drafts the revision for your review before it goes back to the counterparty. Do this for enough deals and the same exceptions start repeating. That tells you something about the Playbook.
A Fallback Accepted Deal After Deal Deserves a Second Look
A playbook captures one moment in your negotiating history, and negotiations keep moving. Watch for three patterns:
- A fallback accepted on nearly every deal may be your real standard.
- A rule that flags the same clause over and over, with Legal accepting it every time, may have a threshold that no longer fits how the team works.
- A tight rule can be deliberate even when the business keeps asking for exceptions, so check the intent before you loosen it.
Harvey’s Playbook Builder treats a playbook as a living artifact, so you can change a fallback, liability cap, or escalation path as your deals change. In our example, the net 60 fallback keeps getting accepted, and the owner has to decide whether it belongs in the standard position.
Harvey for Word Checks Incoming Drafts Against Your Playbook
On every deal, Harvey for Word checks the incoming draft against your Playbook and sorts each covered clause into acceptable, needs review, or unacceptable. Clauses no rule covers get flagged as well. You start with the exceptions already named and make every call yourself.
Between deals, those results show the Playbook owner where to look. A fallback that keeps winning, a rule Legal keeps overriding, or an uncovered clause that comes back on draft after draft is a reason to open Playbook Builder and revise. Each revision changes how the next draft comes back.
Comparing review tools? How AI is transforming contract review software maps the category. For in-house legal teams that want more consistent review without another manual checklist, request a demo to see a Playbook run against a sample draft in Word.
Contract Playbook Questions, Answered
What is a contract playbook?
A contract playbook is a set of rules that defines standard positions, acceptable fallbacks, escalation conditions, and unacceptable deviations for one contract type. In-house legal teams usually own it and apply it to counterparty paper, which keeps review consistent from lawyer to lawyer and deal to deal.
Can you give an example of a contract playbook entry?
Limitation of liability is a common one. A hypothetical rule might set 12 months of fees as the standard cap, allow 24 months for enterprise deals as an approved fallback, and send anything uncapped to Legal. Your exact positions depend on your risk appetite and contract type.
How is a contract playbook different from a clause library?
A clause library stores the language an organization has approved for reuse. A contract playbook tells the reviewer how to evaluate language the counterparty has already proposed, including what's acceptable, which fallback applies, and when a deviation goes to a lawyer.
