Workflow audit for SMEs: measuring work, waiting and rework
A workflow audit measures where work slows down, why it happens and what fixing it would be worth. This guide gives owners and operations leads at SMEs a method for auditing one team or one process and turning the findings into a plan.
Process documentation records how work is supposed to happen. An audit measures how it happens: where requests wait, where information is retyped between systems and where the same question is answered for the tenth time.
For an SME, the result is an inventory of delays, repetition and rework, each with a number attached. Decisions about automation and AI can then rest on measurements.
What a workflow audit measures
The audit follows a workflow: a repeating chain of steps with a trigger, handoffs and a result someone is waiting for. It captures five things for each candidate.
- Volume: how often the workflow runs per week or month.
- Touch time and wait time: the minutes of work on a case, set against the days it spends in queues and inboxes.
- Handoffs: how many people and systems the work passes through, and where it stalls.
- Rework: how often output loops back for corrections or clarification.
- Value at stake: what an hour of delay or a single error in this workflow costs.
Keep touch time and wait time in separate columns. Suppose a quote request arrives on a Monday. It is read on Tuesday and forwarded to purchasing, waits two days for a price, is drafted in twenty minutes on Thursday and is approved the following Monday. The case took a week and about half an hour of work, and the week is what the customer notices. The queue is usually the bigger loss, and it does not show up in a timesheet.
How to run a workflow audit
For one team or one end-to-end process, the five steps below typically take one to three weeks. Interview scheduling sets the pace more than the analysis does.
- Pick a boundary. Choose one team or one end-to-end process, such as quoting, onboarding or invoicing. Write down the trigger that starts a case and the result that ends it.
- Interview the people doing the work. Allow sixty minutes per role. Ask for last week's examples and have people show the steps on screen. Opinions about the process come second.
- Walk one case end to end. Follow one order, ticket or dossier through every system it touches, and note a timestamp at each step: received, opened, passed on, returned, closed.
- Quantify the pattern. Check the walked case against a few others, then extrapolate to volume: hours per month, delay per case, error rate. Record each figure as an estimate with its assumption beside it.
- Rank the findings. Sort by recoverable hours and value at stake.
Give the audit a named lead who knows the business. Tell the team at the start that the subject is the process and that nobody's performance is being assessed. People describe their workarounds more freely once they know that.
Mistakes that weaken an audit
The first mistake is scope. An audit of the whole company produces a list of complaints, while an audit of quoting or invoicing produces figures. Hold the boundary you picked and note anything outside it for a later round.
The second is relying on what people remember. People tend to recall the unusual case, so averages given in an interview can be off. Where a system records timestamps, such as an inbox, a ticket queue or an ERP, use them. If two people give different figures for the same step, the timestamps settle it.
The third is auditing the documented process. Walk a case that happened last week, including the detour through someone's personal spreadsheet.
From findings to a 90-day plan
Group the findings into three categories: fix the process with no new software, configure tools you already own, and build or integrate something new. Schedule the smaller improvements first, so the team gains experience with the changes before a larger build starts.
Give each item an owner, the figure it should move and a date for checking it. One way to lay out the 90 days is process fixes in the first 30, configuration by day 60 and a decision on anything that needs a build by day 90. At each checkpoint, measure the same figures again. The audit baseline is what shows whether a change helped.
Where AI fits in the findings
Consider AI where the audit shows high-volume text and data work: drafting, classifying, summarising, extracting or answering repeated questions from internal knowledge. Unclear ownership and broken approval chains need process changes before any further automation.
For each AI candidate, two questions follow: whether the inputs are usable and whether the saving covers the cost. Our guides to preparing documents and data for an AI workflow and calculating the return on an AI workflow deal with them in turn.
Block Consult's AI readiness and workflow audit combines the measurement described here with those checks. It traces representative cases to set a baseline for volume, effort, waiting and rework, and it ends with a prioritised roadmap and a brief for the first build. The article on choosing a first AI workflow explains how the ranked findings are scored.
Frequently asked questions
- How long does a workflow audit take for an SME?
- Typically one to three weeks for a bounded scope of one team or one end-to-end process. Interview scheduling usually limits the pace more than the analysis does.
- What is the difference between a workflow audit and an AI readiness audit?
- A workflow audit measures where time and money are lost in current operations. An AI readiness audit builds on that evidence and adds data availability, risk and tooling to decide where AI should be used first. Block Consult offers the two as one service.
- Which workflows should we audit first?
- Start with high-volume workflows that have visible waiting time, such as quoting, order intake, invoicing, support triage and recurring reporting.
- Do we need special software to run a workflow audit?
- No. Interviews, one case followed from start to finish and a spreadsheet for the figures are enough. Timestamps from the systems you already use make the figures more reliable.
Related reading
Let's build something durable.
Tell us about your project. We reply within two business days.

