Getting started · Sep 2026
What a Process Audit Covers, and How to Prepare for One
A process audit looks at one workflow in detail before anything is built. Here is what it covers, what to bring and what you should have at the end of it.
Automation projects go wrong when they start from a tool rather than from the work. A process audit starts from the work: one workflow, looked at closely, before anything is built.
What It Looks At
- What starts the work: a call, an email, a form, a payment, a time of day
- Who does each step today, and how long it takes
- Which systems the information passes through
- Where it goes wrong, waits, or gets done twice
- Which steps must always stay with a person
What to Bring
- The person who actually does the work, not only the person who manages it
- A few real examples: sample emails, forms, statements or call notes
- A rough idea of how often the work happens
- Anything that has already been tried
What Comes Next
If automation makes sense, the next step is a plain-language summary of the requirements for you to sign off before any build starts. If it does not make sense yet, that is a useful answer too.
We start with a free, no-obligation process audit of one workflow.