Building a Contract Playbook: Positions, Fallbacks and Examples (2026)

What a contract playbook is A contract playbook is a written guide that tells your team how to handle the clauses that come up in negotiation. For each important clause it records three things: the position you want, the fallback positions you will accept in order, and the line you will not cross. It turns negotiation from a fresh argument every time into applying a decision your company has already made. A playbook does two jobs. It speeds up negotiation, because a reviewer does not have to think from scratch about every redline, they check it against the playbook. And it keeps your positions consistent, so one deal does not quietly accept terms another deal rejected. For companies that sign a lot of similar contracts, it is the single highest-leverage document a legal team can produce. This guide shows how to build one, with worked examples. It is general guidance, not legal advice, and your playbook should be reviewed by a qualified lawyer for your jurisdiction and business. ## How to structure a playbook A good playbook is organised by clause and easy to scan under time pressure. For each clause, capture a consistent set of fields: ```

CLAUSE: [name, e.g. Limitation of Liability] Preferred position: [the wording or terms you want] Why it matters: [one line on the risk this clause controls] Fallback 1: [first concession you will make, and in exchange for what] Fallback 2: [next concession] Walk-away: [the position you will not cross; escalate to legal if pushed past] Approval needed to go past walk-away: [who] Sample language: [drafted wording for the preferred position and key fallbacks] Common counterparty arguments: [what the other side usually says, and your response] The "why it matters" line is what lets a non-lawyer use the playbook with judgement rather than blindly. The "walk-away" and "approval needed" fields are what keep self-serve negotiation safe: a reviewer can move within the fallbacks freely, and only a genuine walk-away issue pulls in a lawyer. Keep the playbook as a living document with a named owner and a review date. Positions change as the law changes, as your risk appetite shifts, and as you learn which fallbacks the market actually accepts. ## Worked example: limitation of liability This is the clause most playbooks start with, because it controls the single biggest financial risk. CLAUSE: Limitation of Liability Preferred position: Liability capped at the fees paid in the 12 months before the claim. Exclude indirect and consequential loss. Mutual cap. Why it matters: Caps the maximum we can be made to pay if things go wrong. Fallback 1: Cap at 12 months fees, but accept a higher multiple (e.g. 1.5x) if the customer accepts the same cap mutually. Fallback 2: Accept carve-outs from the cap for breach of confidentiality and for the indemnity, which is market standard, but resist uncapped liability for data breaches; propose a separate higher sub-cap instead. Walk-away: Uncapped liability for general breach. Escalate to legal. Approval to exceed: General Counsel. Common counterparty arguments: "Your cap is too low for a deal this size." Response: tie the cap to fees, which already scales with deal size, and offer a mutual higher cap rather than an uncapped one. Note how the fallbacks trade: you concede a higher multiple only in exchange for mutuality. A playbook position is strongest when each concession asks for something back. ## Worked example: indemnity CLAUSE: Indemnity Preferred position: We indemnify only for third-party IP infringement claims caused by our product, and for our breach of confidentiality. Mutual where the customer provides data or materials to us. Why it matters: Indemnities can create liability outside the normal cap, so scope matters more than almost any other clause. Fallback 1: Add indemnity for death or personal injury caused by our negligence, which is standard and often legally required. Fallback 2: Accept a data-protection indemnity but subject it to a sub-cap rather than leaving it uncapped. Walk-away: A broad indemnity for "any loss arising from the agreement." Escalate to legal. Approval to exceed: General Counsel. Common counterparty arguments: "We need to be covered if your product causes us a loss." Response: that is what the liability and warranty clauses are for; indemnities should be reserved for specific third-party risks. ## Worked example: termination CLAUSE: Termination Preferred position: Either party may terminate for material breach not cured within 30 days of notice, and for insolvency. No termination for convenience by the customer during the committed term. Why it matters: Controls whether a customer can leave early and stop paying. Fallback 1: Allow termination for convenience with 90 days notice, but only at the end of a committed term, not during it. Fallback 2: Allow early termination for convenience during the term if the customer pays the remaining committed fees. Walk-away: Termination for convenience at any time with no payment. Escalate. Approval to exceed: VP Sales plus Finance. Common counterparty arguments: "We need flexibility to leave." Response: offer a break point at the end of each committed term rather than an any-time exit, which protects your revenue commitment.

2. **Write the preferred position from your best recent contracts.** Look at the terms you actually signed on good deals; those are your realistic preferred positions.
3. **Derive fallbacks from what you have already conceded.** Your negotiation history is the best source of realistic fallbacks, because it shows what the market accepted.
4. **Set walk-aways with legal.** This is the part that must involve a lawyer, because the walk-away defines your real risk boundary.
5. **Add common arguments as you negotiate.** Every negotiation teaches you a counterparty argument and a good response; capture them so the playbook gets smarter. ## Keeping the playbook and the drafting in step A playbook is only as good as its use. The common failure is that the playbook lives in a document, the actual negotiation happens in redlines in a separate tool, and over time the two drift apart. A reviewer concedes something the playbook forbids because, under deadline, they did not check; or the playbook is updated but the templates it is meant to govern are not. The positions and the contracts they are supposed to shape live in different places. That is the single-workspace idea: the company's preferred positions, the templates drafted from them, the clause-level edits a negotiation produces, and the record of what was conceded can live together rather than in separate documents. [Adira](https://adiralaw.com) is built to hold a company persona of your preferred terms and house style, draft contracts that reflect it, and make edits as a structured clause tree with a diff and version history, so a concession is visible and traceable, with a dedicated negotiation-playbook module on its roadmap rather than presented as finished today. You do not need a platform to build the playbook in this guide; the point worth taking is that a playbook creates value only when the positions it records and the contracts they govern stay connected.