DOCUMENT OPS
Amendment Conflict Reviewer: Agent Diff of New Redlines Against the Full Contract Set
An agent reviews a newly redlined amendment in Drive, diffs its indemnity and liability changes against the master agreement and prior amendments.
How it runs
The automated pipeline, trigger to output.
- TriggerNew redlined amendment added to deal folderGoogle Drive
- ActionRetrieve amendment, master agreement, and prior amendmentsGoogle Drive
- ActionAgent reasons across set for indemnity/liability conflictsOpenAI
- LogicBranch if a cross-document conflict is found
- OutputPost structured conflict report to deal team in TeamsMicrosoft Teams
What it does
When a redlined amendment is added to a deal's Drive folder, an agent reads it alongside the master agreement and every prior amendment, then reasons across the full set to find indemnity and liability changes that conflict with or compound existing terms. It catches cross-document risk that a single pairwise diff misses, such as an amendment quietly reinstating liability a prior amendment had capped.
When to use it
Use it for complex, multi-amendment contracts where risk lives in the interaction between documents, not just the latest redline. Best for mature deals or master-services relationships with stacked amendments where conflicting indemnity language is easy to introduce by accident.
How it works
- 1A new amendment file lands in the deal's Drive folder, triggering the agent.
- 2The agent retrieves the amendment, master agreement, and all prior amendments.
- 3It reasons across the set to map current effective indemnity and liability terms and detect conflicts or compounding risk introduced by the new redline.
- 4A logic step branches on whether any cross-document conflict was found.
- 5If conflicts exist, the agent posts a structured conflict report to the deal team in Microsoft Teams.
Set it up
What you configure once, before turning it on.
- 1Connect Google DriveDocs, sheets, slides, files.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect Microsoft TeamsChannels, chats, files.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Document Ops workflows
Narrate new Dropbox PDFs into MP3 audio versions
When a PDF lands in a watched Dropbox folder, extract its text and generate an ElevenLabs voice narration.
On-demand PDF narration via webhook with emailed audio link
Accepts a PDF URL through a webhook, generates an ElevenLabs narration with the requested voice, stores the MP3, and emails the requester a download link.
Triage emailed contract redlines and route by risk
When a counterparty emails a redlined contract, extracts the attachment, diffs clauses against approved templates.
Batch-narrate a Google Drive PDF folder in multiple languages
On a schedule, finds PDFs in a Google Drive folder that lack audio, then generates ElevenLabs narrations in each configured language and files them into per-language subfolders…
Executed Contract Exhibit & Initials Completeness Gate
When a signed contract lands in a Dropbox intake folder, verify every required exhibit, schedule, and initialed page is present.
Draft a negotiation brief from contract clause deviations
An agent reviews a contract against approved templates, researches each deviation.
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.