Contract Review Playbook Template (Clause Positions, Approvals)

Contract Review Playbook: [Contract type, e.g. customer subscription agreement]

A contract review playbook for an in-house legal team: the scope and paper it covers, review tiers, clause-by-clause negotiation positions (preferred, fallback and walk-away), the approval matrix for deviations, the escalation path, a deviation log and how the playbook is kept current. It is built from in-house practice, not from a published standard. Laws named in it are dated EU, UK and US examples with official links, not a statement of what applies to you. Replace every [bracketed] value and every row marked Example. This is a documentation format, not legal advice; check the current official texts and consult a qualified professional before relying on any position.

Document control

Approvals

Revision history

Contents

1. Purpose and principles
2. Scope and paper
3. Review tiers and turnaround
4. Approval matrix
5. Clause positions
6. Escalation and negotiation process
7. Deviation log and playbook maintenance
8. Training and access
9. Glossary and references

1. Purpose and principles

This playbook lets reviewers inside and outside the legal team close contracts of the family named in Document control quickly and consistently, while keeping risk inside limits the business has accepted in advance. It turns the judgment of senior lawyers into written positions, so that the same request receives the same answer whoever reviews it.

Principles:

• Start from our paper. Review on the organisation's template wherever possible. When the counterparty insists on its own paper, map its clauses to section 5 before marking up.
• Positions, not wording. The positions describe outcomes. A reviewer may accept different wording that reaches the same outcome.
• Risk follows value. The tier in section 3 and the approver in section 4 depend on contract value and risk, not on who asks.
• Write down every deviation. Every agreed move to a fallback or beyond is recorded in the deviation log (section 7.1), so that the playbook learns from real deals.
• No silent changes. Reviewers do not accept changes in clean documents; they compare against the last agreed version every time.
• Not legal advice to the business user. Business reviewers apply the positions; they do not interpret law. Anything outside the playbook goes to legal.

2. Scope and paper

Template paper and related documents.

3. Review tiers and turnaround

Red flags that move a contract to T3 regardless of value:

• Any request for unlimited liability other than the carve-outs in 5.1.
• Most-favoured-customer pricing, exclusivity or non-compete obligations on the organisation.
• Source code escrow release triggers wider than insolvency and discontinuation.
• Transfer of ownership of the organisation's pre-existing intellectual property.
• Audit rights over the organisation's premises without notice limits.

Requests arrive through the legal intake channel described in legal-ops/matter-intake-triage; a contract request without the deal value, counterparty name and current draft is not complete and the turnaround clock does not start.

4. Approval matrix

Rules:

• Approval is recorded in the contract management system or by email to the deal record, with the clause, the agreed wording and the reason.
• Approvers cannot approve deviations on deals they sell or are personally compensated on.
• An approval covers one deal. Repeated approvals of the same deviation trigger a playbook review (section 7.2).

5. Clause positions

Each table uses the same columns. "Preferred" is the template. The reviewer named in section 4 may agree the fallback. Beyond the walk-away, the deal needs the top approver in section 4 or is declined.

5.1 Limitation of liability

Purpose: keep total exposure in proportion to the revenue from the contract, and keep certain liabilities outside the cap where the law or fairness requires it.

Note: some liabilities cannot be excluded or limited by law. For example, under the law of England and Wales a contract term cannot exclude or restrict liability for death or personal injury caused by negligence (Unfair Contract Terms Act 1977, section 2(1), https://www.legislation.gov.uk/ukpga/1977/50/section/2). Other legal systems have comparable rules; ask counsel for the governing law of the contract.

Example (Quillmere): annual fees of USD 240,000. Preferred cap USD 240,000, fallback cap USD 360,000 (1.5 times), walk-away above USD 480,000 (2 times). A customer asks for a cap of USD 500,000: this is above 2 times annual fees (USD 480,000), so it needs the general counsel and the CFO.

5.2 Indemnities

Purpose: allocate third-party claims to the party that controls the risk.

5.3 Intellectual property

5.4 Confidentiality

Align with the stand-alone NDA (legal-lite/nda) so that the two do not conflict when both exist.

5.5 Data protection

Purpose: meet the controller and processor rules of the applicable data protection law and keep the processing terms in one place.

Under the EU and UK GDPR, a contract with a processor must cover the matters in Article 28(3) of Regulation (EU) 2016/679 (https://eur-lex.europa.eu/eli/reg/2016/679/oj). US state privacy laws set their own contract terms for service providers. Privacy counsel confirms which regimes apply.

5.6 Payment and price

Note: statutory late payment rules differ between jurisdictions and may set minimum interest or payment periods for business transactions. Check the governing law with finance and counsel.

5.7 Warranties and service levels

5.8 Term, termination and exit

5.9 Insurance

Insurance positions must be checked with the insurance manager every renewal year; the figures are examples only.

5.10 Governing law, disputes and assignment

6. Escalation and negotiation process

Steps:

1. Intake. The requester submits the request, the draft, the counterparty and the deal value through the legal intake channel.
2. Scope and tier. The contract manager checks section 2 and sets the tier from section 3, including red flags.
3. Review. The reviewer compares the draft with section 5 and marks up with tracked changes and short external comments. Internal reasons stay in the deal record, not in the document sent to the counterparty.
4. Negotiation. The reviewer offers fallback positions in order, never the walk-away first. The business owner joins calls where commercial trade-offs are needed.
5. Approval. Deviations beyond fallback go to the approver in section 4 with a one-paragraph summary: the clause, the ask, the proposed answer, the value and the risk.
6. Signature. Signatories follow the delegation of authority matrix. Legal confirms the final version matches the approved version before signature.
7. Handover. The signed contract, key dates and obligations go to the contract register (procurement/contract-register) with an owner for each obligation.

7. Deviation log and playbook maintenance

7.1 Deviation log

7.2 Quarterly review

8. Training and access

Keep the playbook confidential: it reveals negotiation limits. Share it outside the legal team only under the access rules above and mark it as privileged where your legal system allows.

9. Glossary and references

Standard and licence note

Based on in-house legal practice for contract playbooks; no published standard governs this document. The positions, figures and approval limits are examples, not recommendations, and must be set by the organisation's own counsel and finance. Laws are named only as dated EU, UK and US illustrations with links to the official texts; check the current consolidated versions before use. The organisation and deals in the example are fictional. All text is original wording written for this collection. This is a documentation format, not legal advice; consult a qualified professional.

Template licence: MIT.