SOLO LAB / DOCUMENT CONTROL
Laboratory Report Version Control: Tracking Corrected Certificates
A corrected Certificate of Analysis (COA) can arrive under the same filename as the original. Someone who opens a saved copy may see a different report from someone who follows the current link. A version register answers three questions for both readers. Which report is current, what did it change, and who reviewed the effect on existing records?
Confirm what the issuing laboratory sent
Start with the issued document and the message or portal notice that accompanied it. Record the issuing laboratory, report identifier, stated revision or amendment identifier, and issue date. Keep your receipt date in a separate field. The date a file was downloaded tells you when you obtained it.
An amendment may be a separate document that belongs with the original. A complete replacement may carry a new identifier and refer back to the superseded report. Record the relationship the issuer states. If the files conflict or the relationship is unclear, keep the new file pending review and ask the issuing laboratory to identify the current record. The Hong Kong Accreditation Service checklist describes how ISO/IEC 17025 distinguishes amendments and replacement reports. HKAS, clause 7.8.8 checklist
Log the revision and preserve the original
Save each issuer file as received in an access-controlled location. Keep a register entry for each version and cross-reference the earlier entry. Put status labels in the register or file metadata so the original document remains intact. Use one register entry to point readers to the current report and any accompanying amendments. Archive superseded copies under your organization’s retention rules. WHO’s laboratory quality guidance describes a document control log, release of authorized revisions, and an archived copy with its replacement date. WHO, Document Control and Retention
| Register field | What to capture |
|---|---|
| Document identity | Issuing laboratory, report ID, and revision or amendment ID as stated |
| Dates and source | Issue date, receipt date, and a reference to the issuer’s message or portal record |
| Version relationship | Earlier report ID and whether the issuer supplied an amendment or a replacement |
| Change note and status | Issuer’s stated change, open questions, and whether the record is pending, current, or superseded |
| Review and follow-up | Reviewer, review date, affected records, and completed or outstanding actions |
Reconcile affected records before signing off
The assigned reviewer compares the two documents and records what changed at the level needed to update references. Check shared folders, summaries, checklist entries, and other records that cite the earlier report. Update active links and note which historical records need to continue pointing to the version used at the time. If colleagues received a copy, record who needs the revision notice and when the notice was sent. Sign off after documenting the correction, affected records, and any remaining actions with their assigned owners.
Example of a corrected certificate entry
In this fictional example, report LR-104 is filed as the current version. The issuer later sends LR-104-R1 and states that it replaces LR-104 to correct a clerical error in the report header. The reviewer links both records, records the issuer’s explanation, and updates the shared reference to LR-104-R1. The original stays in the archive with the supersession date. An earlier review note keeps its LR-104 citation and gains a cross-reference to the correction. The register records the reviewer and the date those updates were verified.
If you need to check the identifying fields on an issued certificate, see How to Read a Certificate of Analysis. The Research Documentation Library collects the related guides.
