Cost of Poor Quality: 6 Steps to Find and Reduce Hidden Rework

Cost of poor quality is the cost a business incurs because its products or services fail to meet the intended requirements. It includes failures found before delivery and failures found after the customer receives the work. In a service business, that can mean repeat visits, replacement materials, complaint handling, and time spent correcting records.

The measure helps teams see a problem that ordinary expense categories can hide. This article explains six steps for a useful cost of poor quality calculation, provides a worked example, and shows how to turn the result into a focused improvement project.

Cost of poor quality versus cost of quality

Cost of quality is a broader framework. It includes prevention, appraisal, internal failure, and external failure. Prevention covers work that aims to avoid defects. Appraisal covers checking or testing. The failure categories capture the consequences when the process falls short.

The ASQ cost of quality explanation describes this framework. Keep the distinction clear: money spent on a sensible inspection is not the same as money spent fixing defective work.

For example, training a technician on a new process is prevention. Reviewing a completed job is appraisal. Correcting a mistake before handover is internal failure. Returning to fix the same mistake after handover is external failure.

The purpose is to improve the process, not to label every unpleasant expense as poor quality. A customer-requested scope change may be normal billable work. A second visit may also be part of the planned service. Define failure against agreed requirements before counting its cost.

1. Choose a bounded process and a clear failure definition

Start with one workflow, such as installation closeout, invoice preparation, or equipment repair. A whole-company estimate can become too broad to support action, especially when records use different definitions.

Next, state what counts as a failure. For an installation team, it might be correction work caused by a missed requirement in the original scope. For billing, it might be an invoice that needs reissue because the business used the wrong rate.

Separate causes the business controls from other events. A customer’s new request, storm damage, and an original workmanship defect should not share one callback code. Otherwise, the metric can point the team toward the wrong fix.

Choose a reporting period that captures the relevant lag. Some external failures appear weeks after delivery. If you compare current failures only with current jobs, note the timing difference.

Our article on construction quality control software explains how evidence and follow-up records support quality work. The same idea applies to any service process where teams need to distinguish correction from new scope.

2. Map internal and external failure costs

Internal failures occur before the customer receives the final output. Examples include scrapped material, rework, retesting after a defect, and correcting a job record before billing.

External failures occur after delivery. These may include service callbacks, returns, replacements, credits caused by defects, and time spent resolving a valid quality complaint.

ASQ’s cost of quality glossary entry distinguishes prevention, appraisal, and the two failure groups. Use those categories to organize the analysis, then define the local cost items in plain language.

Include the work around the repair where it matters. A callback may involve scheduling, travel, warehouse handling, technician time, and customer communication. Counting only replacement material can understate the burden.

However, avoid double counting. If a labor rate already includes a defined share of overhead, do not add the same overhead again. Ask finance to approve the rate basis and the costs that belong in the model.

3. Capture activity and use defensible cost rates

For each failure, record the source job, failure type, date, reason, labor time, materials, and other direct costs. Keep the fields simple enough that staff can enter them during normal work.

Next, apply agreed rates. A direct labor cost rate differs from a selling rate. Using the customer’s hourly price as the internal cost can overstate the expense unless the analysis explicitly measures a different impact.

For travel, decide whether you use actual recorded cost, a standard internal rate, or another approved basis. The choice should stay consistent across the period and appear in the calculation notes.

Separate measured and estimated amounts. If complaint handling time is not yet recorded, use a clearly documented sample rather than presenting a precise company-wide figure as fact. Improve the data before tightening the target.

Our guide to equipment maintenance logs shows the value of linked work and follow-up records. For quality analysis, use stable IDs so that one failure can connect to its labor, materials, and customer outcome.

4. Calculate the total and choose a useful denominator

A basic calculation adds the internal and external failure costs included in your agreed scope. You can then express the result as an amount per job, per unit, or as a share of a defined revenue base.

Use the denominator that supports the question. Cost per completed installation can help compare similar work. A percentage of revenue can help track the overall burden, but a price change can alter the ratio even when defects do not improve.

Keep the period and scope aligned. If the numerator covers one branch, the denominator should not use company-wide sales. Likewise, avoid dividing failures from old projects by an unrelated group of newly completed jobs without explaining the mismatch.

Do not assume the figure captures every economic effect. Lost future business and damaged trust can matter, but they are harder to measure. Keep those estimates separate from documented failure costs.

A worked example for a service contractor

Consider a fictional contractor reviewing one month’s quality-related correction work. The team records 24 hours of internal rework at an agreed cost rate of $35 per hour. It also records $300 of material waste.

Internal failure cost is therefore $840 plus $300, or $1,140. This includes only the items in the example. It does not imply that every business should use the same rate or cost boundary.

After delivery, the team records 18 callback labor hours at the same rate, $180 of callback travel cost, and $250 of replacement materials. External failure cost is $630 plus $180 plus $250, or $1,060.

The total cost of poor quality in this defined scope is $2,200. If the relevant revenue base is $100,000 for the same reporting scope, the ratio is 2.2%. If the team completed 50 comparable jobs, the average is $44 per job.

Now check the records behind the table. If the replacement material cost already appears in another recorded total, remove the duplication. If some callbacks were paid new work, exclude them from this failure category.

5. Find the causes that deserve action

Group the costs by failure type, process step, or another meaningful category. A high count of small errors and a low count of expensive failures can call for different responses.

For example, missing photos may create many small administration corrections. Incorrect installation measurements may create fewer but much larger return visits. Review both cost and frequency before choosing an improvement.

Next, investigate the process behind the pattern. Was the instruction unclear? Did staff lack the right part or tool? Did a system permit an invalid value? Avoid assuming every failure comes from carelessness.

Review a sample of records with the people who do the work. A reason code can summarize a case but may hide important context. Use it to find where to look, then inspect the evidence.

Choose a specific change and an owner. It could be a clearer handoff, a validation rule, a better kit check, or focused training. A metric without a next action can become another report that nobody uses.

6. Measure improvement without hiding failures

Record the baseline before changing the process. Then track the same cost categories and denominator after the change. If the definition changes, show the break rather than presenting the series as directly comparable.

Expect reporting behavior to affect the number. Better capture can make recorded failure cost rise at first even if the process has not worsened. Compare completeness as well as the total.

Do not create a target that rewards staff for avoiding failure codes. If a supervisor’s score depends only on a low callback count, the team may reclassify defects as new work. Use review and learning rather than blame to protect data quality.

Also track prevention and appraisal spending separately. An improvement may add inspection effort while reducing costly returns. The broader business case should compare those changes without merging them into one unexplained total.

Our guide to business intelligence dashboards explains how definitions and owners turn measures into useful decisions. Quality cost reporting should identify a problem, support a change, and show whether the change worked.

How software can support the calculation

Start with the records your team already keeps. A job system may hold visits, a time tool may hold labor, and accounting may hold credits. Link them through stable identifiers rather than asking staff to reenter every value.

Use a small set of failure codes and allow an explanation. Validate required references, flag missing cost data, and give someone responsibility for uncertain cases. Do not force a false zero when the cost is unknown.

Next, build a reviewable report. A manager should move from the total to the underlying cases and see the rate basis. That makes the metric easier to trust and helps the team correct errors.

Begin with one branch or process. After the pilot, compare data completeness, capture effort, and the usefulness of the resulting actions. Expand only when the team can sustain the process.

Turn hidden correction work into a focused improvement

Cost of poor quality becomes useful when the team can trace it to real failures and choose a practical response. Define the scope, use clear cost rules, and check for duplication. Then improve one process and measure the result with the same definitions.