How to Verify a Product Test Report’s Authenticity and Scope

At UTS, we start by confirming the file with the issuing lab. We check any claimed or required accreditation, then match the sample and results to your product and sales market.

A genuine report can still cover the wrong model or show a failed test. We keep authenticity, product coverage and pass/fail results separate throughout the review.

1. Get the Full Report

We need the full lab-issued report, including attachments and later revisions. A cover page or screenshot leaves too much out.

Check these report details

Field	What we check
Report number and revision	We match the full number and ask which revision is current.
Laboratory and location	We check the lab’s legal name and the site that did the testing.
Applicant and sample	We check who ordered the tests and which sample the lab received.
Dates	We check when the sample arrived, when testing took place and when the report was issued.
Pages and attachments	We check that every listed page and attachment is present.

A newer issue date doesn’t always mean a new test. We ask what changed in the report.

If the supplier provides a supplementary report, we read it alongside the original report it references. Our team checks whether it adds evidence, corrects an error or replaces an earlier version.

We also compare supplier summaries and translations with the lab-issued file. If a model name or result needs correcting, we ask the issuing lab for a controlled revision.

2. Ask the Lab to Confirm Your Copy

We find the lab’s contact details on its official website. The details printed on a report could have been changed.

CNAS records let us check accreditation. For the report itself, we ask the issuing lab to confirm authenticity.^[1]

Subject: Verify report [number / revision]

Does this attached file match your records? Has it been revised, replaced or withdrawn? Which tests were accredited? Please let our team know if you need the original customer’s permission to answer.

Our request identifies the exact file, revision, sample and results we need confirmed. If the portal verifies only the number, we send the full file to the issuing office. An empty search result does not prove the report is fake.

If confidentiality prevents a reply, we ask the supplier to authorize the lab to respond to our team. Until that happens, we record the report as unverified rather than assuming it is genuine or false.

We flag inconsistent report numbers, unexplained changes in sample photos and results that conflict between pages. These are reasons to ask the lab for clarification; appearance alone cannot settle authenticity.

When we check barcodes or QR codes, we require a 100% successful scan rate for the codes checked. For a report QR code, we also check that it opens the lab’s official verifier and shows matching report details. A successful scan alone doesn’t prove authenticity.

Our team checks digital signatures using the lab’s instructions. A pasted signature image cannot show whether someone changed the file.

3. Check Which Tests Are Accredited

We use ISO/IEC 17025 accreditation to assess a lab’s competence for the tests within its accredited scope.^[2]

Accreditation does not certify the product or make a failed test result acceptable.

Our team searches the accreditor’s directory, such as UKAS or CNAS, using the lab’s legal name, accreditation number and testing site.^[3][4]

The scope of accreditation lists what the lab is accredited to do. We match the material, method and property being tested, including any listed ranges or restrictions.^[5]

For a UKAS-marked report, we check which results fall outside accreditation. The report must identify them.^[6]

• Older reports: We check whether the tests were covered when they took place.
• Unclear or flexible scope: We ask the lab or accreditor whether the exact method is covered.
• Outsourced tests: We check which lab performed them and what accreditation it claims.

4. Match the Sample to Your Order

Our team compares the report with your specification and the approved sample from sample evaluation.

Match the sample to the order

Product detail	What we compare
Models and revisions	We identify the tested model and ask the lab for evidence supporting coverage of other models.
Materials and finishes	We compare formulations, colors, coatings and component sources.
Electrical configuration	We compare ratings, power supply, battery and component specifications.
Applicant and manufacturer	We use purchase and production records to link the report’s customer, factory and product.
Sampling	We record who chose the sample, where it came from and its sample or lot number.

For a product family, we request a model-by-model list of differences and the lab’s explanation of which sample represents them. Similar appearance is not enough. Our team needs to know whether the differences affect the particular tests being relied on.

If the report uses a factory model number but your order uses a retail name, we request a documented cross-reference. We compare specifications as well as names so a relabelled product does not get confused with a changed design.

We also distinguish supplier-selected samples from samples selected during an agreed inspection. Where sample selection is part of our assignment, we record the source lot, selection details and sample identification so the lab results can be traced back to the goods.

A test report is a snapshot of the sample tested. During product inspection, we check whether the goods match the approved sample and specification.

5. Check What Was Tested

We map each required test to its method, standard edition, clause, sample or component, report page and result. Missing tests, excluded clauses and unexplained “not applicable” entries go on our query list.

When a report covers selected clauses, we record that limit explicitly. We do not describe the product as having passed the whole standard unless the evidence supports that statement.

For food-contact testing, we ask whether the test conditions cover the intended foods, temperature, contact time and reuse. Under EU rules for plastics, migration tests use standard conditions that represent intended use. Food simulants stand in for food categories during these tests, so we also check which simulants the lab used.^[7]

For RoHS and REACH testing, we check which substances and materials were tested, and which limits were used.

We check the standard edition required for your market and certification scheme, along with any extra buyer requirements.

If the report uses an older edition, we ask the lab which relevant clauses changed and whether the existing results address them. Our team uses that comparison to identify any additional testing needed.

6. Read the Results

What each result means

Entry	What we check
Numerical result	We compare the result with the limit using the same units and material basis.
ND / not detected	We check what ND means and the lab’s detection or reporting limit. ND does not mean zero. If that limit is above the allowed level, ND alone cannot show compliance.
Not tested	We request evidence for the missing test.
Combined samples	We ask whether the combined result supports a conclusion for each material.
Method deviation	We ask how the lab changed the method and whether that affects the result.

On the same mass basis: 1% = 10,000 mg/kg; 1 mg/kg = 1 ppm.

We check whether a result measures substance content in a material or migration into food or a simulant. We cannot compare these as if they were the same test. Converting mg/dm² to mg/kg also needs the relevant surface area and mass.

If a result is close to the limit, we ask the lab for its decision rule: how it accounts for measurement uncertainty when deciding pass or fail. Our team does not apply an extra margin of its own or reinterpret a borderline result from the rounded number alone.^[8]

7. Check What Changed Since Testing

We ask the supplier what changed after testing: materials, coatings, components, design, process or factory. Our team reviews the records with the lab to work out which changes need retesting.

We request the change date and the first affected batch, then link them to the order under review. If the supplier cannot trace which goods used the changed material or component, we record that gap before relying on the older report.

For children’s products subject to CPSC third-party testing, material changes that could affect compliance require new tests for the affected rules. The responsible manufacturer or importer issues a new Children’s Product Certificate based on passing results.^[9]

When we carry out a quality management system audit, our checklist can include material changes, records linking materials to production batches, and test records.

8. Check What the Recipient Accepts

Our team checks any required retesting intervals and the recipient’s limit on report age. We do not assign every report a blanket expiry date. The answer depends on the product rules, buyer requirements and whether the tested version still matches the goods. Our team also asks the lab whether rule changes since testing affect the report’s use.

For toys and children’s product testing, we establish the product type, intended age and sales market before reviewing the test coverage.

Where CPSC requires third-party testing, we check that it accepts the lab for each applicable rule.^[10]

For CE marking, we check which conformity assessment and declaration rules apply to the product. A test report alone is not market approval.^[11]

We ask the buyer, retailer or marketplace for its written submission requirements before treating a report as ready to use. Our team checks the required models, applicant details, document language and supporting records against that request.

If the buyer requires shipment checks, we add its model, label and packaging requirements to the final random inspection checklist. We cannot establish chemical compliance by looking at the goods.

How We Record the Outcome

• Verified, applicable and passing: We record exactly which requirements and product variants the report covers.
• Missing evidence: We list the gaps and advise the buyer to hold any approval that depends on them.
• Failed test: We flag the failed requirement and request corrective action and passing retest evidence before treating it as met.
• Invalid file: If the issuer confirms unauthorized changes, withdrawal or non-issuance, we stop relying on that file and request a verified replacement or new testing.

We keep the report, lab reply, relevant accreditation scope and product comparison with the order record, along with the reviewer’s name, date and decision. Each open point gets a next action and an owner, so an unanswered lab query cannot be mistaken for approval.