AI & RAG

Summarize what changed between two contract versions, clause by clause

On request, compares a new contract version against the prior one, identifies which clauses were added, removed, or reworded, and posts a plain-English redline summary…

CategoryAI & RAG
Enginesim
Difficultyintermediate
Triggermanual
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerManual request naming contract + two versions
  • ActionFetch clause sets for both versionsSupabaseSupabase
  • LogicAlign clauses and classify changes
  • ActionSummarize material changes with before/after quotesOpenAI
  • OutputWrite redline summary to NotionNotionNotion

What it does

Produces a human-readable change report between two versions of the same agreement. Instead of eyeballing a redline, you get a clause-level diff: which obligations shifted, which were dropped, and which are brand new — each with the old and new wording quoted and linked.

When to use it

When a counterparty returns a revised draft and legal needs to know fast what actually moved, or when reviewing your own template updates before they propagate. Useful for negotiation reviews and version-control audits.

How it works

  1. 1A manual trigger names the contract and the two versions to compare.
  2. 2Supabase returns the full clause set for both versions, keyed by section path.
  3. 3A logic step aligns clauses by section and classifies each pair as added, removed, modified, or unchanged.
  4. 4OpenAI writes a plain-English summary of every material change, quoting before and after.
  5. 5The summary, with citations to both source versions, is written to a Notion review page.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SupabaseTables, auth, storage, edge functions.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect NotionPages, databases, comments.
  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.