Redline Negotiation Tracker

Keeps the current version, the open clauses, and who owes the next turn visible on every live negotiation.

Legal / AUTOMATE.md

When a redline comes back, list the clauses still open, the last change to each, and who owes the next turn.

Ready-made: Redline Version Tracker

The job, and what good looks like.

What breaks: once a contract is in negotiation, the working version lives in one inbox and the most recent marked-up copy is usually not the one being forwarded. Deal teams assume a redline is closed because the thread went quiet, while legal is still holding three open positions. When the deal closes, nobody can say which clause was actually agreed or why the company accepted it. What the workflow does: it keeps one current version per negotiation, records every round as it arrives, and lists the clauses that are still open with the last change to each and who owes the next turn. Positions that moved since our last redline are shown side by side, so a reviewer sees what the counterparty gained without re-reading the whole document. A round open longer than the agreed turnaround is chased, and the agreed position is written to the precedent file. What a person still approves: a lawyer accepts or rejects each counterparty position, and the deal owner confirms the final version before signature.

When it is handled

  • One current version per negotiation
  • Open clauses listed with an owner
  • Stale redlines chased on their own
  • Agreed positions saved as precedent

Works with tools like

  • Icertis
  • Ironclad
  • Agiloft
  • DocuSign

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.

Redline Version Tracker

Approve before it runs for the first time?

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.