INDEPENDENT QUALITY SYSTEMS PUBLICATIONPROCESS / CONTROL / EVIDENCE

Management review / PRACTICAL EXPLANATION

Cost of Quality vs Cost of Poor Quality

Cost of quality is a broader view of resources used for prevention, appraisal and failures.

Cost of quality is a broader view of resources used for prevention, appraisal and failures. Cost of poor quality focuses on losses associated with failures. Distinguishing them helps management evaluate whether investment in dependable processes reduces the burden of errors, rather than treating every quality activity as waste.

The QMS Management Review and Performance Evaluation Guide places this topic in its wider QMS context. Agree category definitions with finance. Different reporting conventions exist, so the boundary and assumptions should be explicit in comparisons.

Define the decision and its boundary

Set the scope before collecting detail about cost of quality and poor quality. Identify which activities are included, what triggers the work and where responsibility passes to another person. A broad label can conceal several different arrangements. Use a completed case to test whether everyone understands the same boundary, then record any important exception that would make the ordinary route unsuitable.

A cost model should support a decision rather than become a contest to allocate every minute perfectly. Begin with material categories for which evidence is reasonably available. Improve the model where better information would change priorities. Avoid hiding uncertainty in complex allocations that management cannot explain, and keep the distinction between a cost classification and a judgement about whether the activity is useful.

Put the method into practice

Assign the work in cost of quality and poor quality to roles with practical authority. If a step requires information held elsewhere, agree how that information will be obtained and what happens when it is unavailable. Put the important exception route alongside the ordinary sequence. This gives staff a legitimate way to resolve difficulty without hiding a problem or improvising an unauthorised workaround.

  1. Separate planned prevention and appraisal from internal and external failure.

  2. Use consistent accounting periods and avoid duplicate allocation.

  3. Evaluate the relationship between investment, failures and intended results.

Worked example

A fictional manufacturer increases planned setup verification while reducing repeated batch rework. Its report shows the appraisal effort and failure costs separately rather than presenting only a smaller defect count.

Management considers the total arrangement and whether the verification remains proportionate. Reduced rework does not automatically prove that every added check is worthwhile.

The fictional case illustrates cost of quality and poor quality; it is not a published benchmark or a promised improvement. Compare the explanation with evidence from the affected work before copying the response. A convincing story can suggest a mechanism, but only observations from the real process can establish whether that mechanism applies and whether the proposed response addresses it.

Useful evidence and records

Plan the evidence for cost of quality and poor quality before choosing a document layout. Ask what a replacement owner would need to understand the current position and resume the work. Prefer references to controlled information over pasted extracts that may become obsolete. Assign responsibility for updating the record when a decision changes, including the reason for the revision.

Record elementWhat it should establish
PreventionWork intended to avoid failures
AppraisalWork evaluating conformity
Internal failureLoss found before external delivery
External failureLoss after delivery to recipients

Check the result and avoid a common mistake

Minimising prevention and appraisal spend can increase failure exposure. Equally, spending more on checks does not guarantee a better system if the checks address the wrong mechanism.

Review whether categories are consistent and whether an improvement claim includes the cost of its response. Examine operational outcomes alongside financial estimates.

Include challenge in the review of cost of quality and poor quality. Ask what evidence would lead the team to revise its conclusion and look for that evidence deliberately. A review designed only to confirm success is unlikely to reveal an important limitation. Record a bounded conclusion where appropriate, explaining which conditions were tested and what follow-up is needed for the remaining uncertainty.

Connect the next decision

Keep the owner of cost of quality and poor quality involved until the practical result is understood. Administrative completion may occur before benefits or weaknesses become visible. Agree who will examine the later evidence and who can authorise further action. Where ownership changes, transfer the outstanding assumptions and decisions as well as the documents, so continuity does not depend on personal recollection.

Use Quality Performance Reporting when the work moves to the adjacent decision. The related guide to cost of poor quality explains the wider process dependency. The handover should identify what has been accepted, what remains open and who will review the next evidence. Keep the original decision traceable when later information changes the conclusion.

Practical question

Is a lower total always better? Interpret cost with performance and exposure. A temporary investment may strengthen capability while increasing current expenditure. Conversely, reduced checking costs may conceal a weakened control. Compare the intended result, relevant failure experience and longer-term operating arrangement before deciding whether the change represents improvement.

RESEARCH RECORD

Primary sources

  1. ISO 9001: current public overview ↗ Accessed 15 October 2026
  2. ASQ: cost of quality overview ↗ Accessed 15 October 2026

Sources support the factual context. Examples and implementation suggestions are original explanations, not quotations from ISO requirements.