ISO/IEC 17025 clause 7.8.2: include the information reports need

What clause 7.8.2 requires in practice

Clause 7.8.2 lists the information common to test reports, calibration certificates and sampling reports. Unless there is a valid reason for leaving something out, each report identifies itself and the laboratory, says where the work was done, shows that its pages belong together and where it ends, names the customer, identifies the method, and describes the item and its condition where necessary. It gives the relevant dates, refers to sampling plans where they matter, states that results relate only to the items concerned, presents the results with units, notes departures from the method, names who authorised it and marks results from outside providers.

A second part makes the laboratory responsible for everything in the report except information supplied by the customer. That information must be clearly identified, with a disclaimer when it could affect validity. If the customer supplied the sample, the report states that results apply to the sample as received.

Identify the report and the work clearly

The report needs an appropriate title, laboratory name and address, the location where the activity was performed and a unique identification that makes its components and ending clear. Include the customer's name and contact information, the method and an unambiguous description and identification of the item, including condition when necessary.

Relevant dates include performance and issue dates, plus receipt and sampling dates where critical to validity and application. Where relevant, identify the sampling plan and method. These details help the reader distinguish when the item was obtained, when work occurred and when the result was released.

Explain the result and its boundaries

Provide the results and appropriate units, make clear that the results relate to the items actually tested, calibrated or sampled, and identify additions, deviations or exclusions from the method. Identify the person or people authorising the report and clearly distinguish results supplied by external providers.

The laboratory should not imply that a single tested sample represents a whole production lot unless the technical and sampling basis supports that interpretation. Equally, a report assembled from several sources must not obscure which results the laboratory itself produced.

Handle customer-supplied information separately

Clause 7.8.2.2 makes the laboratory responsible for report information except information supplied by the customer. Customer-provided data must be clearly identified. If that information can affect result validity, include an appropriate disclaimer. A generic disclaimer on every page may be less useful than a clear explanation of the specific information and limitation.

Where the laboratory was not responsible for sampling, state that results apply to the sample as received. Do not imply that laboratory review of a sample label verifies the customer's account of where or how the sample was taken.

Why clause 7.8.2 matters to the laboratory

Reports travel. They are forwarded, excerpted, attached to tender documents and read by people who never met the laboratory. Every missing piece of context is an invitation to misunderstanding or misuse. The common information acts as the minimum context that keeps a report accurate when separated from its covering email. It also draws a clear line around responsibility: who produced which data, which information came from the customer and what the results actually relate to. That clarity reduces disputes, defends the laboratory against implied claims it never made and lets a reader see at a glance how far the report can be trusted.

How to implement clause 7.8.2

Build one reliable base layout, then make sure exceptions are noticed. Test the revised layout on a live report with someone who was not involved in the work, before it becomes the standard layout for all customers.

1. Create a field checklist from the clause and compare it with each current report format to find omissions.
2. Add title, laboratory details, report identification, page marking and an end marker to all templates.
3. Design a place for the performance location, covering on-site and temporary work, and make the field mandatory.
4. Provide a labelled block for customer-supplied information and a prompt asking whether a disclaimer is needed.
5. Add a clear marker for external-provider results and for deviations from the method.
6. Include a standard statement of the as-received limit for customer-supplied samples.
7. Train reviewers to read the report as an outsider would and to question anything that could be taken to say more than was measured.

Two illustrative report distinctions

Evidence and review practice

Common nonconformities with clause 7.8.2

Reviews of report content tend to find omissions rather than errors of fact.

• On-site work is reported with only the laboratory's permanent address and no performance location.
• Customer-supplied details, such as batch identity or sampling site, appear unmarked alongside laboratory data.
• Multi-page reports lack page numbering or an end marker, so a missing page would go unnoticed.
• Departures from the method are recorded in the technical file but absent from the report.
• Results from an external provider are merged into the report with no indication of their source.