01Set a clear trigger and owner
Use the process for safety-significant symptoms, repeated defects, major specification failures, wrong configurations, traceability gaps or an inspection escape that could recur. Name one buyer owner and one supplier owner. Set response dates by risk and operational need rather than using the same deadline for every issue. A routine one-off cosmetic allowance may need a concession record, not a full corrective action.
02Describe the nonconformity without blame
Record the SKU, model, revision, purchase order, lot or date code, sample size, affected quantity and where the issue was found. Cite the exact specification, approved sample or order requirement that was not met. Add measurements and labeled photos when useful. Replace vague statements such as “bad quality” with an observable gap another person can reproduce.
03Contain current exposure first
Before debating cause, identify stock at the supplier, sub-supplier, consolidation warehouse, carrier, buyer warehouse and customer channel. Define quarantine, sorting, rework, replacement or shipment-hold decisions for each location. Record who authorized the action, the method used, quantities checked and resulting disposition. Containment protects the current order; it is not the corrective action itself.
04Separate occurrence from escape cause
Ask why the defect was created and why the control system did not detect or prevent it. Follow facts through material, machine, method, measurement, environment, instructions and handoffs without forcing a preferred diagram. “Operator error” is incomplete unless the review explains what condition allowed the error and why existing training, fixtures, limits or checks failed to control it.
05Choose actions that change the system
Link each verified cause to an action, owner, due date and completion record. Depending on the finding, an action may revise a fixture, parameter limit, work instruction, incoming control, mistake-proofing step, maintenance rule, measurement method, software version or approval gate. Training can support a change, but retraining alone rarely proves that the system now prevents recurrence.
06Control side effects and versions
Review whether the fix changes product function, appearance, materials, dimensions, firmware, tooling, process, packaging, claims, test coverage or destination evidence. Route affected changes through the agreed approval process before use. Update the purchase-order attachment, inspection checklist and approved reference together so the next order does not quietly revert to an obsolete version.
07Verify completion and effectiveness
Completion evidence shows an action happened; effectiveness evidence shows the problem stayed controlled. Check the revised record, first output after change and defined later lots or time window. Use measurements and a planned inspection method where applicable. Reopen the request if the symptom returns, a related defect rises or the action was implemented differently from the approved plan.