Fallback positions: preferred, acceptable and walk-away, in one ladder

A fallback position is one rung on an ordered ladder the firm holds for a single clause type. Rung 1 is the opening ask. The rungs beneath are language you would sign without a fight. The bottom rung is the floor: below it, the reviewer stops negotiating and someone else decides whether the deal continues.

The ladder is what turns a playbook from a document into something a system can run. A list of approved clauses answers one question: does this match? A ladder answers the question a negotiation produces — they said no, what do we send now, and who signs off before it goes.

Three attributes, or the rung is decoration

• The language itself. Not a description of the position but the sentence that goes into the document, in a form a drafter can paste. Descriptions are where 2 reviewers produce 2 different second positions, and the text for each rung belongs where your standard clauses live, which is part of what separates a clause library from a folder.
• The availability condition. What must be true before this rung may be offered: the rung above refused in writing, a term length, a jurisdiction, a value band. Without it a ladder is a menu, and reviewers under time pressure read menus from the bottom.
• The approver. The named role that may authorise this rung. Most playbooks leave it implicit, and it decides whether a position can be offered inside the review or has to wait for a person.

A payment-terms ladder, written out

Read that table by column. Most playbooks already hold the language column. The availability column stops a reviewer opening at rung 3 because the counterparty sounded firm on a call. The approver column is what makes the floor mean something. Rungs are ordered by what each costs the business, not by textual distance from your template.

What a system does with a ladder when a redline arrives

1. Resolve the clause type. Map the incoming clause to the taxonomy entry the ladder hangs off. On the counterparty's template this is the hard step, because the concept may sit in a schedule or be split across sections — see reviewing on the other side's paper.
2. Match the incoming text to the highest rung it already satisfies. If it satisfies rung 2, the negotiation is at rung 2, whatever anyone remembers about the last round.
3. Test the availability condition on the next rung down before proposing it. If the condition is unmet, the output is an escalation, not a proposal.
4. Emit the language for that rung rather than a note that the clause deviates. A proposal a lawyer can accept, reject or edit is a different artefact from a flag.
5. Route to the approver named on the rung, and record which rung was offered. Without that record you cannot later tell a concession from an authorisation.

Step 3 is where availability conditions earn their place. A fallback that is fine in a master agreement can be wrong in the order form beneath it, because the two are ranked against each other — see which document wins when the MSA and the SOW disagree.

The playbook that records only what you want

The common shape is a table with one row per clause and one column of approved language. It supports exactly one operation: comparison. The system says this indemnity is not our indemnity, then stops, because nothing in the record describes an acceptable version.

The ladder does not disappear when it is unwritten. It moves into the heads of the 2 or 3 people who have negotiated the clause a hundred times, so every reviewer's second position differs slightly and escalation happens when someone feels uncomfortable rather than when a stated floor is crossed. Direction belongs on the rung too: an indemnity ladder that never records who indemnifies whom is meaningless one way and dangerous the other, the defect behind an indemnity extraction that returns half the obligation.

A playbook with one position per clause can only tell you something is wrong. A ladder tells you what to send instead, and who may send it.

Where a ladder comes from, and how it is stored

Ladders are recovered from deals the firm has already done, then confirmed by whoever would sign the exception. Three or 4 rungs is usually the whole ladder; a clause with 8 is usually 2 clause types that were never separated.

Storage decides whether it survives. A ladder in prose is re-read by a person every time; a ladder as structured records — clause type, rung order, language, condition, approver role — is queryable, diffable and reportable. Building that, and the reviewer interface over it, is ordinary product work. Neighbouring definitions sit in contract review and redlining, inside our work with legal teams.

• playbooks
• contract negotiation
• clause library
• legal ops