Analysis
Playbook Check
Your positions on a contract, kept as a plain file. Return checks every clause against them and backs each verdict with the quote it rests on.
Playbook: Master Services Agreement (Customer)
- Our side: Customer
- Governing law: English law
Liability cap
- Required: yes
- Priority: high
- Preferred: each Party's total liability is capped at no less than 200% of the Charges paid or payable in the 12 months before the claim
- Acceptable:
- a cap of at least 150% (and below 200%) of the Charges paid or payable in the 12 months before the claim
- Unacceptable: a cap below 100% of the Charges paid or payable in the 12 months before the claim
- Note: below 150% needs partner sign-off
12.3 Liability Cap
Subject to Clauses 12.1 and 12.2, each Party's total aggregate liability arising under or in connection with each Statement of Work, whether in contract, tort, or otherwise, shall not exceed an amount equal to fifty per cent (50%) of the total Charges paid or payable under that Statement of Work in the twelve (12) months immediately preceding the event giving rise to the claim.
12.4 Allocation of Risk
The Parties acknowledge that the limitations and exclusions in this Clause 12 are reasonable having regard to all the circumstances, including the level of the Charges and the availability of insurance.
3 to decide on. Decided 0 of 3.
How it works
From your positions to a verdict
Write
One heading per position: Preferred, Acceptable, Unacceptable, and your model wording. Start from a built-in starter or draft one from your own contract.
Approve
Review the playbook once. Return checks with exactly the version you approved, and shows what changed when the file does.
Run
Return reads the whole contract, section by section. In cloud mode you see how many actions the check will use before anything runs.
Decide
Red for a deviation, amber for a fallback, each with its quote. Fix it, accept it for this contract, or dismiss it.
What you can do
More than a checklist
A plain .playbook.md file
Write it in any editor, keep it under version control, share it with your team. Nothing is locked in anyone's cloud.
No color without a quote
A finding marks the text only when its quote is found in the contract word for word. A paraphrase never counts.
Missing, handled on its own
A required position counts as missing only when every section was checked, and it gets its own list instead of a mark in the text.
You approve what you read
Return uses a playbook only after you have reviewed it. A changed file shows what changed, word by word, before you approve it again.
Notes stay with you
With local AI nothing leaves your computer. In cloud mode Return sends the contract and the fields the check needs. Notes are never sent.
Decisions travel with the contract
Accept a clause for this contract and the decision is saved in the contract's own properties. The next check remembers it.
Fix from your own wording
Three rewrites shaped by your model wording, applied in one undoable step. Where a clause is missing, insert your wording for review.
A report you can hand over
Every position with its verdict, quote and your decision, as a document you can save or export to PDF or HTML.
See it in action
One contract, one playbook
| Position | Verdict | Quote from the contract | Section |
|---|---|---|---|
| Liability cap | Deviation | shall not exceed an amount equal to fifty per cent (50%) of the total Charges… | 12.3 |
| Payment terms | Deviation | within fourteen (14) days of the date of the invoice | 7.3 |
| Confidentiality survival | Deviation | shall survive the termination or expiry of this Agreement for a period of two (2) years | 11.4 |
| Ownership of Foreground IPR | Fallback | Subject to payment in full of the relevant Charges, all Foreground IPR shall vest in… | 8.3 |
| Termination for convenience | Fallback | Either Party may terminate this Agreement for convenience by giving the other Party not less than ninety (90) days' written notice | 14.2 |
| IPR indemnity | Missing | No clause found in the contract |
Limits
What it does not do
- Local models The check needs a model that follows long instructions closely. Of the bundled models, Qwen3.5 35B-A3B passed our tests. It is about 22 GB, so it needs a computer with 32 GB of memory. On a smaller computer, run the check in the cloud with Pro. The window says when the selected model has not passed, or has not been tested.
- A lead, not a lawyer Playbook Check does not judge whether a clause is enforceable and does not know your client, and it can be wrong. Treat every result, including the list of missing positions, as a lead to check.
- Markdown in Playbook Check reads Markdown. Import a Word contract first; a playbook written in Word can be imported the same way.
Check your next contract against your playbook
Free with the built-in local AI on a supported model, or in the cloud with Pro. Read the docs →