DOCUMENT OPS

Review newly archived NDAs for non-standard clauses and log risk notes

When an NDA is archived, an agent compares its clauses against your standard template, summarizes deviations like unusual term length or one-sided indemnity.

CategoryDocument Ops
Enginepaperclip
Difficultyadvanced
Triggerevent
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNewly archived NDA detected in S3AWS S3
  • ActionAgent loads NDA text and standard-terms baselineOpenAI
  • LogicCompare clauses and rate deviation severity
  • ActionDraft structured risk summary with clause notesOpenAI
  • OutputPublish risk assessment page to ConfluenceConfluenceConfluence

What it does

Gives every freshly archived NDA a first-pass legal review. An agent reads the signed document, compares its key clauses to your company's standard NDA terms, and writes up where the counterparty's paper deviates — perpetual confidentiality, broad definitions, missing carve-outs — so reviewers know which agreements actually need a human.

When to use it

Use it when volume makes clause-by-clause manual review impractical but you still want a heads-up on the genuinely unusual ones. It's a triage layer, not a substitute for counsel, and it documents its reasoning in your knowledge base.

How it works

  1. 1A newly archived NDA in S3 triggers the run.
  2. 2The agent loads the document text and your standard-terms reference.
  3. 3It identifies each material clause and compares it against the baseline, reasoning about the direction and severity of any deviation.
  4. 4It assigns an overall risk level and drafts a structured summary with clause-level notes.
  5. 5The assessment is published as a Confluence page linked to the counterparty, ready for reviewer sign-off.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect AWS S3Buckets, objects, signed URLs.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect ConfluenceSpaces, pages, blueprints.
  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.