Test report validity periods in practice

By admin
The short answer

Customer and market requirements add a second layer — some buyers and schemes demand reports within twelve months regardless of stability. Know both layers: technical validity from change control, commercial validity from customer terms.

Key takeawaysRead detection limits and units before reading verdicts: a pass without understanding the limit it passed against is an assumption, not evidence. · Use accredited laboratories whose reports travel across borders, so one test program satisfies both the buyer's QA and the market's regulators. · Track substance-list updates as a routine, because candidate lists grow twice a year and a compliant bill of materials quietly ages out of compliance. · Retest on triggers — material changes, supplier changes, process changes — not on anniversaries alone, since risk follows change rather than calendars. · Test production-equivalent units drawn from bulk material, because golden samples prepared for the lab say nothing about what actually ships.

Validity management is change control with a calendar backup: triggers from the supply chain decide when evidence refreshes, while periodic reviews catch the slow drift that triggers miss. Either layer alone leaves gaps.

Third-party coordination matters because the factory's interests and the test's integrity pull in opposite directions. Independent sampling, independent custody, and independent lab selection are what make the final report bankable.

The buyers who spend least on testing per compliant shipment are rarely the ones who test least — they are the ones who scope precisely, sample representatively, and retest only on genuine triggers.

Why dates mislead

Market surveillance adds the enforcement dimension: authorities asking for evidence want recent, lot-linked documentation. A technically valid but ancient and unlinked report invites deeper scrutiny rather than closing the question.

Illustration: Why dates mislead Decorative illustration for the section "Why dates mislead"; visual only, carries no data.

A test report is a dated measurement of specific samples against specific limits. Its evidentiary power covers goods sharing the tested state — same formulation, same suppliers, same process, same regulated lists. Each divergence narrows the coverage; enough divergence voids it.

Substance-list growth is the silent ager: candidate lists expand twice yearly, and a report predating additions cannot evidence the new entries. Stable products need list-gap reviews even when nothing physical changed — the regulation moved while the goods stood still. Under the WTO TBT framework, solid conformity evidence is what keeps differing national regulations from becoming shipment-stopping surprises.[1]

The process, step by step

Reporting closes the cycle with results per homogeneous material against the applicable limits, plus the method references and detection limits that let a second lab reproduce the verdict. Buyers file the report against the purchase order and material batch, not in a general folder where lot traceability dies.

The cycle's timeline runs sampling-to-report rather than lab-days alone. Laboratory turnaround of five to seven working days is standard for routine scopes; the full cycle adds sampling, transit, and any clarification rounds — plan the order calendar from the cycle, not from the lab's bench time. When the calendar is tight, coordinating RoHS REACH testing in China close to the factory shortens the sample loop when a retest is needed.

Sampling opens the cycle and decides its value: units drawn randomly from finished or near-finished production, covering the color, material, and component variants the scope names. Factory-offered samples are declined in favor of independent draws, and the selection record notes quantities, positions, and witnesses. Factory acceptance testing applies the same logic at the source: verify the product against agreed criteria before it ships rather than disputing it after it lands.[2]

When to refresh

Review triggerFrequencyOwner
Candidate list updatesTwice yearlyBuyer compliance
Supplier change noticesPer eventFactory + buyer QA
Process change noticesPer eventFactory engineering
Stable-product confirmationAnnually rotatingBuyer QA

Assigning owners turns validity from a filing question into a managed routine with accountable hands.

Illustration: When to refresh Decorative illustration for the section "When to refresh"; visual only, carries no data.

Turning results into decisions

Share the relevant pages with the factory promptly with a written corrective request. Suppliers who see precise material-level findings fix precisely; suppliers who receive only pass or fail relitigate the verdict instead of the material.

Read material by material, not verdict first. A report-level pass can hide a borderline material that drifts over the limit with normal batch variation — and that material names the supplier conversation the buyer needs next.

Failures split into three commercial paths: contained substitution of the offending material with retest, lot-wide remediation where contamination spread, or rejection where the supply base cannot deliver compliance. The report's material breakdown, not its headline, chooses the path. RoHS thinking shapes the materials checkpoint: identify the homogeneous materials, know which restricted substances each one risks carrying, and test accordingly.[3]

Mixed-lot shipments need stratified sampling across the material batches, not a single convenient draw. One sample from a three-batch lot proves one batch; buyers who accept single-draw evidence for mixed lots buy uncertainty at testing prices.

Seasonal material substitutions — recycled content ratios shifting with commodity prices, coating suppliers rotating — are the quiet compliance killers. Change-notification duties in the purchase contract turn surprises into scheduled retests.

Report archiving by lot and material batch pays compound interest: customer complaints, market-surveillance queries, and supplier disputes all resolve in hours when the historical file is organized, and stall for weeks when it is not.

Timing note

Draw test samples the week production stabilizes, not the week it starts. Start-up output differs from steady-state output, and testing the learning curve measures noise instead of the lot.

Sources

  1. WTO: Agreement on Technical Barriers to Trade —— WTO portal for the TBT Agreement covering technical regulations, standards and conformity assessment.
  2. Wikipedia: Factory acceptance test —— Overview of factory acceptance testing performed before shipment or installation.
  3. Wikipedia: Restriction of Hazardous Substances Directive —— Overview of the RoHS directive restricting hazardous substances in electrical and electronic equipment.

Frequently asked questions

Can one report cover product variants?

Only variants sharing the tested materials and processes — colors using identical compliant coatings, sizes from the same compounds. Variants with distinct materials need their own material-level evidence; family coverage must be reasoned per material, not asserted per product line.

Is there a standard validity period for RoHS or REACH reports?

No universal regulatory expiry exists — validity follows change control. Commercial practice commonly treats twelve months as a refresh horizon for active products, with earlier refresh on any material, supplier, process, or list change. Check customer contracts for stricter terms.

What voids a report immediately?

Any change to the tested state: reformulation, supplier or sub-supplier switch, process chemistry change, or new regulated substances covering the product's materials. The report still evidences the old state — which no longer ships.

How should stable products be handled?

Annual confirmation testing on rotating materials plus list-gap reviews each time candidate lists update. Full-scope annual reruns of unchanged stable products waste money; targeted confirmation sustains the file at a fraction of the cost.