DOCUMENT OPS

Contract Redline Comparison and Version Diff

Compares a counterparty's returned contract against your standard template, highlights every material change, and posts a redline summary for negotiation review.

CategoryDocument Ops
Enginesim
Difficultyadvanced
Triggerevent
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerReturned contract uploaded to Drive folderGoogle DriveGoogle Drive
  • ActionRead returned contract versionGoogle DriveGoogle Drive
  • ActionFetch matching standard templateGoogle DriveGoogle Drive
  • ActionGenerate clause-by-clause diff with AIOpenAI
  • LogicRank changes by negotiation impact
  • OutputPost ranked redline to deal SlackSlack

What it does

When a counterparty sends back an edited contract, this fetches your baseline template and the returned version, then has an LLM produce a clause-by-clause diff: what was added, deleted, or weakened. The redline summary makes negotiation prep fast and unambiguous.

When to use it

Use during active negotiation when redlines come back and someone has to manually compare against the original. This is for deal desks and legal ops that want a consistent read on what the other side actually changed.

How it works

  1. 1A new returned contract uploaded to the Drive negotiation folder triggers the run.
  2. 2The returned version content is read from Google Drive.
  3. 3The matching standard template is fetched from Drive by contract type.
  4. 4OpenAI produces a clause-by-clause diff flagging material changes and weakened protections.
  5. 5A logic step ranks the changes by negotiation impact (blocker, negotiate, accept).
  6. 6The ranked redline summary is posted to the deal Slack channel for the negotiating lead.

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 SlackChannels, DMs, threads, mentions.
  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.