Insights
What does an operations audit include?
Short answer: an operations audit examines how work and decisions actually move through a business. It finds where they get stuck, what depends on undocumented knowledge, and how much is waiting on the founder. Then it gives you a prioritised list of what to fix first. It is a diagnosis, not a financial audit or a compliance check.
What a useful audit examines
1. Decisions and ownership
Which decisions come to the founder, which could be made by someone else, and where ownership is unclear. A common finding is an outcome, such as customer complaints or supplier payments, that several people touch but nobody owns.
2. Bottlenecks
Where requests, approvals and work queue up, and why. A queue might come from one overloaded person, a missing decision rule, or a step that only exists because “we’ve always done it that way”.
3. Documentation
Which repeating processes are written down, which live in someone’s head, and which of those gaps carry real risk. If the one person who knows how payroll works is off sick, what happens?
4. Information flow
How progress, numbers and problems reach the founder: whether there is regular reporting, or whether the founder only finds out when something has already gone wrong.
5. Founder time
What the founder actually spends their week on, compared with the work only they can do. This is often the most revealing part.
How the information is gathered
- Conversations with the founder about priorities, frustrations and where they feel stuck.
- Conversations with the team. The clearest view of where work stalls usually comes from the people doing it.
- Looking at how work really happens: existing documents, the tools and WhatsApp groups the team relies on, how requests are made and tracked.
- Following a few real examples from start to finish, such as a customer order, a purchase approval or a new hire, to see where they slow down.
What you should receive
At minimum, a prioritised fix list: what was found, why it matters and the order to tackle it in. A good audit makes the priorities specific enough to act on. “Improve communication” is not a finding. A specific finding sounds more like this hypothetical example: “Purchase approvals above a set amount routinely wait days for the founder. Delegate them to the operations lead, with a clear spending limit.”
What an audit is not
- Not a financial audit. It doesn’t verify your accounts.
- Not a performance review of your staff. The focus is on how the system works, not on judging individuals.
- Not the fix itself. It tells you what to change. Making the change is the next step, whether your team does it or you bring in help.
How to prepare
- List the decisions and questions that come to you most often in a typical week.
- Note the two or three initiatives that stalled most recently, and what you think got in the way.
- Gather whatever exists: an org chart, job descriptions, any written processes, the reports you get.
- Tell your team what the audit is for, so they speak openly.
What happens next
Findings about ownership, decision rights and missing processes usually lead to building that structure: see Business Systems & SOPs. Findings about plans that don’t get executed usually point to execution support: see Fractional Chief of Staff. Some fixes your team can make on its own.
Start with an Operations Audit
Our Operations Audit looks at exactly these areas and gives you a prioritised fix list.