DOCUMENT OPS

Ask the agent to investigate clause drift for a specific contract

A chat-triggered agent that, given a contract name, fetches the signed copy and the current template, reasons through clause differences and their downstream obligations.

CategoryDocument Ops
Enginepaperclip
Difficultybeginner
Triggerchat
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerChat request names a contract to investigate
  • ActionSearch Drive and retrieve signed copy plus templateGoogle DriveGoogle Drive
  • ActionReason over clause differences and obligationsOpenAI
  • LogicDecide which deviations are material
  • OutputReturn narrated drift assessment in chat

What it does

This is an on-demand agent you query in chat. Name a contract and it locates the executed copy and the matching current template in Drive, then works through the agreement clause by clause — not just listing textual differences but reasoning about what each deviation means for obligations, renewal exposure, and risk. It replies with a narrated assessment and concrete next steps.

When to use it

Use it for ad hoc deep dives — a one-off question from finance or a deal review where you need an interactive, reasoned answer about a single contract rather than a batch report or a fixed pipeline.

How it works

  1. 1A chat message naming the target contract starts the agent.
  2. 2The agent searches Drive, retrieves the signed agreement and the current template, and reads both.
  3. 3It reasons over the clauses, weighing each difference against standard terms and obligations.
  4. 4It decides which deviations are material and worth surfacing.
  5. 5It returns a narrated drift assessment with recommended actions directly in the chat thread.

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
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    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.