Document Automation
Product features
By practice area
By company size
Contract Review
PRODUCT FEATURES
Resources
LearN
Case Studies
Pricing

What a contract playbook is, what goes in one, a worked example for a liability cap, and how to build a contract review playbook your team will use.
Gavel Exec reviews, redlines and drafts contracts inside Microsoft Word, checked against your own playbooks. Start with 25 free queries, no credit card required.
A contract playbook is a written guide to how your organization negotiates one type of contract. For each clause that gets negotiated, it records your standard position, the fallback positions you will accept, the point where you walk away, who can approve an exception and the reasoning a reviewer needs to apply it. Legal teams use playbooks so every reviewer negotiates the same way.
By the Gavel Team. Last updated October 30, 2026.
A contract playbook is your organization's set of negotiating positions for a type of agreement, written down so anyone reviewing that agreement applies them the same way. It covers the clauses that get negotiated, the alternatives you accept and who decides when a request goes further.
You will also see it called a contract review playbook, usually when the team applies it to the other side's paper, or a negotiation playbook when it guides the whole negotiation. In-house legal teams, law firms that negotiate the same agreements for many clients, and procurement and sales teams that handle routine contracts without a lawyer on every deal all use them.
A playbook is confidential. It lists the concessions you are prepared to make, so it stays inside the team while your template and your redlines go to the counterparty.
A contract playbook has a short header that says what it covers and an entry for each negotiated clause. Each entry gives the reviewer a position, the alternatives and the person who decides, with enough reasoning to handle requests the playbook did not anticipate.
The header states the contract type, which side you represent, any deal-size or risk thresholds, the owner and the date of the last review. Each clause entry then contains:
The table below shows one complete entry for a limitation of liability clause in a vendor master services agreement (MSA), written for the customer. A full playbook repeats this structure for each clause your team negotiates.
Illustrative example only. Positions depend on the deal, the industry and the governing law. This example is not legal advice.
| Playbook element | Example entry |
|---|---|
| Issue | Limitation of liability in a vendor MSA where your company is the customer |
| Why it matters | The cap sets the most you can recover if the vendor fails to perform or mishandles your data. A low cap shifts that risk to you. |
| Standard position | Mutual cap equal to the fees paid or payable in the 12 months before the claim. Breach of confidentiality, breach of data protection obligations, indemnification obligations and gross negligence or willful misconduct sit outside the cap. |
| Fallback 1 | Keep the 12-month general cap. Replace the uncapped data protection and confidentiality carve-outs with a separate higher cap of three times annual fees. |
| Fallback 2 | Lower that separate cap to two times annual fees. The vendor's indemnity for third-party intellectual property (IP) infringement claims stays uncapped. |
| Walk-away point | A general cap below six months of fees, any cap on the vendor's IP infringement indemnity, or an exclusion of liability for data breaches. |
| Approver | Contract manager for Fallback 1. Senior counsel for Fallback 2. General counsel and the business owner, with the security team for data terms, for anything past the walk-away point. |
| Reviewer guidance | Check whether "fees" means fees paid or fees payable, and whether the cap applies per claim or in total. If the vendor processes personal data, confirm the data processing agreement (DPA) does not set a lower cap of its own. |
For complete examples, Gavel publishes free contract playbooks for NDAs, master services agreements and data processing agreements, each with a full position table, sample language and a review checklist.
A template is the draft you send, a clause library holds approved language to reuse and a checklist lists what to look for. A playbook is the only one of the four that tells a reviewer what to accept, what to escalate and who decides.
| Tool | What it holds | Used when | Answers |
|---|---|---|---|
| Template | A complete first draft of your preferred agreement | You send the first draft on your own paper | What do we propose? |
| Clause library | Approved clauses and alternative wording, organized by topic | Drafting or responding to a markup | What language may we use? |
| Checklist | Issues a reviewer must look for | Reviewing any draft | Did we check everything? |
| Playbook | Positions, ordered fallbacks, walk-away points, approvers and guidance for each negotiated clause | Reviewing the other side's paper or its changes to yours | Can we accept this, and if not, who decides? |
The four work together. The template sets the standard positions, the clause library supplies the fallback language and the playbook ties them to approval rules.
Start with one contract type and the deals you have already signed. Write down what you accepted, set approval rules and test the result on live contracts before you roll it out.
Add the next contract type once reviewers are using the first playbook.
A reviewer reads the incoming draft clause by clause, compares each one with the playbook and responds with the standard position or an approved fallback. Anything the playbook does not cover, or anything past a walk-away point, goes to the named approver.
Many teams group decisions into three tiers so reviewers know when to act on their own:
Clear tiers let junior lawyers and contract managers close routine agreements without waiting for a senior lawyer, and they send the unusual requests to the person accountable for them.
AI contract review software turns each playbook position into a rule, checks a draft against every rule and reports which clauses meet your positions and which do not. Most tools also propose edits, often as Word tracked changes, that bring a clause back to your standard or an approved fallback.
Gavel Exec is AI contract review and drafting software that runs inside Microsoft Word as an add-in and on the web. In Gavel Exec you can start from a built-in playbook written with practicing attorneys, write rules by hand, or generate rules from checklists, spreadsheet playbooks and signed agreements in .docx, Portable Document Format (PDF) or comma-separated values (CSV) files. Each rule passes or fails with the reason, and you can insert the proposed changes as tracked changes or as negotiation comments. Playbooks are created in the Word add-in, carry over to the web app and can be shared with Read-Only or Edit Access. See contract playbook software for the full workflow and how to write playbook rules that AI applies well.
Other tools report results in different shapes: pass, fallback or flag in some, and acceptable, needs review or not acceptable in others. Our comparison of the best contract playbook software covers ten tools, how each builds playbooks and what each costs. Gavel Exec costs $160 per user per month, or $1,740 per user per year, with 25 free queries per user and no credit card.
Whatever tool you use, a lawyer stays responsible for the result. American Bar Association (ABA) Formal Opinion 512 (July 29, 2024) applies lawyers' existing duties to generative AI, including competence and the duty to keep client information confidential. In practice, a lawyer reads each result before it goes into a draft.
Before AI can apply a playbook written for people, rewrite each entry as one rule per issue that states what passes, where in the contract to look and the fallback language to propose.
Playbooks fall out of use when they sit in a shared drive, reflect positions nobody accepts in practice or never change. Four habits keep them current.
A template is the draft you send on your own paper. A playbook tells reviewers which changes to that draft, or to the other side's draft, they can accept, which need approval and which they must refuse.
Yes. Teams use "contract review playbook" when they apply it to the other side's paper and "negotiation playbook" when they use it across the whole negotiation. The contents are the same: positions, fallbacks, walk-away points and approvers.
One named lawyer should own each playbook and approve every change to it. The business teams that live with the contract, such as procurement, sales, finance and security, should review the positions that affect them.
Review it at least quarterly, and sooner when the law, your risk appetite or your standard templates change. Look at the exceptions approved since the last review: a fallback approved again and again is a sign it should become the standard.
Yes. Signed agreements show what you have accepted in practice, which is the best starting point for fallbacks. Some AI tools, including Gavel Exec, can generate draft playbook rules from signed agreements, checklists or spreadsheet playbooks for a lawyer to review.
No. A playbook lists your fallback positions and walk-away points, so it is an internal, confidential document. Share your template or your redlines with the counterparty, and keep the playbook inside the team.
Related reading: best AI contract review tools for lawyers, the best contract playbook software comparison and playbook-based AI redlining for in-house teams.
What Claude offers lawyers and law firms in 2026: which plan to buy, how client data is handled, Claude for Legal plugins, Cowork and Claude's limits.
Client intake and CRM software for law firms compared by firm size: what each tool does, what it costs and how it hands off to documents.
28 verbatim Reddit comments about Gavel Exec and Gavel Workflows from r/LawFirm, r/legaltech and r/Lawyertalk, grouped by topic, each linked to its thread.