Business Process Audit: What Happens

What is a business process audit, and what is it not?

A business process audit is an outside review of how work moves through your business in reality, as opposed to how the org chart or the procedures manual says it moves. Those two things are almost never the same, and the gap between them is where the audit earns its keep.

It is worth being clear about what it is not. It is not a financial audit. Nobody is checking your books for compliance. It is not a performance review of your staff, and it goes badly if staff believe it is. And it is not a sales demo dressed up as analysis, where the findings mysteriously all point at one software product. A proper audit is allowed to conclude that some processes are fine as they are.

The core method is simple: observe, map, measure, prioritise. The auditor watches real work happening, draws each core process as it actually runs, measures where the time and errors sit, and hands back a ranked list of what to fix first and what to leave alone.

The reason SMEs get so much out of this is that nobody inside the business can see it. The owner sees the version of the business that reaches them. Staff see their own patch and the workarounds they have normalised over years. Someone from outside, watching with fresh eyes for a few days, sees the whole flow, including the parts everyone has stopped noticing. In most audits the biggest finding is something no one mentioned in the kickoff meeting, because inside the business it had stopped looking like a problem. It just looked like how things are done.

What happens in the first week: shadowing real work

The first week is mostly watching, and it is the part clients find strangest until they see the results. The auditor sits with the people who do the work, in person or on screen, and follows real jobs end to end: an enquiry becoming a quote, a quote becoming a job, a job becoming an invoice, an invoice becoming money in the bank.

This is deliberate. If you ask people to describe their process, you get the tidy version, the process as they believe it works, or as they think you want to hear it. If you watch them for half a day, you see the real one. The specific things we watch for:

• Re-keying: the same information typed into more than one system by hand. Every instance is time, and every instance is a chance for the two copies to disagree.
• Workarounds: the spreadsheet on someone's desktop that patches a gap in the official system. Workarounds are gold in an audit, because each one marks exactly where a system fails its users.
• Waiting: work sitting in a queue for an approval, a decision, or a piece of information that lives in one person's head.
• Interruptions to the owner: every time someone has to walk over, call, or message the owner to get a decision or a fact. Each one is a small marker of owner dependence, and they add up to the discount a buyer would apply to the business, which we cover in the owner-dependence discount.
• Tribal knowledge: steps that only work because a specific person knows the trick, the contact, or the password.

One note for owners: brief your team honestly before this starts. The audit is about the process, not the people, and the staff who show the auditor their workarounds are doing the business a favour. Teams that hide the mess produce a polite audit and a useless one.

How does the process mapping work?

Process mapping turns a week of observation into pictures a business owner can argue with. Each core process gets drawn as a simple flow: the steps, who does each one, which system it touches, where it waits, and where it forks into exceptions. No specialist notation, no consulting theatre. If a diagram needs training to read, it has failed.

Two maps get drawn for the processes that matter most. The first is the process as people describe it. The second is the process as it was actually observed. Putting them side by side is reliably the most valuable moment of the audit, because the differences are the findings. The quote that is supposed to go out same-day but waits three days for the owner to check pricing. The five-step order process that has quietly grown to eleven steps, four of which exist to patch an old software limitation nobody remembers.

Alongside the maps, each process gets some basic numbers attached: how often it runs, roughly how long it takes, how many hands touch it, and where the errors come from. Precision is not the goal at this stage. Knowing that order entry consumes about 12 staff hours a week and produces the majority of your invoice disputes is enough to rank it against everything else.

The mapping also surfaces the data question that sits under everything: how many places does the same information live, and which copy is the real one? Most SMEs discover the same customer or job exists in three or four systems that quietly disagree. That finding usually points to the fix we describe in the single source of truth guide, and it explains why data work so often comes before automation in the recommendations.

What is the scorecard, and what do the findings look like?

The scorecard condenses everything observed into a handful of scored dimensions, so you can see at a glance where the business is solid and where it leaks. Ours scores areas like data quality and connectedness, process consistency, automation readiness, owner and key-person dependence, and reporting reliability. Each score comes with the evidence behind it, not just a number on a dashboard.

The findings themselves follow a fixed discipline. Every finding states three things:

1. What we observed, specifically. Not "invoicing is inefficient" but "invoices are drafted in Xero, copied into a Word template for formatting, then PDF'd and sent manually, adding around 15 minutes per invoice and causing the numbering mismatches your bookkeeper reconciles monthly".
2. What it costs, in hours, errors, or risk, using the numbers gathered during mapping.
3. What fixing it would involve, honestly, including when the answer is a process change or a policy decision rather than anything you would buy.

Findings then get ranked into a short prioritised list. Some are quick wins: a setting, a template, a rule change that costs nothing and pays back immediately. Some are structural: data cleanup, a system connection, an automation build. A good audit is explicit about which is which, and about what to leave alone. There are always processes that look untidy but work fine, and recommending work on them wastes your money and the auditor's credibility.

What you should never see in the findings: vague scores with no evidence, recommendations that all happen to require the auditor's favourite software, or a fix list with no costs attached. If every problem's answer is a purchase, you got a pitch, not an audit.

What do you get at the end, and what does it cost?

At the end of Emendo's Business Readiness Audit you get three things in writing: the scorecard with evidence behind each score, the process maps for your core workflows, and a prioritised roadmap that says what to fix first, what it will roughly cost, and what to leave alone. We walk you through it in a working session where you can push back on anything, because findings you do not believe are findings that will not get acted on.

The audit is fixed-price at $1,990 inc GST, runs over about two weeks, and the full fee is credited toward any engagement started within 90 days. That structure is deliberate. Fixed price means the scope cannot creep. The credit means that if the audit leads to work, it effectively cost you nothing, and if it does not, you still own a written map of your business that is useful for planning, for training, and eventually for a buyer's due diligence.

What it asks of you: a kickoff conversation, access for the shadowing days, and honesty. Do not tidy up before we arrive. The audit is worth the most when it sees the business as it actually runs on a normal week, mess included. The businesses that get the least value are the ones that stage-manage the visit.

What happens next is up to you. Some owners take the roadmap and action the quick wins themselves. Others go on to a Data Readiness Sprint from $6,000 plus GST, or an automation build, typically $8,000 to $25,000 plus GST, in the order the roadmap sets out. Either way, you make the decision with a written, evidenced picture of your own business in front of you, which is a better position than most owners have ever been in.

FAQ

Questions owners ask