Retest workflow after rohs reach testing failure: part 6
A retest that must convince an absent buyer needs more than good numbers; it needs a traceable chain from the failed lot through the correction to the verified result. This guide shows how to assemble that chain with documented processes and accredited evidence, so the passing report closes the episode instead of opening new questions.
Key takeawaysA buyer-facing retest must argue its own credibility through linked records, not through a lone passing report. · Documented processes with defined responsibilities turn a retest from an event into verifiable evidence [1]. · Accredited results travel across borders because competence frameworks behind them are mutually recognised [2]. · Name the cause, record the correction, and witness the sampling before the laboratory ever sees the retest pieces. · Keep the failed report in the file: a complete failure-to-fix story reads stronger than a solitary pass.
Some retests need to do more than satisfy the engineering team; they must convince a buyer who was not present for any of it. That buyer reads the file looking for gaps: Was the sample representative? What changed since the failure? Who verified the change? A bare passing report answers none of these questions, so sceptical buyers default to holding the order. The retest file must argue its own credibility.
Credibility comes from structure, not from adjectives. A file that links the failed report to a defined lot, a named cause, a recorded correction, a witnessed sampling, and an accredited verification tells a closed story. Each link is a document, and each document answers one objection before it is raised. Building that chain is the subject of this sixth part of the retest-workflow series.
Two bodies of background knowledge support the approach: the discipline of managing quality through documented processes and continual improvement, and the international framework that makes accredited laboratory results mutually trusted [1] [2]. Neither replaces the laboratory work; both decide how the laboratory work is received.
What the sceptical reader looks for
Read your own file as a buyer who trusts nobody. The first question is scope: which lots does this file cover, identified by codes a warehouse can actually find. The second is causation: which material and substance failed, and what entry point the investigation named. The third is correction: what changed, in which document, effective on which date. The fourth is verification: who drew the retest samples, from which population, under what identification. The fifth is competence: which laboratory, under what accreditation, using which methods.
Files fail this reading in predictable places. Scope is described as recent production instead of named lots. Causation is described as supplier issue without naming the supplier, the material, or the mechanism. Correction is described as improved control without a revised document. Sampling is undescribed. Accreditation is asserted without a scope page. Each gap converts a potential approval into a follow-up email, and follow-up emails convert into delayed shipments.
The remedy is to draft the file against this checklist before the retest is booked. If any of the five questions lacks a documentary answer, the investigation is not finished. Laboratories test samples; files convince buyers. Both halves must be ready before either is final.
Documenting the process the quality way
Quality management discipline treats the failure-to-retest cycle as a controlled process with inputs, activities, outputs, and records. The failed report is an input. Containment, investigation, correction, and sampling are activities with owners and criteria. The passing report and the updated control documents are outputs. At each handover, a record captures what was decided and on what evidence. This is ordinary process thinking, and it is what separates a defensible file from a folder of PDFs.
The standard references on quality management describe exactly this architecture: processes defined and controlled, responsibilities assigned, and improvement driven by evidence [1]. Applied to a retest, the architecture is lightweight: one page naming the episode owner, one sampling plan, one correction record, one verification note. Small documents, rigorously linked, outperform thick files with no thread.
Version control deserves emphasis because corrections so often evaporate. A revised work instruction needs a version number and an effective date; a supplier commitment needs a dated letter with lot scope; a segregation arrangement needs labelled locations and valid dates. When the UTS team audits a retest file, these dated links are what get checked first, because undated claims cannot be verified against production reality.
Making the laboratory half travel
Even perfect factory records cannot rescue a weak laboratory half. The laboratory must be competent for the specific substances and matrices, the methods must suit the thresholds, and the sampling chain must reach the laboratory intact. Accreditation is the buyer's shortcut for judging competence at a distance: an independent body has assessed the laboratory against international criteria, and mutual recognition arrangements let that assurance cross borders [2].
Sellers should verify scope rather than assume it. Ask the laboratory which methods on the quotation sit inside its accredited scope and request the scope schedule. Confirm that detection limits suit the thresholds being judged and that the report will identify the sample, the method, and any deviations. These questions cost nothing at quotation stage and are nearly impossible to fix after results arrive.
Chain of custody completes the laboratory half. The sampling note should let a stranger match the laboratory's sample description to the factory's held lots: matching identifiers, matching quantities, matching dates, and a named sampler. Sealed, labelled, and documented samples survive buyer scrutiny; anonymous pouches do not. Photograph the sealed samples before dispatch and file the courier record with the report.
Assembling the file so it reads itself
| File section | Contents | Answers which doubt | Typical omission |
|---|---|---|---|
| Episode cover | Product, lots, dates, owner, timeline | What exactly are we talking about | Undated narrative with no lot codes |
| Failure record | Failed report plus plain reading of material and margin | What failed and by how much | Hiding the failed report |
| Containment note | Held lots, locations, quantities, release criteria | Did suspect goods leak meanwhile | Verbal hold with no record |
| Cause and correction | Named entry point, revised documents, supplier letters | What changed and since when | Claimed improvement, no document |
| Verification | Sampling note, lab report, scope page, custody photos | Why should I trust this pass | Anonymous sample, no scope page |
Presenting the outcome honestly
How the outcome is described matters. A passing retest on a defined corrected lot means exactly that: the defined lot, in its corrected state, met the tested limits. It does not mean the supplier is permanently cured, the process is incapable of recurrence, or unrelated lots are covered. State the conclusion with its boundaries, and the file gains authority precisely by refusing to overclaim.
Where residual risk remains, say what controls it. Perhaps incoming batches of the implicated material now require supplier declarations plus periodic verification. Perhaps a second-source pigment is approved only after first-article testing. Preventive controls with owners and frequencies turn a closed episode into a stronger system, which is the improvement loop quality thinking expects [1].
Finally, close the episode formally: record the disposition of held stock, the release authority, and the date. Informal releases undo formal investigations. A signed closure note, filed with the verification report, lets the business move on without leaving the file open to reinterpretation months later.
Sources
- Wikipedia: ISO 9000 —— Overview of the ISO 9000 family of quality management standards.
- ILAC: International Laboratory Accreditation Cooperation —— ILAC homepage describing the international cooperation on laboratory and inspection body accreditation.
Frequently asked questions
What does quality management have to do with a single retest?
Quality management thinking requires that processes be defined, controlled, and improved on evidence rather than assertion. In a retest context that means written sampling plans, identified lots, recorded corrections, and verified results. Buyers trust files built this way because every claim has an attached record.
How do I verify a laboratory's accreditation covers my test?
Ask for the accreditation certificate and its scope schedule, then check that the specific test methods appear in the scope. General accreditation of the laboratory is not the same as accreditation for your substance-matrix combination. Keep the scope page in the file next to the report.
Is a passing retest enough without a confirmed root cause?
No. A retest that passes while the cause is unknown leaves the mechanism free to recur in the next lot. Buyers know this, which is why they ask what changed. If the investigation genuinely cannot name the cause, say so, widen the scope, and apply preventive controls across all candidate entry points rather than claiming a fix.
Should the original failed report stay in the file?
Keep the failed report, because it defines the scope of the episode. Discarding it suggests the history is being curated. A complete file with a failure, a documented correction, and a passing verification reads as competence; a file with only a pass reads as luck.