ISO/IEC 17025 clause 7.8.8: amend issued reports without losing history
Clause 7.8.8 requires changes to issued reports to be clearly identified and, where appropriate, the reason included. An amendment must be issued through a further document or data transfer clearly linked to the original report. A complete replacement needs its own unique identification and a reference to the original it replaces.
What clause 7.8.8 requires in practice
Clause 7.8.8 deals with reports that have already been issued and later need to change. Every change is made visible in the report, and where it helps the reader, the report also gives the reason for it. After issue, an amendment is made only as a further document or data transfer that carries wording such as an amendment to a named report serial number, or an equivalent form of words. That amendment must meet all the requirements of the standard, in the same way as the original.
When a complete new report is needed, it is given its own unique identification and refers to the original report that it replaces.
The clause does not forbid correction. It protects the history, so the recipient can always recognise which document is current, what changed and which original it relates to. Silent overwriting of an issued report is the outcome the clause is designed to prevent.
Decide whether the issue is an amendment or replacement
Identify what changed and its technical significance. A correction to a customer detail and a changed reported result may require different explanation and follow-up, but neither should create an ambiguous report history. Apply all relevant reporting requirements to the amendment, including review and authorisation.
The standard permits equivalent wording to identify an amendment; it does not require one exact English phrase in every system. The essential point is that the recipient can recognise the update and the report to which it relates. If issuing a complete new report, identify it uniquely rather than reusing the original as though nothing changed.
Control electronic distribution
A portal or shared link can make silent replacement easy. Ensure the system preserves the issued history and clearly communicates the new status. Consider customers who downloaded the earlier version: changing the server file does not necessarily inform them that their copy has been superseded.
Appropriate customer communication and any recall decision should follow the applicable contract and nonconforming-work controls. Clause 7.8.8 does not replace the need to evaluate technical significance under clause 7.10 when the original work or result was nonconforming.
Preserve the supporting record
Retain the original and amended technical information under clause 7.5.2 and issued reports as technical records. The report history and the underlying correction should be connected. A new report number without a traceable technical basis is no more convincing than an overwritten worksheet.
Make responsibilities clear for initiating, reviewing, authorising and distributing amendments. A customer request to change wording should receive technical review where it affects interpretation or scope. Commercial preference does not justify altering an unfavourable conclusion without a valid basis.
Why amendment control matters to the business
Errors in issued reports do happen: a wrong customer detail, a transcription slip, a recalculated result. What matters commercially is how the correction is handled. A customer who discovers an unexplained replacement file loses confidence in every earlier report.
A disciplined amendment route shows maturity. It lets the customer see exactly what changed, protects the laboratory when a dispute asks which version was relied on, and gives regulators and assessors a clear audit trail. It also prevents the quiet substitution of an unfavourable conclusion with a more comfortable one, which would damage both impartiality and reputation.
How to implement clause 7.8.8
Design the amendment route before it is needed, because corrections are usually made in a hurry. A small laboratory can run this with a short written routine and a numbering rule. The test of success is that a customer receiving a correction can immediately see what changed and why, without a phone call.
- Define the difference between an amendment document and a full replacement report, and who decides which route applies.
- Create the wording and numbering that identify an amendment and link it to the original report serial number.
- Require that amendments pass through the same technical review and authorisation as the original report.
- Make the report portal or file store keep issued versions, with clear status, so nothing is replaced silently.
- Decide how customers who already hold the earlier version are told about the change.
- Link the amendment to the underlying technical record so the correction can be explained, and connect it to nonconforming work handling where the original result was affected.
Two illustrative report changes
A testing laboratory identifies a transcription error in a released report. It evaluates the effect, corrects the record with traceability and issues a clearly identified amendment or replacement linked to the original. It considers the required customer action rather than simply emailing a file named “final final”.
A calibration laboratory reissues a complete certificate after correcting an uncertainty statement. The replacement has unique identification and refers to the certificate it replaces. The laboratory evaluates whether the earlier result's use requires further action and retains the complete history.
Common mistakes and useful evidence
Evidence includes the original issue, changed information, amendment or replacement, authorisation and relevant technical evaluation. Retain distribution or communication evidence as appropriate to the process. A particular revision-number format is optional, but it must make status and relationships unambiguous.
Avoid reusing the original identifier without a clear amendment basis, leaving two apparently current versions available, deleting the earlier report, or changing results solely to satisfy a customer's preferred outcome. Traceability protects both the laboratory and the customer from uncertainty over which result is valid.
Frequently asked questions
Can we overwrite a PDF on the customer portal?
Not as a silent replacement that loses the issued history or obscures the change. The amendment or replacement must meet the identification, traceability and reporting requirements.
Must every amended report use one prescribed phrase?
No. Equivalent wording can identify the amendment and original report clearly. The meaning and traceable connection matter more than a single fixed phrase.
Does issuing a corrected report close the nonconforming-work investigation?
Not automatically. Evaluate significance, affected work, customer action and possible recurrence through the relevant processes. A report correction is only one possible action.
Turn this requirement into reliable laboratory practice
Sterling can help review the full correction route from discovered error to customer communication. Bring an anonymised amended report to a laboratory consultation to identify improvements in version control, technical review and follow-up.
Build the team's understanding through Nonconformity Management. Discuss the relevant scope, employee learning and agreed access to Effivity ISO & GRC automation software with Sterling; laboratory technical decisions remain with competent, authorised personnel.
ISO/IEC 17025 requirements hub · Reporting requirements · Technical-record amendments · Nonconforming work