A case-based corrective-action framework that converts defect signals into containment, validated root-cause elimination, effectiveness evidence, and reusable manufacturing controls.
CAP should be triggered by risk, recurrence, customer impact, or a measurable failure of process readiness—not by presentation preference.
Pilot or production quality performance exceeds the approved defect-rate threshold.
Safety, compliance, critical function, or major customer requirements are at risk.
The same defect returns after a prior action, showing that the cause or control was not eliminated.
A Poka-Yoke, inspection control, reaction plan, or process gate fails to protect the output.
The process cannot repeatedly hold the required performance window.
Complaint, rejection, audit finding, or field feedback indicates a systemic issue.
Scroll through the cards. Each stage builds on the previous one, and the next stage should not begin until the current output is clear.
Start from a measurable deviation: defect rate, complaint, repeat issue, control failure, or readiness-gate miss.
Protect current output before investigating the full cause. Stop, segregate, inspect, rework, or hold affected material.
Describe what failed, where, when, how much, and against which approved requirement. Avoid cause language at this stage.
Reconcile the denominator, confirm defect quantities, remove category overlap, and use Pareto to focus on the vital few.
Use 5-Why, process comparison, trial evidence, capability data, or controlled testing. Do not stop at operator error.
Separate immediate correction from corrective action and future prevention. Assign an owner, due date, acceptance criteria, and required evidence.
Confirm the action during pilot or production. Verify recurrence, capability, defect trend, and correct execution at the shopfloor.
Transfer the learning into PFMEA, Work Instructions, Control Plans, Poka-Yoke, training, NPI gates, and the lesson-learned library.
A CAP can fail before root-cause analysis begins when the rate basis and Pareto basis are mixed together.
In the reference case, the top two defect groups represented 70.9% of all nonconforming units.
Protect the customer and current output while the real cause is still being investigated.
Repair, replace, or rework the specific nonconforming output already created.
Remove the verified root cause from the current process and project.
Convert the learning into a reusable rule that protects future projects and production.
Pareto analysis identified two priority branches. One branch came from incomplete process readiness. The other came from uncontrolled manual variation. Both required different corrective and preventive actions.
A CAP is closed only after implementation, objective verification, and system transfer are complete.
Add the missed failure mode or strengthen the existing control.
Update the method, frequency, limits, reaction plan, and ownership.
Replace manual judgement with fixtures, sensors, interlocks, or automation.
Convert the failure into a mandatory readiness or release gate.
Reuse the verified learning in the next relevant product or process.
“A corrective action becomes governance when the next project is protected before the defect returns.”
See how risk is identified through PFMEA and translated into built-in prevention through Poka-Yoke.