Most legal teams do not have a contract playbook. Of those that do, most never open it.
From Playbook to Practice was a SpotDraft webinar moderated by Marshall Deutz, a Product and Solutions expert at SpotDraft, with Aprajita Tyagi, Senior Corporate Counsel at Miro, and Anna Pototschnig, a Senior Legal Counsel at Calix. In the audience poll, 61% had no playbook, 22% had one that was mostly a reference document, 11% used it in reviews and negotiations, and 6% had it embedded in their contracting workflow. Here is what separates a playbook people use from one that sits in a folder.
Tyagi's test: does it help you decide quickly in a live negotiation? A playbook is a decision tool, not a textbook, and it need not contain everything. Her team sorts positions into traffic signals. Red items are boundaries that cannot be accepted, and pushback goes to leadership. Yellow items, such as indemnity scope or warranty exclusions, mean pause, check, and escalate or draft new language if needed. Green items can be accepted as they are. A good playbook also explains why each item sits where it does and lists fallbacks the team has used before.
If nobody has added a provision or fallback in a long time, nobody is relying on the document.
Reviewers asking about items the playbook already covers are not opening it.
Inconsistent redlines mean people rely on personal judgment, not the fallbacks the team drafted.
When everyone asks the longest-tenured colleague what the company offered before, that person's memory is the real playbook. Deutz called this a single point of failure.
A stale playbook pushes reviewers to maintain their own lists and negotiate from those.
Pototschnig described where playbooks break once they meet a real deal.
Both panelists described positions you hold, positions with reviewer flexibility, and positions you rarely spend time on. Pototschnig called the middle bucket the most important, because that is where explanation matters: what the tool is for, what data it touches, how critical the service is, and what can go wrong. She also separates the protection you need from the exact wording, so phrasing that delivers the protection need not be rejected.
Tyagi's rule: be very prescriptive on items like customer data used for model training, indemnities and license scope, and explain why. Everywhere else, give principles and trust the reviewer. Pototschnig added that linked provisions should be flagged together, so negotiating limitation of liability prompts a check of indemnity and carve-outs.
Authority depends on risk, revenue, whether the deal is strategic, and whether the issue reaches privacy or InfoSec. Tyagi sends uncapped damages and expanded indemnity scope to leadership. Both stressed giving the approver the facts: what you pushed back on, why the counterparty wants it, and a short risk summary. Tyagi's example: customers ask for an indemnity on AI feature output, then narrow it to the wrapper layer her company built, which raises investigation costs and warranty scope. That is why the escalation path needs to be written down, ideally in a defined approval workflow.
Pototschnig wants one authoritative version inside the workflow, such as a Word add-in or the CLM, owned by legal, with a defined review process, controlled access to sensitive fallbacks, and superseded versions archived. She has seen a fallback quoted to a counterparty as "agreed before", which cost the team leverage because that deal had a different risk profile.
A concession to a counterparty with major leverage may be a one-off. The same issue across comparable deals may signal a market shift or a weak preferred position. A repeated exception is a reason to reassess, Pototschnig said, not an automatic change, and any new standard should be approved by someone with authority. Tyagi's team logs deviations as parked items and now uses an NDA review skill built with Claude that sends them to a shared Miro board. Her warning: the log is useless unless the team meets and acts on it.
Pototschnig suggested tracking four things.
Freshness is the hard part. In the second poll, 57% named keeping the playbook up to date as their biggest challenge, ahead of handling exceptions (24%), getting people to use it (10%) and getting business teams to follow it (9%). Pototschnig recommends a deeper annual review, a review after any important change, and quarterly or half-yearly check-ins with procurement, sales and the business, all under a named owner.
Pototschnig: pick one agreement type your team handles regularly, test the guidance against a few real negotiations, and assign someone to maintain it. Tyagi: ask the newest person on the team how useful the playbook has been.
If your newest lawyer opened the playbook mid-negotiation tomorrow, would it tell them what to do? If not, you have a decision problem, and a document nobody trusts with it.
Deutz noted that SpotDraft's CLM includes structured playbooks with standards and fallbacks, an agentic option using skill files, and a Word plugin. Read our contract playbook guide for more.
