How often should I audit my business systems?

Run the full 7-part audit once a quarter, every 90 days. That's the cadence that matches how fast small-to-mid-size businesses change. If you go longer than that between audits, the gap between your documented systems and what's actually happening will widen too far. Less is fine for one-off deep-dives, more just creates audit fatigue.

What's the fastest way to grade business systems?

Pick three customers and three team members, and ask each of them one question: 'If you had to grade the consistency of how we do things from 1 to 10, what would you give us?' Average the six answers. That's a rough grade in 30 minutes. For a deeper read, use the 7-part self-audit or start with the Owner Dependency Score.

Should the business owner run the audit or the team?

Both, separately, and then compare. Owners consistently over-score. Team members tend to be closer to reality because they work with the systems every day. The gap between your score and theirs is a second data point on its own. If you score yourself at 50 and your team scores you at 30, that 20-point gap is the problem to solve first.

What score means my systems are working?

55 or higher out of 70 means your business is running on systems, not on you. Below 40 means you have procedures but not real systems. Between 40 and 55 means you're mid-systemisation, with documentation mostly in place but ownership and measurement still patchy. The score matters less than the trajectory. A business moving from 30 to 45 in 90 days is in a better position than a business sitting at 55 that hasn't moved in a year.

How to Grade Your Business Systems (Honest Self-Audit)

Imagine your customers fill out a report card on your business systems.

Not your product. Not your people. Your systems. The way orders get processed. The way queries get answered. The way invoices get sent. What grade would they write at the top? An A? A C? A D?

Now imagine your team filling out the same card. The people who actually follow (or work around) your systems every day. What would they write?

Now the hardest one. You fill it out. Honestly. No grading on a curve. What do you put?

Most owners never ask these questions. And that's exactly why it's worth asking. Because the gap between the grade you'd give yourself and the grade your team and customers would give you is usually where your freedom (and profit) is leaking out.

Why most owners never grade their systems

Self-audit feels like self-criticism.

You built this thing. You're proud of it. You don't want to sit down with a pen and go looking for everything that's broken. So you don't. You keep moving. You keep firefighting. You keep telling yourself the systems are "good enough for now."

Here's the thing. An honest grade isn't a judgment on you. It's a starting line. You can't improve what you haven't measured. And you can't measure it until you're willing to look at it clearly.

Grading your systems is the cheapest, fastest piece of business improvement work you'll ever do. No consultant. No software. Just you, a pen, and 20 minutes.

Let's make a start.

The 7-part self-audit

Score each question from 1 (bad) to 10 (great). Total out of 70.

Be ruthless. If you're unsure, go lower. If your gut says "yeah, kinda," that's a 4, not a 7.

The 7-Part Business Systems Self-Audit

Score each from 1 (bad) to 10 (great). Total out of 70.

Documentation. If a key team member vanished tomorrow, could a new hire pick up their work from the docs?
Consistency. Do customers get the same experience every time?
Ownership. Does every system have a name next to it (and is that name not yours)?
Measurement. Can you show the metric each system is hitting or missing?
Maintenance. When was each system last reviewed and updated?
Adoption. Is your team actually following the system, or just nodding?
Customer outcome. Does the system produce what customers actually value?

Total your score. Under 40 = procedures, not systems. 40 to 55 = mid-systemisation. 55+ = systemised. Re-grade every 90 days.

1. Documentation

If a key team member vanished tomorrow, could a new hire pick up their work from what you have documented?

A 10 means the next person in the seat reads the documents and does the job. A 1 means the knowledge is in someone's head and walks out the door with them.

2. Consistency

Do your customers get the same experience every time?

Ring your own business from three different phones. Send three enquiries through three different channels. Would all six touchpoints feel like the same company? If the answer depends on who happens to pick up, you're not scoring a 10.

3. Ownership

Does every system have a name next to it, and is that name not yours?

A system without an owner is a wish. The owner is the person responsible for making sure the system gets followed, reviewed, and updated. If your name is on more than a handful, your business is still running on you.

4. Measurement

Can you show me the metric each system is hitting (or missing)?

Documentation tells the team what to do. Measurement tells you whether it's actually working. If you've got a sales system but can't tell me the conversion rate, you don't really have a system. You have a hope.

5. Maintenance

When was each system last reviewed and updated?

Systems rot. Tools change. People change. Customer expectations change. If your last review was more than 90 days ago, the system is already drifting. If there's never been a review, you've got a monument, not a living document.

6. Adoption

Is your team actually following the system, or just nodding when you ask?

The easiest way to check: pick a system and ask three team members to walk you through the current version. If they tell you three different stories, the documented system is fiction. Real adoption shows up in behaviour, not in head nods during team meetings.

7. Customer outcome

Does the system produce what the customer actually values?

This is the one owners skip. A beautiful, well-documented system that produces a mediocre customer experience is still a bad system. Ask: does the output of this system make my customer's life easier, faster, or better? If not, you're systemising the wrong thing.

How to interpret your score

Add up all seven. Out of 70.

Under 40/70: you have procedures, not systems. Don't try to fix everything. Start by mapping your Critical Client Flow and picking one system within it to document properly.
40 to 55/70: you're mid-systemisation. You've done the documentation work. Now shift focus to ownership and measurement. The gap between "written down" and "actually running" is usually where you are.
55+/70: you're systemised. Well done. Your next move is continuous improvement. Build a rhythm of 90-day reviews so the systems keep pace with the business.

Most owners I work with come in somewhere between 25 and 45. That's not failure. That's the starting point. The grade you earn today is less important than whether you'll have a higher one in 90 days.

What an honest grade looks like: Shannon Smit

Shannon Smit runs SMART Business Solutions in Melbourne. An accounting firm with a niche global speciality in transfer pricing. From the outside she looked like a success story. Award-winning. Fast-growing. Serious clients.

On the inside, she was burning out. Working 70-hour weeks. Every complex case came back to her. The firm's systems had been built around her expertise, which meant the firm couldn't really run without her.

When Shannon graded her systems honestly, she saw it. The documentation score was low because the sophisticated, specialist work had never been written down. The ownership score was low because her name was on too many systems. The adoption score was mid because the team followed systems they knew about, but there were big gaps around the specialist work.

She didn't try to fix everything at once.

She mapped the Critical Client Flow. She identified a Systems Champion inside her team to drive the documentation. She focused on the 10 to 20 percent of systems that delivered 80 percent of the value. Then she set up measurement so she could see which systems were hitting and which were missing.

The outcome?

998 hours of repetitive work eliminated across the firm every year. Shannon moved from technician to advisor. She took her first long holiday in years. The team kept running the business. The tangible value of the firm went up because the intellectual property was finally documented, not trapped in her head.

Shannon Smit on how she systemised SMART Business Solutions and saved 998 hours per year.

That's the before-grade-to-after-grade arc in one story.

Where owners typically fail the grade

After running this audit with hundreds of business owners, the pattern is brutally consistent.

Documentation is usually the highest score. Most owners have made at least some SOPs. Maybe they sat down one Saturday and wrote things out. Maybe they bought a template pack. Maybe they asked a team member to write it up. Either way, something exists.

Measurement and adoption are usually the lowest. Owners build systems but never track them. They assume that because the document exists, the work is being done. It usually isn't. Or it's being done, but nobody's measuring whether it's producing the result.

The gap between "we have documents" and "we have systems that run the business" is where most businesses live. That gap is your real score.

If you want to improve one thing, improve the measurement layer. As soon as a system has a metric attached to it, adoption goes up on its own. People follow what they know is being tracked. It's not a trust issue. It's a visibility issue.

How to go from D to A

Don't try to fix everything.

Pick the lowest-scoring area on your Critical Client Flow. Just one. Improve it over the next 30 days. Get documentation tight, assign an owner, attach a metric, and check adoption weekly.

Then do the next one. Then the next.

Re-grade every 90 days. Same seven questions. Same 1 to 10 scale. Watch the number creep up. This is the boring, compounding work that separates businesses that genuinely systemise from businesses that talk about systemising.

If you want to go deeper on the building blocks, I've written more on the characteristics of good business systems, another on what is a business system, and a guide to improve your business systems once the foundations are set.

A faster starting point

The 7-part audit above is deep. It's the work.

If you're not ready for deep yet, start with something faster. The Owner Dependency Score is a two-minute read on how reliant your business is on you personally. It's a great first grade, and it tells you where the biggest leaks are hiding.

What grade would your business get?

Get a fast read in two minutes with the Owner Dependency Score.

The bottom line

You already have systems. The question is what grade they deserve.

Run the 7-part audit. Score it honestly. Look at the gap between documentation and adoption. Pick the lowest score on your Critical Client Flow and improve it first.

Then do it again in 90 days.

Simple beats perfect. Always.

If you want to go further, high-performance business systems share a set of traits you can target once the basic audit is solid. And if you're the owner running the audit yourself, consider handing the implementation to someone else on your team. The detail work suits a Systems Champion far more than it suits you.

systemHUB platform — build, measure, and improve your business systems — systemHUB: one place to build, store, measure, and improve every system in your business.

Ready to move faster? systemHUB gives you a single place to build, store, and measure every system in your business. It comes loaded with 100+ templates and built-in tracking so your adoption score stops being a guess. Try it free.