What to do when a sample fails
A failed sample is the cheapest failure in the whole order, because nothing has been committed and the factory still has every reason to fix it.
- The sample is a test of the specification, not a verdict on the factory.
- If two people can read the specification differently, the specification is the fault, not the sample.
- A second sample is cheap; a first production run against an ambiguous specification is not.
First: a failed sample is the cheap failure
Nothing has been committed. The tooling has not run, the deposit has not moved, and the factory still has every reason to make the second attempt work. Compare that with the alternative — discovering the same problem on a production run — and the sample round looks like what it is: the cheapest inspection in the order.
So the productive question is not accept or reject. It is what did this tell us.
Diagnose before you decide
A sample fails for one of three reasons, and they have three different responses.
| Cause | What it looks like | What to do |
|---|---|---|
| The specification was ambiguous | Two people read it differently and both are right | Fix the specification. This is the most common cause and the only one worth fixing before anything else. |
| The sample is outside the specification | The specification is clear and the sample misses it | Reject against the named field. This is the case where a factory has to re-run it. |
| Neither — the specification was wrong | The sample is correct but the product is not what you wanted | Change the specification, not the factory. This is a design change and it is normal. |
Only the second row is a factory problem. Moving factory in the first or third row reproduces the same failure with a new supplier and a new lead time.
The three questions that turn a rejection into a fix
- What did the specification say? Read the wording, not your memory of the intention. If the field was not written down, it was not specified.
- What did the sample do? Measure it against the tolerance, not against a feeling. A "slightly off" color is not a finding; a color outside a stated standard under a stated light is.
- Which of the two is wrong? Write the answer down. That sentence is the change to the specification, and it is what the second sample is built from.
What a sample cannot tell you
This is the part that catches buyers who approve quickly, and it is the reason our own records carry a field list rather than a photograph.
A sample confirms only what it tested. It does not confirm:
- a fall rate at a stated water temperature
- a salt-spray standard on the hardware
- whether a strand or a skirt survives a full carton
- whether the tolerance holds on the two-thousandth piece
- whether the pack survives the same carton
Those are all specification lines, and every one of them is checkable — just not by looking at a sample. The sample-to-production gap is the term for exactly this, and it is on this site because it is the failure mode that survives a normal quality conversation.
The field guide for the second round
Before the second sample, add these to the specification if they are not already there:
- [ ] The tolerance band for every dimension, in mm or grams
- [ ] The color standard and the light it is checked under
- [ ] The test method for anything behavioural: fall rate, tracking, buoyancy
- [ ] The salt-spray standard and hours for every metal part
- [ ] The pack, and what the product looks like after a full carton
A second sample made against those is a different document from the first one. That is the whole point of a failure.
Where to go next
- Where programmes go wrong — the four failure modes and the control for each
- How to compare two factory quotations
- What a QC record should contain — the fields to ask for before the next run
- From sketch to tooling — why a change after the mould is cut resets the programme
- A first order from China, step by step
- The specification builder
- Send a specification
