Published

The wastewater report was submitted on Tuesday. On Thursday, the laboratory sends a corrected certificate for a sample collected during the reporting period. The facility needs to know which filed value it affects, who must assess the change and whether any further submission is required.
Preserve the original submission and review the new evidence against it. Connect the corrected certificate to its earlier version, the affected calculation and the owner’s decision. If the applicable reporting process requires an amendment or notification, retain that action and its outcome alongside the original filing.
Retain the exact report, supporting attachments, calculation worksheet and submission confirmation used for the filing. Give the corrected certificate its own receipt time and preserve the laboratory’s issue date and revision reference. A sample collected in June can still belong to the April–June reporting period when its corrected certificate arrives in July.
Connect both certificates to the same sample, sampling point, facility, permit condition and reporting period where those references apply. A newer file is not enough to explain what changed. The reviewer should be able to open the earlier evidence and see which calculation or conclusion depended on it. The controlled revisions guide explains why stored version history and an approved release serve different purposes.
Different arrivals need different checks. Assign the assessment to the responsible environmental reviewer, and record the permit condition or reporting instruction used for the decision. Missing or conflicting evidence stays assigned for clarification rather than silently replacing a filed value.
| Evidence received | What the reviewer checks | What the file retains |
|---|---|---|
| First valid result | Sample identity, reporting period and any estimate or missing-result explanation in the filing. | The assessment of its effect and the resulting reporting action. |
| Replacement certificate | Laboratory revision, method, units, qualifiers and values used in the filed calculation. | Both certificates, the affected worksheet and the review decision. |
| Correction with no effect on filed values | Whether the change affects another statement, qualification or reporting obligation. | The reason the filing stands or why another action remains necessary. |
| Certificate for a different scope | Facility, sample point, permit condition and reporting period. | The reassignment or clarification and the responsible owner. |
Link the new certificate to its earlier source, sample and submitted report.
Check the change, its reporting basis and the action assigned to the owner.
Keep any amended package, submission result and unresolved query connected.
“Approved for amendment” and “amendment submitted” answer different questions. Record unsuccessful attempts and the external reference or acknowledgement returned through the required channel. If further confirmation is expected, leave that follow-up visible with an owner and due date. A replacement report should identify the earlier submission it corrects without making the earlier package disappear.
Fictional facility, samples, dates and reporting procedure. Example North Facility’s ENV-1042 file covers April–June monitoring. The authorised filer submits report revision 1 on July 7 and records confirmation SUB-1042-A. On July 9, the laboratory replaces the certificate for sample W-17. This example’s reporting instructions require an amended report when a correction changes a reported result; staff verify that rule before acting.
The coordinator records the July 9 receipt, laboratory revision and W-17 reference, then links the certificate to ENV-1042 and the earlier certificate. Report revision 1, its worksheet and SUB-1042-A remain available to authorised reviewers.
The environmental reviewer confirms the sample point, method and units. The corrected concentration changes from 0.40 to 0.45 mg/L. The worksheet’s fictional average uses four equally weighted results: 0.20, 0.30, 0.40 and 0.50 mg/L. Replacing 0.40 with 0.45 changes that average from 0.35 to 0.3625 mg/L before any reporting-rounding rule is applied.
The reviewer checks the programme’s actual calculation and rounding instructions and identifies the affected reported field. Under this example’s stated rule, the owner approves an amendment and assigns the filer. The assessment identifies the governing instruction and keeps any separate notification or operational follow-up visible.
The filer submits approved report revision 2 with the required explanation and attachments through the external channel. ENV-1042 retains the submitted package and confirmation SUB-1042-B, linked to SUB-1042-A. The returned result is recorded as received; an internal approval is not used as a substitute for that result.
A reviewer can retrieve the original package, corrected certificate, recalculation, decision and amended submission in sequence. Staff use the revised report for subsequent reporting work. Any outstanding regulator query remains assigned, and the next reporting period has its own file rather than absorbing this correction.
The figures demonstrate a traceable recalculation, not a monitoring method, permit limit or conclusion about compliance. A correction that leaves the reported value unchanged still needs the relevant assessment. The reason for retaining the filing unchanged belongs in the file alongside any other required action.
Give the laboratory contact, facility operator, environmental reviewer and authorised filer the access needed for their tasks. A corrected certificate should not open unrelated facility records or private review correspondence to an external recipient. Check search, downloads and any exported review package under the agreed department, facility and partner boundaries.
Apply the organisation’s approved retention and preservation rules to the linked evidence. Marking a report superseded does not by itself authorise deletion of the original submission. Keep the receipt, assessment and source references needed to explain the correction for as long as the applicable rules require.
Preserve the original submission, review the changed evidence and record the authorised decision. When a further submission is required, retain the package and its actual result with the earlier filing. The continuing file should explain both what the organisation reported and what it did when the evidence changed.
The open-source foundation — API-first, deployable into your own AWS account, and free to use. Right for architecture validation and early implementation.
Production-ready editions for departments and complex workflows. Start with a Proof-of-Value deployment or go straight to production.
For governance-heavy environments with residency, sovereignty, assurance, and multi-jurisdiction requirements. Talk to us about the right deployment model.