Building a house playbook when your partners disagree on everything
A method for turning a shelf of closed matters into one tiered position document a partnership can actually live with — including what to do about the clauses nobody agrees on.
Every firm that tries to write a playbook hits the same wall in week one. Two partners have negotiated the same clause for fifteen years and arrived at different answers, both defensible, both backed by matters that closed. Asking them to agree in the abstract produces a meeting. It does not produce a playbook.
The way through is to stop asking for agreement on the position and start asking for agreement on the fallback tier.
The structure that makes disagreement survivable
A playbook entry in LexCore is not one position. For each clause type it holds a policy position, tiered fallbacks, and a guidance note for the reviewing lawyer. The tiers are what carry the disagreement:
- Tier 1 fallbacks are pre-approved — an associate may concede them without asking anyone.
- Tier 2 fallbacks require sign-off — the review escalates rather than deciding.
- The guidance note is where a partner's reasoning lives, in prose, for the person doing the work at 11pm.
So the contested clause does not need a winner. The strict position becomes the policy position; the other partner's answer becomes a Tier 2 fallback with their reasoning attached. Nothing is conceded automatically, and nothing is lost.
Start from closed matters, not from a blank document
- Pull twenty to thirty closed agreements of one type. One type — mixing MSAs and leases produces a playbook that is right about neither.
- For each clause type, read what was actually signed, not what the first draft asked for. The signed text is the firm's revealed position; the opening draft is its aspiration.
- Where the signed text clusters, you have a policy position. Where it scatters, you have a fallback ladder, and the scatter itself tells you the tiers.
- Write the guidance note last, and write it to the associate, not to the file.
The clauses nobody agrees on
There is usually a short list — limitation of liability, IP ownership, and whatever the firm's practice mix makes contentious — where no tiering ends the argument. Leave those with a strict policy position and a guidance note that says the disagreement exists. A review will escalate them to a human every time, which is the correct outcome: the firm has decided that this clause is a partner's call, and the playbook now records that decision instead of hiding it.
A playbook is not a machine for removing judgment. It is a machine for spending judgment on the clauses that need it.
Keep reading
The Lawyer Analysis Metric: documenting human supervision in-tenant
Why the audit trail needs to record who approved a finding, who overruled it, and under which supervision policy — and what that record is for.
Why we reject findings that fail the exact character offset test
Most legal AI products work on summaries of chunks. Here is the failure mode that introduces into an indemnities review, and how we anchored CitationGate to verbatim spans instead.