DOCUMENT OPS

When the master template changes, find every contract now out of sync

Triggers whenever the master contract template is edited in Drive, re-checks all previously signed agreements against the new language.

CategoryDocument Ops
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerMaster template edited in DriveGoogle DriveGoogle Drive
  • ActionLoad new template and all signed agreementsGoogle DriveGoogle Drive
  • ActionDiff each agreement against updated clausesOpenAI
  • LogicKeep only agreements now out of alignment
  • OutputOpen Linear remediation ticket per affected contractLinearLinear

What it does

When legal updates the master template, this workflow figures out which already-signed agreements no longer reflect the new standard. It diffs each historical contract against the revised template and creates a tracked remediation ticket for every one that now needs an amendment or addendum.

When to use it

Use it right after you tighten a clause — say a new data-processing addendum or a revised liability cap — and need to identify the back catalog of live contracts that predate the change and should be renegotiated at renewal.

How it works

  1. 1An edit to the master template file in Drive triggers the run.
  2. 2The new template and all signed agreements are loaded from Drive.
  3. 3An OpenAI model compares each agreement to the updated clauses and identifies gaps introduced by the change.
  4. 4A logic step keeps only agreements that fall out of alignment with the new language.
  5. 5For each, a Linear issue is opened with the affected clause, the gap, and the contract reference for remediation tracking.

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 LinearIssues, projects, cycles, triage.
  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.