Legal playbook · AI Employee: Lex

Counterparty Redline Tracking

Redline review time drops sharply

Install this playbookBack to marketplace
The problem

Contract negotiations are a redline ping-pong that legal can't easily see across the org. Sales sends the customer's redlines to legal in email; legal responds; sales forgets what version is current; the customer's counsel sends yet another Word doc with tracked changes that no one merges cleanly. By the time it's signed, everyone hopes they're on the same version. Repeat customer-driven redlines ("we always add liability caps") never get systematically captured; every negotiation reinvents the wheel.

At a glance
Trigger
Ticket event
Approvals
None (surface + summarise)
What it does
Read-only
Systems
Ironclad
How it feels in production

An hour-by-hour walkthrough.

Contract negotiation with Acme Corp is in flight. Their counsel sends a redlined MSA back. Sales AE forwards to Lex. Lex parses the redline: - Total edits: 34 tracked changes across 12 sections - Material edits: 8 (materially changing our position) - Minor / typographical: 26 - New sections proposed by counterparty: 2 (uptime SLA credit table, source-code escrow) For each material edit, Lex compares against our playbook (standard positions, acceptable fallbacks, non-negotiables): - "Reduce liability cap from 12 months fees to 6 months" → against playbook; standard position is 12; fallback authorized to 9 months for enterprise; below that = escalation to GC. - "Extend audit rights to 3 years post-termination" → playbook allows 2 years; 3 is a legal escalation. - "Add source-code escrow with third party" → new; not in playbook; legal + product decision. Lex drafts the response redline: accepts fallbacks where authorized, rejects with playbook rationale where not, escalates novel items. Response sent to legal reviewer with the diff summary + playbook citations. Legal reviews in 15-20 minutes vs. 2 hours from scratch. Every round tracked: version, sent by whom, when, key changes. Sales sees the round history + current-position summary. When signed, the signed version + full negotiation history archives to Ironclad. Post-close: Lex extracts what customers commonly redline + surfaces to legal for playbook updates.
How it works

Step by step.

  1. 01

    Parse counterparty redline into structured edits

    Word doc / PDF redline → structured edit list per clause + change type (deletion, insertion, replacement). Classify: material vs. minor / typo. Material edits get individual analysis.

    Word / PDF parser · Redline extractor · Clause library
  2. 02

    Compare each material edit against playbook

    Playbook per contract type: standard position, acceptable fallbacks, non-negotiables. Each edit categorised: within-fallback, requires-approval, escalate.

    Negotiation playbook · Fallback matrix
  3. 03

    Draft response redline with playbook citations

    Accept fallbacks where authorized; reject with playbook rationale where not; escalate novel items to legal + business. Response redline generated in Word for legal to review + edit.

    Word template engine · Playbook citations
  4. 04

    Legal review + send

    Legal reviews the drafted response with per-edit reasoning. Approves, edits, or escalates novel items. On approval, response sent to counterparty; round tracked.

    Slack · Teams · Web UI · Email · Ironclad
  5. 05

    Round tracking + post-close learning

    Every round tracked. Sales sees current round + position summary. On close: signed version + negotiation history archives. Post-close: extract common redline patterns to feed playbook updates.

    Ironclad · Analytics · Playbook iteration
Systems and wiring

What you connect to make this run.

Ironclad · DocuSign CLM · Concord

read+write

CLM as the round-by-round repository. Each version tagged with round number + sender + timestamp. Signed version + negotiation history archived together.

Word / Google Docs · PDF parser

read

Redline extraction from tracked-changes Word docs + PDFs with markup. Handles complex nested changes + comment threads.

Negotiation playbook · Fallback matrix

read+write

Standard positions per contract type, authorized fallbacks per role, non-negotiables. Updated based on post-close pattern learning.

Slack · Teams · Email

read+write

Response drafting + review + send. Sales visibility into round status without needing to be in the redline weeds. Legal + business escalation as needed.

What changes

Before and after, honestly.

Time per redline round (receive to respond)
Before
3-8 business days
After
1-2 business days
Legal hours per redline round
Before
3-6 hours
After
20-40 minutes (review the drafted response)
Version-tracking errors (sending wrong version)
Before
5-15% of negotiations
After
Under 1%
Playbook coverage of common counterparty edits
Before
40-60%
After
85%+ (updates driven by pattern extraction)
Related

Playbooks that pair with this one.

Legal

MSA & SOW From Templates

Initial template flow; redline flow is the negotiation continuation.

Legal

Contract Status Lookup

Round history queryable through the same lookup mechanism.

Frequently asked

Answers about this playbook.

What if the counterparty sends redlines outside Word (native language, PDF markup)?

Parser handles PDF markup + several native formats. Non-standard formats (image-based markup, handwritten) fall back to legal manual entry; Lex still tracks the round.

How does it handle multi-round negotiations where positions drift?

Each round tracked with position snapshot. Legal + sales see the drift arc — helpful for spotting scope creep or position erosion. Fallback authorization applies per-round; second-round asks for same concession revisit.

What about parallel negotiations of related documents (MSA + DPA + order form)?

Related-document tracking. Redlines on one document may affect another (order-form pricing depends on MSA payment terms). Cross-document consistency checks surface conflicts.

Can it draft a whole clause revision (not just accept/reject counterparty's edit)?

Yes — for playbook-covered situations, alternate clause language drafted. Legal reviews the alternative before send. Reduces round count by proposing acceptable middle ground rather than binary accept/reject.

How does it interact with our contract-management team?

Contract managers see round status + position drift. They can override playbook ("strategic deal, authorized to accept broader fallback") with GC signoff. Playbook overrides logged for future consistency.

See it run on your data.

Free plan, no credit card. Connect the systems this playbook needs and run it against a past event first.

Book a demoMore Legal playbooks