Key takeaway
A corrected batch and a changed process answer different questions. Define the follow-up population and criterion before calling a systemic action effective.
Make the recurrence question operational
A quality manager needs to know whether an action changed the process responsible for a defined nonconformance. A record of sorting suspect units may establish containment, while a new fixture or instruction may address the recurring condition. Decide which failure mechanism, process and population the effectiveness claim covers before assembling historical forms. A closure total cannot supply those boundaries.
ASQ distinguishes correction of the immediate unit or lot from corrective action addressing a cause, then describes a later data-based effectiveness check. NASA’s product-verification guidance records discrepancies against requirements for follow-up. These are useful technical references for an original review method. This guide does not set a regulatory CAPA requirement, certification rule or appropriate safety threshold for any actual manufacturer.
A prospectively defined effectiveness record
This hypothetical quality action Q12 addresses reversed loading on fixture F2 for product family P. The team segregates a suspect lot, investigates the mechanism and changes the fixture. Before examining follow-up, it defines a local check covering the next three production lots on F2 using the same product revision, with all recorded loading failures and inspection coverage retained. Its invented criterion is no recurrence in that bounded check.
The first two lots supply complete inspection records without the defined recurrence. The third lot used an unapproved-in-the-scenario alternate fixture and has incomplete records. The completed decision is that the planned test is unfinished. The team does not report three clean lots, rewrite the third as F2 production or use the lack of a complaint as a substitute for the required observation.
| Review field | Completed illustrative entry | Consequence |
|---|---|---|
| Mechanism / process | Reversed loading; fixture F2; product P revision A | Pin scope of the systemic claim |
| Containment | Suspect lot segregated under separate disposition | Containment recorded; not effectiveness |
| Implemented action | Fixture change X4 linked to Q12 | Record change and incorporation evidence |
| Planned population | Next three F2 lots, same revision; complete inspection coverage | Define evidence before inspecting results |
| Observed population | Two qualifying lots; third on alternate fixture with gaps | Planned population not completed |
| Decision | Effectiveness review remains open | Assign replacement observation and assess scope change |
Keep the exposure denominator
Count the inspected units or opportunities within each qualifying lot, not just the number of signed forms. State how much exposure was actually observed after the change and which conditions remained the same. Three small lots can mean much less operating exposure than one large lot. A review needs that context even when its local closure rule is lot-based.
In Q12, the manager records 200 inspected units in each of the first two lots: 400 qualifying observations. The third contains 150 units outside the chosen fixture scope, with 30 lacking the specified inspection record. Those facts do not justify describing 550 fully observed units on F2. The example’s counts are invented and support only its bounded record decision, not a statistical demonstration that recurrence is impossible.
The proposed review also records why observations were excluded. Recovering the third lot’s thirty missing inspections would improve that lot’s own evidence, but would not make its alternate-fixture exposure qualify as F2 observations. Likewise, the 120 retained inspections from that lot should not raise the F2 denominator from 400 to 520. Keep both the applicability reason and the coverage reason, so fixing one does not conceal the other. When the responsible owner defines a separate alternate-fixture review, give it its own population and conclusion rather than silently combining it with Q12’s existing check.
Treat a changed process as a changed test
Write a scope-change rule before follow-up starts. A new supplier, fixture, product revision, shift pattern or inspection method may change whether an observation belongs in the planned population. The responsible quality owner should decide whether to exclude it, extend the window or design a separate review. Record the decision and reason; do not let the export filter settle the technical question silently.
For the illustrative alternate fixture, the team preserves its actual records, creates a separate applicability question and seeks a third qualifying F2 lot. It also checks whether X4 should apply elsewhere. That second question is not answered by the F2 effectiveness result. A source archive can honestly contain a completed local review and an open broader action; merging them into one success label would erase the useful distinction.
Make the claim narrower than the dashboard
When review finishes, retain the chosen mechanism, implemented change, actual exposure, observation window, exceptions and approving role beside the conclusion. State what was examined and what was outside scope. A bounded clean follow-up can support the stated local decision without establishing a permanent zero-failure rate. Preserve later related nonconformances so the conclusion can be reconsidered using the same mechanism definition.
Use readiness to assign missing observation and due diligence to ask whether an evaluator needs process-level follow-up or merely form content. An initial description can communicate how these layers connect without distributing complaint text, confidential fixture details or staff information. The useful handoff is a recurrence-review record with its limits. A named introduction, real sample and license remain separate permissions; the quality decision does not grant commercial reuse.