Business process audit checklist: 40 questions to ask before you change anything

A process audit is not about catching people out. It is a structured way of finding out whether a process does what everyone assumes it does. Done before an improvement or automation project, it saves you from fixing the wrong thing.

Use these questions with the person who owns the process and at least two people who do the work. Answers that start with "I think" are worth writing down, because they mark where nobody has checked. Score each question: yes, partly or no. Anything below yes is a finding.

1. Purpose and ownership

• Can the owner state in one sentence what the process is for and who receives its output?
• Is there one named owner, and do the people doing the work know who it is?
• Is the start point and end point written down and agreed?
• Does anyone own the end-to-end result, or only their own section?
• Has the purpose changed since the process was designed?

2. Triggers and inputs

• What starts a case: a form, an email, a phone call, a calendar date?
• Do cases arrive through more than one channel? Is each tracked?
• Is anything required to start a case frequently missing on arrival?
• Can a case be started without the information needed to finish it?
• Is there a place where a case can be received and never noticed?

3. Steps and handoffs

• Does the current process match the documented one? When was that last checked?
• How many times does a case change hands between people or teams?
• For each handoff, is there a time limit and a named recipient?
• Are there steps that only pass a case along without adding anything?
• Are there approvals that are almost never refused? What do they cost in waiting?

4. Data and systems

• Is the same data entered in more than one place?
• Which spreadsheets sit outside the main system, and who maintains them?
• Where is the single source of truth for a case's status?
• Do systems exchange data automatically, or by export and import?
• Can someone outside the team find out where a case stands without asking?

5. Exceptions and rework

• What share of cases come back for correction?
• What are the three most common reasons?
• Is there a defined route for exceptions, or does each person improvise?
• Who decides when a case is an exception?
• Is the cost of an exception tracked anywhere?

6. Controls and risk

• Which steps carry financial, legal or safety risk?
• Is anyone able to both create and approve the same item?
• Are approval limits written down and applied consistently?
• Is there an audit trail showing who did what and when?
• Does the process rely on one person's knowledge or access?

7. Performance

• Is cycle time measured, from trigger to finish, including waiting?
• Is volume known by week and by season?
• Is the rework rate known?
• Does anyone look at these numbers regularly, and does anything happen as a result?
• Do customers or internal recipients complain, and about what?

8. Documentation and people

• Is there a written procedure, and does it include the exceptions?
• Could a new starter follow it without help? Has anyone tried? See SOP optimization for how to test this.
• Is there a review date, and has it been kept?
• Do people have the training and permissions they need?
• Do staff know who to ask when something unusual comes up?

Reading your results

Count the "no" and "partly" answers per section. A few findings in each section is normal. A cluster in one section tells you where to look:

• Mostly sections 1 and 2: the process has no clear edges. Fix scope and ownership before anything else.
• Mostly sections 3 and 4: handoffs and double entry. This is where automation pays back, after the simplification.
• Mostly sections 5 and 6: rework and risk. Look at rules and checks at the start of the process, not the end.
• Mostly sections 7 and 8: you cannot see the process. Start with measurement. The improvement framework shows how.

Keep the answers. When you repeat the audit in six months, the comparison is more useful than the first result. And if you want an outside view, a process consulting engagement starts with exactly this kind of walk-through.

Related reading and services