ISO/IEC 17025 clause 7.8: issue clear and reliable reports
ISO/IEC 17025 clause 7.8 concerns how results reach the customer. Reports must be reviewed and authorised, communicate results accurately and include the information needed for correct interpretation. The challenge is not simply fitting fields onto a template: the report must match the activity, the evidence and what the customer has asked the laboratory to conclude.
What clause 7.8 requires in practice
Clause 7.8 governs how results leave the laboratory. At its foundation, results are reviewed and authorised before release. They are usually delivered as a report that is accurate, clear, free of ambiguity and objective. The report carries what was agreed with the customer, what a reader needs to interpret the results, and anything the method itself demands. Issued reports are kept as technical records, and they may be paper or electronic.
The clause then splits into specific parts: information common to all reports, additions for test reports, calibration certificates and sampling, and rules for statements of conformity, opinions and interpretations, and amendments. Simplified reporting is possible by agreement with the customer, provided that information not shown remains readily available. The outputs the laboratory needs are a controlled release process, report formats suited to each service and a way of handling changes after issue.
7.8.1–7.8.2: establish a reliable reporting foundation
Review and authorise results before release, retain issued reports and make their meaning clear. Common information identifies the laboratory and activity, the customer, item, method, dates, results and authorisation, with other details required by the circumstances. Consult the full clause when designing the reporting arrangement rather than treating this summary as a complete field list.
Identify relevant customer-provided information and externally supplied results. Where the laboratory did not perform sampling, the report must make the appropriate limitation clear. Simplified reporting can be agreed, but information omitted under those arrangements still needs to be readily available where the standard requires it.
7.8.3–7.8.5: adapt the content to the service
Test reports, calibration certificates and sampling reports have different information needs. Test reporting includes conditions, uncertainty or other information where needed for interpretation and applicable requirements. Calibration reporting includes uncertainty and information on metrological traceability, with relevant conditions and adjustment information.
Where the laboratory is responsible for sampling, the necessary sampling details support interpretation of subsequent results. Do not use one generic report design if it obscures these differences. A calibration interval recommendation also requires attention to the relevant customer agreement rather than being inserted as an automatic universal recommendation.
7.8.6: make conformity statements defensible
When providing a statement such as pass or fail, document and apply the decision rule, considering the relevant risk unless the prescribed-rule circumstances apply. The report needs to make clear which results and specifications the conclusion concerns and the rule used where it is not inherent in the requested specification or standard.
Connect this with contract review under 7.1. A laboratory should not wait until a borderline result appears before deciding how acceptance will be determined. A clear early agreement protects the customer and the laboratory from misunderstandings.
7.8.7–7.8.8: separate interpretation and preserve amendment history
Only appropriately authorised people should release opinions and interpretations, with a documented basis. Identify them clearly and base them on the relevant results. Record applicable discussions when such interpretations are communicated directly to customers.
Changes to issued reports need clear identification and linkage. Where a replacement is issued, it needs its own identification and a reference to the original. Avoid silently replacing a file at the same download link without preserving an understandable record of what changed.
Why clause 7.8 matters to the laboratory
The report is the product the customer sees. A technically perfect measurement that arrives in a confusing report can still lead to a wrong decision, and a missing limitation can turn a correct number into a misleading one. Reporting errors are also visible, which makes them damaging: a wrong customer name, a missing unit or a conclusion nobody agreed to appear in front of regulators, buyers and lawyers. Good reporting practice protects customers from misuse of results and protects the laboratory from claims that it implied more than it measured. It is also a daily display of competence, since the report is often the one part of the laboratory that most customers ever read.
How to implement clause 7.8
Treat reporting as a designed service, then test it with fresh eyes. Start with the services where customers ask the most questions about reports, as these are likely to show the weakest points.
- Collect a sample of recent reports of each type, including one with a conformity statement, one with external results and one that was amended.
- Compare each with the clause for its report type and note missing, unclear or unnecessary content.
- Define who may review and authorise each kind of report, and make that authorisation visible in the document.
- Build templates that handle the common fields but leave room for conditions, deviations, customer-supplied data and external results.
- Set a release rule for electronic delivery so nothing reaches the customer before authorisation.
- Agree simplified formats only in writing with the customer, and note where the omitted information can be retrieved.
- Ask someone outside the laboratory to read a report and say what conclusions they would draw, then adjust wording where they read it differently.
Construction example: a pass statement without an agreed basis
A fictional construction client asks a laboratory to add “complies” to a materials report after receiving the numerical result. The original request did not establish the relevant decision rule. The laboratory first clarifies the specification, reporting need and applicable requirements instead of treating the word as a harmless formatting edit.
The review determines whether the requested conclusion is technically supported, how the rule is agreed or prescribed, and what report amendment is needed. The customer receives a conclusion with a defensible basis rather than an unexplained commercial reassurance.
Manufacturing example: customer-supplied sample identity
A manufacturer supplies a sample described as coming from a particular production batch. The laboratory did not witness its selection. Its report should not accidentally imply that the laboratory verified the batch origin or that the result represents every item in that batch.
Identify the relevant customer information and the sampling limitation. This helps the buyer understand what the result supports. It also illustrates why report review should consider the claim a reader could infer, not only whether the numbers match the worksheet.
IT and BPO example: an incorrect report distribution
A records-processing team uploads authorised reports to a customer portal, but a software configuration change maps one customer's document to another account. The laboratory needs to address confidentiality and data controls as well as the distribution process. Outsourcing the upload does not remove those responsibilities.
Clear roles, controlled changes and checks on recipient mapping are practical safeguards. Technical authorisation should remain distinct from administrative publication. This is an illustrative support-process scenario, not an assertion that portal services themselves require laboratory accreditation.
Useful evidence and common mistakes
Review a representative set of reports, including different service types, externally supplied results, conformity statements and amendments. Compare them with the contracts, technical records and authorisations. Test whether someone unfamiliar with the job can understand the limitations and the basis of conclusions.
Avoid using an accreditation symbol outside the body's permitted conditions, implying that all advertised activities are accredited, or presenting interpretation as an unqualified measurement fact. Accreditation claims must match the granted scope and applicable rules.
Explore each numbered part
7.8.1 · review and authorise results before release
Establish clear review and authorisation before laboratory results leave your control. This guide explains accurate and objective reporting, customer-agreed information, technical-record retention and simplified reports. Examples show why an electronic portal or a regular customer relationship does not remove the need for a controlled release and an understandable result.
7.8.2 · include the information reports need
Build reports that identify the laboratory, customer, item, method, activity and result without ambiguity. This guide explains the common reporting information, customer-supplied data, external results and sampling responsibility. Examples help laboratories avoid misleading conclusions when a report combines verified observations with information supplied by someone else.
7.8.3 · report test results with useful context
Add the information needed to interpret test results, including relevant conditions, uncertainty, conformity statements and other method or customer requirements. This guide explains the specific reporting triggers and sampling connection, with examples showing why a bare number or pass label may leave the customer unable to use the result correctly.
7.8.4 · issue meaningful calibration certificates
Explain calibration results with their uncertainty, relevant conditions and metrological traceability, including before-and-after information where available. This guide covers the additional certificate requirements, sampling links and limits on recommending calibration intervals. Examples help laboratories issue certificates that support the customer's measurement decisions rather than merely confirm that a service occurred.
7.8.5 · report sampling so results can be interpreted
Communicate the sampling information needed to understand later test or calibration results. This guide explains dates, item identity, location, methods, relevant conditions and uncertainty inputs, with examples showing how a report can overstate its meaning if the reader cannot distinguish the sampling event from the laboratory measurement itself.
7.8.6 · make defensible conformity statements
Explain how a measured result becomes a statement that a specification is met or not met. This guide covers documented decision rules, measurement uncertainty, false-accept and false-reject considerations and clear reporting, with examples showing why a pass/fail conclusion needs an agreed technical basis rather than a convenient comparison of rounded numbers.
7.8.7 · control opinions and interpretations
Provide useful technical interpretation without blurring the boundary between measured results and professional judgement. This guide explains personnel authorisation, the documented basis, clear identification in reports and records of verbal discussions. Examples show how laboratories can help customers understand findings without making unsupported product-certification or inspection claims.
7.8.8 · amend issued reports without losing history
Correct or replace an issued laboratory report while preserving a clear connection to the original. This guide explains identification of changes, amendment documents or data transfers and uniquely identified replacement reports, with examples showing why overwriting a portal file or silently sending a revised PDF can leave customers using inconsistent results.
Frequently asked questions
Can a report be electronic?
Yes, provided the applicable requirements are met. Appropriate integrity, access, authorisation and retention controls remain necessary.
Does every report need a pass-or-fail conclusion?
No. It depends on the service and agreed or applicable requirements. When a conformity statement is made, apply the relevant decision-rule and reporting provisions.
Can a report be simplified for a regular customer?
Yes, when agreed with the customer. Required information omitted from the simplified report must remain readily available, and review, authorisation and accurate reporting still apply.
Make your reports easier to trust and use
Discuss reporting and accreditation preparation with Sterling. We can connect customer requirements, technical review, documentation and team training. Effivity ISO & GRC automation software can support agreed action and evidence workflows, while your laboratory retains control of technical reports. Explore ISO/IEC 17025 awareness training for a common foundation.