Desk notes · In-house legal · How the desk works
What a contract playbook looks like
Most legal teams have positions. Few have them written down in a form someone else can apply. A playbook is that form: a table, one row per clause, five columns.
Ask an in-house lawyer what the company accepts on liability and you will get a clear answer. Ask them to write down the answer for every recurring clause, with the point at which they would walk away, and the answer is usually that it lives in their head and in last year’s signed contracts. That works while the same lawyer reviews every document. It stops working the moment the queue is shared — with a new hire, another team or an external desk.
What it is not
A playbook is not your template; the template is your opening draft, and the playbook is what you do when the other side changes it. It is not a policy either; a policy says what the company values, and the playbook says what number goes in clause 12. And it is not a memo. Prose invites interpretation, and the purpose of a playbook is to remove it.
The five columns
- Clause. The term, named the way it appears in the contracts you actually see.
- Your position. What you ask for in the first round.
- Acceptable fallback. What anyone applying the playbook may agree without asking.
- Red line. What is never agreed without a decision from the person in the last column.
- Who decides. A role, not a name: head of commercial legal, privacy lead, CFO for financial terms.
A short template
Six rows from a buyer’s playbook for supplier agreements. Your positions will differ; the shape should not.
| Clause | Your position | Acceptable fallback | Red line | Who decides |
|---|---|---|---|---|
| Price changes | Fixed in year one; then once a year, 90 days’ notice, capped at an agreed index | Flat annual cap, with a right to terminate the affected items above it | Changes at the supplier’s discretion | Head of procurement |
| Liability cap | Mutual, 12 months’ fees | The greater of 12 months’ fees and a fixed amount set by contract value | Cap below the value of one order | Head of commercial legal |
| Uncapped liability | Wilful misconduct, gross negligence, fraud, death and personal injury, confidentiality, IP indemnity | Confidentiality and data under a separate, higher cap | IP indemnity capped | Head of commercial legal |
| Payment terms | 60 days from a correct invoice | 30 days | Payment in advance for recurring supply | Finance |
| Sub-processors (DPA) | General authorisation, 30 days’ notice, objection right | 14 days’ notice, objection with termination as remedy | No notice of changes | Privacy lead |
| Governing law | Our law, our courts | A neutral EU law; CISG excluded | Law of a country where we have no counsel | Head of commercial legal |
Two rules make the table usable. Positions are written as text someone can put in a redline, not as principles: “12 months’ fees”, not “a reasonable cap”. And the fallback is a genuine pre-approval: if the desk agrees it, nobody asks afterwards why.
What goes around the table
A header with the contract type, the governing law per template, the version number, the date and who approved it. A short list of value or counterparty thresholds above which everything escalates regardless of the table. And a notes column, if you need one, for the reason behind a position. The reason is what lets a reviewer argue it with the counterparty instead of just repeating it.
How to fill it in
Do not start from a blank page. Take the last ten signed contracts of the type and read what you actually agreed. The positions you hold in practice are the first draft of the playbook; the session with your lawyers is about correcting them, not inventing them. Expect ten to fifteen rows per contract type. More than twenty usually means the table is describing the template rather than the negotiation.
How it changes
Every escalation that ends in a decision is a candidate for a new row or a new fallback. Collect them, review them monthly with whoever approves the playbook, and issue a new version. Old versions stay on file, so any signed document can be traced to the rules that applied when it was negotiated.
Several teams
A group with several business units or entities keeps one common core — the rows the group decides centrally, typically liability, data protection, sanctions and governing law — and one table per team on top of it. Each team approves its own table. The common core changes only with the GC’s approval.
Why it is worth the afternoon
A playbook makes review consistent across people, measurable — every deviation is visible against a written position — and delegable. It is also the one document that keeps its value whoever is doing the work. Teams that build it for an external desk usually find their own lawyers use it first.
Next step
No playbook yet?
Building it is the first thing the desk does with a new team. Send one real contract to start.