DOCUMENT OPS

Send a weekly clause-drift digest across the active contract portfolio

On a weekly schedule it scans all contracts processed that week, aggregates deviation patterns by clause type.

CategoryDocument Ops
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule
  • ActionQuery last seven days of drift reportsNotionNotion
  • LogicAggregate deviations by clause type and risk
  • ActionWrite trend digest with template-fix suggestionsOpenAI
  • OutputEmail digest to legal leadershipGmailGmail

What it does

Instead of reacting to one contract at a time, this rolls up a week of drift activity into a single executive view. It groups deviations by clause type across every agreement reviewed, spots which sections counterparties keep pushing back on, and turns that into a digest legal leadership can act on at the template level.

When to use it

Use it when you want to fix the source of drift, not just police it — for example noticing that the indemnity clause was renegotiated in eleven of twelve deals this week, which signals the template itself needs updating.

How it works

  1. 1A weekly schedule kicks off the run.
  2. 2All drift reports from the past seven days are queried from the Notion database.
  3. 3Deviations are aggregated by clause type and risk level into a frequency table.
  4. 4The model writes a narrative digest calling out the top recurring deviations and a suggested template change for each.
  5. 5The digest is emailed to the legal leadership distribution list via Gmail.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect NotionPages, databases, comments.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect GmailRead, draft, send, label.
  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.