Cost of Quality
What is Cost of Quality?
Cost of quality is the total cost an organization incurs to prevent, find and fix defects, plus the cost of failures that reach customers. It shows how much poor quality really costs.
Updated November 2026 · 5 min read
Cost of quality is a way of measuring how much an organization spends because products and services are not always right the first time. It adds up the cost of preventing problems, checking for them, fixing them before customers notice and dealing with them after customers do. The idea is that quality is not free to achieve, but poor quality is usually far more expensive.
The concept was developed in manufacturing quality management, notably by Armand Feigenbaum and Joseph Juran, and is now applied to services and software. In technology, the cost of quality shows up as testing, code review and monitoring on one side, and as incidents, outages, rework and lost customers on the other. For IT financial management, measuring it helps leaders see that investing in prevention often reduces total cost.
Definition of Cost of Quality
Cost of quality is the sum of costs incurred to achieve good quality and costs incurred because of poor quality. It is usually divided into four categories: prevention costs, appraisal costs, internal failure costs and external failure costs. This is often called the prevention, appraisal and failure model.
The first two categories are the cost of good quality, spent to stop defects or catch them early. The last two are the cost of poor quality, incurred when defects occur. Poor-quality costs are often much larger and harder to see. Quality experts have long argued that spending more on prevention and appraisal reduces failure costs by a greater amount, lowering the total.
Prevention and Appraisal Costs
Prevention costs are spent to stop defects from happening, such as training, design reviews, coding standards, automated testing frameworks and architecture work. Appraisal costs are spent to find defects, such as testing, code review, quality assurance teams, security scanning and audits.
In software, many of these costs are built into delivery practices. Automated tests and continuous integration pipelines are prevention and appraisal investments that catch defects before release. Because they are part of everyday engineering work, their cost is often buried in team budgets rather than reported separately.
Internal and External Failure Costs
Internal failure costs arise when defects are found before reaching customers, such as rework, bug fixing, failed builds, rolled-back deployments and delays. External failure costs arise when defects reach customers, such as incidents, outages, support calls, service credits, lost revenue, regulatory penalties and damage to reputation.
External failures are typically the most expensive, both directly and indirectly. An outage of a customer-facing system can cost far more in lost revenue and trust than the testing that would have prevented it.
Importance of Cost of Quality in IT Financial Management
Much of the cost of poor quality in technology is hidden. It appears as unplanned work, overtime, support costs and lost productivity rather than as a line in the budget. Measuring cost of quality makes these costs visible.
It also shows the financial case for investing in prevention and good engineering practices.
Revealing Hidden Costs
Teams that spend a large share of their time fixing defects, handling incidents and reworking releases have less capacity for new work. This lost capacity is a real cost, even if it does not appear as a separate expense.
Measuring failure costs, such as engineering hours on incident response and rework, and translating them into money using labor costs, shows leaders how much poor quality is consuming. This often reveals that failure costs exceed the visible cost of quality assurance.
Justifying Prevention
Prevention investments, such as test automation, better monitoring or reducing technical debt, are often hard to justify because their benefits are avoided costs. Cost of quality analysis quantifies those benefits by showing how failure costs fall as prevention improves.
This supports capital budgeting and prioritization decisions, giving quality improvements a business case that can compete with feature work for funding.
How to Measure Cost of Quality
Measuring cost of quality involves defining what falls into each category, collecting data on time and money spent and tracking the totals over time.
Precise measurement is difficult, so organizations usually start with estimates and improve them. A rough figure that shows the scale of failure costs is enough to start the conversation about prevention.
Collecting the Data
Prevention and appraisal costs can be estimated from team structures and time allocations, such as the share of engineering time spent on testing and review, and the cost of quality tools. Internal failure costs can be estimated from time spent on bug fixing and rework.
External failure costs come from incident records, support volumes, service credits, outage duration and estimates of lost revenue. Incident management and service desk tools provide much of this data, which can be combined with IT service costing to put a value on each incident.
Tracking and Improving
Cost of quality should be tracked over time and broken down by product, service or team. A healthy trend is rising prevention spending and falling failure costs, with total cost of quality declining.
Measures such as change failure rate, mean time to restore service and the share of work that is unplanned complement the financial view. Together, they show whether quality investments are paying off. Including cost of quality in regular reviews of IT cost optimization keeps quality on the agenda alongside more visible savings opportunities.
Examples of Cost of Quality in IT Financial Management
The examples below show cost of quality applied to technology.
Both use illustrative figures.
In each, quantifying failure costs made the case for prevention clear.
Measuring a Team's Cost of Quality
A product team of 30 engineers, with a fully loaded cost of $180,000 each, spends about 25 percent of its time fixing bugs and handling incidents, an internal and external failure cost of $1.35 million a year in labor alone. Service credits and support costs from outages add another $400,000.
The team spends about $300,000 a year on testing tools and quality engineering. Total cost of quality is about $2.05 million, with 85 percent coming from failure. The analysis supports a proposal to invest more in prevention. Before the analysis, the team's quality spending was seen as overhead, while the far larger failure costs were not tracked at all.
Investing in Test Automation
The team invests $500,000 in test automation and better monitoring. Over the following year, time spent on bugs and incidents falls to 15 percent, reducing labor failure costs to $810,000, and service credits fall to $150,000.
Failure costs drop by $790,000, while prevention spending rises by $500,000. Total cost of quality falls by $290,000, and the team gains capacity equivalent to three engineers for new work. That freed capacity is arguably the larger benefit, since it lets the team deliver more without hiring.
Conclusion
Cost of quality measures the total cost of preventing, finding and fixing defects and of failures that reach customers, using the prevention, appraisal and failure model. It shows that poor quality is usually more expensive than the investment needed to avoid it.
In IT financial management, cost of quality reveals hidden costs such as incidents, rework and lost capacity, and builds the financial case for prevention. Estimating costs in each category, tracking them over time and connecting them to engineering measures helps organizations invest in quality where it pays off.
Related terms
Labor Costs
Labor costs are the total expenses of employing people to do work, including salaries, wages, benefits, payroll taxes, bonuses and the cost of contractors and outsourced staff.
Capital Budgeting
Capital budgeting is the process organizations use to evaluate and select long-term investments, using measures such as net present value, internal rate of return and payback period to compare options.
IT Service Costing
IT service costing is the process of calculating the full cost of delivering each IT service, such as email, hosting or the service desk, by assigning direct costs and allocating shared costs to it.
IT Cost Optimization
IT cost optimization is the continuous practice of aligning technology spending with business value, reducing waste and inefficiency while protecting or increasing investment in the capabilities that matter most.