How to write a contract review playbook
A playbook is written as one table per contract type: for each recurring clause it states the standard position, the acceptable fallback and where the limit lies. It is the department's own document, and it can be loaded into whichever tool reviews the contracts. Here is how I write one for contracts under Swedish law, using a non-disclosure agreement as the example.
Updated by Nils-Erik Jansson
- Standard.
- Your position when you hold the pen. Written as contract wording, so the tool can compare it word for word.
- Fallback.
- What you accept if the counterparty will not agree to the standard. Often two steps, each written as wording.
- Limit.
- What you do not accept without a decision from someone other than the reviewer. State what is unacceptable and why, in one sentence.
Example: a non-disclosure agreement
A mutual NDA at a Swedish company. The positions are examples, not advice. Yours will look different.
Definition of confidential information
Standard
All information disclosed in connection with the purpose, in any form, with no marking requirement
Fallback
Marking required for written information; oral information protected if confirmed in writing within thirty days
Limit
Marking requirement with no confirmation rule for oral information
Escalation: Responsible lawyer
Comment: A marking requirement with no confirmation rule leaves the protection empty.
Duration of confidentiality
Standard
Three years from disclosure, with no time limit for trade secrets
Fallback
Two years
Limit
Less than two years, or a time limit for trade secrets as well
Escalation: General counsel
Comment: The Swedish Trade Secrets Act gives protection that should not be contracted away through a short confidentiality period.
Exceptions
Standard
The four usual ones: publicly known, already known, received from a third party without breach, independently developed, with the burden of proof on the recipient
Fallback
None
Limit
An exception for "generally useful knowledge", or a residuals clause letting the recipient use what it retains in memory
Escalation: General counsel
Comment: Residuals clauses make confidentiality worthless for know-how and are not accepted.
Governing law and disputes
Standard
Swedish law, Swedish general courts with the Stockholm District Court as first instance
Fallback
Arbitration under the expedited rules of the SCC (the Arbitration Institute of the Stockholm Chamber of Commerce)
Limit
Foreign law, or a forum outside the Nordic countries
Escalation: General counsel
Comment: An NDA is rarely worth a dispute abroad.
Contractual penalty
Standard
No contractual penalty, damages under the general rules
Fallback
A capped penalty, with the right to damages beyond the penalty
Limit
An uncapped penalty, or a penalty as the only remedy when we are the disclosing party
Escalation: Business owner together with a lawyer
Comment: The level of the penalty is a business decision; its structure is a legal one.
Return and deletion
Standard
On request and when the agreement ends, with the right to keep an archive copy under confidentiality and whatever the law requires
Fallback
Deletion with written confirmation
Limit
A deletion requirement covering backups without any carve-out
Escalation: Responsible lawyer
Comment: A requirement that cannot be met technically should not be signed.
The example has six rows. A full NDA playbook also covers the parties, the purpose, permitted recipients, personal data, permitted use and a disclaimer for the material disclosed.
Why playbooks go unused
The playbook was written as a policy, and the tool cannot compare against an aim. Nobody owns it, and old positions linger. The limits were set too tight: if everything is escalated, nothing is.
Putting it into Claude
The playbook is loaded as knowledge, with your template and two or three reviewed contracts beside it.
Putting a contract review playbook into ClaudeDownload
Free. No sign-up and no email address.
Background
What the playbook does in the tool
With a playbook, a review tool can read an incoming contract and mark where it departs from your positions, how serious each departure is, and what your fallback is. The result is a list to work through. The lawyer decides. Responsibility for the advice stays the same whatever the tool suggested, as the Swedish Bar Association's guidance makes clear [1].
Without a playbook the tool does what it can: it points to clauses that tend to be risky in general. That has some value, but it is not your review.
The structure per clause
I use the same five fields for every recurring clause.
| Field | Content |
|---|---|
| Standard | Your position when you hold the pen. Written as contract wording, so the tool can compare it word for word. |
| Fallback | What you accept if the counterparty will not agree to the standard. Often two steps, each written as wording. |
| Limit | What you do not accept without a decision from someone other than the reviewer. State what is unacceptable and why, in one sentence. |
| Escalation | Who decides when the limit is reached: the responsible lawyer, the general counsel or the business owner. Name or role. |
| Comment | Why the position is what it is, in two sentences, so that a new colleague understands it and the tool can explain the deviation to whoever asks. |
That gives one table per contract type. That is the whole playbook.
Example: a non-disclosure agreement
Here are some rows from a playbook for a mutual NDA at a Swedish company, governed by Swedish law. The positions are examples, not advice. Yours will look different.
| Clause | Standard | Fallback | Limit |
|---|---|---|---|
| Definition of confidential information | All information disclosed in connection with the purpose, in any form, with no marking requirement | Marking required for written information; oral information protected if confirmed in writing within thirty days | Marking requirement with no confirmation rule for oral information |
| Duration of confidentiality | Three years from disclosure, with no time limit for trade secrets | Two years | Less than two years, or a time limit for trade secrets as well |
| Exceptions | The four usual ones: publicly known, already known, received from a third party without breach, independently developed, with the burden of proof on the recipient | None | An exception for "generally useful knowledge", or a residuals clause letting the recipient use what it retains in memory |
| Governing law and disputes | Swedish law, Swedish general courts with the Stockholm District Court as first instance | Arbitration under the expedited rules of the SCC (the Arbitration Institute of the Stockholm Chamber of Commerce) | Foreign law, or a forum outside the Nordic countries |
| Contractual penalty | No contractual penalty, damages under the general rules | A capped penalty, with the right to damages beyond the penalty | An uncapped penalty, or a penalty as the only remedy when we are the disclosing party |
| Return and deletion | On request and when the agreement ends, with the right to keep an archive copy under confidentiality and whatever the law requires | Deletion with written confirmation | A deletion requirement covering backups without any carve-out |
Escalation and comment for the same rows:
| Clause | Escalation | Comment |
|---|---|---|
| Definition of confidential information | Responsible lawyer | A marking requirement with no confirmation rule leaves the protection empty. |
| Duration of confidentiality | General counsel | The Swedish Trade Secrets Act gives protection that should not be contracted away through a short confidentiality period. |
| Exceptions | General counsel | Residuals clauses make confidentiality worthless for know-how and are not accepted. |
| Governing law and disputes | General counsel | An NDA is rarely worth a dispute abroad. |
| Contractual penalty | Business owner together with a lawyer | The level of the penalty is a business decision; its structure is a legal one. |
| Return and deletion | Responsible lawyer | A requirement that cannot be met technically should not be signed. |
The example has six rows. A full NDA playbook also covers the parties, the purpose, permitted recipients, personal data, permitted use and a disclaimer for the material disclosed.
How it goes into Claude is covered in putting a contract review playbook into Claude.
Why playbooks go unused
One reason is that the playbook was written as a policy: "we aim for reasonable limitations of liability". The tool cannot compare against an aim. Write wording.
Another is that nobody owns it. When the business has negotiated a new position three times in a row, that is the new standard, and the playbook should change. Without an owner, old positions linger and the lawyers stop trusting the tool.
A third is that the limits were set too tight. If everything is escalated, nothing is. The limit should be reached only in exceptional cases.
How HOVR Legal works with this
A playbook for the contract types you use most is part of contract process design. The playbook is your text and can be moved into another tool if you switch.
Frequently asked questions
- What is the difference between a playbook and a template?
- The template is the contract you send. The playbook is what you accept when the counterparty changes it, or when you review the counterparty's paper. The template has one text per clause. The playbook has three: your standard, your fallback and your limit, plus who may decide when the limit is reached. Without a playbook the tool reviews against nothing and answers with general advice.
- How many contract types does a playbook need?
- Start with one: the contract type that comes up most often and where legal is most often the bottleneck, for example NDAs or purchase agreements. When it works in real matters, build the next one on the same structure.
Sources
- [1]Vägledning om användning av generativ AI i advokatverksamhet, Sveriges advokatsamfund, 12 June 2025, in Swedish; the Swedish Bar Association's guidance on generative AI in legal practice; section 3 on responsibility for advice
Back to Legal operations
More under Legal operations
- Legal intake and triage for business requests
HOVR Legal builds a way in for the business's legal questions: channel, categories, four routes, triage rule, response times and measurement. No new system.
- Contract process design: mapping and redesign before CLM
HOVR Legal maps the contract process with you: templates, approval rules, who signs, where the contract is kept and renewals. Before or without buying a CLM.
- Outside counsel management and external legal costs
HOVR Legal sets up how you manage outside counsel: which matters go out, a panel, engagement terms, billing guidelines and follow-up of the cost.
- Part-time interim legal operations lead
HOVR Legal takes on the legal operations lead role one or two days a week: plan, implementation, measurement and handover, reporting to the general counsel.
- A legal front door for a legal team of three
One way in for the business's legal questions: a form, four routes, response times and measurement. Built for a small department with no new system.
- Measuring the legal department: five metrics, no system
Five metrics from the inbox and invoices: requests per category, time to first response, standard route share, outside counsel spend, contract lead time.
- Managing outside counsel: panel, fixed fees and invoices
A panel of three to five firms, an instruction per matter, fixed fees where possible, three-point invoice review and an annual review.
- Template library and playbook as a process
Why template libraries die and how a small legal department keeps its templates and playbooks alive.
- Interim head of legal operations: when and how
When a legal department needs a part-time interim head of legal operations, and what the role does in the first ninety days.
- Legal operations maturity model for small teams
CLOC's twelve competencies and ACC's maturity model adapted to a legal department of one to ten lawyers.
- The legal department budget and annual cycle
How a legal department of one to ten lawyers builds a budget management understands: five lines, invoices as the basis, and a case the CFO can assess.
- The contract process in eight steps, request to archive
A process map for a small legal department: request, triage, template or draft, review, negotiation, approval, signing, archive and monitoring.