First establish which document has been amended.
An amendment can arrive as a replacement laboratory report, an attachment explaining a correction, or a supplier's revised certificate of analysis. These are not automatically the same record. Start with the issuer, report number, specimen reference and version relationship before comparing individual results.
NATA identifies failure to mark amended reports, unclear changes and missing reasons for changes among reporting nonconformances. Its examples also distinguish an accredited activity from a result outside the accredited scope. That makes a revision's identity and stated scope useful review points; the guidance is not a certificate for an offered batch. NATA: reporting and technical-record nonconformances.
For an Australian laboratory procurement file, record whether the new document comes from the original laboratory or from an intermediary. If a supplier has assembled a COA from separate reports, retain that distinction. A new supplier summary should not silently replace the original analytical source.
Compare the records field by field.
Keep both versions available during review. Do not rely only on the document title, because a filename can change while the issued report reference stays the same. Ask the issuer to explain the relationship if the revised document does not make it clear.
| Field | Record from the earlier version | Question for the revision |
|---|---|---|
| Issuer and reference | Laboratory or supplier name, report number and issue date | Who issued this replacement and which document does it replace? |
| Specimen and lot | Sample reference and its recorded batch relationship | Has the specimen description changed, or only a transcription field? |
| Result and units | Exact reported value, units and qualifications | Which result lines changed, and what is the stated reason? |
| Method and scope | Method reference, relevant scope statements and external-provider notes | Does the interpretation or scope of the result differ? |
| Earlier decision | Internal review reference and what it authorised | Which reviewer needs to reconsider that decision? |
The ledger is your procurement record, not a rewritten laboratory report. Preserve the issuer's wording and ask for clarification where a comparison leaves a gap.
A corrected field and a new analysis answer different questions.
A changed address, an amended specimen description and a newly reported measurement can have different consequences. Ask whether the revision corrects an administrative error, changes the interpretation of existing data, or reports additional analytical work. Do not decide that distinction from the word “revised” alone.
If new work is reported, ask which specimen and method produced it and how it relates to the earlier report. If only an administrative field changed, record the issuer's explanation without treating the revision as a fresh measurement. The out-of-specification guide covers the separate question of an investigation or additional testing after an unexpected result.
Keep requests neutral: ask what happened and which evidence supports the corrected record. Do not ask for a preferred result or edit an issuer's document locally to make it fit an accepted specification.
A changed lot reference needs a clear explanation.
Hypothetical example: a receiving file contains report R, matched by the supplier to lot A. A later document has the same result values but a different lot field. The unchanged numbers do not establish that the two files describe the same tested specimen.
Keep the original lot mapping, the new document and the explanation linking them. Ask whether the changed field corrects the record or identifies different material. Your reviewer can then determine whether the earlier batch decision still applies. Do not infer a new batch test from an unchanged table of results.
This example describes a document problem, not an actual Wholesale Lab Peptides incident or laboratory result. The useful output is a resolved mapping and a recorded decision, rather than the deletion of the older PDF.
Connect the revision to the decision it may affect.
Identify the order, receiving entry, internal specification or packaging record that relied on the earlier document. A revision can matter even after delivery if it changes the identity, units, interpretation or limitations on which an earlier decision was based.
Send the authorised internal reviewer a short comparison showing the affected fields and the issuer's explanation. Keep open questions separate from confirmed changes. A revised result is not automatically an acceptance or rejection decision; the technical criteria and the person responsible for that decision still need to be identified.
Use the COA checklist for a complete first-pass document review and the quality-agreement guide for assigning responsibilities. This page concerns revision handling, not a replacement acceptance standard.
Retain the history and make the current version easy to find.
Once the revision has been reviewed, identify the current issued document in the working file and retain the earlier version with its superseded status visible. Record the reviewer, date, explanation received and any follow-up. A shared folder containing two unlabelled versions invites a later team member to use the wrong one.
If a supplier or laboratory needs to clarify a field, refer to the exact issued report and line. For an eligible documentation enquiry, use the Australian document-enquiry brief. Describe the required record and the unresolved relationship; an enquiry does not establish that a particular report exists or has been verified.