Rework is the most expensive cost that does not appear on a cost line.
In a factory, it is the unit that fails inspection and goes back to the line. In a software team, it is the feature that ships with a bug and has to be rebuilt. In both cases, the labour is paid twice, the materials are consumed twice and the schedule slips.
The customer may or may not notice. The margin definitely does.
What makes rework uniquely damaging is not the cost of any single instance — it is the invisibility of the total. Because rework is accounted for as normal operating cost, it is never seen as a single problem. It is distributed across every cost category, hidden in aggregate, and therefore never addressed at the root.
The Cost of Poor Quality in Manufacturing: What the Benchmarks Show
The standard measure of rework in manufacturing is the Cost of Poor Quality, or COPQ. Industry benchmarks put COPQ at 5–30% of revenue for manufacturers who have not actively measured and reduced it.
For a company with $10M in annual revenue, that is $500,000 to $3,000,000 per year in rework, scrap, warranty claims and inspection costs. Most manufacturing CEOs know their scrap rate. Very few know their total COPQ — because the data required to calculate it is spread across production, quality, logistics and finance, and nobody has been asked to aggregate it.
The four components of COPQ — and why the most expensive ones are the most hidden:
| Component | What It Includes | Visibility to CEO |
|---|---|---|
| Internal failure costs | Scrap, rework, re-inspection, defect-related downtime | Low — absorbed into production line |
| External failure costs | Warranty claims, customer returns, contract penalties | Medium — appears as one-off commercial costs |
| Appraisal costs | Inspection labour, testing equipment, quality audits | Medium — visible as headcount |
| Prevention costs | Training, process documentation, tooling maintenance | High — approved as budget items |
The first two categories are the most expensive and the most hidden. External failure costs in particular are often categorised as one-off commercial costs rather than as quality failures — which means they never trigger the operational investigation that would prevent the next occurrence.
The Cost of Defects in Technology: The Engineering Time That Disappears
In software teams, the equivalent measure is the cost of technical debt and defect resolution. A feature that ships with a critical bug requires the engineering team to stop current work, diagnose the issue, implement a fix, test the fix and redeploy.
If the bug affects a production system, there is also a customer impact cost: support tickets, SLA penalties and potential churn.
A single critical bug in a production system can consume:
- 40–80 hours of engineering time across multiple team members
- At a fully loaded cost of $100 per engineer-hour: $4,000–$8,000 for one bug
- Plus the opportunity cost of the work not done while the team was fixing the defect
- Plus the customer relationship cost if the bug caused a service disruption
Annualised, the numbers are significant:
> A team that resolves two critical bugs per month is spending $96,000–$192,000 per year on work that produces no new value. That is a senior engineer's fully loaded annual cost, spent entirely on undoing work that was already done.
Why Rework Is Hidden: The Accounting Problem
The reason rework is hidden is structural. It is accounted for as normal operating cost.
The labour that goes into rework is on the same payroll as the labour that goes into productive work. The materials consumed in scrap are on the same materials line as the materials consumed in production. There is no rework line on the P&L.
This is a visibility problem at its most expensive. The CEO who does not see rework as a dollar figure cannot make a business case for the investment required to eliminate it. It remains a quality metric — a defect rate, a bug count — rather than a financial one.
> When the CEO sees rework as a dollar figure on a monthly report rather than as a defect rate on a quality dashboard, the conversation changes. The investment in better tooling, clearer specifications and more rigorous review processes becomes a financial decision with a calculable return — not a quality initiative with an uncertain one.
The Management Failure Behind Rework: Where It Actually Starts
The root causes of rework are different in manufacturing and technology, but the management failure is the same: a system that prioritises speed over quality at the point of delivery.
In manufacturing, rework concentrates where:
- The specification is unclear or changes after production has started
- The tooling is worn and the maintenance schedule has been deferred
- The operator training is insufficient for the complexity of the task
- The quality check is performed at the end of the process rather than at each stage
In technology, rework concentrates where:
- The requirements were incomplete when development started
- The testing was inadequate or skipped under schedule pressure
- The code review was bypassed to meet a deadline
- The deployment process does not include a rollback plan
In both cases, the decision to proceed without adequate preparation is made by people who are measured on speed — delivery date, sprint velocity, time to market — rather than on the cost of the rework that results. The incentive structure produces the outcome.
The Intervention: Upstream, Not Downstream
The intervention that reduces rework is not more inspection. Inspection catches defects after they are created. The intervention is upstream — and it follows three steps in order:
Step 1: Make the cost visible.
Calculate total COPQ or defect resolution cost as a monthly dollar figure and report it to the CEO alongside revenue and margin. When the number is visible, it becomes a priority. When it is buried in a quality dashboard, it remains a quality team problem.
Step 2: Move the quality check upstream.
In manufacturing, this means in-process inspection at each stage rather than final inspection at the end. In technology, this means test-driven development and mandatory code review rather than QA at the end of the sprint. The cost of catching a defect early is a fraction of the cost of catching it late.
Step 3: Address the root cause, not the symptom.
A defect that recurs is a process failure, not a quality failure. The investigation should end with a process change, not a corrective action that addresses the individual instance. Corrective actions without process changes produce the same defect again.
How EVOSYST Addresses Rework
The Cross-Silo Margin Recovery engagement addresses rework through process and technical debt defect reduction. The target is a measurable reduction in rework cost within the first 90 days of the engagement, reported to the CEO as a dollar figure recovered — not as a defect rate improved.
The distinction matters. A defect rate is a quality metric. A dollar figure is a business result. The CEO who sees both understands the business case for the investment. The CEO who sees only the defect rate is managing a quality programme, not a financial recovery.
*To find out what rework is costing your business in real money, start with the Executive Leak Assessment. Two weeks. A priced report of your five to ten largest operational leaks.*
About the Author
M.K. Hasan
Founder, EVOSYST · Global CHRO & Strategic Advisor to CEOs
M.K. Hasan helps CEOs and Boards find the revenue their business is losing and get it back. He works across Strategy, People and Operations through focused diagnostic and recovery sprints.
Request an Executive Leak Assessment