What Is a Contract Playbook (and How to Build One)

A contract playbook is a written record of the positions your team has already agreed to take on the clauses that come up again and again: what you ideally want, what you will accept as a fallback, the point past which you walk away, and the exact wording approved for each. The one thing most people get wrong is treating a playbook as a policy document to be read once. Used properly, it is a lookup table someone opens mid-negotiation, the same way a support agent opens a macro instead of writing every reply from scratch. (Adira, which publishes this guide, builds contract review and CLM software that runs on a playbook like the one described here. This guide works whether or not you ever use ours.)

Below is what a playbook actually contains, the three Indian legal defaults that must be baked in before anything else, a worked example of a position written badly and well, and a step-by-step way to build your first one without spending a quarter on it.

Plain meaning: what a playbook actually does

Without a playbook, every redline is a fresh decision. Someone reads the other side's liability cap, guesses whether it is acceptable, asks a colleague, waits for a reply, and the contract sits for two days over a clause the company has effectively already decided a hundred times before.

A playbook removes the guessing by writing the decision down once, for the clause type, not for the deal. It turns "is this liability cap okay?" into "does it match, beat, or fall short of the position we already agreed?" The second question can be answered by someone who has never negotiated a contract in their life, which is the entire point.

A playbook is not the same as a clause library. A library is a bank of pre-written wording, useful, but it does not tell you when to hold the line. A playbook adds the negotiating logic on top: which clauses are flexible, how flexible, and who can approve which level of flexibility.

Who uses it, and the moment it actually gets opened

A playbook is built by whoever carries legal risk for a company: in-house counsel, a founder before there is a legal team, or an outside lawyer setting up a company's first template set. It gets used by whoever does the day-to-day negotiating, which in most companies is not a lawyer: a sales rep sending out an order form, a procurement manager redlining a vendor MSA, an HR lead reviewing an offer letter.

It bites the moment someone reads the other side's version of a clause and has to decide whether to push back, accept it, or escalate. Without a playbook, that decision defaults to "ask legal" for everything, which is slow, or "just accept it," which is risky. A playbook lets most of those calls get made on the spot, correctly, by someone who is not a lawyer.

The four positions every clause needs

A playbook entry that only states one number is not a playbook, it is a wish. A usable entry states four things for each key clause:

• Ideal position: what you ask for first, the strongest version you would sign if the other side simply agreed.
• Fallback position: the point you will concede to without escalating, the line a non-lawyer can accept on their own authority.
• Walk-away position: the point past which the deal needs a real decision, not a redline, someone with the authority to say no to the whole contract.
• Approved wording: the actual clause text for the ideal and fallback positions, ready to paste in, not a description of what the wording should achieve.

A worked example, for a liability cap in a mid-size services contract: ideal is uncapped liability for breach of confidentiality and IP warranties, with a general cap at 12 months' fees; fallback is a general cap at 12 months' fees with no carve-outs; walk-away is anything below 3 months' fees, or a cap that also covers confidentiality and IP breaches. Anyone on the deal team can accept the fallback unassisted. Anything worse than the walk-away number is escalated, no discretion involved. That is also what makes AI-assisted review useful in the first place: a tool checking a contract against a real playbook is checking deviations from your positions, not flagging generic patterns. We cover that comparison in How to Review a Contract With AI.

The Indian non-negotiables to bake in before anything else

Three positions should never be left to individual judgment, because Indian law does not treat them as negotiable in the way most templates, especially US-originated ones, assume.

Post-employment and post-engagement restraints. Section 27 of the Indian Contract Act, 1872 says plainly:

"Every agreement by which any one is restrained from exercising a lawful profession, trade or business of any kind, is to that extent void."

Read the section on Indian Kanoon. This is not a reasonableness test the way US non-compete law usually works; it is binary. If the restraint operates after the relationship ends, it is void, however short the duration or narrow the territory looks. The Delhi High Court confirmed this on 25 June 2025 in Varun Tyagi v Daffodil Software Private Limited (FAO 167/2025), quashing an injunction against a departing employee and holding that a post-termination restrictive covenant cannot be enforced because Section 27 voids it outright. Your playbook's walk-away position on any non-compete should be "not after termination, full stop," not a shorter number of months. Full detail in Are Non-Compete Clauses Enforceable in India?

IP assignment period and territory. Section 19 of the Copyright Act, 1957 sets two default rules that apply the moment a contract goes quiet on duration or geography. Section 19(5):

"If the period of assignment is not stated, it shall be deemed to be five years from the date of assignment."

Section 19(6):

"If the territorial extent of assignment of the rights is not specified, it shall be presumed to extend within India."

Read both on Indian Kanoon. This is not theoretical. In Pine Labs Private Limited v Gemalto Terminals India Private Limited (Delhi High Court, Division Bench, 2011), an assignment clause used the word "assigns" but never stated a period or territory. The court held that Sections 19(5) and 19(6) were "inevitably triggered" by that silence, reading the missing period as five years and the missing territory as India-only, regardless of what the parties probably intended. Approved wording for any assignment clause should always state "in perpetuity and throughout the world" explicitly, never leave it implied. Full detail in IP Assignment Clause Explained.

Stamping. Section 35 of the Indian Stamp Act, 1899 says an instrument chargeable with duty cannot be admitted in evidence or acted on by a public officer "unless such instrument is duly stamped." Read it on Indian Kanoon. An unstamped contract is not void, but it can become unusable in court exactly when you need it most, after a dispute has already started. A playbook should specify which contract types need stamping, and on what value, as a checklist step before execution, not a judgment call left to whoever sends the contract out. Full detail in Is an Unstamped Agreement Valid?.

None of these three are things a fallback position can soften. They are pass or fail, and belong in the playbook as fixed rules, checked before the flexible positions are even discussed.

Red flags in a playbook itself

Normal	Red flag	Why it matters
Separate positions for pilot, mid-size and enterprise deals	One position applied to every deal size	A liability cap that is fine on a small pilot can be dangerously thin on a large enterprise deal, and vice versa
A stated walk-away line for every key clause	Fallback position only, no walk-away	Without a stop point, "just one more concession" has nowhere to end, and nobody notices until the contract is signed
Non-compete position is "not after termination," period	Non-compete position is "up to 12 months, India only"	Section 27 is binary; a moderate-sounding number is still void, and a playbook that treats it as a spectrum will approve an unenforceable clause
Approved wording pasted directly into the contract	Only a description of the position, no actual clause text	A non-lawyer negotiating from a description will draft it themselves, which reintroduces exactly the inconsistency the playbook exists to remove
Reviewed after every few dozen deals or a relevant court ruling	Written once, never revisited	A playbook is a snapshot of legal positions at the time it was written, not a permanently correct standard
Clear approval threshold for who can accept what	No stated authority levels	Without thresholds, everything either gets escalated (slow) or nothing does (risky), and there is no consistent rule for which
IP and stamping treated as fixed checklist items	IP and stamping folded into the "flexible" clause list like liability or payment terms	These are statutory defaults, not negotiating room; folding them into ordinary flexible clauses invites a fallback position that quietly waives a legal protection

A position written badly, and well: IP assignment wording

Bad approved wording, copied from a generic US-style template and used as-is in an Indian playbook:

"Contractor hereby assigns to Company all right, title and interest in the Work Product."

This reads as a complete, permanent transfer. Under Section 19(5) and 19(6), it is neither. Silence on period and territory means the assignment defaults to five years, inside India only, exactly the outcome the Delhi High Court reached in Pine Labs v Gemalto on almost identical wording.

Better approved wording, corrected for the Indian default rules:

"Contractor hereby assigns to Company, in perpetuity and throughout the world, all right, title and interest in the Work Product, including all drafts, source code, documentation and derivative works, whether created before or after the date of this Agreement."

What changed: an explicit period ("in perpetuity") and an explicit territory ("throughout the world") replace the silence that would otherwise trigger the statutory five-year, India-only default, and the scope was widened to cover drafts and derivative works, not just the final deliverable, which is a separate common gap. This is the kind of fix a playbook should carry as approved wording, ready to paste, rather than as a note telling a non-lawyer to "check the IP clause is broad enough."

How to build your first playbook

You do not need every clause type covered before a playbook is useful. Four steps get a working version out fast:

1. Pick your highest-volume contract type. The MSA you send to every customer, the NDA you sign with every vendor, the offer letter every new hire gets. Volume is what makes a playbook pay off; a one-off joint venture agreement does not need one.
2. List the 8 to 12 clauses that actually get negotiated. Liability cap, indemnity, termination, IP assignment, payment terms, and confidentiality account for most real redlines. Start there, not with every clause in the document.
3. Write ideal, fallback, walk-away and approved wording for each, linking to a clause explainer where the team needs the reasoning, not just the number. For the three non-negotiables above, the walk-away is not negotiable at all: it is a legal default, stated as a rule.
4. Set approval thresholds. Decide, in writing, who can accept a fallback position alone, and what triggers escalation. A common split: anyone on the deal team can accept a fallback; only legal or a named approver can go below the walk-away line, with a documented reason.

A playbook covering ten clauses well, with real approved wording and clear thresholds, beats one listing forty clauses with vague guidance and no walk-away line. Test a first draft by pasting a real incoming contract into Weave, Adira's free browser-based contract tool, and checking each clause against your written positions by hand before you automate anything.

How a playbook connects to negotiation and AI review

A playbook is the input, not the output, for two things teams often build separately and then wonder why they disagree. The negotiation workflow, who redlines what, how asks are sequenced, what a buyer's leverage looks like against a seller's, sits on top of the positions a playbook defines; we cover that layer in How to Build a Contract Negotiation Playbook. AI-assisted review is only as good as the playbook it checks against: an AI tool told to "flag risky clauses" in general will apply generic patterns, while the same tool checking a contract against your actual fallback and walk-away positions tells you something you can act on immediately. See How to Review a Contract With AI for how that comparison works in practice, and Contract Risk Scoring: What It Is and What It Misses for where a playbook-driven score can still go wrong.

US and global contrast

Playbooks as a practice originated largely in US and UK in-house legal teams, and most published templates and playbook software still carry US defaults: reasonableness-tested non-competes, "work made for hire" language that assumes automatic, permanent, worldwide IP ownership with no separate period or territory line, governing law defaulting to a US state. None of these transfer cleanly. "Reasonable in time, geography and scope" is the wrong test entirely in India, where Section 27 asks only whether the restraint operates after the relationship ends. And "hereby assigns all right, title and interest," with nothing said about period or territory, is exactly the wording that triggered the five-year, India-only default in Pine Labs v Gemalto. A playbook built by copying a US or UK template and swapping the company name is not a lighter version of an India-correct one. It is missing the three fixed positions that matter most.

FAQ

Is a contract playbook the same as a clause library? No. A library is a bank of pre-written wording. A playbook adds the negotiating logic: which clauses are flexible, how far, and who can approve each level of flexibility. Most teams need both, but the playbook is what makes a clause library usable by non-lawyers.

Who should own and maintain the playbook? Whoever carries legal risk for the company, usually in-house counsel or a founder before there is a legal hire. Ownership includes reviewing it whenever a major deal type changes, a new jurisdiction is added, or a relevant court ruling shifts a settled position.

Can a non-lawyer really negotiate off a playbook safely? Yes, for anything within the fallback position, because the judgment call was already made by whoever wrote the playbook. A clear walk-away line means anything worse gets escalated automatically, so the non-lawyer never has to decide something outside their competence.

How does AI contract review actually use a playbook? A well-built AI review tool compares the contract against your written positions and flags where it deviates, rather than applying a generic idea of what a "risky" clause looks like. Without a playbook, an AI tool is guessing at what your company considers acceptable.

What is the minimum playbook a small team should start with? Ten to twelve clauses on your single highest-volume contract type, each with a fallback position, a walk-away line, and approved wording. Add the three non-negotiables (non-compete restraint, IP assignment period and territory, stamping) as fixed rules even at this minimum size, since these are not judgment calls.

---

This guide explains what a contract playbook contains and how to start building one. It does not tell you whether a specific position in your playbook, or a specific clause in a contract in front of you, is right for your situation or enforceable as drafted. For that, especially for the walk-away line on anything with real money or real risk attached, get a lawyer to review your playbook before your team starts negotiating off it. This is not legal advice.