DOCUMENT OPS

Send a weekly digest of contracts that drifted from standard clauses

On a weekly schedule, scans the contracts folder from the past week, diffs each against the standard clause library.

CategoryDocument Ops
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires
  • ActionList and read past week's contractsGoogle DriveGoogle Drive
  • ActionDiff each contract and score driftOpenAI
  • LogicRank by total drift, trim tail
  • OutputPublish ranked digest to NotionNotionNotion

What it does

This workflow gives leadership a recurring readout instead of per-contract noise. Each week it gathers the contracts processed in the period, diffs every one against the standard clause library, and produces a ranked digest showing which agreements drifted furthest from approved language.

When to use it

Use it for a legal or operations lead who wants a Monday-morning view of negotiation exposure across all active deals, rather than reacting to documents one at a time. It surfaces the riskiest agreements for follow-up without anyone manually compiling them.

How it works

  1. 1A weekly schedule triggers the run.
  2. 2All contracts added to the Google Drive folder during the past week are listed and read.
  3. 3OpenAI diffs each contract's clauses against the standard library and tallies a drift score per document.
  4. 4A logic step ranks the contracts by total drift and trims the long tail.
  5. 5A consolidated digest is published to Notion with the ranked list and top deviations per contract.

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.