Audit Evidence Collection

Turns control tests and auditor requests into tracked assignments with an owner, a due date, and attached evidence.

macOS — coming soonSee the 3 automations
Legal / AUTOMATE.md

Every Monday at 9:00am, pull the failed control checks and email each owner the specific evidence still missing.

Ready-made: Evidence Gap List

The job, and what good looks like.

What breaks: audit season starts as a spreadsheet of questions and ends as a scramble across shared drives. Evidence that exists is hard to find, and evidence that does not exist is usually discovered two weeks before the deadline. Control owners rarely see the result of a failed test, so the same gap returns the following year under a new name. What the workflow does: it turns each control test and each auditor request into a tracked assignment with a named owner, a due date, and a link to the evidence. Failed checks are listed weekly with the specific evidence still missing rather than a generic reminder. When a request has waited past its date, the owner and the auditor contact are both named in the escalation. Once evidence is attached it is filed against the control, so next year's request starts from the same place. What a person still approves: the control owner signs off that the evidence answers the control, and the audit lead decides what goes to the auditor.

When it is handled

  • Every audit request has an owner and a date
  • Evidence attached to the control, not a folder
  • Failed tests tracked through to a fix
  • Audit questions closed before the deadline

Works with tools like

  • Vanta
  • Drata
  • AuditBoard
  • Diligent

Ready-made automations. Pick the one that fits.

Each one is a plain-language document. Run it as it is, or change the timing, the rules and the tools to match your team.

Audit Request Tracker

When an auditor submits a request, log the owner and the due date, then post the open list in the audit channel every Friday.

When an auditor submits a request

Control Test Reminder

7 days before a scheduled control test, email the control owner the evidence you expect and the date it is due.

7 days before a scheduled control test

Evidence Gap List

Every Monday at 9:00am, pull the failed control checks and email each owner the specific evidence still missing.

Every Monday at 9:00am

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.

Evidence Gap List

Approve before it sends the email?

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.

Related workflows.

Compliance tracking

Holds every regulatory obligation with a named owner, a due date, and a current status, so a requirement that went overdue cannot sit unnoticed.

Write your own

Policy updates

Publishes the revised version from the approved source, retires the copy before it, and records who has read the version that is actually current.

Write your own

Regulatory filings

Assembles each regulator submission from recorded figures with their sources, so the filed pack can be rebuilt and defended without a search.

Write your own

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.

macOS — coming soon