KT Farley, Chief Privacy Officer and Associate General Counsel at Helix, described the moment her review queue stopped being hers alone:
"The ability to create and store reusable prompts and share them across the team has completely changed the work required to review standard work. Junior teammates now run the checklist prompt first and bring me the output as the predicate for my review."
That handoff is what a contract playbook template makes possible.
A contract playbook template is a repeatable grid, usually a six-column table, that records for every negotiated clause a preferred position, an acceptable fallback, a walk-away line, a one-sentence rationale, and a named escalation owner. Build it once, and a deal that used to wait on you moves while you sleep.
Below is the structure, then the same grid filled in with worked examples for the six clauses in-house teams negotiate most, each showing preferred, fallback, and walk-away positions you can lift and adjust to your risk tolerance. Copy the structure into a Google Doc or your CLM and the whole thing is ready to populate.
Here at GC AI, the enterprise-grade legal AI built for in-house counsel by a three-time general counsel, we turn a playbook like the one below into a button you press: load your filled-in grid once, and GC AI reads each counterparty clause, matches it to your preferred, fallback, and walk-away positions, and drafts the redline.
More than 2,100 legal teams, including 300+ public companies, run their contract work on GC AI as of September 2026. Build the playbook here, then run it where the review happens.
What's Inside a Contract Playbook Template?
A contract playbook template turns the judgment a senior lawyer carries in their head into a reference any reviewer can run, so first-pass redlines come back consistent whether you wrote them or a contract manager did. It captures, for each clause your team negotiates, the position you open with, the alternatives you will accept, and the terms that require a senior sign-off. The practitioner threshold for building one: enough volume, complexity, and risk overlapping on one contract type to repay the setup.
The template is the empty structure. The playbook is that structure filled in with your company's approved positions, signed off by whoever owns legal risk. The distinction earns its keep because an unapproved fallback is worse than no playbook at all: it hands a junior reviewer authority they were never granted.
A working template has six columns, and every clause row carries all six:
Clause. The provision being negotiated (limitation of liability, indemnification, IP ownership, and so on).
Preferred Position. Your gold-standard language, inserted on the first pass into counterparty paper.
Acceptable Fallback. Pre-approved alternatives a reviewer can accept without escalating.
Walk-Away. The line that gets the deal killed or kicked to senior counsel. No reviewer accepts past this without sign-off.
Rationale. Why the position exists, in one sentence, so reviewers apply judgment instead of pattern-matching.
Escalation. Who approves an exception, and how fast they respond.
The rationale column is the first one playbooks skip and the one that earns its keep. A reviewer who knows why a 12-month liability cap matters can hold the line on a clause that reads differently while creating the same exposure. A reviewer working from language alone misses it.
A contract playbook template is the scaffolding; your approved positions and a named escalation owner are what make it safe to delegate.
The Contract Playbook Template Structure
Here is the blank structure. Copy it into a spreadsheet, a Word table, or your CLM, and populate one row per negotiated clause. Keep the column order: reviewers read left to right, from opening position to escalation.
Clause | Preferred Position | Acceptable Fallback | Walk-Away | Rationale | Escalation |
[Clause name] | [Your gold-standard language] | [Pre-approved alternatives] | [The line requiring sign-off] | [One-sentence why] | [Approver + SLA] |
Three rules keep the template usable as it grows:
Size it to the contract type. A short-form contract playbook (NDAs) runs 6 to 12 clauses. A SaaS MSA or DPA playbook runs 15 to 25. A broad commercial review playbook can reach 20 to 30. Past that, reviewers stop reading and start guessing.
Write fallbacks as executable decisions. "Accept mutual cap at 18 months of fees" is a decision a reviewer can execute on the spot. "Consider the totality of the commercial relationship" leaves the reviewer guessing.
Name a human in the escalation column. "Escalate to legal" is a dead end. "Escalate to the Deputy GC; 24-hour SLA" tells the reviewer exactly what happens next.
A note on the second column heading you will see in other templates: some call the gold-standard language "Standard Position." Either label works. The function is the same, the language you insert before anyone has pushed back.
Whose paper you are on changes how the reviewer reads the grid. On counterparty paper, they work left to right: insert the preferred language first, concede toward the fallback only when pushed. On your own template, the preferred position is already in the draft, so the playbook runs in reverse, telling the reviewer which incoming redlines to accept and which cross the walk-away line. One playbook covers both directions; mark the clauses where your position shifts with leverage.
The worked examples below name a Deputy GC and a GC because that is the shape of a mid-size department. On a team of one, the escalation column names you, and its job shifts: it flags which exceptions deserve outside counsel before anyone accepts them. Write the column anyway. The playbook is what lets the business self-serve within the fallbacks while you spend your hours on the exceptions.
Build the structure to match the contract in front of you, and cap the row count so the playbook stays a reference a reviewer finishes reading.
Worked Clause Examples
The structure above is portable across any contract type. Below, it is filled in for the six clauses in-house teams negotiate most, with positions you can lift and adjust to your own risk tolerance. Each one links to the full clause breakdown in the GC AI Clauses Library, where the standard variants and market language live. Most teams extend the grid with a few more high-traffic provisions: governing law, assignment, and non-solicitation each have their own breakdown to copy positions from.
Treat these as a starting point calibrated to a mid-market SaaS or commercial vendor relationship. Your numbers will move with deal size, leverage, and industry. The thresholds below are illustrative defaults to adjust; they stand in for the legal judgment a specific deal still requires.
Limitation of Liability
The limitation of liability clause caps the damages one party can recover from the other, and it is the single most negotiated provision in commercial contracts, the position it has held for years in WorldCC's Most Negotiated Terms surveys, because it converts unknown exposure into a known number. The cap is usually expressed as a multiple of fees paid; the fight is over the multiple, the lookback period, and which damages sit outside the cap.
Clause | Preferred Position | Acceptable Fallback | Walk-Away | Rationale | Escalation |
Limitation of Liability | Mutual cap at 12 months of fees paid; standard exclusions (confidentiality breach, indemnification obligations, IP infringement) carved out and uncapped; consequential damages waived mutually. | Cap up to 18 months of fees, or a fixed multiple (1.5x to 2x annual fees) where fees are small relative to risk; super-cap on data-breach liability at 2x to 3x the general cap. | Any clause removing the cap entirely, establishing unlimited liability for the company, or making the cap non-mutual in the counterparty's favor on a high-value deal. | An uncapped or one-sided liability clause turns a fixed-fee contract into open-ended financial exposure. | Deputy GC for any super-cap above 3x; GC for any uncapped term; 24-hour SLA. |
The carve-out list is where preferred positions become walk-aways. A 12-month cap with a broad indemnity carve-out that swallows the cap is functionally uncapped, which is why the rationale column tells the reviewer to read the cap and the carve-outs together.
Indemnification
The indemnification clause allocates which party pays when a third party brings a claim, and it is the clause likeliest to arrive over-broad on counterparty paper. The preferred position is mutual, claim-specific indemnities tied to each party's own obligations; the danger is an open-ended indemnity with no cap and no defense control.
Alexandra Sepulveda, Assistant General Counsel at Trust and Will, described the exact scenario a playbook is built to handle:
"Imagine a redline comes back asking for unlimited indemnity. I'll tell GC AI, 'Here's the clause and why we can't accept it. Draft a four-sentence response to sales, collaborative tone, options to move forward.'"
The result is a clear, diplomatic note she can send fast. The playbook row is what made her "why we can't accept it" immediate. She stated the position on sight, because it was already written down.
Clause | Preferred Position | Acceptable Fallback | Walk-Away | Rationale | Escalation |
Indemnification | Mutual indemnities scoped to defined claim types (third-party IP infringement, breach of confidentiality, gross negligence, willful misconduct); indemnifying party controls defense with consent rights for the indemnified party; subject to the liability cap except for standard carve-outs. | Asymmetric scope where the company's deliverable risk genuinely differs from the counterparty's; first-dollar defense without a deductible if the indemnity is otherwise capped. | Unlimited or uncapped indemnity in the counterparty's favor; indemnity for the counterparty's own negligence; defense obligations with no consent or settlement-approval rights. | An uncapped or one-directional indemnity is the most common way unlimited liability re-enters a contract after the cap is negotiated. | GC for any uncapped indemnity; Deputy GC for asymmetric scope; 24-hour SLA. |
Intellectual Property
The intellectual property clause governs who owns what gets created, used, or licensed under the contract, and it is where a poorly drafted line costs the company an asset it thought it kept. The preferred position holds each party's pre-existing IP and grants only the license the deal requires; the trap is an assignment or "work made for hire" sweep that captures more than the deliverable.
Clause | Preferred Position | Acceptable Fallback | Walk-Away | Rationale | Escalation |
Intellectual Property | Each party retains all pre-existing IP; counterparty receives a limited, non-exclusive license scoped to the contract's purpose and term; any IP the company pays to have created is assigned to the company. | Non-exclusive license extending to affiliates; joint ownership of jointly developed IP with clear use rights for both parties; feedback license (perpetual, royalty-free) on product feedback only. | Assignment of the company's pre-existing or background IP; exclusive license that blocks the company's own use; broad work-made-for-hire language sweeping in IP beyond the paid deliverable. | An over-broad assignment or exclusivity grant gives away an asset the company built and intended to keep. | GC for any assignment of background IP or exclusivity; 24-hour SLA. |
Termination
The termination clause sets how and when either party can exit, and the in-house priority is symmetry: a contract you can leave for convenience but the counterparty can only leave for cause is a liability dressed as a benefit. The fight is over notice periods, cure windows, and termination-for-convenience rights.
Clause | Preferred Position | Acceptable Fallback | Walk-Away | Rationale | Escalation |
Termination | Mutual termination for convenience on 30 to 90 days' notice; termination for material breach with a 30-day cure period; clear post-termination data-return and transition obligations. | Convenience right for the company only on longer notice where the counterparty has made dedicated investment; auto-renewal with a clear, reasonable opt-out window (60 days or less). | No termination-for-convenience right for the company; cure periods under 10 days; auto-renewal with no practical opt-out or a multi-year lock-in with no exit. | A contract the company cannot exit on reasonable notice is an open-ended commitment regardless of how the relationship performs. | Deputy GC for any multi-year lock-in or one-sided convenience right; 24-hour SLA. |
Confidentiality
The confidentiality clause defines what counts as confidential, how long the obligation lasts, and what each side can do with the other's information, and it is the clause that should be mutual by default in almost every commercial relationship. The common over-reach is a one-sided obligation or a definition so broad it captures publicly available information.
Clause | Preferred Position | Acceptable Fallback | Walk-Away | Rationale | Escalation |
Confidentiality | Mutual obligation; confidential information defined by marking or reasonable identification; standard exclusions (publicly available, independently developed, rightfully received); survival of 3 to 5 years post-termination, or indefinite for trade secrets. | Indefinite survival for all confidential information if the deal involves sensitive technical data; broader definition covering information that should reasonably be understood as confidential given context. | One-sided obligation binding only the company; no standard exclusions; perpetual obligation on ordinary business information with no trade-secret limitation. | A one-sided or unbounded confidentiality obligation creates compliance burden and breach exposure with no reciprocal protection. | Deputy GC for one-sided obligations; 24-hour SLA. |
Data Protection
The data protection clause, usually executed as a DPA attached to the MSA, governs how the counterparty handles personal data: what it can process, how fast it reports a breach, and what happens to the data at termination. It carries regulatory exposure the other five clauses do not, because notification duties and fines fall on the data controller, and a weak DPA turns a vendor's security incident into the company's legal problem.
Clause | Preferred Position | Acceptable Fallback | Walk-Away | Rationale | Escalation |
Data Protection | Vendor processes personal data only on documented instructions; breach notice without undue delay and no later than 72 hours after awareness; security measures tied to a named standard (SOC 2 Type II or ISO 27001); deletion or certified return of personal data at termination. | Breach notice within 5 business days where the vendor's incident process requires it; audit rights satisfied by third-party reports instead of on-site audits; sub-processor changes on advance notice with a right to object. | Any right to use personal data for the vendor's own purposes, including model training; no breach-notification obligation; data-protection liability excluded entirely or left under the general cap with no super-cap. | Regulatory fines and notification duties fall on the controller, so a weak DPA converts the vendor's security failure into the company's exposure. | Privacy counsel or GC for vendor-purposes processing or a missing breach-notification duty; 24-hour SLA. |
A worked example becomes your playbook only after you adjust it to your risk tolerance and whoever owns legal risk signs off on each row.
How to Run the Template With AI
A filled-in template is a reference. Running it against every contract by hand is still the bottleneck: a reviewer has to read the counterparty's clause, find the matching playbook row, and draft the redline. This is the step AI contract review built for in-house teams collapses.
GC AI is the enterprise-grade legal AI built for in-house counsel, used by 2,100+ legal teams across 47 countries and 300+ public companies, with an NPS of 80. Legal departments running their contracts on it include Columbia Sportswear, Snyk, Viant, Eventbrite, Interface, Hitachi, Liquid Death, and Tipalti. CEO and co-founder Cecilia Ziniti, a three-time general counsel (Anki, Bloomtech, and Replit) and in-house counsel at Amazon and Cruise, built GC AI to solve the problems she hit firsthand.
With Playbooks, you load your filled-in template once and GC AI applies it to every contract: it reads each counterparty clause, flags where it lands against your preferred, fallback, and walk-away positions, and drafts the redline in Word with a plain-language note on where the term settled.
Pre-built playbooks ship for NDAs, DPAs, and MSAs, and Easy Playbooks builds custom ones from your own materials. For the backstory, see the introduction to GC AI Playbooks.
The enterprise security diligence is already cleared: SOC 2 Type II and SOC 3, GDPR compliance, AES-256 encryption, and zero data retention agreements with its AI model providers wherever feasible, so your prompts and contract text never train third-party models.
The Trust and Will example earlier is this workflow in miniature: a redline comes back asking for unlimited indemnity, the playbook already holds the position and the rationale, and GC AI drafts the response to sales while the lawyer keeps moving.
Load the template once, and the review that used to start from a blank redline starts from your position already applied.
Want a solutions attorney to load a real playbook and redline a live contract against it on your own paper?
Common Questions Before You Run It
"We already have a CLM. Does this replace it?" No. A contract management system stores and routes contracts; the playbook governs the positions inside them. As CEO Cecilia Ziniti puts it, "We're not going to build CLM as it currently exists." GC AI runs through an API inside the CLMs and workflows teams already use, so you load your playbook into GC AI, keep your CLM as the system of record, and the two run alongside each other.
"How do I trust the redline?" Every GC AI output cites the source clause with Exact Quote, so a reviewer checks the language against the contract before sending. The playbook holds the position; the lawyer keeps the judgment.
"Will my team adopt it?" GC AI runs inside Microsoft Word, where in-house lawyers already draft, and 97.5% of teams report value before month one, per GC AI's December 2025 ROI study of more than 100 customers. Adoption is the playbook becoming the first step a junior reviewer takes, the move KT Farley described. Teams that want structured onboarding start with GC AI's courses, CLE-eligible in California.
Get the Template
There are two ways to get to a working playbook.
The fast path: let GC AI build it. Start a 14-day trial, open Easy Playbooks, and point it at your existing standards, past redlines, or the structure above. GC AI drafts the filled-in grid for you to route for sign-off, so teams typically have a usable first playbook the same day instead of building one from a blank page.
The manual path: open a blank Google Doc, spreadsheet, or your CLM, recreate the six-column structure from the section above, then drop in the six worked clause examples as your starting rows. Swap in your company's positions, route it to whoever owns legal risk for sign-off, and load it into your review workflow. The fields line up with what Bloomberg Law's playbook guide recommends capturing: sample language, rationale statements, and approval workflows.
Either path, date it and revisit it. Reopen the playbook after any deal that forced an escalation, and put a quarterly review on the calendar even when nothing escalated: thresholds drift with the market, and a fallback approved under last year's risk posture may be wrong under this year's. Version the file and date each sign-off so a reviewer always knows the positions in front of them are current.
For the build-it-from-scratch process, see the companion guide on how to build a contract playbook and run it with AI. For the deeper mechanics of turning your existing standards into AI-ready positions, see the related guide on turning contract standards into an AI playbook. To see the market language behind any position above, the GC AI Clauses Library breaks down each clause variant.
Write your positions down once, get them signed off, and the next redline starts from your line already drawn. The GC who does that this week reviews the next contract from their position instead of a blank page:
Frequently Asked Questions
What Is the Difference Between a Preferred Position and a Fallback?
A preferred position is the gold-standard language your team inserts into counterparty paper on the first pass, before anyone has pushed back. A fallback is a pre-approved alternative a reviewer can accept without escalating when the counterparty rejects the preferred position. The walk-away line sits past the fallback: any term beyond it requires a senior lawyer's sign-off.
How Many Clauses Should a Contract Playbook Have?
A contract playbook should be sized to the contract type: NDA playbooks run 6 to 12 clauses, SaaS MSA and DPA playbooks run 15 to 25, and broad commercial review playbooks reach 20 to 30. Past 30 clauses, reviewers stop reading the playbook and start guessing, which defeats the consistency the playbook exists to create.
Can In-House Teams Use a Contract Playbook to Let Non-Lawyers Review Contracts?
Yes, a contract playbook lets procurement, sales, and contract managers handle first-pass review within pre-approved bounds, escalating only when a term crosses the walk-away line. The safeguard is that every fallback must be approved by whoever owns legal risk before it goes live; an unapproved fallback gives a non-lawyer authority they were never granted and creates professional-responsibility exposure.
What Is a Contract Negotiation Playbook Template?
A contract negotiation playbook template is the same six-column grid framed for the negotiation table: for each clause it records the position you open with, the fallbacks you can trade without escalating, and the walk-away line that ends the conversation or sends it to senior counsel. It gives a reviewer the give-and-take ranges in advance, so concessions are pre-approved instead of improvised mid-thread.
Do I Need a Separate Playbook for Each Contract Type?
Yes, in practice. The preferred positions and thresholds that fit an NDA differ from those that fit a SaaS MSA or a DPA, so teams build one template structure and maintain a separate filled-in version per contract type. GC AI ships pre-built playbooks for NDAs, DPAs, and MSAs as starting points, so you adapt an existing one instead of drafting each from scratch.
Where Can I Get a Free Contract Playbook Template?
You can build one in minutes from the six-column structure and worked examples in this guide: recreate the structure in a Google Doc, spreadsheet, or your CLM, then use the worked examples for limitation of liability, indemnification, IP, termination, confidentiality, and data protection as your starting rows. Populate each row with your company's approved positions, and route it for senior sign-off before your team runs it.
