The Operations Audit: What to Measure If You Want to Know What's Actually Broken
You know something's not working.
Your team's frustrated. Reports take forever. Data doesn't match. Decisions get delayed.
But you don't know what's actually broken.
Is it the tools? The process? The people? All three?
Without the right metrics, you're guessing.
And guessing at what to fix is how you waste time and money on solutions that don't solve anything.
Here are the 10 metrics you need to measure in your business.
Why Metrics Matter
Most businesses measure revenue, profit, customer satisfaction.
Those are important. But they're lagging indicators. They tell you what happened, not why.
Operational metrics are different. They're leading indicators. They tell you where things are breaking before it costs you real money.
If you know your reporting takes 5 days instead of 1, you can fix that before it causes a missed deadline or a wrong decision.
If you know your data accuracy is 87% instead of 98%, you can address it before it ruins a quote or a costing analysis.
The right metrics let you diagnose the actual problem. Then you can fix it.
The 10 Metrics That Matter
Metric 1: Month-End Reporting Time
What to measure: How many hours does it take to pull together your standard monthly reports?
Why it matters: Reporting time is a proxy for system efficiency. If it takes 40 hours to pull five standard reports, your data's fragmented, your processes aren't documented, or your tools are broken.
How to measure it: Track actual time spent on month-end reporting for the last three months. Average it.
What's healthy:
Simple business (20 people, straightforward operations): 16–24 hours
Mid-sized manufacturing (35–50 people): 30–50 hours
Larger or more complex: 60–100 hours
If you're above this: Your data's likely fragmented across multiple sources, your reports are manual, or there's no documentation. You're losing 1–2 days a month to friction that shouldn't exist.
Remember, that 5 people spending 1 hour on something isn’t 1 hour of time, it’s 5…
Metric 2: Data Accuracy Rate
What to measure: What percentage of your operational data is accurate, complete, and consistent?
This is harder to measure than you think. You need to define what "accurate" means for your business. For production data, it might be: does the entry match the actual production record? For costing, does it match the timesheet data?
Why it matters: If you can't trust your numbers, you can't make good decisions. Wrong data cascades. A 5% error rate in labour data turns into wrong costing, wrong pricing, wrong margins.
How to measure it: Pick your three most critical data streams (production, labour, material). Audit a sample (50–100 entries). Check accuracy against source documents or systems. Calculate the error rate.
What's healthy:
Below 95%: Your data's broken. Fix this first.
95–98%: Acceptable, but you're leaving money on the table. Errors still happen.
98%+: Good. Occasional errors, but not systemic.
If you're below 95%: Someone's not owning data quality. There's no process. Entries are made by different people with no standard. This is your biggest problem.
Metric 3: Ad-Hoc Data Request Turnaround
What to measure: When someone asks a data question—"What's our margin on Project X?" "How many hours did we spend on Department Y last month?"—how long does it take to answer?
Why it matters: Ad-hoc request speed reveals how well your data's organised. If it takes 3 hours to answer a simple question, your data's scattered. If it takes 15 minutes, you've got decent structure.
How to measure it: Next time someone asks a data question, time how long it takes to answer it accurately. Do this for 5–10 requests. Average it.
What's healthy:
Under 15 minutes: Your data's well-organised. Someone can find and pull what they need quickly.
15–60 minutes: Acceptable, but you're spending time digging. Data could be more accessible.
Over 60 minutes: Your data's scattered. Different people store things different places. Nobody knows where to look.
If you're over 60 minutes: This is a process problem. Data lives in three spreadsheets and nobody knows which is the source of truth.
Metric 4: Process Documentation Score
What to measure: What percentage of your critical processes are documented?
Critical processes: month-end reporting, data entry, reconciliation, costing, invoicing, anything that matters to your business.
Why it matters: Undocumented processes live in people's heads. When Sarah leaves, the process leaves with her. When someone new arrives, they have to reverse-engineer how things work. That's wasted time and higher error risk.
How to measure it: List your top 15 critical processes. For each one, ask: is there written documentation that someone new could follow? Yes or no. Calculate the percentage.
What's healthy:
Below 50%: Most of your business is undocumented. This is a serious risk.
50–75%: You've documented some key processes, but gaps remain.
75–90%: Good. Most processes are documented, though some are still tribal knowledge.
90%+: Excellent. Your processes are captured. New people can learn quickly.
If you're below 50%: Your business is fragile. If key people leave, you're in trouble. This is your second priority after data accuracy.
Metric 5: System Integration Points
What to measure: How many times do you manually move data between systems?
For example:
Data from timesheet system copied into costing spreadsheet
Production numbers from one system typed into another
Customer data from CRM manually entered into invoicing system
Why it matters: Every manual data transfer is an error opportunity. It also wastes time. If you're moving the same data between three systems, you're doing work that should be automatic.
How to measure it: Map out your data flow. Every time data is manually touched to move between systems, that's one integration point. Count them.
What's healthy:
0–2 manual integration points: Minimal. Your systems mostly talk to each other.
2–5: Moderate. Some friction, but manageable.
5–10: High friction. You're spending significant time moving data around.
10+: Critical. This is a major inefficiency.
If you're above 5: You need to either integrate your systems or change your processes to minimise manual data movement.
Metric 6: Error Discovery Lag
What to measure: When an error occurs in your operational data, how long before someone notices?
For example: a data entry mistake on Monday. When do you catch it? Thursday? Next week? Never?
Why it matters: Fast error discovery limits damage. If you catch a costing error the day it happens, you can fix one quote. If you catch it three weeks later, you've already invoiced based on wrong costing.
How to measure it: Next time you find an error, track back to when it actually occurred. Calculate the lag. Do this for 10 errors. Average the lag.
What's healthy:
Same day or next day: Good. Errors are caught quickly.
2–3 days: Acceptable, but some damage is done.
Over 1 week: Poor. Errors cascade before being caught.
If you're over 1 week: You don't have systematic error-checking. Someone's not reviewing data regularly. You're flying blind.
Metric 7: Report Accuracy Confidence
What to measure: When you present a report to leadership, how confident are you that the numbers are right?
This is subjective, but it matters. Rate it 1–10. 10 = absolutely certain. 1 = guessing.
Why it matters: Low confidence in your reports means you don't trust your data. That leads to bad decisions because decision-makers either ignore the data or second-guess it.
How to measure it: Ask your finance person, your operations manager, your director: on a scale of 1–10, how confident are you in our monthly reports? Average their scores.
What's healthy:
8–10: High confidence. People trust the reports.
6–8: Moderate confidence. People use the reports but with some scepticism.
Below 6: Low confidence. People question the data. Decisions get made on gut feel instead.
If you're below 6: Your data's not trustworthy. This is urgent.
Metric 8: Percentage of Time on Data Maintenance vs. Strategy
What to measure: How much time does your operations/finance team spend fixing data problems versus doing actual analysis and strategy?
Why it matters: If your team spends 70% of their time maintaining data, they're only spending 30% on strategy and improvement. That's your constraint.
How to measure it: Ask your operations and finance people to track their time for a week. Categorise: data maintenance (entering, fixing, reconciling, moving between systems) versus strategy (analysis, improvement, planning).
What's healthy:
20–30% on maintenance, 70–80% on strategy: Healthy balance.
40–50% on maintenance, 50–60% on strategy: Acceptable, but tilted toward maintenance.
60%+ on maintenance: Unacceptable. You're not getting strategic value from your team.
If you're above 50% on maintenance: This is your biggest opportunity. Get your team out of data maintenance and into strategy.
Metric 9: System Change Latency
What to measure: When your business process changes, how long before your systems reflect that change?
For example: you change how you calculate labour costs. How long before that change is in your costing spreadsheet?
Why it matters: If changes are slow to implement, your systems fall behind reality. You're making decisions based on old rules.
How to measure it: Next time you make a process change, time how long it takes to update your systems. Do this for 3–5 changes. Average the time.
What's healthy:
Same day or next day: Good. Your systems stay current.
1–2 weeks: Acceptable, but you're potentially making decisions on outdated rules.
Over 1 month: Poor. Your systems are drifting away from reality.
If you're over 1 month: Your systems aren't flexible. They're built in a way that makes changes hard. This is a design problem.
Metric 10: New Person Onboarding Time
What to measure: How long does it take a new finance or operations person to be fully productive?
Why it matters: Long onboarding time means processes aren't documented well, knowledge is scattered, and the team has to spend time teaching instead of working. Short onboarding time means your processes are clear and documented.
How to measure it: Look at your last three hires in finance/operations. How long until they could handle month-end reporting independently? How long until they could answer a data question without help? Average it.
What's healthy:
2–4 weeks: Good. Clear processes, good documentation.
4–8 weeks: Acceptable, but there's room to improve.
8+ weeks: Poor. New people are a burden on the team for months.
If you're over 8 weeks: Your processes aren't documented. Knowledge is in people's heads. This is a scaling problem.
Putting It Together: Your Operational Health Score
You've got 10 metrics. Now what?
Rate yourself on each one:
Red (broken, needs urgent fixing): 0 points
Yellow (acceptable but improvable): 5 points
Green (healthy): 10 points
Add them up. You've got a score out of 100.
90–100: Your operations are solid. You can maintain and optimise.
70–89: You've got gaps. Pick the highest-impact ones and fix them.
50–69: Multiple problems. You need a systematic approach to improvement.
Below 50: Your operations are struggling. You need external help to get back on track.
Where to Start
You don't fix everything at once.
Look at your scores.
If data accuracy is below 95%: That's your first priority. You can't make good decisions on bad data. Fix this before anything else.
If reporting time is over 50 hours: That's your second priority. Someone's drowning. That time could be freed up.
If documentation is below 50%: That's your third priority. You're at risk of losing critical knowledge.
If system integration points are above 5: That's your fourth priority. Manual data movement is stealing time.
Fix those four things and you've solved 80% of your operational problems.
How This Changes Your Business
Once you've diagnosed your actual problems using these metrics, you can fix them.
Better data accuracy means better decisions.
Faster reporting means faster action.
Better documentation means less dependence on individuals.
Fewer manual integration points means more time for strategy.
Your team stops drowning. They start contributing.
Your decisions get better because they're based on data you trust.
And you spot problems before they become crises.
That's the shift.
Your Next Step
You know what to measure now.
Spend a week gathering these 10 metrics for your business.
You don't need perfect data. Just honest assessment.
Once you've got your scores, you know where you stand.
Then you can pick your path: DIY, software, or get help.
If you want someone to walk through this audit with you—to help you measure these metrics accurately and design a plan to improve—we're here for that conversation.
We'll audit your operations, show you where the real problems are, and talk through your options for fixing them.
No pressure. Just clarity.
Office Mango helps manufacturing and distribution businesses understand what's actually broken in their operations. We use metrics like these to diagnose problems, then we design solutions that fit your situation—whether that's a one-off Reporting Automation project, a Bespoke Solution for bigger challenges, or a Retainer arrangement for ongoing partnership and continuous improvement.
