How to Read a Pakistani Lab Test Report: What Validates It, What Raises a Flag, and What to Ignore

Most sourcing teams either trust the report without reviewing it or forward it to a quality team that does a quick visual scan for the pass/fail result. Neither approach is adequate. A test report is a legal document making specific technical claims. Those claims are either supported by a verifiable accreditation chain and technically appropriate methodology or they're not. And the difference is consequential.

This guide is for the person in your organisation who receives test reports from Pakistani suppliers and needs to evaluate them properly. You don't need to be a chemist. You need to know what to look for and what questions to ask.

The anatomy of a credible test report

Before diving into what to check, it helps to understand the physical structure of a properly formatted test report from an ISO/IEC 17025-accredited laboratory.

A well-constructed test report has the following sections, not necessarily in exactly this order but all present.

The header contains: the laboratory's name and contact information, the report's unique identification number, the date of issue, and the date or dates of testing (which should precede the issue date).

The sample information section identifies: who submitted the sample, the sample description (what it is), the sample reference number, and ideally when the sample was received by the laboratory. This section is important because it connects the report to a specific physical sample.

The accreditation statement is usually near the header or in a footer. It reads something like: "This report is issued in accordance with the laboratory's accreditation by PNAC (Pakistan National Accreditation Council) under ISO/IEC 17025:2017, Accreditation Certificate Number [X], Accreditation Scope [Y]." This is the legal statement that the testing was conducted under the accreditation framework.

The test results section is typically a table listing: the test name, the test method (with the specific standard code and version), the result found, the specified limit or reference value, and a pass/fail or compliant/non-compliant determination for each parameter. This is the substantive content of the report.

The uncertainty or measurement uncertainty statement: good reports include a statement about measurement uncertainty for quantitative results. This tells you the confidence range around the reported number. A result of 28 mg/kg with uncertainty of �3 mg/kg, compared against a limit of 30 mg/kg, is a different situation from a result of 28 mg/kg with uncertainty of �1 mg/kg.

The authorization section: the report should be signed or digitally authorized by a qualified person at the laboratory, identified by name and role (e.g., laboratory manager, technical director, authorized signatory). An unsigned or anonymously authorized report has no accountability chain.

The scope limitation statement: good laboratory reports include language noting that the results relate only to the sample as received, and that the report may not be reproduced in part without the laboratory's written permission. This is standard ISO/IEC 17025 practice.

The first check: accreditation verification

This is the most important check and takes under five minutes.

Find the PNAC accreditation certificate number in the report. It will be in the accreditation statement section described above. Write it down.

Go to pnac.gov.pk. Navigate to the accredited laboratories search. Enter the certificate number or the laboratory name.

Verify three things: first, that the laboratory appears in the database (if it doesn't, the certificate number may be fabricated, or the accreditation may have lapsed before the database was updated). Second, that the accreditation is currently valid (check the expiry date on the scope document against the report date). Third, that the accreditation scope includes the specific test methods referenced in the report you're reviewing.

That last point requires a little attention. The scope document lists specific standard codes. A laboratory accredited for EN ISO 14362-1 is accredited for azo dye aromatic amine testing using Part 1 of that standard. It is not automatically accredited for EN ISO 14362-3, which covers 4-amino-azobenzene and requires a separate protocol. If the report covers aromatic amines but only references Part 1, and your requirement includes the amines covered by Part 3, the report is incomplete for that requirement.

If the specific test method in the report doesn't appear in the accreditation scope, the result for that method is not covered by the PNAC accreditation, even if the laboratory is accredited for other methods. You can still use the result for internal information, but not as internationally recognized compliance documentation.

The second check: method reference and version

Every test result in a compliance-quality report should reference the specific test standard used: the number, the part, and the year of the version. Not "formaldehyde testing." EN ISO 14184-1:2011. Not "colour fastness." ISO 105-C06:2010. The specificity matters for several reasons.

Standards are updated periodically. A newer version of a standard may have modified the extraction procedure, the reference conditions, or the pass/fail criteria. If a buyer's specification requires the current version of a standard, a test conducted under an older version may not satisfy that specification even if the laboratory is accredited.

Method specificity is also the basis for comparison between reports. If one supplier's report references EN ISO 14362-1 and another's references AATCC TM 81 for aromatic amines, they may be testing for similar but not identical analyte lists under different extraction conditions. The results are not directly comparable without understanding the methodological differences.

From October 2026, PFAS testing for EU REACH PFHxA compliance should reference the relevant LC-MS/MS targeted analysis method. A report referencing "PFAS screening" by total fluorine methodology does not satisfy the REACH compound-specific limit requirement. Different methods answer different regulatory questions.

The third check: result vs. limit, and the numbers near the edge

The results table should show, for each parameter, three things: the result, the limit, and the pass/fail determination.

Start with the obvious passes, the ones significantly below the limit. These don't need much attention.

Focus your attention on results that are close to the limit. A result of 27 mg/kg against a limit of 30 mg/kg for aromatic amines is passing. But with measurement uncertainty, the actual value in the sample could plausibly be above 30 mg/kg. A good report will tell you the measurement uncertainty for that result. A borderline result without uncertainty information is incomplete.

Pay particular attention to results reported as "<LOD" or "<LOQ." LOD is the Limit of Detection: below this level, the laboratory's equipment cannot reliably distinguish the substance from background noise. LOQ is the Limit of Quantification: below this level, the laboratory can detect but not accurately quantify the substance.

For a regulated substance with a limit of 30 mg/kg, a result of "<LOD" where the LOD is 25 mg/kg means the substance wasn't detected at levels above 25 mg/kg. That's fine. But for a regulated substance with a limit of 25 ppb (parts per billion), a result of "<LOD" where the LOD is 50 ppb means the laboratory's equipment isn't sensitive enough to detect the substance at or below the regulatory limit. The LOD is above the limit being tested against. That result is not useful compliance evidence. For PFAS testing at the EU REACH limit of 25 ppb, the laboratory must demonstrate that its LOD for the specific PFAS compounds is below 25 ppb. If the LOD is above that, the result " <LOD" doesn't confirm compliance.

The fourth check: sample description and traceability

The report should describe the sample in enough detail to connect it to a specific production lot or shipment. Ideally: product description, reference number or article number, lot or production batch identifier, and the date the sample was submitted.

A report that describes the sample as "fabric sample" with no further identification raises a traceability concern. Whose fabric? From which production run? From which supplier? If the report ever needs to be referenced in an audit, an enforcement action, or a buyer dispute, the connection between the report and the specific goods needs to be traceable.

Serious quality programmes use a chain of custody form that travels with the sample from the factory floor to the laboratory: the production lot number, the sample extraction date, who cut the sample, who packaged it, and who delivered it to the laboratory. The laboratory's report then references the chain of custody number.

This level of traceability is standard practice in pharmaceutical testing, where it's mandatory. In textile testing, it's good practice that the most rigorous buyers are beginning to require.

The fifth check: date coherence

The sample receipt date at the laboratory should precede the testing date, which should precede the report issue date. The report issue date should be within the production period being covered.

A report dated months after the production shipment was made, covering samples from that shipment, has chain-of-custody and timing concerns. Testing done after the fact, on separately drawn samples, doesn't verify the compliance of the goods that shipped.

A report where the testing date is before the sample receipt date is an error or, in a worst case, a fabrication. Either way, it's a flag.

What to ignore: the certificate portfolio

Supplier presentations often accompany test reports with a collection of certificates: ISO 9001 quality management, SA8000 social accountability, various environmental certifications, Oeko- Tex certificates, BSCI audit reports, and others.

These are legitimate business credentials. An ISO 9001 certificate from a reputable certification body genuinely means the company has implemented and had audited a quality management system. An SA8000 certificate means the facility was assessed for social compliance. What they don't do is substitute for a PNAC-accredited test report showing specific chemical compliance for a specific product. A beautiful array of eight certificates doesn't tell you whether the fabric in the specific shipment contains aromatic amines above the EU limit. Only an accredited test report covering the specific method for the specific sample does that.

When reviewing compliance documentation, focus on test reports with specific method references, specific results against specific limits, and PNAC accreditation for the applicable methods. The certificate portfolio is background context, not primary compliance evidence.

What to do when a report has problems

The most common problems in test reports from Pakistan, and the appropriate response to each:

Missing accreditation statement: ask the laboratory to re-issue the report with the PNAC accreditation information included. Any accredited laboratory should be able to do this immediately. If the laboratory says it can't include the accreditation statement, that's because the testing wasn't done under accredited conditions.

Method not specified to the required standard: ask whether the laboratory can confirm the method used against the specific standard required. If the laboratory used a different method, ask whether the applicable standard is in their accredited scope and can be run on a retained sample or a new sample.

Result close to limit without uncertainty: ask the laboratory for the measurement uncertainty statement for that specific parameter. Accredited laboratories are required under ISO/IEC 17025 to have calculated measurement uncertainty for quantitative methods. If they can't provide it, that's a quality system gap.

Sample description insufficient: ask the supplier to confirm the production lot and sample extraction details in writing, and request that future samples are submitted with chain of custody documentation.

Report date after shipment date: this is the most serious concern and should trigger a conversation about why the testing wasn't completed before shipment. If it becomes a pattern, it indicates the testing programme is being run for documentation purposes after the fact rather than as a genuine pre-shipment compliance check.

Building a verification protocol for your organisation

The most efficient way to institutionalize this is a short verification checklist that anyone in your organisation who receives test reports from Pakistan can apply.

The five questions the checklist covers: Is the PNAC accreditation number present and verifiable on pnac.gov.pk? Is the specific test method referenced and in the laboratory's current accreditation scope? Are all results shown against applicable limits with pass/fail determinations? Is the sample description sufficient to trace to a specific production lot? Do the dates in the report (receipt, testing, issue) form a coherent chronological sequence?

If all five are yes: the report is formally adequate. Keep it in the compliance file and note the laboratory for use on future orders.

If any are no: follow up before accepting the report as compliance documentation. Most issues are correctable with a request to the laboratory.

This takes five minutes per report. It creates a defensible record of your due diligence in evaluating supplier compliance documentation.

The broader system this supports

Individual test report verification is the entry point. Beyond verification of individual reports, a mature compliance programme builds a history of results across suppliers and time. Which suppliers consistently produce clean results? Which are borderline on specific parameters? Where have results trended upward toward limits, possibly indicating a process change at the supplier?

Test reports, when properly verified and organized, become a supplier performance database. The laboratory that issues consistently under accredited conditions, for the same suppliers across multiple seasons, becomes a trusted data source for the entire compliance programme.

That database is what your ESG team needs for CSRD Scope 3 documentation, what your CSDDD due diligence file requires as process evidence, and what your customs documentation needs if a shipment is selected for market surveillance testing at the destination port.

For testing services with full accreditation documentation and report support, contact Tti Labs at customerservices@ttilabs.net or 111-786-001.