DOCUMENT OPS

Flag clause deviations when a redlined contract lands in Drive

Watches a Google Drive folder for incoming redlined contracts, diffs each clause against your standard clause library.

CategoryDocument Ops
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew redlined contract in Drive folderGoogle DriveGoogle Drive
  • ActionRead and segment contract into clausesGoogle DriveGoogle Drive
  • ActionDiff each clause against standard clause libraryOpenAI
  • LogicKeep only material deviations
  • OutputWrite deviation report to NotionNotionNotion

What it does

When a counterparty returns a marked-up contract, this workflow compares the negotiated text against your approved clause library clause-by-clause and produces a structured deviation report. Each flagged item names the clause, shows the standard language next to the proposed language, and rates how far it drifted.

When to use it

Use it when your legal or deals team receives third-party redlines through a shared Drive folder and needs a fast first-pass review before a lawyer reads the whole document. It catches off-standard indemnity, liability cap, and termination language without manual line-by-line reading.

How it works

  1. 1A new or updated file in the watched Google Drive folder triggers the run.
  2. 2The contract text is read from Drive and segmented into named clauses.
  3. 3OpenAI matches each clause to its counterpart in the standard clause library and scores the deviation.
  4. 4A logic step keeps only clauses that materially differ from the approved baseline.
  5. 5A Notion page is created with a side-by-side table of standard vs. proposed language and a severity tag per deviation.

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 NotionPages, databases, comments.
  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.