Supplier corrective action requests: raising one, judging the reply, closing it properly

Deciding which events justify a formal request

Raising one for every discrepancy trains the supplier to treat them as paperwork, and floods your own follow-up capacity. Reserve the formal route for defects that reached your line or your customer, repeats of a previously reported issue, anything affecting a designated significant characteristic, evidence of an unnotified process change, and shipments with missing or false documentation. Handle single trivial discrepancies through the rejection note and track them, so that recurrence promotes them automatically. Writing the criteria down protects the engineer who has to explain to a buyer why a valued supplier is receiving one.

What to include so the reply can be useful

Send the physical evidence or clear images of it, the affected lot identifiers and quantities, the exact requirement breached with its drawing revision or specification reference, and the immediate impact on your operation. State separately what containment you need and by when, and what you expect from the investigation. Suppliers frequently return a poor response because the request described a symptom without a boundary — no lot codes, no quantities, no reference to what was measured and how — leaving them to guess which of their production is implicated. Name the person on your side who will judge the response, so it does not arrive addressed to a mailbox.

Recognising a weak response before you file it

Three patterns account for most inadequate replies. The cause is attributed to operator inattention with a promise of retraining, which explains nothing about why the system allowed it. The containment covers their finished stock and ignores material already in transit or held at your site. Or the corrective action is an additional inspection step, which detects rather than prevents and quietly adds cost that will be recovered from you later. Ask what changed in the process, the tooling, the setup or the specification, and treat added inspection as an interim measure with an expiry.

Escalation that changes behaviour rather than temperature

When responses stall or a defect repeats, escalation should move up their organisation, not increase the volume of yours. A defined ladder helps: engineer to engineer, then a request for a dated recovery plan signed by their site management, then controlled shipping where product is verified and certified before dispatch at their cost, then involvement of the commercial relationship and a hold on new business. Each step should be announced in advance with the exit condition stated, because escalation without a route back becomes punishment and produces defensiveness rather than engineering effort.

Closure, cost recovery and what each does to the relationship

Close on evidence from production after the change, not on the plan to make it, and record what you accepted so the next occurrence can be judged against it. Cost recovery is a separate decision with its own consequences: chargebacks for sorting, line stoppage and expedited freight are legitimate, and they also reliably shift the supplier's attention from engineering the fix to disputing the invoice. Quantify the loss regardless, then choose deliberately whether to recover it or trade it for engineering commitment, and make sure the same person is not doing both.

Frequently asked questions

How fast should a supplier respond to one?

Containment within the working day for anything that can stop your line or reach your customer, an initial investigation summary within days, and the verified permanent fix once production evidence exists. Setting a single deadline for the whole response encourages a rushed cause statement to meet it. Separating the containment clock from the investigation clock gets you protected quickly while still allowing the engineering work to be done properly.

Should we charge a supplier for the administrative effort of processing a rejection?

Standing charges per rejection are common and they are blunt. They recover some genuine cost and they also generate arguments over trivial events, and can push a supplier towards hiding marginal discrepancies rather than declaring them. If used, publish the schedule in advance, apply it consistently, and keep it separate from recovery of real damages such as sorting labour or a stopped line, which should be evidenced case by case.

What if the supplier says our drawing or specification caused the defect?

Test the claim seriously, because it is right more often than people expect — ambiguous tolerancing, an unstated surface requirement, a datum scheme that cannot be fixtured, or an acceptance criterion described only in words. If they are right, the corrective action belongs on your engineering process, and you should say so in writing. Suppliers who are overruled on a legitimate technical objection stop raising them, which costs you far more than the original defect.