DOCUMENT OPS

Weekly Contract Drift Digest: Summarize Liability Changes Across the Active Deal Portfolio

On a weekly schedule, it scans all contracts edited in the past week in a Drive folder, diffs each against its prior version.

CategoryDocument Ops
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires
  • ActionList contracts changed this week and fetch version pairsGoogle DriveGoogle Drive
  • ActionDiff each pair and rate indemnity/liability severityOpenAI
  • LogicDrop unchanged contracts and rank by risk severity
  • OutputEmail consolidated portfolio drift digest to legal leadershipGmailGmail

What it does

Runs weekly across an entire folder of active contracts, finds every document that changed in the last seven days, diffs each against its prior version, and rolls up all indemnity and liability movements into one executive digest emailed to legal leadership. Instead of per-document alerts, it gives a portfolio-level view of where risk shifted this week.

When to use it

Use it when a GC or deal-desk lead wants a Monday-morning readout of risk-clause activity across many simultaneous negotiations, rather than a stream of individual notifications. Best for teams managing dozens of live contracts where the question is "what moved this week."

How it works

  1. 1A weekly schedule triggers the run.
  2. 2The workflow lists all contract files modified in the past seven days in the watched Drive folder and fetches current and prior versions.
  3. 3An OpenAI step diffs each pair and extracts indemnity and liability changes, summarizing severity per contract.
  4. 4A logic step drops contracts with no risk-clause changes and ranks the rest by severity.
  5. 5A consolidated digest, ordered by risk impact, is emailed to legal leadership via Gmail.

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 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.