Redlining with AI using a negotiation playbook
By the ChamberOne team 4 minute read
Every experienced commercial lawyer carries a playbook in their head. They know which liability cap they accept, which indemnities they strike, and which clauses are worth a fight. A junior who lacks that knowledge marks up a draft differently each time. AI tools can mark up a contract in seconds, but unless they are told your positions, they apply an average view. Writing the playbook down fixes that for both people and tools. This piece is for commercial and in-house lawyers and describes how to build and use one without giving up control.
Key points
- A playbook states preferred, fallback and walk-away positions for each clause, with a reason.
- Tell the tool the side you act for, the jurisdiction and to say 'no playbook entry' when none applies.
- Read every proposed edit against the original and check the defined terms and interactions.
- Test on closed deals first and update the playbook after each negotiation.
What a playbook contains
A playbook sets out, clause by clause, how you want to deal with the usual terms. For each one it states three positions. The preferred position is what you ask for. The fallback is what you will accept if pushed. The walk-away is the point beyond which you escalate or decline.
It also says why. A note that explains the risk behind a position helps a junior judge a variation that the playbook did not anticipate, and helps a tool word a comment properly.
An example of one entry
Take a limitation of liability clause in a supplier agreement where you act for the customer. Preferred: the supplier's liability is capped at a multiple of annual fees, with no cap for certain losses such as breach of confidentiality. Fallback: a lower multiple, with the same carve-outs. Walk-away: any cap that applies to data protection breaches, or any exclusion of direct loss. Escalate to the partner if the supplier insists.
Notice the structure. It is short enough to apply quickly, specific enough to test, and honest about where the lawyer must decide.
Writing the playbook
- 1
Start with the document type you review most, such as a master services agreement or an NDA.
- 2
List the ten to twenty clauses that matter, and add any that your clients always ask about.
- 3
Write the three positions for each, and a sentence of reasoning.
- 4
Note the side you act for, since positions reverse between customer and supplier.
- 5
Mark the jurisdiction and any law that affects the position.
- 6
Have a second lawyer test it on a past contract and note where it was unclear.
- 7
Give it an owner and a review date.
Using it with an AI tool
Give the tool the playbook and the draft and ask for a clause-by-clause comparison. For each clause it should say which position the draft is closest to, quote the text, propose wording that moves it to the preferred or fallback position, and explain the change in a sentence. It should say 'no playbook entry' where there is none, and should not invent a position.
Ask it to list anything in the draft that the playbook does not cover. Unusual clauses are where lawyers must think hardest, and a tool is more useful at pointing to them than at deciding them.
A lawyer approves every change
Treat the output as a proposed mark-up, not a final one. Read each suggested edit against the original clause. Check that the new wording works with the definitions and with other clauses. Check that the tool has not silently changed something you did not ask it to change. Compare the final document against the original with your usual comparison function.
Then apply judgement about the deal. A playbook is a default. The relationship, the value, the other side's bargaining position and the client's wishes can justify a departure, and only a lawyer can decide that.
- Read each edit against the original clause
- Check the new wording against definitions and other clauses
- Compare the final document with the original
- Treat the output as a final mark-up
- Accept a change without checking nothing else was altered
- Leave unclear which side you act for
Where it goes wrong
Tools can misread a clause and propose an edit that answers the wrong problem. They can apply a customer-side position when you act for the supplier if the instruction is unclear. They can miss that a defined term changes the meaning of a clause. And they can produce comments that sound firm but are wrong in law, because the tool does not know your jurisdiction unless told.
Test the setup on closed deals before using it on live ones. Compare its mark-up with what a senior lawyer did and note the differences.
Handling the other side's draft and your own paper
Playbooks work best on the counterparty's paper, where you want to find what departs from your position. When you use your own paper, the playbook is a check that the draft still says what you want after a long negotiation. Ask the tool to compare the latest version with the playbook as well as with the previous version, since changes accumulate and a clause that has been softened twice may now sit below the walk-away position without anyone noticing.
Keep a record of each round: what was proposed, what was accepted, and which playbook position it fell under. At the end of the deal you will have a short list of concessions, which is useful to the client and to the next negotiator. It also helps you decide whether to alter the playbook.
Be careful with confidentiality. A counterparty's draft may be marked confidential, and your client's commercial terms are sensitive. Use only tools your firm has approved, and check what happens to the text you send.
Keep the playbook current
Review it after each negotiation that taught you something. Add the objections you heard and the compromises you reached. Retire positions that the market has moved away from. Record changes and reasons. A stale playbook applied consistently is worse than none, because it produces consistent errors.
- 1Finish a negotiation that taught you something
- 2Add the objections and compromises
- 3Retire positions the market has left
- 4Record changes and reasons
- Then back to step 1.
Document analysis in ChamberOne
- Upload a contract and get its type, parties, key dates, clauses and citations, each linked to the source paragraph.
- Risk flags on clauses are suggestions a partner can override.
What it does not do
- The site does not describe a negotiation playbook or automatic redlining feature.
- The analysis is produced by an AI model and can miss or misread things. Check it against the document.
- The document text is sent to the AI provider chosen for this feature.
This article is general information about the law, legal practice and technology, current when it was published. It is not legal advice. Laws and guidance change: check the sources linked above and take advice on your own circumstances from a lawyer qualified where you are.
Read next
AI contract review: a first-pass checklist for lawyers
What to ask an AI to flag on a first read of a contract, what it tends to miss, and where a lawyer must read every word.
5 minute readWhat AI document analysis extracts well, and what it misses
What AI document analysis does well on parties, dates, clauses and citations, and what it misses, with ways to spot the gaps.
5 minute readAI-assisted engagement letters: what to automate and what stays human
Merge fields and templates handle the routine parts of an engagement letter, while scope, fees and limits of liability need a lawyer's decision.
5 minute read