Skip to content
Spoiled Ratten Spoiled Ratten Brooklyn · Est. 2019

Test report validity periods (batch 2 guide 3)

The short answer

Declarations of compliance are only as credible as the test evidence behind them, and regulators increasingly ask to see that chain. This guide shows how to link each declaration to specific reports, keep the evidence current as formulations change, and use accredited testing so the paperwork travels across borders. Treat the file as a living record, not as a one-time certificate.

Key takeawaysRetest when formulations, suppliers, or processes change rather than on a fixed calendar alone, since composition follows inputs, a step that matters because restricted substance rules limit specific materials in electrical and electronic products[1]. · Keep pre-production and mass-production samples clearly separated in the file, because only the latter represents what consumers receive, a logic familiar from acceptance testing practice, where agreed criteria decide pass or fail before shipment[2]. · Check that the laboratory method matches the applicable regulation for your market instead of accepting a generic migration screen, a discipline reflected in quality management vocabulary, where documented processes replace ad hoc judgments[3]. · Control sample custody from carton to laboratory bench, since an unsealed sample invites questions no report can answer, a step that matters because restricted substance rules limit specific materials in electrical and electronic products[1]. · Scope each test to the exact material, food type, and use condition, because migration results only mean something under defined conditions, a logic familiar from acceptance testing practice, where agreed criteria decide pass or fail before shipment[2].

Migration testing looks technical from the outside but rests on buyer decisions that require no laboratory background: choosing the right sample, stating the use conditions honestly, and keeping the paper chain intact. Laboratories execute brilliantly when instructed precisely and merely adequately when instructed vaguely. This guide focuses on the instruction side, where buyers control the outcome.

The most common instruction failures are familiar across categories: pre-production samples presented as representative, use conditions understated to ease limits, and custody gaps that let anyone question the result. Each has a simple preventive routine described below. None of them costs money; all of them save it.

Readers under shipment pressure should start with the scoping and custody sections, which resolve most urgent cases, then adopt the tracking routine for the longer term. Substance requirements evolve and supplier formulations drift, so a file that was complete last year may be thin today.

Making declarations traceable to evidence

A declaration of compliance is a claim that points to evidence, and the pointing must be explicit: report numbers, dates, materials, and methods listed or directly referenced. Restricted substance rules explain why buyers test at all: certain materials are limited in electrical and electronic products, so composition evidence belongs in the file.[1] Declarations that gesture vaguely at testing history fail the first serious document review, regardless of how good the underlying reports are. Precision in referencing costs minutes and saves shipments.

Each product-to-material-to-report link should survive staff turnover, which means writing it down where successors will look rather than keeping it in someone's memory. The engineers at UTS Inspection check the test scope against the materials and use conditions before booking laboratory time. A simple mapping table maintained per product family serves this purpose for years with minimal upkeep.

Change control completes the chain: formulation tweaks, supplier switches, and process changes should trigger a review of affected links rather than silent aging. Acceptance testing practice follows the same logic: agree the criteria first, test against them, and let the result decide whether the goods move forward.[2] Flagging the affected declarations at the moment of change keeps the file honest without requiring constant full retesting. The discipline is administrative, but it is what separates credible files from decorative ones.

Where food contact budgets go wrong

Decision pointWhat to checkTypical evidenceNext action
Detection limitsLimit of detection versus thresholdMethod details from the laboratoryUse a more sensitive method if needed
Sample originPre-production versus mass productionSampling note with carton numbersRedraw from packed cartons
Declaration linkageReports referenced with datesMapping table product to reportsRepair references before shipping
Change controlFormulation or supplier changesChange log and supplier noticesRetest affected materials
List currencyPanel against current requirementsDated panel versus current listsExtend the panel this round

Use the matrix as a pre-booking checklist: any row without evidence becomes a scope item rather than an assumption.

Illustration: Where food contact budgets go Decorative illustration for the section "Where food contact budgets go"; visual only, carries no data.

From use description to linked declaration

  1. Schedule the next reviewSet retest triggers for supplier changes, formulation tweaks, and elapsed time so the file stays current. Pre-agreed triggers remove debate from busy weeks.
  2. Describe the use honestlyWrite down the food type, contact time, and temperature for the reasonably foreseeable worst case. Honest inputs let the laboratory choose simulants and exposures that the report can defend.
  3. List contact materialsMark every material with food contact on the bill of materials, including seals, coatings, inks, and adhesives. Components that look incidental often dominate migration results.
  4. Confirm method and marketCheck that the proposed method serves the regulation of your destination market rather than a generic screen. Method-market mismatches produce elegant but irrelevant reports.
  5. Draw production samplesTake specimens from packed mass-production cartons with custody notes recording the source. Pre-production samples describe intent; only production samples represent consumer exposure.

Why good products ship with thin paperwork

Update tracking is the maintenance contract for the whole compliance file: regulations add substances, lower limits, and refine methods while products sit unchanged. Restricted substance rules explain why buyers test at all: certain materials are limited in electrical and electronic products, so composition evidence belongs in the file.[1] A routine that maps list updates against the bill of materials converts regulatory drift into scheduled tasks. Without it, the file silently expires and the discovery moment is always inconvenient.

Illustration: Why good products ship with thin Decorative illustration for the section "Why good products ship with thin"; visual only, carries no data.

Prioritization keeps the routine affordable: high-attention substances, food-contact-critical components, and products in strictly enforced markets lead the review queue. Acceptance testing practice follows the same logic: agree the criteria first, test against them, and let the result decide whether the goods move forward.[2] Stable inputs from well-controlled suppliers follow on a lighter cycle rather than escaping review entirely. The written schedule matters more than its exact intervals, because unwritten schedules evaporate under workload.

Retest triggers should be defined in advance so decisions stay consistent across team changes: supplier switches, formulation tweaks, process changes, and elapsed time since the last round each get their threshold. Quality management vocabulary frames this as process control: documented steps, clear responsibilities, and records that allow the next reviewer to retrace the decision.[3] Pre-agreed triggers remove debate from busy weeks and give suppliers predictable expectations. The file then shows a system working rather than a series of improvisations.

A reminder before the file closes

Keep the product-to-report mapping current enough to survive staff turnover. If a successor cannot trace each declaration to dated reports within an hour, the file is decorative rather than functional.

Sources

  1. Wikipedia: Restriction of Hazardous Substances Directive —— Overview of the RoHS directive restricting hazardous substances in electrical and electronic equipment.
  2. Wikipedia: Factory acceptance test —— Overview of factory acceptance testing performed before shipment or installation.
  3. Wikipedia: ISO 9000 —— Overview of the ISO 9000 family of quality management standards.

Frequently asked questions

How should declarations of compliance reference test evidence?

Explicitly, with report numbers, dates, materials, and methods listed or directly referenced so a successor or inspector can trace each claim within an hour. Vague gestures at testing history fail serious document review. A maintained mapping table per product family serves for years.

When does a formulation change require retesting?

Whenever the change could plausibly move migration or composition results for the affected materials: new suppliers, adjusted formulations, different coatings or inks, and process changes all qualify. Log the change, assess the affected links, and retest those specifically rather than the entire file.

How should laboratories be briefed for useful results?

Share complete product information upfront: materials, use conditions, target markets, and the regulation you aim to satisfy. Competent laboratories question mismatched scopes when fully informed. Thorough briefing converts laboratory expertise from a purchased commodity into genuine collaboration.

What custody practice supports defensible reports?

Sealed bags, clean tools, carton-identified specimens from finished production, and a note recording sampler, date, and transit path. Composite across cartons for heterogeneous lots. These habits cost little and remove challenges that analytical excellence cannot fix.