DOCUMENT OPS
AI clause-risk review for incoming contracts
An agent reads each new contract PDF against your playbook, flags risky or missing clauses, and posts a redline-style risk memo to the legal channel before anyone signs.
How it runs
The automated pipeline, trigger to output.
- TriggerNew contract PDF in Dropbox intakeDropbox
- ActionRead full contract textDropbox
- ActionAgent reviews clauses against playbookOpenAI
- LogicRoute high-risk contracts to urgent path
- OutputPost risk memo to legal Slack channelSlack
What it does
Gives every inbound contract a first-pass legal review. An agent compares the document to your clause playbook, scores risk, lists problem clauses with the offending language quoted, and delivers a memo to legal.
When to use it
Use this when contracts need a clause-level read against standard positions (liability caps, indemnity, auto-renewal, governing law) and your reviewers are drowning in volume. It triages so humans focus on the genuinely risky paper.
How it works
- 1A new contract PDF in the Dropbox intake folder fires the trigger.
- 2The agent reads the full document text.
- 3It evaluates each clause against the configured playbook, quoting the actual language and assigning a low / medium / high risk level per issue.
- 4A logic step routes high-risk contracts to a separate urgent path.
- 5A risk memo with findings and an overall recommendation is posted to the legal Slack channel.
- 6The risk score and memo link are written to Airtable for tracking.
Set it up
What you configure once, before turning it on.
- 1Connect DropboxFiles and folders.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Connect AirtableBases, tables, views, automations.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Document Ops workflows
Flag redline deviations when a contract lands in Drive
Watches a Google Drive folder for incoming counterparty contracts, diffs each clause against your approved template library.
Gate contract signing on clause-deviation approval
When a contract is submitted for signature via webhook, diffs its clauses against approved templates and either auto-approves clean documents or holds them in Slack for explicit…
Triage emailed contract redlines and route by risk
When a counterparty emails a redlined contract, extracts the attachment, diffs clauses against approved templates.
Draft a negotiation brief from contract clause deviations
An agent reviews a contract against approved templates, researches each deviation.
Log contract clause deviations to a Notion review register
On a daily schedule, scans a Drive contracts folder, diffs clauses against approved templates with OpenAI.
Weekly audit of clause drift across the contract repository
Each week, scans all executed contracts in Drive, measures how far each clause has drifted from approved templates.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.