[Workflows and Associates]

Repeat work, done every week. Nothing leaves without a yes.

Describe a routine in plain language. Clausel turns it into numbered steps and tests it on your own contracts. An Associate applies your skill, its code runs in a sealed sandbox, and a connector reaches your other systems. Before any write, the run stops for a person.

Book a demo See the templates
Weekly renewal radar Live
Run 37, started 08:00
  1. 1
    Every Monday at 08:00, firm time Schedule
  2. 2
    Contracts that renew within 90 days Input
    • Aloe Logistics MSArenews 14 Nov
    • Kestrel Foods supply agreementrenews 30 Nov
    • Northwind SaaS subscriptionrenews 2 Dec
  3. 3
    Apply your notice skill Skill
  4. 4
    Work out each last date Sandbox
  5. 5
    A person checks this Human
    Waiting for you

    Three renewals found. Aloe needs notice by 15 October, 22 days from today. Put all three decisions in the diary?

    Edited: put Aloe and Kestrel Foods in the diary. Leave Northwind for next week.

  6. 6
    Put it in the diary Connector
  7. 7
    Write a report Output
Budget used0%

The run stops at step 5 until you answer.

Write it the way you would brief a junior.

You describe the routine in a sentence or two. Clausel lays it out as numbered steps you can read and change, then runs it against contracts you already hold, so you see what it would have done before it does anything.

Your brief

3 of 20Tested on 20 of your NDAs, the workflow would have stopped 3 for a person and passed 17. None were left undecided.

The steps Clausel proposes

  1. When a contract arrives through the intake APITrigger
  2. Only carry on if it is a non-disclosure agreementLogic
  3. Review against the NDA playbookAI
  4. Only carry on if a high-risk finding is raisedLogic
  5. A person checks thisHuman, commercial team
  6. Tell someoneOutput, the matter's lawyers
Off keeps the steps saved. Nothing runs. Dry-run runs every step and records what it would have done. Nothing is written, sent or changed. Live runs for real. Steps that write still stop and wait for a person to approve them.

  1. Describe

    A sentence in plain language, or start from one of 31 templates.

  2. Read the steps

    Numbered, in words you would use. Change any step before it runs.

  3. Test on your contracts

    See what it would have done across contracts you already hold.

  4. Switch it on

    Off, Dry-run or Live. Move back a step at any time.

Thirty-six building blocks, in seven kinds.

Every workflow is made of the same parts, and each part says in plain words what it does. The blocks with a dashed underline write outside Clausel, so the run waits for approval before they act.

Input 5

What the run works on.

A contractContracts that matchDocumentsDuties that matchAsk at the start

AI 8

The legal work, grounded in your playbooks and skills.

Review against the playbookExtract answersDraft a documentCompareAsk ClauselSummariseWork over documentsAsk an Associate

Logic 2

Decide what happens next.

Only carry on ifFor each

Human 2

A person approves, edits, rejects or answers.

A person checks thisAsk a person

Output 11

What the run leaves behind.

Tell someoneCreate an obligationUpdate a dutySet a fieldBuild a review tableSave the documentRoute for approvalWrite a reportFile a playbook learningPost to the firm's systemSend for signature

Connector 7

Read from, and carefully write to, the tools you use.

Read emailRead from DriveRead the calendarSend an emailPut it in the diaryWrite to DriveCall a system

Code 1

A sealed sandbox with no network, used to build files.

Run code

A dashed underline waits for a person's approval, then runs exactly once.

Five ways a run begins.

Start it yourself, put it on the calendar, or let it wake when something happens in the firm.

Pull the plug halfway. It picks up where it stopped.

Each step keeps its own record. When a run is interrupted, a server restart or a lost connection, it resumes at the step that did not finish. A step that finished never runs again, so nothing is filed twice.

  • A budget on every run, so a runaway loop stops itself
  • Human checkpoints wait in your Inbox, under Waiting for you
  • Approved writes run exactly once, even if the run restarts
Finished. Every step ran once.

Connect the system your firm already runs.

Register any system by its OpenAPI description, whether it's a practice-management tool, a billing platform or an internal service. Its operations become steps a workflow can call.

  • The key is stored encrypted and never shown again
  • Reading calls run freely
  • Anything that writes waits for approval, then runs once
  • Each write carries an idempotency key, so a retry cannot post twice
  • Registered once per firm, used by every workflow
https://pm.yourfirm.example/openapi.json
••••••••••••••••••••
Stored encrypted. Clausel will not show it again.
  • GET/matters/{id}Look up a matterRuns freely
  • GET/clients/{id}/contactsList client contactsRuns freely
  • POST/matters/{id}/notesFile a note on the matterWaits for approval
  • PATCH/matters/{id}Update the matter stageWaits for approval

Name an Associate. Give it skills, connectors and one job.

A short interview turns a workflow into a named Associate with a persona and a one-sentence mandate. It works with the skills and connectors you allow, you can talk to it in the chat, and your guardrails travel into every step where it uses AI.

ClauselWhat should this Associate look after?
YouRenewals. Nothing should roll over without us deciding.
ClauselWhich contracts, and who decides?
YouEvery commercial contract. The matter partner decides.
ClauselAnything they must never do?
YouNever agree a renewal or contact a counterparty.
N

Nora

Renewals Associate, commercial team
Makes sure no commercial contract renews without the matter partner deciding first.
Guardrails: never agrees a renewal, never contacts a counterparty. Applied to every AI step.

Nora's first week in Dry-run, before she goes Live.

Dry-run. Nothing was written or sent.

Thirty-one workflows ready to switch on.

Ten of the 31 are shown here. Each template is a full set of steps you can read, test on your contracts and adjust before it runs Live.

Weekly renewal radar

Mondays

Every contract that renews in the next 90 days, with the notice date and what it takes to get out.

Daily deadline brief

Each morning

Today's and this week's deadlines and obligations, grouped by matter.

Signature chase

Daily

Documents out for signature that have stalled, and who is holding them up.

NDA triage

When one arrives

Reviews each incoming NDA against your playbook and stops the risky ones for a person.

POPIA compliance sweep

Monthly

A South African example: finds contracts that process personal information without the terms POPIA expects.

Playbook drift check

Monthly

Signed contracts that ended up outside your current positions.

Template freshness check

Quarterly

Templates that no longer match the playbook they are meant to follow.

Contracts health report

Monthly

Contracts missing dates, parties or a type, so searches and alerts stay accurate.

Counterparty exposure report

On demand

Everything you have signed with one counterparty, and where the risk sits.

Inbox watcher

Needs Gmail connected

Picks up contracts that arrive by email and files them for review.

Frequently asked questions

No. Steps that write, whether they put a meeting in the diary, save to Drive or call your own system, wait with a draft of what they will do. A person approves it, and only then does it run, once.

It resumes at the step that did not finish. Steps that already finished keep their result and are never repeated, and every run has a budget so it cannot keep going indefinitely.

Test it on contracts you already hold, then leave it in Dry-run for as long as you like. Dry-run records what each step would have done without writing anything.

Your Clausel repository and matters, Gmail, Google Drive and Google Calendar once they are connected, and any system you register by its OpenAPI description.

No. An Associate is a workflow with a name, a persona and a mandate. It follows the steps you approved and the guardrails you set. Test it on contracts you already hold, then leave it in Dry-run to see what it would have done. Where enabled, it can propose one change to its own instructions after a review. The change is tested first, kept only if its score rises, and a person adopts it.

[Give the routine to an Associate.]

Start with the renewal radar. In a demo we show it on a repository, running in Dry-run, where it saves and sends nothing.

Book a demo Next: drafting