Document redaction
Builds the redacted copy and the redaction log as one versioned pair, so the record of what was withheld and why travels with the document.
No ready-made setup for this job yet.
Describe the job in a sentence, the way you would brief a colleague: when it should happen, what to check, and what to hand you. That sentence is the automation.
The job, and what good looks like.
What breaks: redactions get made in whatever tool was open that day and the log is a text file somebody keeps locally, so the record of why a page was withheld is often the thing that goes missing. A paralegal spends days re-deriving the basis for a page that was already cleared, and a reviewer who questions one redaction has nothing to point at. What the workflow does: it takes the set approved for production, applies the redaction grounds the matter owner already agreed, and writes one line per redaction recording the page, the ground, who approved it, and when. The redacted copy and the log are versioned together, so the document that went out and the log describing it cannot drift apart. A redaction applied outside the workflow is flagged as unlogged, and a ground that is not on the agreed list goes back to the reviewer rather than being applied quietly. The production package is assembled from the log rather than assembled first and described afterwards. What a person still approves: a lawyer applies or removes each redaction, and the matter owner approves the production set before it is sent.
When it is handled
- One log line per redaction
- Redacted copy and log versioned together
- Unlogged redactions surfaced before production
- Production package built from the log
Works with tools like
- Relativity
- Everlaw
- iManage
- Microsoft Purview
- Exterro
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.
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
Get the app
It runs on your computer, next to your files.
- 2
Add the automation
Paste the instructions into the app, or save them as a file next to your work.
- 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.