Version two, or was it three?
A client points out the sampling address is wrong on a report. Someone edits it and emails a new PDF. A week later, an additional test is added and the report is reissued again. Then a transcription error in one result is found, and the report is amended once more. The client's consultant, who received the first version, never received the others. When a question comes up months later, nobody can say quickly which version went to whom, or why each was changed.
Why amendments get messy
- Amendments are handled by editing and re-sending PDFs.
- Reasons for amendment are not recorded in a structured way.
- Version marking on reports is inconsistent.
- Not every original recipient is sent the amended version.
- Amendment types are not tracked, so causes are not addressed.
Recipients are part of the problem. A report may go to the client, their consultant and a regulator's contact, and each may have forwarded it. The lab can only notify the people it sent it to, which is why recording every recipient of every version matters.
What it costs
Clients and third parties may rely on superseded reports. Assessors expect a clear amendment process and records. Without reason tracking, the lab cannot see that most amendments come from a particular cause, such as registration errors, which could be fixed.
| Aspect | Edit and resend | Versioned reissue |
|---|---|---|
| Reason | Email note | Recorded reason code and description |
| Approval | Informal | Signatory approval recorded |
| Version marking | Varies | Clear version and replacement statement |
| Recipients | Whoever is remembered | All original recipients notified |
| Analysis | None | Amendments by cause |
Amendments also take signatory time. Each one needs checking, approval and an explanation to the client, and when the process is informal, the same questions are asked again for every amendment. A standard route with reasons and templates makes each one quicker to handle properly.
How we build it
- An amendment is started from the original report, with a reason code and description.
- The change is made in the LIMS or the report data, and the new version is generated with clear version marking and a statement of what it replaces, following your procedures.
- An authorised signatory approves the amended report.
- Every recipient of earlier versions is sent the new version with a notice, and the client portal shows only the current version as current, with history available.
- Amendment reasons are reported monthly so causes can be addressed.
Amendments that do not change results, such as a corrected address, can follow a lighter approval path if your procedures allow, while changes to results always go through a signatory. The rules are yours, set once and applied consistently.
What changes
Clients always know which version is current. Every amendment has a reason and an approval. The lab can see which kinds of errors cause amendments, and fix them at source.
Assessors can be shown the complete history of any amended report, with reasons and approvals, in one place. Registration errors, often the most common cause of amendments, become visible, which is usually the prompt to improve sample intake.
Recognise this?
- Amended reports are edited PDFs sent by email.
- Reasons for amendments are not recorded.
- Not all recipients get the amended version.
- Version marking is inconsistent.
- You cannot say what causes most amendments.