DOCUMENT OPS

Flag clause drift when a signed contract lands in Drive

Watches a Drive folder for newly signed agreements, compares each one against the current master template.

CategoryDocument Ops
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew signed contract added to Drive folderGoogle DriveGoogle Drive
  • ActionLoad agreement text and current master templateGoogle DriveGoogle Drive
  • ActionRun clause-by-clause drift comparisonOpenAI
  • LogicAny high-risk deviation detected?
  • OutputPost drift report to legal Slack channelSlack

What it does

Every time a countersigned agreement is dropped into a watched Google Drive folder, this workflow pulls the matching master template and runs a clause-level comparison. It surfaces added, removed, and materially reworded clauses, then routes a structured drift summary to your legal channel so nothing slips into the repository unreviewed.

When to use it

Use it when sales or vendors return signed contracts and your team needs to know, immediately, where the executed copy diverged from the approved template — indemnity caps loosened, governing law swapped, payment terms stretched. Ideal for teams filing dozens of agreements a month who can't read every page.

How it works

  1. 1A new file in the signed-contracts Drive folder triggers the run.
  2. 2The agreement text and the current master template are loaded from Drive.
  3. 3An OpenAI model performs a clause-by-clause diff, classifying each change by section and risk.
  4. 4A logic step checks whether any high-risk deviation was found.
  5. 5If drift exists, a formatted report (clause, old text, new text, risk) is sent to the legal Slack channel; clean documents are logged silently.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Google DriveDocs, sheets, slides, files.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.