Contract Intake Triage

Routes every contract request to the right lawyer with the type, value, and risk already read off the document.

Legal / AUTOMATE.md

When a contract request lands in the intake queue, sort it by type, value, and risk, then post the routing list to the legal channel.

Ready-made: Intake Triage Routing

The job, and what good looks like.

What breaks: contract requests arrive by email, chat, and a shared drive, and nobody agrees where they belong. A twelve-page master services agreement and a one-page non-disclosure agreement land the same morning, both marked urgent, so the real priorities wait. What the workflow does: it reads each request as it arrives, pulls the document type, contract value, counterparty, and requested start date, then checks the request against written routing rules. Low-value standard paper goes to the standard queue. Anything carrying a non-standard clause, a value above the approval threshold, or a data processing term goes to a named lawyer with the reason for the escalation written next to it. Missing fields come back to the requester as a short list instead of sitting unresolved. What a person still approves: the lawyer decides whether a flagged item is genuinely unusual, and the business owner confirms the counterparty details before anything goes out for signature.

When it is handled

  • Every request assigned within one business day
  • No request left without a named owner
  • Value, term, and counterparty captured at intake
  • Routine paper cleared without lawyer time

Works with tools like

  • Ironclad
  • Icertis
  • Agiloft
  • DocuSign CLM

You stay in charge.
At every step.

It compares and flags. Every legal call stays yours.

  • It never signs or advises

    It quotes deviations against your playbook. Accepting, signing and advising stay with a lawyer.

  • Every flag shows its source

    Each deviation quotes the clause it is about, every step is recorded, and a file change can be put back.

  • Confidential stays contained

    Each automation reaches only the folders you connect for it, and a local model keeps processing on your machine.

Intake Triage Routing

Approve before it posts in Slack?

ReviewApprove

Before you download.

Where does it run?
On your Mac or Windows computer, in the background. It keeps working after you close its window, and only reaches the folders and apps you connect for each automation.
How does it connect to our CRM and other tools?
Through each app's own connection where it offers one, signed in once by you, or by using the app in a browser the way you would. Each automation gets only the connections you give it, and the tools a page names are examples you can swap for your own.
Does it run when my computer is asleep?
It keeps your computer awake while a job runs and just before a scheduled one. While the computer is closed or off, nothing runs; when it wakes, it checks the inbox, calendar and other sources it watches for anything that arrived meanwhile.
How does my team use it?
Each person who runs automations installs the app. Keep a project in a shared folder, such as Google Drive or a network drive, and teammates can open it and follow every run, while one person owns it and runs it.
Do I need anyone technical to set it up?
No. Download the app, add an automation in plain words, and connect only what that job needs. Nothing runs until you switch it on.

Already have tools for this? Here is the difference.

Contract management systems

Storing signed contracts and running approval routes.

Their rules can't read new paper against your playbook or explain a deviation in plain words.

Flowchart automation tools

Moving records between apps.

Clause-level judgment does not fit into branches, and every exception becomes another one to maintain.

AI chat assistants

Summarizing a contract when you paste it in.

Nothing happens until someone asks, and the playbook lives in a chat instead of a document you control.

AUTOMATE.md

Your routine, written in plain words. It runs on its own, follows your rules, handles the exceptions a flowchart can't, and asks you when it matters. The file stays yours, whichever AI model runs it.

Start with one job.
Make it your own.

macOS — coming soon
  1. 1

    Get the app

    It runs on your computer, next to your files.

  2. 2

    Add the automation

    Paste the instructions into the app, or save them as a file next to your work.

  3. 3

    Try it, then turn it on

    Run it once and check the result. It only runs on its own once you switch it on.