1. First-pass contract review against your playbook
Every incoming contract waits in a queue for a lawyer to read it end-to-end and flag risky clauses by hand — a bottleneck for sales and procurement.
Trigger: Email or Webhook (contract uploaded)
How the workflow runs
- Trigger
Contract submitted. An Email/Webhook trigger receives the document.
- Knowledge
Compare to your playbook. A Knowledge node holds your clause standards and fallback positions; the contract is checked against them — with citations.
- Agent
Flag deviations + suggest redlines. An Agent node lists non-standard clauses (liability, indemnity, term, jurisdiction) and proposes edits.
- Approval
Lawyer reviews the flags. An Approval node puts the qualified opinion where it belongs — the agent surfaces, counsel decides.
- Output
Return the marked-up summary. An Output node sends the risk summary back to the requester.
Channels & connectors
- Webhook
- Knowledge base
- Approval / HITL
Outcome
Routine contracts get a consistent first-pass in minutes; lawyers start from a flagged summary instead of a blank page.
Why it helps
Cuts the review bottleneck without removing the lawyer — the machine reads and flags, the human judges.
Build spec
1 agent — 1 review agent; the lawyer sign-off is an Approval node.
System prompt (paste-ready)
You are a contract first-pass reviewer. Compare the incoming contract against the clause standards and fallback positions in the playbook (Knowledge). Identify non-standard or missing clauses — liability, indemnity, term, termination, jurisdiction, IP, confidentiality — cite the playbook position each deviates from, and propose specific redline edits. Output a structured risk summary {clause, issue, playbook_position, suggested_edit, severity}. This is a first pass for a lawyer to review — never present it as legal advice or a final position.MCP connectors
- Document intake (email/upload) — via Email/Webhook trigger
- Contract/DMS store — via a Tool (MCP) node
Built-in tools
- document parsing (contract PDF/DOCX)
- knowledge_search (clause playbook + fallbacks)
Guardrails
- First-pass only — every flag is reviewed by a lawyer at the Approval node before anything goes back
- Deviations cite the specific playbook position, not a generic opinion — no ungrounded legal claims
- The agent flags and suggests; it never sends redlines to the counterparty itself
Output & delivery
The agent produces a cited, clause-by-clause risk summary with suggested redlines; a lawyer reviews it at the Approval node, then an Output node returns the marked-up summary to the requester.
