OPERATIONSSep 2026 · 8 min read

What an operations audit actually finds

Not a maturity model or a slide deck. Here is the real list of what turns up when you spend three weeks looking at how a business actually runs, and what it is usually worth.

Key takeaways
  • The findings are rarely surprising to the people doing the work. They are almost always surprising to the owner, because nobody had added them up.
  • The five that turn up most often: work done twice, information trapped in one person’s head, customers waiting on an internal handoff, software nobody opens, and a process that only works when one specific person is in the building.
  • The value of an audit is not discovering the problems. It is quantifying them so the business can rank them honestly.
  • A finding without a number attached is an opinion. The number is what makes it possible to decide what to fix first.

Businesses are reasonably sceptical about audits, and they should be. The word carries baggage: a consultant arrives, interviews some people, and produces a document full of maturity models and frameworks that nobody reads twice.

That is not what this is. So here is the concrete version: what actually turns up when you spend two to four weeks looking closely at how a mid-sized business runs.

1. The same work happening twice

This is the single most common finding, and it is almost never visible from the top. Someone in sales enters the customer details. Someone in operations re-enters most of the same details into the delivery system because the two do not talk. Someone in finance types it a third time to raise the invoice.

Each person considers this normal, because it is the job as it was handed to them. Nobody has ever sat in all three seats and noticed. The number is usually somewhere between four and fifteen hours a week across the business, and when you cost that out it tends to be the finding that gets fixed first.

2. Information living in one person’s head

Every business has at least one of these. The person who knows which supplier to call for the unusual request. The one who knows the pricing exception that applies to three legacy accounts. The one whose approval everything routes through because they are the only one who can spot the error.

The finding here is not that the person is bad at their job. It is the opposite: they are so good at it that the business has been able to avoid writing anything down. That is a genuine operational risk, and it is also the single biggest blocker to automating anything in that area, because you cannot automate a rule nobody has articulated.

3. Customers waiting on an internal handoff

When we map the path from a customer’s first contact to the work being delivered, the delay is almost never in the parts anyone measures. It is in the gaps between them. A request sits in someone’s inbox over a weekend. A quote waits two days for a sign-off from someone who did not know it was waiting. A job is ready to schedule but nobody told the scheduler.

These gaps are invisible in every system the business already has, because each individual system shows its own step completing quickly. Only the end-to-end view shows the customer waiting nine days for something that involved six hours of actual work.

4. Software nobody opens

Every business over about twenty people is paying for tools it has stopped using. A CRM that was replaced but never cancelled. Seats for people who left. Two products that overlap because different departments bought them separately. A premium tier nobody needed.

This is the least interesting finding intellectually and often the fastest money. It requires no change management and no build. Someone just has to look at the list, which nobody has done in two years because it is nobody’s job.

5. The process that only works when one person is in

Related to the third finding but distinct, and more serious. There is usually at least one process that quietly depends on a specific individual being physically available. When they take a week off, the work does not stop, it queues, and then everyone spends the following week catching up while pretending that was normal.

Businesses tend to describe this as a staffing issue. It is usually a documentation and systems issue wearing a staffing costume.

What makes it an audit rather than an opinion

Anyone can walk into a business and notice friction. The part that makes it useful is what comes next: putting a defensible number on each finding, and being honest about the difference between what we measured and what we estimated.

For every priority finding we document what is happening and how we established it, what it is costing now, what it will cost if nothing changes, what fixing it is worth, and what we are uncertain about. Losses that are already happening get separated from losses that might happen later. Where the evidence is thin, we say so and name what would need validating.

That last part matters more than it sounds. An audit that presents every finding with equal confidence is not an audit, it is a sales document. Some things we can prove from your own numbers in an afternoon. Others are a reasoned estimate with assumptions attached, and you deserve to know which is which before you spend money on it.

What you get at the end

A written baseline of how the business currently runs, and a prioritised roadmap, usually three improvements. Each one has a target, a measure, a timeframe, and an owner on both sides. Not thirty recommendations. Three, ranked, with numbers.

Three is deliberate. A list of thirty things is a way of avoiding the decision about what matters most, and it reliably produces zero change. Three is a list a business can actually act on.

The audit is a fixed fee agreed before we start, and the full amount credits against implementation if you go ahead within 60 days. If you want to know what we would find in yours, book a 30-minute call or read more about how we work.

Frequently asked questions

Two to four weeks depending on scope. A focused audit on one function area is about two weeks. A standard multi-function audit across one or two locations is three. Three or more locations, or a heavy systems footprint, runs four or more. Most of that time is fieldwork, with the last stretch spent on synthesis and presenting back.

Minimally. It is interviews and observation, typically thirty to sixty minutes per person, plus access to the systems and numbers we need. We work around your schedule. The most disruptive part is usually that people start noticing problems they had stopped seeing, which is generally a good thing.

It often does, and that is useful rather than wasteful. Most businesses know roughly where the friction is. What they do not have is the number next to it, or a ranking against the other five things they also know about. Confirming a suspicion with evidence is what makes it possible to actually act on it.

WorkAbout usDown to collaborate? We’re ready when you are.