Chapter 31: Verifying Effectiveness: The Step That 80% of Plants Skip

Here's the hard truth: most plants implement corrective actions and close NCRs without ever proving the action worked. They completed it. They documented it. That feels like success. It isn't.

Clause 10.2.3 requires you to "review the results of the corrective actions taken." That means you have to go back and check. Not immediately after implementation—you need enough process cycles to confirm that the defect *doesn't* come back.

The verification step has two parts: proof of implementation and proof of effectiveness.

Proof of implementation is straightforward. You're checking that the corrective action actually happened. Did the temperature probe get replaced? (Yes, we have the receipt and the old probe.) Did the operator training happen? (Yes, signed attendance sheet.) Did the die maintenance schedule change? (Yes, here's the updated schedule in the maintenance system.) This is easier and takes 1-2 weeks.

Proof of effectiveness is harder and takes longer. You're asking: "After we implemented this action, did the defect stop happening?" You can't know this until you've run the process enough times to be confident. That timing depends on your production volume and cycle time.

• High-volume process (500+ units per day): Run 30 production cycles = 1-2 days of monitoring. Check 100% or a representative sample for the specific defect that triggered the NCR.
• Mid-volume process (50-200 units per day): Run 50 cycles = 1-2 weeks. Maintain focus on the specific characteristics that were out of spec.
• Low-volume or batch process (< 50 units per day): Run 100 cycles or wait 4 weeks—whichever is longer. The longer wait ensures seasonal or drift-related variations surface.

For the plating temperature example: if you replace the temperature controller on January 20 and your plating line runs 200 units per day, you'd monitor the next 30 production cycles (6 days of production). You'd log temperature for each run, confirm it stays within ±0.5°C of setpoint, and verify no surface finish rejects on those runs. On January 26, after 6000 plated units with zero temperature-related rejects, you close the NCR and document: "Corrective action verified effective. No recurrence detected across 30 production runs."

If instead you said "We replaced the controller on January 20; it's now January 22; we haven't seen the problem again; NCR closed," you've proven nothing. By February, the same problem might resurface.

Evidence you need to retain in the closed NCR:

• What the process output looked like before the corrective action (e.g., temperature logs showing drift, reject rates)
• What you changed (e.g., controller model, calibration interval, alarm setpoint)
• What the process output looked like after the action (e.g., temperature logs showing stability, zero related rejects)
• The date range and number of units/cycles monitored
• Sign-off from the quality or operations manager confirming effectiveness

This verification step is where your NCR system starts paying for itself in continuous improvement. When you analyze your closed NCRs at the end of each quarter and ask "Of the 23 NCRs we closed, how many recurred?" you get a measure of system health. Plants with rigorous verification typically see recurrence rates below 5%. Plants without it see rates of 15-30%.

That difference compounds. Fewer defects mean fewer customer complaints, fewer reworks, higher on-time delivery, lower scrap, and happier customers. And it all starts with saying, "We're not closing this NCR until we prove it worked."

Your ISO 9001 audit will test this directly. Expect the auditor to ask about 2-3 closed NCRs from the past three months: "Walk me through the verification that this corrective action prevented recurrence." If your answer is sound, you pass. If you say "Well, we did the action and haven't seen that problem since," you've just revealed a system weakness that will be noted in the audit report.

In the next chapter, we'll address how to build the measurement and monitoring systems that feed defect detection in the first place—because the best NCR system in the world is useless if you're not catching problems before they reach customers.

ISO Continuous Improvement in Manufacturing: Moving Beyond Corrective Action to Proactive Performance Gains

Most Canadian manufacturers we work with have a corrective action system. What they don't have is a continuous improvement system that actually moves the needle on performance.

Here's the distinction: corrective action is reactive and backward-looking. Something went wrong, and you're preventing it from happening again. Continuous improvement is forward-looking and competitive. You're systematically raising the baseline — making things better than they were, not just less broken than they could be.

ISO 9001 Clause 10.3 requires you to establish, implement, and maintain a process for continual improvement. It doesn't specify *how*. That flexibility is intentional. But the vagueness creates a problem: many manufacturers interpret "continual improvement" as "doing corrective actions well." They don't. Corrective action is a subset of improvement, not the whole system.

The difference matters. In 2026, your customers — especially in automotive and aerospace — expect measurable year-over-year gains. Auditors (both internal and third-party) are looking for evidence that you're *intentionally moving the dial*, not just cleaning up messes. And your team needs a framework that doesn't feel like another bureaucratic requirement bolted onto their daily work.

This chapter walks you through building a continuous improvement system that integrates cleanly with your QMS, reduces external audit findings, and gives your operators and supervisors a legitimate voice in how work happens.