DOCUMENT OPS

Counterparty NDA Clause Diff Reviewer

Compares an incoming counterparty NDA against your standard template clause by clause, summarizes every deviation, and opens a Linear issue for legal to review the redlines.

CategoryDocument Ops
Enginesim
Difficultyadvanced
Triggerevent
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerCounterparty NDA arrives in intake mailboxGmailGmail
  • ActionExtract contract text from email or attachmentGmailGmail
  • ActionDiff clauses against standard template with OpenAIOpenAI
  • LogicCheck for material deviations
  • OutputOpen Linear issue with per-clause diffLinearLinear

What it does

When a counterparty sends back their own NDA paper instead of signing your template, this compares the two clause by clause, identifies where their language deviates (term, jurisdiction, carve-outs, return-of-materials), writes a plain-English summary of each deviation, and opens a Linear issue so legal can act on the redlines.

When to use it

Use it when counterparties routinely substitute their own NDA and someone has to manually diff it against your standard form. It surfaces exactly what changed so review focuses on deviations, not re-reading the whole document.

How it works

  1. 1A counterparty NDA arrives in the intake mailbox.
  2. 2The contract text is extracted from the email or attachment.
  3. 3An OpenAI step aligns each incoming clause to the matching clause in your standard template and produces a deviation summary.
  4. 4A logic step checks whether any material deviations were found.
  5. 5If deviations exist, a Linear issue is created with the per-clause diff summary attached for legal review.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GmailRead, draft, send, label.
  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.