In Short
The real cost of a manual operational exception is the combination of the investigation time it takes a skilled employee to reconstruct context across systems, the delay it introduces downstream, and the inconsistency risk of a decision that depends on who happened to handle it. Most operations only track the first of these, and even that is rarely measured directly.
Ask an operations leader how much a recurring exception costs their team, and the honest answer is usually: nobody's measured it. It doesn't appear on a P&L line. It shows up as a quality manager who's harder to schedule around, a shipment that occasionally leaves a day late, and a decision that would probably come out differently depending on which shift handled it. None of that gets tracked, which means none of it gets prioritized, even when it's genuinely expensive.
The Three Costs That Actually Matter
1. Investigation Time
This is the part that's at least theoretically visible: the time a skilled person spends pulling records from the ERP, checking a reading against the QMS, calling a supplier for a document, and piecing it together before they can even start deciding what to do. For a moderately complex exception, this routinely runs from twenty minutes to well over an hour, and it's almost always done by someone whose time is expensive precisely because they're the one who knows where to look.
2. Downstream Delay
The exception doesn't resolve in isolation. A shipment held for a quality question delays a customer order. A supplier discrepancy left unresolved for a day pushes a production run. These delays compound in ways that are genuinely hard to trace back to the original exception, which is exactly why they're underweighted when someone decides whether fixing the process is worth the effort.
3. Inconsistency Risk
This is the cost most operations never quantify at all: two people handling the same type of exception will not make identical decisions, because the decision rule lives in someone's head rather than in a document. That's a quality and compliance exposure in any regulated or audited environment, and it's a customer-trust exposure everywhere else.
A Practical Way to Estimate It
You don't need a formal time-and-motion study to get a useful number. Pick one recurring exception type and walk through four questions with the person who actually handles it:
- How many times does this specific exception happen in a typical month?
- Realistically, how long does it take from 'someone notices' to 'a decision is made and acted on', including the waiting and interruptions, not just active work?
- What's the fully loaded cost of the person's time who typically handles it?
- What happens downstream when this exception isn't resolved same-day: does it delay a shipment, hold a production run, or create a customer-facing issue?
Multiply the frequency by the time by the cost, and you have a conservative floor. It's a floor because it excludes downstream delay and inconsistency risk entirely, both of which are real but harder to price precisely. Most leaders are surprised by the number even before adding those in.
The exceptions worth engineering a solution for aren't the dramatic ones. They're the boring, recurring ones that happen every week, cost real time every time, and have quietly become someone's whole job without ever being named as such.
Why This Matters Before You Talk to Anyone About a Fix
The single biggest reason exception-handling projects stall or get deprioritized is that nobody can point to what the current state actually costs. Without a baseline, any proposed fix looks like discretionary spend rather than a return on a documented, ongoing cost. Building that baseline, even a rough one, is what turns 'this is annoying' into a business case.
How We Approach This With Manufacturers
This is exactly what our Operational Exception Assessment is built to produce: a documented baseline for one real, recurring exception, including the cost estimate above and a clear picture of what a properly engineered resolution path would look like, before any commitment to build anything.
Frequently Asked
