Building a Contract Playbook Your Team Will Actually Use
.svg){kind=small}
Webinar Recap & Key Takeaways
Most legal teams agree that a contract playbook is worth having. Far fewer have one their team actually reaches for when a negotiation gets messy. In a live poll during this session, 61% of attendees said they don't have a playbook at all, and only 6% said theirs is embedded into their contracting workflow. Among those with a playbook, the biggest challenge by far was keeping it up to date (57%).
This panel, hosted by SpotDraft, brought together two in-house lawyers who negotiate technology and commercial agreements every day. Rather than treating the playbook as a document legal writes once and files away, the discussion focused on what happens when it meets reality: a counterparty rejects your preferred position, the business needs the deal signed today, or an ask comes in that no one has seen before.
The session covered how to structure a playbook around decisions rather than completeness, where to be prescriptive and where to trust judgment, how to tell a one-off exception from a market shift, and how teams are using negotiation history and AI to keep their playbooks alive.
Session highlights
05:43 Aprajita Tyagi introduces a traffic-light framework for sorting clauses into escalate, pause, and accept.
08:13 Anna Pototschnig explains why playbooks fail when they ignore the underlying transaction or a counterparty’s third option.
15:18 Aprajita shares telltale signs a playbook isn’t being used, from stale update dates to repeated Slack questions.
19:03 The panel discusses where playbooks should be prescriptive, especially on high-risk clauses like data usage and indemnities.
25:48 Anna explains how to tell a one-off exception from an emerging standard, using AI trials as an example.
29:58 Aprajita outlines who should approve exceptions based on risk, deal value, and subject matter.
37:31 Anna makes the case for one authoritative playbook inside the workflow, with controlled access to fallbacks.
51:34 Aprajita shares how her team uses a Claude skill to log playbook deviations for regular review.
Every red line that you make or every red line that you agree to is data."
- Aprajita Tyagi, Sr. Corporate Counsel, Miro
Watch the webinar now!
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.svg)
