Pennies, Prevention, and the Price of Poor Quality
There is a line item missing from most project budgets. It does not appear in the cost baseline, it is not tracked in the risk register, and it is rarely discussed in steering committee meetings. Yet it is often the most expensive item on the project.
It is the cost of poor quality — and by the time it shows up, it is usually too late to budget for it.
The Four Categories of Quality Cost
The Cost of Quality (CoQ) framework, is widely used in quality management and referenced in ISO 9001, divides quality-related costs into four categories. Understanding these categories is the first step to managing them.
1. Prevention Costs
These are the costs incurred to prevent defects from occurring in the first place. Training, quality planning, requirements reviews, process documentation, and design reviews all fall into this category. Prevention costs are investments — they reduce the likelihood of defects downstream.
Most organisations underspend here. Prevention feels optional when budgets are tight. It rarely is.
2. Appraisal Costs
These are the costs of measuring and monitoring quality — testing, inspections, audits, and quality reviews. Appraisal costs are necessary, but they do not prevent defects; they detect them. The goal is to catch problems before they reach the customer or end user.
3. Internal Failure Costs
These are the costs incurred when defects are found before delivery — rework, re-testing, scrapping and redoing work, and the management time spent resolving issues. Internal failure costs are painful, but they are recoverable. The defect was caught before it caused damage beyond the project team.
4. External Failure Costs
These are the costs incurred when defects reach the customer or end user after delivery. Warranty claims, emergency fixes, reputational damage, lost contracts, regulatory penalties, and the cost of rebuilding trust all fall here. External failure costs are the most expensive category by a significant margin — and the hardest to quantify.
The general rule of thumb in quality management is the Rule of Ten: a defect that costs R1 to prevent costs R10 to fix internally and R100 to fix externally. The numbers vary by industry and context, but the principle holds consistently.
Who Actually Pays?
This is the question most project budgets do not answer honestly.
When poor quality occurs on a project, the cost is distributed — often invisibly — across multiple parties:
The project team absorbs the immediate cost through overtime, rework, and the stress of firefighting. This cost rarely appears in the project budget as “quality failure.” It appears as schedule overrun, resource overrun, or simply disappears into the general chaos of a troubled project.
The organisation absorbs the medium-term cost through delayed benefits realisation, lost productivity during extended stabilisation periods, and the management attention diverted from other priorities to resolve the crisis.
The customer or end user absorbs the long-term cost through workarounds, reduced confidence in the system or product, and the erosion of trust in the team that delivered it.
The project manager absorbs the reputational cost — sometimes unfairly, sometimes not. A project that delivers on time and on budget but fails on quality is not a successful project. The schedule and budget metrics look fine; the quality failure shows up six months later when the system is in production.
The Invisible Budget Line
Here is the uncomfortable truth: most organisations do not measure the cost of poor quality. They measure rework hours (sometimes), they track defect counts (occasionally), and they conduct lessons learned sessions (rarely, and usually too late to be useful). But they do not calculate what poor quality actually cost the project in total — prevention, appraisal, internal failure, and external failure combined.
This means the same quality failures recur on project after project, because the true cost is never surfaced, never attributed, and never used to justify the investment in prevention that would have avoided it.
ISO 9001:2015 Clause 10 (Improvement) requires organisations to react to nonconformities, take corrective action, and review the effectiveness of those actions. The Cost of Quality framework is the mechanism that makes this requirement meaningful — it turns “we had some issues” into “poor quality cost us X, and here is what we should invest in prevention to avoid it next time.”
A Practical Starting Point
You do not need a sophisticated quality cost tracking system to start applying this thinking. Begin with three questions at your next project retrospective or lessons learned session:
- What did we rework, and how long did it take? Multiply by the hourly cost of the resources involved. That is your internal failure cost for this project.
- What issues reached the customer or end user? Estimate the time spent resolving them post-delivery, plus any reputational or contractual impact. That is your external failure cost.
- What would it have cost to prevent these issues? A requirements review, an additional test cycle, a quality audit at a key milestone. Compare that number to the failure costs above.
In most cases, the prevention investment is a fraction of the failure cost. The business case for quality is usually obvious — once you do the arithmetic.
The Bottom Line
Poor quality is not free. It is simply billed to a different account — one that does not appear in the project budget but shows up in overtime, rework, emergency fixes, and eroded trust.
The Cost of Quality framework does not make quality more expensive. It makes the cost of ignoring quality visible — and that visibility is the first step toward doing something about it.
