Environmental compliance evidence is information used to determine whether an applicable obligation has been fulfilled. Recordkeeping preserves that information with enough context to make it usable. The strongest system connects each requirement with relevant records and a reasoned evaluation rather than collecting documents without a clear purpose.
The compliance obligations guide explains the whole process. The article on compliance evaluation shows how evidence becomes a conclusion. This guide focuses on evidence design and reliability.
Start with the question being answered
Identify the requirement, activity and period. Ask what information would demonstrate fulfilment and what would reveal a failure.
A procedure shows intended arrangements. A completed record shows something about implementation. A measured result may show an operating outcome. These forms of information serve different purposes.
Do not assume that more records always provide stronger evidence. A large archive can still omit the one event, location or submission relevant to the requirement under review.
Preserve essential context
A record should be identifiable and connected to the relevant activity. Dates, locations, equipment, methods and responsible people may be important depending on the task.
For a measurement, units and reporting basis matter. For a submission, preserve the version sent and evidence of the appropriate delivery. For an inspection, retain findings and follow-up rather than only a tick showing attendance.
The context should allow a competent reviewer to interpret the record without relying entirely on the author’s memory.
Distinguish original records from reconstruction
Keep original evidence and maintain a visible trail of corrections. Record who changed information, when and why where appropriate.
If a record must be reconstructed, identify that fact and the sources used. Do not backdate it or present it as a contemporaneous original.
Reconstruction may help establish facts, but it may not fulfil a requirement to create or retain a particular record at the relevant time. That question needs assessment against the actual obligation.
Check completeness
Compare expected records with what is available. A folder containing inspection forms does not show whether every required inspection occurred unless there is a way to reconcile the schedule.
For event-triggered records, identify the events that should have generated them. Operational logs, service records or change records can help test coverage.
Record gaps explicitly. Missing evidence is not the same as evidence that no problem occurred. The evaluator needs to understand whether the available information supports a conclusion.
Protect reliability
Use suitable access controls, backup and change management. These support evidence integrity without making every record inaccessible to operational users.
For digital systems, test retrieval and restoration. A backup process that has never been checked may not provide the continuity the organisation assumes.
Where data is transferred or calculated, preserve important source information and calculation logic. A dashboard value can become difficult to defend if the original records and transformations are no longer available.
Separate records from conclusions
An evaluator should identify the evidence used, the applicable criterion and the reasoning. Keep that evaluation distinguishable from the underlying record.
This allows a later reviewer to understand why the same evidence supports a particular conclusion and where limitations remain.
If new evidence changes the conclusion, add a traceable revision. Do not silently alter historical findings or remove an inconvenient limitation from the record of what was originally evaluated.
Establish retention on a justified basis
Check specific legal, authorisation, contractual and other relevant requirements. Then consider justified operational and evidential needs.
There is no universal retention period for all environmental compliance records. A laboratory result, training record and historical site document can have different requirements and purposes.
Environment Agency permit-management guidance explains that certain permits specify periods and otherwise calls for consideration and documentation of retention needs within its England context. Do not generalise that guidance into a fixed number of years for every organisation.
Control access and disposal
Make evidence available to authorised people who need it, including deputies and evaluators. Protect personal and sensitive information appropriately.
Disposal should follow a controlled decision consistent with applicable duties. Suspend routine destruction where a relevant preservation requirement or hold applies, obtaining advice where needed.
Keep enough information about the disposal process to explain what happened. Deleting records solely because they show an adverse result undermines the reliability of the entire system.
Test the evidence trail
Choose a requirement and trace it through the control, record and evaluation. Then reverse the test: choose a record and identify the duty or decision it supports.
These exercises reveal broken links, duplicate storage and unclear ownership. They also help distinguish useful evidence from forms maintained only because they have always existed.
EPA’s EMS evaluation guidance provides the general checking context. The practical recordkeeping approach here aims to make that checking reproducible: another competent person should be able to understand the source, facts, conclusion and limits without reconstructing the whole history.
Include contractor and laboratory evidence in the test. External records need the same clear connection to scope and period, and the organisation needs a reliable route for receiving and reviewing them before they are required for a decision.
Plan for system replacement before migration. Test that dates, attachments, approval history and source references survive the move. A successful transfer of visible values may still lose the context needed to evaluate historical compliance or explain an earlier management decision.