Cost of quality reporting means giving failure costs a line of their own: a booking code for rework, one for sorting, one for special freight, and a monthly report that always pulls the same numbers. Without it, every figure is a one-off estimate that nobody can defend twice.
Most companies can name their scrap figure and nothing else. Not because the other costs are missing from the books — they are all in there — but because they were booked under production, logistics and service, and nobody ever asked which of them were failure costs.
That is a reporting problem, not an accounting problem. The accounts are correct. What is missing is a second view across them. This article is about building that view: which costs to capture, which booking codes you need, how often to report, and who owns the number once it exists. If you first want to know where these costs sit in your P&L, start with Cost of Poor Quality: Where It Hides and come back here.
The same cost, booked once and reported twice
sorting shift
re-inspection
express shipments
return handling
price concessions
lost orders
field returns
customer audits
Nothing is moved and nothing is re-booked. Reporting adds a view across the accounts you already have.
Why talking about "Failure Costs" changes everything
1. It places blame where it belongs
When we talk about “quality costs,” we suggest that quality itself is costly. This creates resistance to quality initiatives. People think, “We can’t afford all that quality stuff.”
Talking about “failure costs” flips the script. It shows that failures—not quality—drain resources.
A worked example: a plant tracks “quality costs” at 15% of production costs. The number looks high. Management starts cutting quality programmes to save money. Failures go up. When the same costs are relabelled as “failure costs”, everyone understands the goal is fewer failures, not less quality work.
2. It motivates action
“Quality costs” sounds like a necessary evil. “Failure costs” sounds like something to eliminate.
Which would motivate your team more:
- “We need to manage our quality costs better”
- “We need to eliminate these failure costs”
The second statement creates urgency. It points to a clear enemy: failures.
3. It aligns with business goals
Every business wants to reduce costs. When we frame the issue as “failure costs,” we align quality work with cost reduction. This helps quality professionals get buy-in from finance and operations teams.
4. It highlights the Return on Investment
Prevention and appraisal activities aren’t just expenses—they’re investments that reduce failure costs. When you track failure costs separately, the ROI of quality initiatives becomes clear.
A worked example: a software company spends $50,000 on developer training. Bug-fixing
costs fall by $200,000 a year. Counted as an investment in lower failure costs, that
is a 400% return.
5. It changes behavior
Words shape actions. When teams track “failure costs,” they naturally focus on reducing failures, not cutting quality programs.
A hospital that switched from “quality costs” to “failure costs” saw their approach change. Instead of viewing safety checks as bureaucratic overhead, staff saw them as failure prevention investments.
6. It creates a common language
The term “failure costs” is easier for everyone to understand—from frontline workers to executives. It builds a common cause across departments.
7. It makes success measurable
“Reducing quality costs” is vague. “Reducing failure costs” gives you a clear metric. You can track progress and celebrate wins when failure costs decrease.
How to set up cost of quality reporting
To use failure cost thinking, you need to track these costs. Here’s how:
Step 1: Identify all failure-related costs
These are the two failure halves of the cost of quality model. Prevention and appraisal belong to it too, but they are what you spend to avoid failure, not what failure costs you.
Internal Failure Costs
- Scrap materials
- Rework labor
- Testing again after fixes
- Machine downtime
- Lower yield rates
- Extra inventory from unreliable processes
External Failure Costs
- Customer returns
- Warranty claims
- Lost customers
- Regulatory fines
- Discounts for quality issues
- Legal settlements
- Customer service costs
- Brand damage
You do not have to build that list from scratch — the failure cost capture template has it, and you delete what does not apply to you.
Step 2: Create systems to track these costs
You might use:
- Special codes in your accounting system
- Failure tracking software
- Regular failure cost audits
- Employee surveys to capture hidden costs
What you ask controlling for
| Cost | Where it sits today | What you need | Who supplies it |
| Scrap | scrap account | already there | Controlling |
| Rework | production hours | booking code FC-RW | Production |
| Sorting, containment | overtime, temp labour | booking code FC-SO | Production |
| Special freight | logistics invoices | reason code on the invoice | Logistics |
| Credit notes, concessions | sales deductions | reason code on the credit note | Sales |
| Warranty, field returns | service budget | booking code FC-WA | Service |
| Lost orders | nowhere | one written line per case | Sales |
Code names are examples — use whatever your system allows. What matters is that each row has a code and a name behind it.
Step 3: Report failure costs regularly
Create dashboards showing:
- Total failure costs
- Failure costs as a percentage of sales
- Failure costs by category
- Trends over time
- Comparison to targets
If you want a first order of magnitude before any of this reporting exists, the free calculator gives you one in ten minutes.
Step 4: Use the Rule-of-Ten to drive improvement
The Rule of Ten is a rule of thumb, not a measurement: the later a defect is found, the more it costs, roughly by a factor of ten per stage. Use it to make the case, not to put a figure in a report.
- Show that a $10,000 prevention investment could avoid $100,000 in internal failures
- Explain that a $50,000 problem today could become a $500,000 problem if customers find it
- Calculate how much earlier detection would save
Step 5: Track both types of failure costs
Keep internal and external failure costs separate in your reports. This shows:
- If problems are leaking to customers (bad)
- If you’re catching more problems internally (good)
- Where to focus your next improvement efforts
For example, high internal costs might mean poor processes. High external costs might mean weak testing.
The hidden benefits of tracking Failure Costs
Beyond the obvious financial benefits, tracking failure costs:
- 1. Builds a problem-solving culture: Teams become focused on finding and fixing root causes.
- 2. Improves customer experience: Lower failure rates mean happier customers.
- 3. Reduces stress: Fewer failures mean fewer emergencies and less firefighting.
- 4. Boosts morale: People like doing things right the first time.
- 5. Creates competitive advantage: Lower failure costs mean either higher profits or lower prices.
How to start without a project
Three roles, one number
A rising figure in the first months is usually better capture, not worse quality. Say that out loud before the first report, or the system dies in month three.
- 1. Pick one area where failures hurt most
- 2. Identify the costs these failures create
- 3. Track these costs for 30 days
- 4. Share the findings with your team
- 5. Brainstorm solutions to reduce these costs
- 6. Implement improvements
- 7. Track results
- 8. Expand to other areas
Useful strategies to consider
Data Visualization
Create compelling charts showing failure costs over time to make the impact visual and immediate for stakeholders:
- Use simple color coding to show, which costs are trending up or down each month.
- Add comparison lines showing what happens to profits when failure costs come down.
Success Stories
Collect and share case studies of how failure cost tracking led to significant improvements in your organization:
- Document exact numbers and specific changes that created the improvements.
- Create short video testimonials from team members who saw processes improve firsthand.
Executive Sponsorship
Secure support from top leadership by showing how failure cost reduction directly impacts financial results:
- Create a simple one-page brief that ties failure costs directly to metrics executives already care about.
- Schedule quarterly reviews where leaders can see progress and publicly recognize successful teams.
Integration
Build failure cost tracking into existing systems rather than creating separate processes that feel like extra work.
- Add failure cost codes to your current financial tracking software so reporting happens automatically.
- Train supervisors to discuss failure costs in regular team meetings instead of creating special “quality meetings.”
Conclusion
The shift from “quality costs” to “failure costs” is more than wordplay. It changes what the company looks at. By focusing on failure costs, you get everyone to work on cutting waste and making customers happy.
As Philip Crosby taught us, “Quality is free.” The cost of doing things right is usually lower than the cost of fixing mistakes.
Start small. Track failure costs in one area. Use the data to make things better. Share your wins. Then spread to other areas. After three months you will know whether it holds.
Remember: Quality saves money. Failures waste money. When you talk about failure costs, you change how people think. When you change thinking, you change action.
What failure costs will you start tracking today?
Frequently Asked Questions about Failure Costs
Isn't this just semantics? Does changing the name really matter?
It’s not just semantics. Language shapes thinking. When you talk about “quality costs,” you create resistance to quality initiatives. When you talk about “failure costs,” you create allies in reducing failures.
The test is simple: put both sentences into the same budget meeting. “We need to reduce quality costs” reads to finance as a proposal to cut quality. “We need to reduce failure costs” reads as a shared goal.
Won't focusing on failure costs lead to blame and finger-pointing?
Not if done right. The goal isn’t to blame individuals but to improve systems. Make it clear that you’re hunting for process issues, not people to punish.
How do I convince my organization to switch to failure cost thinking?
Start with a pilot project. Track failure costs in one area. Show the insights gained and the improvements made. Success will speak for itself.
What's the first step in implementing failure cost tracking?
Begin with your most painful, expensive failures. Track those costs first. The dramatic numbers will help you build momentum.
How detailed should our failure cost tracking be?
Start simple. Track major categories of failure costs. As your system matures, you can add more detail. Don’t let perfectionism prevent progress.
How Do Top Companies Use Failure Cost Thinking?
Three signs, in this order. First: the figure goes up because more is being booked, not because more is going wrong.
Second: somebody in controlling asks for a booking code that does not exist yet.
Third: in a meeting, somebody from production quotes a failure cost figure without quality having asked. From the third sign on, the system carries itself.
How do I know it is working?
Three signs, in this order.
First: the figure goes up because more is being booked, not because more is going wrong.
Second: somebody in controlling asks for a booking code that does not exist yet.
Third: in a meeting, somebody from production quotes a failure cost figure without quality having asked. From the third sign on, the system carries itself.
