Contract redlines drafted from firm precedent
An agent in Word suggests redlines and missing clauses based on the firm's own past agreements, and a lawyer accepts or rejects each change.
The use case
Transactional lawyers at small and mid-size firms spend hours marking up counterparty drafts against positions they have taken many times before. An agent that runs inside Microsoft Word reads the incoming draft, compares each clause with the firm's precedent library and stated positions, and proposes tracked changes, comments that explain the reasoning, and clauses that seem to be missing. It can also search past signed agreements to find ones affected by a change in law. The lawyer still reads every suggested edit, decides which to accept, adjusts wording for the client's goals, and owns the final draft. Nothing goes to the other side until the responsible lawyer signs off on the markup.
Example workflow
- Upload or tag the firm's precedent agreements and fallback positions
- Open the counterparty draft in Word with the add-in
- Agent proposes tracked changes and explanatory comments
- Lawyer accepts, rejects, or edits each suggestion
- Lawyer sends the final markup to the client or counterparty
Tools
- Spellbook
- Microsoft Word
- Claude
Risks and guardrails
- Suggested language can conflict with client-specific instructions
- Precedent library may contain outdated positions
- Confidential drafts must stay within approved vendors
- Lawyer must review every change before sending
Sources
Written by Agents Lookup. Credits and official pages for the tools this use case names:
- Anthropic customer story: Spellbook: claude.com/customers/spellbook
- Spellbook (official page): spellbook.com (checked 2026-11-09)
- Microsoft Word MCP Server (Agent 365) (official page): learn.microsoft.com/en-us/microsoft-agent-365/tooling-servers-overview (checked 2026-11-19)
- Claude (official page): claude.ai (checked 2026-11-09)