Nonconforming Sample: The Corrective-Action Evidence to Request From a Supplier
Start with the record, not the reassurance
When a sample does not meet the requirement, ask the supplier for a written corrective-action record for that sample: what deviated, what scope of production is covered, what they assessed as the cause, what specifically changes as a result, and what evidence exists that the change was checked. A sentence such as "we will do better next time" cannot be reviewed, compared with your own inspection notes, or carried into the next order. A record can.
The important limit to hold from the first minute: this record describes one nonconforming sample and the response to it. It is not a commitment that the next sample or shipment will conform, and it is not a certificate of any kind.
Separate the three things that get blurred together
A single paragraph of reply usually mixes three different kinds of statement, and they deserve different weight:
- Observation — what was actually found, which you can photograph and measure.
- Explanation — why the supplier believes it happened, which is a hypothesis until it is tested.
- Change — what is different afterwards, which should be identifiable as a specific revision, setting, tool, instruction, material lot or inspection step.
Asking for these as separate fields is what turns a reply into evidence. If the supplier sends one blended sentence, the polite follow-up is to ask which sentence is the observation, which is the cause, and which is the change.
The corrective-action evidence worksheet
Use the table below as a blank worksheet. Fill the middle column from the supplier's reply and keep your own notes in the right-hand column. Leave a field marked open rather than guessing an answer for it — an open field is information too.
| Field | What you are asking the supplier to enter | Gap worth watching for |
|---|---|---|
| Sample identification | ||
| Requirement the sample was checked against | ||
| Observed deviation | ||
| How the deviation was measured or observed | ||
| Scope: which lots, tooling, shift or production window this record covers | ||
| Root cause as stated by the supplier | ||
| Containment: what happens to items already produced | ||
| Corrective action: what specifically changes | ||
| Verification: how the change was checked, and by which role | ||
| Open items the supplier has not resolved | ||
| Date of record and the role that authorised it |
A useful discipline: if a field cannot be completed by the supplier, ask them to write "not available" instead of leaving it empty, so the gap is visible to everyone reading the file later.
Suggested wording for the request
The following is an editorial suggestion for how to phrase the ask, not a contractual or legal requirement:
Please send the corrective-action record for sample [your sample ID], covering the observed deviation, the scope of affected production, the root cause as you assessed it, the change made, and the evidence that the change was verified. If a field is not available, please state that rather than leaving it out; we will record it as an open item.
Two further suggestions that tend to help: ask for the record in writing and in the language your own team will quote internally, and ask which parts of the record the supplier treats as confidential before you circulate it.
Reading the reply: what a thin record looks like
These are patterns to notice in an answer, not accusations:
- "We will strengthen inspection" adds checking but does not change a cause, so the same deviation can still be produced and then caught — or missed.
- A cause stated as operator attention or care, with no change to the process, leaves the process able to reproduce the deviation.
- No scope statement means you cannot tell whether items already made are affected.
- Verification written only as "checked and acceptable", with no method and no result, cannot be reviewed by anyone.
- A record that covers a different sample, part or lot than the one you sent is a record about something else.
None of these proves bad faith. Each one means the record does not yet let you make a decision, and the honest next step is to say which field is still open.
Keep your own side of the file
Retain the sample, your photographs, the requirement you checked it against, and the method you used to measure it. When your record and the supplier's record disagree, that disagreement is the finding worth resolving first — before any discussion of the next order, a price, or a schedule.
What this record does not do
- It does not certify the supplier. A screening result — a document review returned on a brief, a profile entry, a directory listing — summarises what was found in the material provided. It is not certification, not an audit, and not a qualification, and it does not confirm that a corrective-action record exists for your sample.
- It does not predict the next result. Corrective action taken on one deviation is evidence about that deviation.
- It is not covered by a delivery term. Incoterms® rules quoted on a quotation allocate delivery responsibilities and risk between buyer and seller in a sale; they do not describe product quality and they do not describe payment terms. Reading a delivery term as a quality commitment is a category error.
- A standard name is context, not evidence. ISO publishes an official overview of ISO 9001 in the area of quality management. That is background for the vocabulary used in these conversations, not evidence about your supplier's documentation; ask the supplier for the records that apply to your part and your sample rather than inferring them from a reference to a standard.
This article is a commercial documentation suggestion. It is not legal, customs or regulatory advice.
Next action for this sample
Put the worksheet, photographs, acceptance requirement and supplier reply into one evidence packet. Mark each field confirmed, supplier-stated or still open. The on-site Sourcing Desk tool can prepare your notes locally; it does not send them or arrange a review. A further order needs your case-specific decision.