Playbooks vs Fallback Positions

The short answer A contract playbook and fallback positions are not competing tools, they are different levels of the same thing. A playbook is the whole guidance document for negotiating a type of contract. Fallback positions are one part of it: the ranked set of acceptable compromises for a single clause. Put simply, a playbook is the book, and fallback positions are the moves it records for each clause. You build a playbook; fallbacks live inside it. If you only remember one thing: fallbacks tell a negotiator what to accept on a clause, and the playbook tells them everything else they need around that, why the position matters, what to ask for first, when to escalate, and sample wording. ## What a contract playbook is A contract playbook is a reusable guide for negotiating a particular contract type, for example an NDA, an MSA, or a SaaS agreement. For each clause that gets negotiated, a good playbook sets out: - The preferred position: what you ideally want the clause to say.

• The rationale: why that position matters and what risk it protects against.
• The fallback positions: the acceptable compromises, in order, if the preferred position is rejected.
• The walk-away point: the line you will not cross without escalation.
• Sample wording: approved language for the preferred position and key fallbacks.
• Escalation guidance: who to involve when a counterparty pushes past the fallbacks. A playbook lets someone who is not a specialist negotiate a standard contract confidently, and keeps positions consistent across everyone who uses it. ## What fallback positions are A fallback position is a pre-agreed, acceptable alternative for a single clause when you cannot get your preferred position. Fallbacks are usually ranked from best to least preferred, so a negotiator knows the order to concede in and where the floor is. Take a liability cap. The preferred position might be a cap at 12 months' fees. The first fallback is 18 months' fees; the second is 24 months' fees with certain carve-outs; the walk-away is anything uncapped. Those graded options are the fallback positions for that one clause. ## How they fit together The relationship is simple: fallback positions are a component of a playbook, not an alternative to one. - A playbook without fallbacks is just a statement of ideal positions. It tells a negotiator what to want but not what to do when the other side says no, which is most of real negotiation.
• Fallbacks without a playbook are a loose list of concessions with no rationale, no sample wording and no escalation path. Negotiators apply them inconsistently because the context is missing.
• A playbook with fallbacks is the complete tool: preferred position, why it matters, graded compromises, and the point to escalate, all in one place. ## When to use each - Build a playbook when a contract type comes up often enough that repeating the thinking is wasteful, or when people other than senior lawyers need to negotiate it. The playbook captures the whole approach once.
• Focus on fallback positions when you are inside a negotiation and need to decide, clause by clause, what you can accept and in what order. In practice you are reading the fallbacks out of the playbook.
• Start with fallbacks for your most-negotiated clauses if you have no playbook yet. The clauses that get pushed back most, liability, indemnities, IP, termination, data protection, are where graded fallbacks deliver value fastest, and they become the backbone of a fuller playbook later. ## Common mistakes - Treating them as either-or, when fallbacks belong inside a playbook.
• Writing preferred positions with no fallbacks, leaving negotiators stuck at the first 'no'.
• Fallbacks with no walk-away point, so concessions slide with nothing to stop them.
• A playbook so long no one reads it mid-negotiation; keep each clause entry tight and skimmable.
• Never updating either as the market or your risk appetite shifts. ## Keeping both consistent and used A playbook and its fallbacks only create value if negotiators actually apply them the same way every time, and if what was agreed feeds back to improve them. The friction is practical: the guidance lives in one document, the contract in another, and matching clause to fallback is manual each time. ## Where a single workspace fits The gap between a playbook and a live negotiation closes when your standard positions sit next to the document being reviewed. When a tool reads a clause, marks it against your preferred and fallback positions, and shows where it falls short, the playbook stops being a separate file to remember and becomes part of the review itself. A tool like Adira marks each position as favourable, neutral or unfavourable to your side against your own standards and lets you edit toward an agreed position in plain language with a clean diff, so preferred positions and fallbacks are applied consistently as contracts come through. The thinking still belongs in your playbook; the workspace keeps it applied the same way every time.