Contract playbook

The contract playbook was born in Anglo-Saxon legal departments, then in legal ops teams, to pass on knowledge that had stayed tacit: how far the company is willing to go on liability, intellectual property, personal data, termination, penalties. It writes that knowledge down, clause by clause, so that a junior lawyer or a salesperson can answer the counterparty without escalating every question.

It differs from the clause library, which gathers approved wordings, and from the contract template, which assembles a complete version of them. The playbook adds strategy: why the clause is drafted that way, what the company can concede, in which order, and who decides. It belongs to contract governance, alongside approval workflows and delegation of signing authority.

Each clause sheet has four levels. The standard position, linked to the wording in the clause library. The fallback positions, ordered from the most to the least favorable, each with its wording. The red line, the position the company refuses whatever the counterparty. Finally the delegation: who may grant each fallback, from the salesperson to the general counsel, and when to escalate.

The sheets rest on the applicable law. Under French law, article 1170 of the Civil Code (Code civil) deems unwritten any clause that deprives the debtor’s essential obligation of its substance; article 1231-5 lets the judge reduce a manifestly excessive penalty clause; article L. 442-1 of the Commercial Code (Code de commerce) sanctions a significant imbalance between business partners. The playbook recalls these limits so that a granted fallback remains enforceable and a red line is argued.

The most common approach starts from what exists. The legal department rereads the last difficult negotiations and notes, for each disputed clause, what was asked, granted and refused. Those findings become the first fallbacks and red lines. Five clauses are enough for a first version: liability, confidentiality, personal data, intellectual property, termination.

Each sheet is approved by legal and, for fallbacks with a financial impact, by finance or general management. The playbook is then shared with sales and procurement with a simple rule of use: what is in the playbook is decided without a lawyer, everything else is escalated. A periodic review adds new concessions and removes positions that have become obsolete.

For the legal department, the playbook turns individual expertise into a collective asset: positions survive a lawyer’s departure, answers to counterparties are consistent from one deal to the next, and time goes to the clauses that fall outside the frame. It also provides a ready argument: every frequent request from a counterparty has a written answer.

For sales and procurement, it shortens cycles: a request for a liability cap is settled in the meeting if the fallback is authorized. For general management, it makes visible the level of risk accepted across the portfolio. The most common mistake is the playbook that is too long and never read: one sheet per clause, one page per sheet, and sample wordings rather than principles.

With AI, the playbook becomes executable. The tool compares the contract received from the counterparty with the recorded positions, flags each deviation, classifies it as matching an authorized fallback or crossing a red line, and proposes the fallback’s counter-wording. The lawyer no longer reads the whole contract but the list of deviations, with the source clause alongside, and keeps the decision.

The playbook connects with the other notions of this glossary: it draws its wordings from the clause library, feeds contract review in the CLM, reflects legal ops practice and states what may be changed by amendment (avenant). The documented positions also serve the contract manager, who knows during performance which concessions were made and why.