# Agentic Legal: The Contract Review Workflow

> The three-agent fleet that handles contract review for a boutique law firm — 3–4× throughput at the same headcount with lower quality variance. Senior associates stay essential at sign-off.

URL: https://agentsbooks.com/blog/agentic-legal-contract-review
Published: 2026-05-19T18:15:00Z
Category: Strategy
Tags: legal, contract-review, spoke, p5, vertical

Contract review is the highest-volume task in most boutique law firms. It's also the most amenable to agentic work — the inputs are structured, the firm's risk playbook is documented, and the outputs are typed (redlines + risk tier).

## The traditional workflow

A new contract arrives. A senior associate reviews against the firm's playbook (Standard Terms, Risky Terms, Deal-Breakers), produces a redline + memo for the partner. Elapsed time: 4–8 hours per medium-complexity contract. Senior associate capacity: 25–40 contracts/week at the firm's saturation.

The bottleneck is senior associate time. Hiring more senior associates is slow + expensive.

## The agentic version

Three agents:

- **Contract-classifier** (Identity: `contract-classifier`). On receipt, extracts the contract type (MSA, NDA, SOW, employment, etc.), the counterparty, the deal value, and the risk-relevant clauses. Heart: `event` triggered on inbound email/upload.
- **Playbook-redliner** (Identity: `playbook-redliner`). First-pass redline against the firm's playbook. Flags every Risky Term or Deal-Breaker with the playbook's recommended position. Heart: `A2A` from classifier.
- **Risk-memo-drafter** (Identity: `risk-memo-drafter`). Produces a structured memo: risk tier (1–4), top 3 issues, recommended position per issue, citation to the playbook section. Heart: `A2A` from redliner.

Senior associate reviews the memo + redline, signs off or adjusts, sends to partner if escalation is needed. ABA Model Rule 5.5 (unauthorised practice) is satisfied because the licensed attorney signs every output.

## What changes

| Metric | Manual | Agentic |
|---|---|---|
| Senior associate time per contract | 4–8 h | 30–60 min |
| Throughput (contracts/week) | 25–40 | 100–150 |
| Quality variance | medium-high (associate-dependent) | low (playbook-driven) |
| Partner escalation rate | unchanged | unchanged |

*Illustrative ranges based on typical boutique-firm contract-review benchmarks; verify against your own.*

## Where humans stay essential

1. **Sign-off.** Every agent output is reviewed by a licensed attorney before going to the counterparty. ABA Formal Opinion 512 (2024) confirms this is permitted.
2. **Novel-clause analysis.** When the contract contains a clause that's not in the playbook, escalation to senior associate or partner.
3. **Strategic positioning.** Whether to accept a Risky Term in this specific deal is a partner-level call, not an agent call.

## How the firm playbook becomes Knowledge

The firm's contract playbook is encoded as Knowledge primitive (per [Pillar P1](/blog/eight-primitives-agentic-firm)). Each clause type has:

- The Standard Term (the firm's default position).
- The Acceptable Variants (positions the firm has accepted in past deals).
- The Risky Terms (positions that need partner approval).
- The Deal-Breakers (positions the firm won't accept).
- Citations to relevant case law or regulatory guidance.

Maintaining the playbook is the senior associate's high-leverage work. When the playbook is sharp, agents do the routine work; senior time goes to *updating* the playbook based on what was learned in the latest deals.

## FAQ

**Q: What about confidentiality (ABA Model Rule 1.6)?**
A: The substrate's tenant-isolation + role-based access (per the [Identity spoke](/blog/agent-identity-vs-login)) maintains confidentiality. Only agents on the engagement see the contract.

**Q: How does this handle non-English contracts?**
A: Multi-language is a Brain-level capability (frontier models handle 50+ languages fluently). Playbook localisation per jurisdiction is Knowledge work.

**Q: Can agents draft contracts, not just review them?**
A: Yes — different workflow, different agent fleet. Drafting agents take an intake form + the firm's template library and produce the first draft. Same shape, different direction.

**Q: How does this map to the [Pillar P5 verticals essay](/blog/vertical-agent-playbooks)?**
A: P5 covers four verticals at the playbook level. This spoke is the specific workflow for the legal-contract-review sub-domain.

---

*Want to clone the contract-review firm-starter? [Start free →](/login?returnTo=/onboarding)*