Supplier Corrective Action Closure

A supplier ships a batch with the wrong label. The customer contains the stock and asks for a corrective action.

A closure metric should not treat the supplier's first apology as proof the underlying cause is fixed. SMA publishes a supplier corrective action procedure describing containment, root cause, action and closure, and Lockheed Martin has a supplier response guide with its own requirements.

These are buyer-specific examples, not universal deadlines. Define the request population to include formal corrective action requests issued in the period, and state whether minor supplier complaints are tracked separately.

Set a closure rule, since a complete response, implemented fix and verified effectiveness can be different milestones and each stage should be recorded. Contain immediate risk by identifying affected lots, stopping use when needed and protecting customers, because waiting for a root-cause report should not delay immediate control.

Describe the nonconformity with item, lot, specification, evidence and date, since a vague quality concern may lead to an equally vague answer. Ask for a root cause by asking why the process allowed the defect and why controls failed to catch it, and avoid treating operator error as an endpoint without evidence.

Agree the action, linking the proposed fix to the identified cause, because a training note may not solve a flawed label template, and assign separate dates for response due, implementation due and effectiveness review, since a single deadline can hide an unfinished verification period. Preserve supplier evidence such as revised procedures, sample test results and training records, sharing only what the contract permits.

Verify implementation, because a supplier saying done is not necessarily evidence that the line uses the new control, so request an appropriate sample or audit, and check effectiveness later, since several subsequent lots may be needed to show that the problem did not recur and certainty should not be claimed from a single good sample. Distinguish overdue from open, as a request can remain open within an agreed plan while an overdue one needs escalation, and show both counts.

Handle rejected responses by recording why a root cause or action was inadequate and when the revised response is due, without quietly resetting the original clock. Calculate a rate by cohort, counting eligible requests due for closure in the period or requests opened in a mature cohort, state the denominator, and track age, because the oldest open high-risk request may matter more than the average closure rate, so pair metrics with severity.

Escalate repeated failures, consider sub-suppliers whose earlier defect the direct supplier should coordinate, keep commercial and quality decisions separate since a credit or replacement does not prove recurrence prevention, and review recurrence by reopening or linking a new case if the same defect appears after closure. Use risk-based verification, avoid artificial closure because closing cases when a reporting month ends gives a flattering rate while leaving risk unresolved, share lessons internally since receiving checks, specifications or forecasts may also contribute, document final approval by a named quality owner, review the contract for agreed stages and times, and remember that for owners closure is a measure of verified problem solving, not just response speed.