DOCUMENT OPS
Risky Clause Detector with Tiered Approval Routing
Scans incoming contracts for high-risk clauses and routes them to the right approver — auto-approving low-risk deals and escalating risky ones to legal in Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerNew contract in Dropbox intake folderDropbox
- ActionFetch contract file contentDropbox
- ActionScore risk and quote flagged clausesOpenAI
- LogicBranch on risk tier
- ActionEscalate high-risk to legal Slack channelSlack
- OutputLog outcome to Airtable registerAirtable
What it does
Reads each incoming contract, scores it against a risk rubric (unlimited liability, indemnification, exclusivity, non-standard payment terms), and decides who needs to sign off. Clean contracts get fast-tracked; risky ones get escalated with the exact offending language quoted.
When to use it
Use when contract volume is high enough that routing everything to legal creates a bottleneck. This filters the firehose so legal only sees what actually needs a human, while standard agreements move without delay.
How it works
- 1A new contract file in the Dropbox intake folder starts the run.
- 2The file content is pulled from Dropbox.
- 3OpenAI scores the contract against the risk rubric and quotes any flagged clauses.
- 4A logic branch splits on the risk score: low-risk routes one way, high-risk another.
- 5Low-risk contracts post a brief auto-approved note; high-risk contracts post an escalation to the legal Slack channel with the quoted clauses and a required approver.
- 6The outcome and risk tier are written back to an Airtable contract register for audit.
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.