WorkflowCorporate Legal Department

Contract Redlining

Contract redlining that places each clause of a vendor’s paper on the company’s playbook ladder, proposes the rung its signed deals support, and sends what counsel may not agree to alone up to the general counsel.

Watch it work Book a walkthrough

Follow one vendor agreement through each feature ↓

Watch with transcript →

The problem

Each vendor’s paper puts the liability cap somewhere new

A vendor’s master agreement lands in the queue in its own layout and its own order. Commercial counsel reads all of it to find the terms that move, then works out how far to give on each from a playbook document and from what colleagues remember agreeing last time.

Authority gets checked by habit. A second-fallback cap on a large deal can go out without the general counsel seeing it, and a comment that hints at the next rung tells the vendor to wait for it. When the vendor’s next version comes back, an edit made with tracking off can sit in a clause everyone thought was settled.

Built forCommercial counselGeneral counselContract managersLegal operations teams

The Problem Today

Vendors send their own paper, and counsel must decide on each term how far to move and who may agree to it.

3.1 h: of in-house review per contract, on average published
56%: of legal teams cannot execute a standard contract in a week published

Worked by hand today

Clauses
Playbook
Past deals
Authority

Same vendor, two positionsFallbacks live in a document and in memory
Fallbacks leak in commentsThe vendor reads the position and waits for it

The Solution

Each clause on its ladderEach term placed from preferred, through two fallbacks, to walk away
The rung from signed dealsChosen from what the company signed with similar vendors, deal cited
Big terms go up firstAnything beyond counsel’s authority goes to the general counsel before release
Markup back the same hourTracked changes and comments that keep the internal ladder private

Built-in controls

Nothing reaches a vendor until a person sends it
Whoever prepares an escalation cannot approve it
Each decision and agent step on the record

What You Get

Counsel negotiate from what the company actually signs, and each big term reaches the right person.

25 min: of counsel review per contract, down from 3.1 hours our estimate

A playbook tuned by real dealsSee where signed deals land, rung by rung
No silent edits between roundsEach returned version compared with the last one sent
One clear answer for the businessRequesters see dates and status, never positions

On the vendor’s paper

Contract redlining on the vendor’s paper, clause by clause and round by round

Nine parts of the work, in the order a contract moves through legal, each on its own screen.

01Contract requests
A request queue that triages new vendor paper before counsel is assigned
How it works
- Open requests by age and paper: 23 across 6 commercial counsel, 17 on the counterparty’s paper
- Triage opens each new upload, matches it to its playbook and estimates the changes
- Counsel is suggested by load, and the contract manager assigns
Contract managerAnswers the business with a date, and places each new agreement with the lawyer who has room for it before anyone has read a page.
02First pass
A first pass that maps every clause of their paper to a playbook topic
How it works
- Splits the vendor’s own layout into 58 clauses, each with its page
- 41 pages and 20 sections, each clause mapped to a topic
- Places each clause on its ladder: 39 within the playbook, 19 need a change
Commercial counselOpens a forty-one page cloud agreement already sorted into what can stay, what she can fix herself and what has to go up.
03Indemnity on its ladder
A four-rung playbook ladder beside each clause, with their draft marked on it
How it works
- Their one-sided, uncapped indemnity sits past walk-away
- Our markup lights the second fallback: mutual, capped at 2× annual fees, $3,680,000
- A line across the ladder shows where the reviewing counsel’s authority ends
Commercial counselSees how far a term moves and on what basis, without opening the playbook file or asking a colleague what they gave the last vendor.
04Signed deals as precedent
The rung picked from deals the company signed, ranked by similarity
How it works
- Only executed agreements from the last 36 months, same counterparty class
- Similarity weighs class, annual fees, data held and signing date, threshold 0.80
- Of 7 comparable deals, 2 closed at the first fallback and 5 at the second
- The closest, at 0.93, opens with its signed clause text
Commercial counselNegotiates from the company’s own signed history, not from whichever deal she happened to work on last.
05Liability cap, escalated
An authority line that sends any rung past counsel’s limit upstairs
How it works
- Their cap: 6 months of fees, $920,000, with no data-incident cap
- Proposed: 1× annual fees, $1,840,000, and $5,520,000 for data incidents
- A second fallback over $1,000,000 a year escalates automatically
General counselSees each term past a lawyer’s limit before the markup leaves, so the signed copy is never where a second-fallback cap first shows up.
06Comment to the vendor
Comments to the vendor checked so no fallback or walk-away slips out
How it works
- An edited comment is checked before it saves
- Wording that reveals an internal position is refused, with a request to rephrase
- The cap comment argues from the risk across 40 hospitals
Commercial counselRewrites a comment in her own voice, knowing that a phrase hinting at the next rung is caught before the vendor reads it.
07Escalation memo
A one-page memo with the dollar exposure of each escalated term
How it works
- Five terms beyond counsel’s authority, each with their draft, our markup and the signed deal
- Exposure in dollars: uncapped indemnity to $3,680,000, no data-incident cap to $5,520,000
- Approve, change the rung or reject with a reason, each signed and logged
General counselDecides the handful of terms that carry real exposure in one sitting, without reading the whole agreement.
08Release to the vendor
A release that stays locked until each escalated term is decided
How it works
- The release button stays locked while any of the 5 escalations is open
- Once decided: 19 tracked changes, 19 comments, 9 signed deals cited internally
- Counsel releases, and the contract manager sends with a short cover note
Contract managerSends each round knowing nothing beyond a lawyer’s authority is in it, and can give the requester a send time.
09Rounds with the vendor
A round tracker that finds edits the vendor made with tracking off
How it works
- Each returned version compared word by word with the last one sent
- Round 3 from an imaging equipment vendor: 2 untracked edits found
- Shall respond became may respond, and certificates before the first visit became on request
Commercial counselCatches a quiet change to an agreed clause before signature, with no need to reread forty-seven clauses each round.

Five terms on a $5,520,000 cloud deal went to the general counsel

The terms past the reviewing counsel’s authority on one three-year cloud agreement, as the escalation memo set them out.

Term	Their draft	Our markup	Why it went up
Indemnity	Uncapped, one-sided	$3,680,000 cap, each way	Second fallback on a contract over $1,000,000 a year
Liability cap	$920,000, no data-incident cap	$1,840,000; $5,520,000 for data incidents	Their draft is past walk-away, and the rung is a second fallback
Data use	Any lawful purpose, including their own products	The health system’s own services only, no sale	Patient-data use always goes to the general counsel
Audit rights	A security report only if one is available	An independent security audit report each year	Second fallback on a contract over $1,000,000 a year
Renewal increase	$165,600 a year at 9%	At most $92,000 a year	Second fallback on a contract over $1,000,000 a year

Around the redline

The issue list, the playbook and the record behind each markup

What counsel, the general counsel and legal operations open around the redline.

Issue list of 19 changes, each with their draft, our markup on the ladder, the signed deal cited, who decides and its status, ready to export — **The issue list**All 19 changes in one table: their draft, our rung, the signed deal behind it, who decides and the status. The 39 clauses within the playbook sit on a toggle.

Signed deal opened from a citation: the executed indemnity clause capped at two times annual fees, with its execution date, deal number and annual fees — **The executed clause**Each citation opens the signed clause with its execution date and annual fees. Only fully signed versions are cited; drafts and unsigned redlines are left out.

Escalation memo as the preparing counsel sees it: terms awaiting decision, each locked with a note that only the general counsel can decide — **Prepared, so not hers to approve**Seen by the counsel who prepared the memo, each term is locked: only the general counsel can decide it.

Cloud and SaaS contract negotiation playbook, version 7: each topic with its preferred, first fallback, second fallback and walk-away terms, and signed counts — **The playbook, measured**Version 7 of the cloud and SaaS playbook: 31 topics with four rungs each, beside where 86 signed agreements of the last 12 months actually landed.

Settings: authority matrix v3 by rung and contract size, five playbooks, precedent rules with a 0.80 threshold, and roles with separation of duties — **Who may agree to which rung**Counsel decides a second fallback only under $1M a year. Patient-data use always escalates, and a walk-away exception goes to the general counsel with the chief financial officer (CFO) informed.

Audit log for the cloud agreement: the send, the release, five approvals by the general counsel and each agent step from clause mapping to the memo — **Each step on the record**Agents and people in one log, newest first: the send 38 minutes after the request, the release, five approvals, the memo and each agent step.

Walk away is a line the markup can never be placed on

The agents prepare. These calls stay with named roles, each on the record.

Choosing a different rungCounsel may move a term off the proposed rung only with a reason on the record, and the change is redrafted to match.

Agreeing past counsel’s authorityThe general counsel decides each escalated term. The counsel who prepared the memo cannot approve it.

Offering walk awayThe ladder stops above it. A walk-away exception goes to the general counsel, with the CFO informed.

Changing the playbookLegal operations drafts a change from where signed deals land. Only the general counsel approves a new version.

Six agents map, cite, draft and check, while people decide and send

AI contract review in six jobs, from the clause map to the round tracker, with the limits each one keeps.

Clause mapper

Splits any counterparty paper into clauses and maps each to a playbook topic, with page and line.

Never changes the counterparty’s text

Playbook checker

Places their draft and our markup on each topic’s ladder, and chooses the rung from signed precedent.

Never proposes below walk-away
Never picks a rung without a citation

Precedent finder

Finds executed deals with similar counterparties and cites the signed clause.

Never cites an unsigned draft
Says so when a deal is of another class

Redline drafter

Writes the tracked changes and the comments the vendor reads, in the company’s voice.

Never reveals a fallback or walk-away position
Never sends

Authority router

Checks each rung against the reviewer’s authority and writes the escalation memo.

Never approves
Never lowers a threshold

Round tracker

Compares each returned version with the last one sent, and finds untracked edits.

Never accepts a change

Rungs, precedent and sign-off in contract redlining

What is contract redlining?

Contract redlining is marking up the other side’s draft with tracked changes and comments. Here, agents map each clause of the vendor’s paper to the playbook, place each term on its ladder, pick the rung from signed deals, and draft the change and the comment. Counsel decides each rung.

Can AI redline a contract on the vendor’s own paper?

Yes. The clause mapper splits any layout into clauses with page and line and maps each to a playbook topic, so third-party paper is read like the company’s own templates. Nothing goes to the vendor until counsel releases it and the contract manager sends it.

How does it choose between the first and the second fallback?

From what the company has actually signed. The precedent finder ranks executed agreements of the same counterparty class by similarity and shows where each closed. The playbook checker proposes the rung those deals support and cites the closest. Counsel may choose another, with a reason.

What stops a comment from giving away our fallback position?

The redline drafter writes each comment for the vendor, and an edited comment is checked before it saves. Wording that names a fallback, a walk-away or how far the company can go is refused, and counsel is asked to rephrase it.

Who decides a term beyond a lawyer’s authority?

The authority router checks each rung against the authority matrix and writes a memo to the general counsel with the dollar exposure. The counsel who prepared it cannot approve it, and the markup stays locked until each term is decided.

How do I build a contract negotiation playbook it can use?

Each topic needs four rungs: preferred, first fallback, second fallback and walk away. The playbook page shows where signed deals landed on each rung. When they cluster on a fallback, legal operations can draft a change for the general counsel to approve as a new version.

Corporate Legal Department