How to build a contract playbook
Your positions, fallbacks and red lines, written once. Then applied to every contract.
Guide · Updated 17 October 2026 · By the Claren team
The short answer
- A contract playbook is how your team negotiates, written down: the positions you take, the fallbacks you'll accept and when a deal goes to someone more senior.
- Build it from the two or three contract types that fill your week, one clause at a time, with the reason for each position.
- Write it to be applied line by line, by a junior lawyer or by AI, not to be admired.
- In Claren, your playbook goes into the envoys' memory once, and every contract comes back redlined in Word against it, with a summary of what's off-playbook.
What a contract playbook is
The way your best lawyer negotiates, written so everyone else can.
A contract playbook sets out, clause by clause, what your team wants in a contract, what it will accept instead, and what it will never accept without approval. It is the answer to the question every reviewer asks on every contract: is this one fine?
With a playbook, a new lawyer reviews like your most experienced one, and the business gets the same answer whichever lawyer it asks. Without one, every review starts from scratch, positions drift from lawyer to lawyer, and the knowledge of what was conceded last time leaves when the person who conceded it does.
For in-house teams the case is stronger still. The same few contract types come round again and again: NDAs, supplier agreements, customer terms, DPAs. The positions barely change. What changes is how much time the team has to apply them. A playbook is what lets that work be handed off, to a junior lawyer, to the business for the simplest cases, or to AI.
It is also what makes AI contract review useful. A tool without your playbook can tell you what a contract says. A tool with it can tell you what to change.
What goes in a contract playbook
Six parts for every clause that matters.
- The clause. Named the same way every time, in the same order, so a reviewer can work through a contract and the playbook side by side.
- Your standard position. What you want, in a sentence or two, with example wording a reviewer can drop straight into the draft.
- Why. The reason behind the position. It lets a reviewer, or an AI, judge the cases the playbook didn't foresee.
- Fallbacks, in order. What you'll accept when the first position is refused, listed in the order you'd offer them, each with example wording.
- Red lines. What is never acceptable, and what is acceptable only with approval. Say which is which.
- Who escalates. Who approves each exception: the GC, finance, the security team. This is what keeps a playbook safe to hand on.
How to create a contract playbook, step by step
Seven steps, most of them a morning's work for the first contract type.
- Start with the contracts you see most. Don't try to cover everything. Pick the two or three contract types that fill your week, often NDAs, supplier agreements and customer terms. The first playbook is better narrow and used than complete and unread.
- Read the last twenty of each. Pull your recent signed contracts and the redlines behind them. The clauses you argued about are the ones the playbook needs first. The clauses nobody ever touched can wait.
- Write your standard position for each clause. For every clause that matters, write what you want and why, in a sentence or two. Limitation of liability: the cap you want and what sits outside it. Indemnities: which you give, which you need, which you never give. Term and termination: notice periods, renewals and exit rights. Data protection: what the other side commits to when it handles personal data. Governing law: where you'll accept disputes.
- Add fallbacks, in order. Negotiation is about what you'll accept when your first position is refused. List the fallbacks in the order you'd offer them, with example wording for each, so nobody drafts from a blank page.
- Draw the red lines and the escalation path. Some terms are never acceptable. Others are acceptable with approval. Mark which are which, and name who approves. That is what makes the playbook safe to hand to junior lawyers, to the business, or to AI.
- Write it to be applied, not admired. One clause per section, in the same order every time. Short sentences: positions, not essays. Example wording for the standard position and each fallback. A note on what to do when the contract says nothing at all.
- Keep it alive. Every negotiation teaches you something. When you accept a new fallback, or a position stops holding, update the playbook. Give it an owner and a date it was last reviewed.
A contract playbook template
For a supplier agreement. Replace the positions with your own; keep the shape.
| Clause | Our position | Fallback | Escalate if |
|---|---|---|---|
| Limitation of liability | Mutual cap at 12 months' fees. Data breach, confidentiality and indemnities sit outside the cap. | Cap at 24 months' fees with a super-cap for data breach. | Supplier asks for a cap below 12 months' fees, or caps data breach at the general cap. |
| Indemnities | Supplier indemnifies for IP infringement and data protection breaches. | IP indemnity only, uncapped; data protection inside a super-cap. | We are asked to give any indemnity beyond our own IP. |
| Term and termination | Twelve months, no auto-renewal. We may end for convenience on 30 days' notice. | Auto-renewal with 60 days' notice to opt out, and a renewal reminder logged. | No termination for convenience, or a term over three years. |
| Data protection | Our DPA applies. Sub-processors listed, with notice of changes. Breach notice within 48 hours. | Supplier's DPA if it meets our standard terms; breach notice within 72 hours. | Personal data leaves the UK or EU without approved transfer terms. |
| Payment | Net 45 from a valid invoice. Fees fixed for the initial term. | Net 30. Annual increases capped at CPI. | Payment in advance for more than one quarter. |
| Governing law | England and Wales, courts of London. | The supplier's home law, if it is the law of a US state, the UK or an EU member state. | Any other law, or mandatory arbitration abroad. |
| Silence | If the contract says nothing on a clause above, add our standard wording. | Accept silence on payment terms only. | Silence on liability or data protection. |
An NDA playbook
The contract most teams should playbook first: high volume, low judgement, the same points every time.
| Clause | Our position | Fallback | Escalate if |
|---|---|---|---|
| Mutual or one-way | Mutual, unless only we disclose. | One-way in our favour when only we disclose. | One-way against us. |
| Definition | Information marked or reasonably understood as confidential. | Marked information only, with oral disclosures confirmed in writing within 30 days. | Everything we disclose, with no exclusions. |
| Exclusions | The usual four: public, already known, independently developed, received from a third party. | None. These are standard. | Any of the four is removed. |
| Term | Two years from disclosure. | Up to five years; trade secrets for as long as they remain secret. | Perpetual for all information. |
| Permitted disclosure | Employees, advisers and affiliates who need to know, on the same terms. | Employees and advisers only. | No disclosure to our professional advisers. |
| Non-solicitation | Not in an NDA. | Twelve months, limited to people we worked with directly. | Any non-compete, or non-solicitation over twelve months. |
| Governing law | England and Wales. | The other side's law, if the UK, an EU member state or a US state. | Any other law. |
Where a playbook lives
The same positions, kept three ways.
| In Claren | In a Word document | In a general assistant | |
|---|---|---|---|
| Applied to every contract, the same way | ✓Yes | Depends who reviews | If someone pastes it in |
| Tracked-change redlines in Word | ✓Yes | Made by hand | Copied in by hand |
| A comment explaining every change | ✓Yes | If the reviewer adds one | —No |
| Fallbacks applied in order | ✓Yes | By hand | If asked |
| A summary of what's off-playbook | ✓Yes | —No | If asked |
| One playbook for the whole team | ✓Yes | ✓Yes | One per person's chat |
| Picks up contracts from Slack on its own | ✓Yes | —No | —No |
| Learns new fallbacks as you approve them | Into memory | When someone edits it | —No |
| Every reviewed contract filed with its terms | Datastores, kept by envoys | —No | —No |
— Not part of it.
AI contract playbooks
Most legal AI can now read a playbook. The difference is where it lives, and who applies it.
Reviewing against a playbook is no longer rare. Spellbook has playbooks inside Word. Microsoft's Legal Agent in Word compares a contract with your playbook and redlines with tracked changes. Claude for Legal compares a contract with a playbook clause by clause, from a profile each lawyer writes for themselves.
All of these put the playbook in the hands of one lawyer at the keyboard. The lawyer opens the document, runs the review, checks the result and sends it. The playbook makes that lawyer faster. It doesn't take the contract off their desk.
An in-house team needs the second thing. The playbook is the team's, not one person's. Contracts arrive from the business, not from a lawyer's own inbox. And the value is in every NDA and every supplier agreement being reviewed the same way, without waiting for someone to have a free hour.
That is how Claren uses a playbook. It isn't a file one lawyer loads. It is part of how the team's AI employees work.
How Claren applies your playbook
From the positions you write to a redline ready to send.
- It goes into memory once. Your positions, fallbacks and escalation points go into the envoys' memory, with your preferences down to the format. You don't paste it into a chat again. More
- Every envoy in the team follows it. The playbook belongs to the legal team. Each of its envoys applies the same positions, on every contract, whoever asked. Other teams can keep their own.
- The contract arrives. From the Claren app, from a DM, or from a Slack channel the team's envoys watch. A routine can pick up every contract that lands there, with nobody needing to ask. More
- It comes back redlined in Word. Tracked changes in the Word document itself, as a lawyer would make them, with a comment on every change explaining the position behind it.
- Fallbacks are applied, and the rest is flagged. Where the other side's wording falls short of your position, the envoy applies your fallback. A summary lists what's off-playbook, so a lawyer reads the exceptions first.
- You sign off. Before anything leaves the team, the envoy asks. The lawyer approves, adjusts or escalates, as the playbook says. More
- The playbook learns. When you approve a new fallback or say why a change was wrong, it goes into the envoys' memory. The next contract gets it.
No written playbook yet?
Most teams don't have one. That isn't a reason to wait.
Your team already has a playbook. It is spread across your templates, your past redlines and your lawyers' heads. Claren builds a first draft from your templates and past deals, and your team refines it from there. Or teach the envoys your positions as you go, contract by contract, and they keep them.
Either way, start with one contract type, usually the NDA, and widen from there. The envoys' memory grows with every review you correct, and the second month needs less of you than the first.
Reviewing against the playbook with Claren
The same positions, applied at volume.
Legal teams hand Claren their NDAs, supplier contracts and distribution agreements, and get tracked-change redlines back against their playbook. Every change carries a comment. Every fallback is applied the same way, on the first contract and the hundredth.
The playbook travels with the work: from customer agreements and strategic partnerships to HR policies and compliance documents, across jurisdictions. The positions don't drift, and the team gets hours back every week.
“Claren helps me quickly spot what we might have missed and focus on what actually matters.”
See Claren in action.
More on contract review
Questions
What is a contract playbook?
A written guide to how your team negotiates a type of contract: your standard position on each clause and why, the fallbacks you'll accept in order, the red lines, and who approves an exception.
How do you create a contract playbook?
Start with the two or three contract types you see most. Read your last twenty of each, write your standard position and the reason for every clause that matters, add fallbacks in order, mark the red lines and who escalates, and give the playbook an owner who keeps it current.
Is there a contract playbook template?
Yes: one row per clause, with four columns: the clause, your position, your fallback and when to escalate. The template on this page shows a supplier agreement and an NDA in that shape. Replace the positions with your own.
What should an NDA playbook cover?
Whether the NDA is mutual, the definition of confidential information, the standard exclusions, the term, who may receive the information, any non-solicitation, and governing law. NDAs are the best place to start: high volume and the same points every time.
What is an AI contract playbook?
Your positions, fallbacks and escalation points, written so an AI can apply them. In Claren, the playbook goes into the envoys' memory once, and every contract is checked against it and returned as a tracked-change redline in Word.
Do we need a written playbook to start with Claren?
No. Claren can build a first draft from your templates and past deals for your team to refine, or you can teach the envoys your positions as you go, and they keep them.
What comes back when Claren reviews a contract?
Tracked changes in the Word document, a comment on every change, your fallback positions applied, and a summary of what's off-playbook.
Can different teams have different playbooks?
Yes. Each team has its own envoys, and each envoy its own memory, so commercial and procurement can each keep their own positions.
Is our playbook used to train AI models?
No. Neither Claren nor its model providers train AI models on your data. Your playbook only ever improves your own envoys.
