DOCUMENT OPS

Weekly digest of clause changes across all contracts signed this week

On a weekly schedule, scans every contract signed in the last seven days, diffs each against its negotiated draft.

CategoryDocument Ops
Enginepaperclip
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires
  • ActionList PDFs signed in the last 7 daysGoogle DriveGoogle Drive
  • ActionLocate matching draft for each signed fileGoogle DriveGoogle Drive
  • LogicDiff clauses and classify each contract clean or changed
  • OutputPublish weekly clause-change digest to NotionNotionNotion

What it does

Instead of alerting per contract, this builds a weekly rollup. It gathers everything signed in the past seven days, diffs each executed PDF against its draft, and writes a Notion page grouping deals into clean versus changed, with the specific clauses that moved listed under each changed contract.

When to use it

Use it when per-document alerts would be noise but leadership still wants visibility into how often counterparties alter terms before signing. Good for a Monday legal-ops review or a counsel who reports change trends to the business.

How it works

  1. 1A weekly schedule triggers the run.
  2. 2The workflow lists all PDFs added to the Drive 'Signed' folder in the last seven days.
  3. 3For each, it locates the matching negotiated draft and diffs the clauses.
  4. 4It classifies each contract as clean or changed and collects the altered clauses.
  5. 5A single Notion digest page is published with a clean-vs-changed summary and per-contract detail.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Google DriveDocs, sheets, slides, files.
  2. 2
    Connect NotionPages, databases, comments.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    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.