Skip to content
Mission nominal

Test report validity periods (batch 2 guide 2)

Last pass12 min ago
Median latency78 min
Tiles served today2.41M
By admin Spica Space
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 takeaways

  1. Read detection limits before celebrating a pass, since a non-detect above the regulatory threshold answers nothing, a connection buyers recognize from CE marking practice, where conformity evidence supports the marking decision[1].
  2. Link every declaration of compliance to the specific reports behind it, with dates and material references that an inspector can follow, a caution supported by acceptance sampling theory, which ties conclusions to defined plans rather than single specimens[2].
  3. Retest when formulations, suppliers, or processes change rather than on a fixed calendar alone, since composition follows inputs, a connection buyers recognize from CE marking practice, where conformity evidence supports the marking decision[1].
  4. Keep pre-production and mass-production samples clearly separated in the file, because only the latter represents what consumers receive, a caution supported by acceptance sampling theory, which ties conclusions to defined plans rather than single specimens[2].
  5. Check that the laboratory method matches the applicable regulation for your market instead of accepting a generic migration screen, a connection buyers recognize from CE marking practice, where conformity evidence supports the marking decision[1].

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.

The paper chain inspectors actually ask for

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. CE marking practice reinforces the habit: the marking decision rests on conformity evidence, and test documentation is part of that evidence.[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.

Illustration: The paper chain inspectors actually Decorative illustration for the section "The paper chain inspectors actually"; visual only, carries no data.

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 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 sampling literature makes the same point from the other side: without a defined sampling plan, one result cannot carry the whole lot.[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.

The expensive scoping mistakes, compared

Decision pointWhat to checkTypical evidenceNext action
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
Product scopeExact materials with food contactBill of materials marked by contactList each material in the scope note

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

From use description to linked declaration

  1. Read limits before resultsCompare detection limits against thresholds before celebrating any non-detect. Results above the threshold prove nothing regardless of how clean the number looks.
  2. Link declaration to reportsPoint each declaration explicitly at its supporting reports with numbers and dates. Traceable paperwork survives inspector review; vague gestures do not.
  3. 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.
  4. 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.
  5. 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.
Illustration: From use description to linked Decorative illustration for the section "From use description to linked"; visual only, carries no data.

Recurring weaknesses in food contact files

Update tracking is the maintenance contract for the whole compliance file: regulations add substances, lower limits, and refine methods while products sit unchanged. CE marking practice reinforces the habit: the marking decision rests on conformity evidence, and test documentation is part of that evidence.[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.

Prioritization keeps the routine affordable: high-attention substances, food-contact-critical components, and products in strictly enforced markets lead the review queue. Acceptance sampling literature makes the same point from the other side: without a defined sampling plan, one result cannot carry the whole lot.[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. CE marking practice reinforces the habit: the marking decision rests on conformity evidence, and test documentation is part of that evidence.[1] 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

Before filing any pass report, check the detection limit against the threshold it is supposed to clear. A non-detect above the limit is an open question, not a certificate.

Sources

  1. Wikipedia: CE marking —— Overview of CE marking as conformity marking for products sold in the European Economic Area.
  2. Wikipedia: Acceptance sampling —— Overview of acceptance sampling including AQL concepts used in product inspection.

Frequently asked questions

Should pre-production samples be used for compliance files?

Only as development guidance, never as product evidence, since they cannot capture the full process sequence or represent shipped lots. Draw compliance specimens from packed mass-production cartons with custody notes. The distinction belongs in writing in the file itself.

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.

See it on your own assets.

Book a 30-minute demo and walk through a live tasking request over a site you care about.

Request a demo