Accident Record Retention That Stands Up

Accident record retention keeps incident evidence, corrective actions and decisions accessible when insurers, regulators or auditors need clear proof fast.

A solicitor’s letter arrives two years after a slip in a loading bay. The accident form is easy enough to find. The photograph has gone, the contractor’s details sit in an old inbox, and nobody can show when the damaged flooring was repaired. That is the point at which accident record retention stops being an administrative task and becomes an operational test.

A completed form is not, by itself, a defensible incident record. Teams need a connected account of what happened, what evidence was available, who acted, what changed, and how the organisation checked that the risk was controlled. The record must remain accessible for as long as there is a credible regulatory, civil, insurance, employment or learning need to rely on it.

Learn MoreIncidents & Accident ManagementHow an incident is recorded against the people and place involved, so the file is still usable when someone asks.

Why Accident Records Need More Than a Filing Date

An accident record can be requested long after a shift has ended, a contractor has left site or a manager has moved on. It may be needed to respond to an insurer, support a reportable incident investigation, defend a claim, identify a recurring failure or demonstrate that remedial work was completed.

The difficulty is that the evidence is rarely created in one place. The initial report may be in an accident book or digital form. CCTV may sit in a separate security system. Inspection records, maintenance tickets, training records, risk assessments and contractor documents may all be held elsewhere. If those items cannot be connected quickly, the organisation has evidence in theory but not proof in practice.

Good retention therefore preserves context, not just documents. It shows the state of the workplace at the time of the event and the decisions made afterwards. It also protects the organisation from a familiar problem: reconstructing a serious event from partial records, fading memory and disconnected systems.

What an Accident Record Should Contain

The contents should reflect the seriousness and nature of the incident. A minor first-aid event will not require the same evidential depth as a workplace injury, dangerous occurrence or contractor incident. However, the core file should create a reliable timeline.

For incidents requiring investigation, retain the following connected evidence:

• the original report, including date, time, location, people involved and immediate treatment or response;
• investigation notes, witness accounts, photographs, diagrams, CCTV references and relevant communications;
• associated risk assessments, inspection results, maintenance history, permits, contractor records and training or competence evidence;
• notifications and reports made to insurers, regulators or other relevant parties, including the submitted version and confirmation of submission;
• corrective actions, assigned owners, due dates, completion evidence and checks that controls remained effective;
• decisions made during review, including why an action was proportionate, deferred or considered unnecessary.

Keep the original record intact. If an investigator corrects a factual error or adds information later, the system should show what changed, who changed it and when. Silent edits weaken confidence in the record, particularly where a matter progresses to a claim or formal investigation.

Accident Record Retention Is Not a Single Retention Period

There is no sensible universal number that works for every accident record. UK organisations must consider applicable health and safety rules, reporting obligations, limitation periods, insurance terms, contractual requirements, sector rules and data protection duties. A statutory minimum may set a baseline for a particular record, but it may not reflect the full period in which an allegation, claim or regulatory question could arise.

For example, records supporting a report under the Reporting of Injuries, Diseases and Dangerous Occurrences Regulations may have specific retention expectations. Personal injury claims can arise after the incident date, while incidents involving children, occupational illness or potential long-term harm can require a longer view. Healthcare, care, education, construction and regulated facilities may also have additional sector requirements.

The practical answer is a documented retention schedule that groups records by type and risk. It should state the retention period, the legal or operational rationale, the record owner, where the evidence is held and what happens when the period ends. It should also distinguish between routine incidents and files subject to an active investigation, claim, complaint or legal hold.

A defensible schedule asks four questions: what are we required to keep, how long could the matter reasonably remain live, what personal data does the file contain, and who has authority to approve disposal? If the answer is unclear, seek competent legal or specialist advice rather than applying a blanket deletion rule.

Turn Retention into a Controlled Workflow

Retention fails when it relies on someone remembering to save attachments, chase actions and move files into a shared folder. The better model begins at the point of reporting.

A site team should be able to log an incident on the spot, attach photographs and identify the precise area, asset, activity or contractor involved. The report should trigger proportionate investigation tasks and bring in the relevant risk assessment, inspection history and maintenance information. Once corrective actions are assigned, their evidence should feed back into the same case record.

This creates a clear chain: incident, investigation, action, verification, closure. It also means a compliance manager can see whether similar incidents are occurring across sites, whether actions are overdue and whether a local issue points to a wider control failure.

Learn MoreIssue Reporting & RequestsHow follow-up from an incident becomes an assigned action, with completion evidence staying on the record.

CalmCompliance supports this approach by connecting incident forms, site information, assets, risk assessments, actions and audit trails in one operational record. The evidence assembles as teams complete the work, rather than being collected under pressure after an incident escalates.

Protect Sensitive Information without Losing Access

Accident files often contain special category personal data, particularly health information. Broad access is rarely appropriate. At the same time, overly restrictive storage can prevent managers from finding evidence when it is needed.

Use role-based access so that people see only the information required for their responsibilities. A site manager may need incident details and assigned actions, while HR, health and safety leaders or authorised investigators may require access to more sensitive information. Record who viewed, exported or amended key information where the system allows it.

Retention also requires controlled disposal. Once the approved period has expired, records should be securely deleted or anonymised in line with the organisation’s policy. Disposal should be evidenced, not assumed. Keeping everything indefinitely is not a safe alternative: it increases privacy exposure, makes searches slower and can leave outdated material in circulation.

Keep a Legal Hold Separate from Normal Disposal

A retention schedule should pause when a file becomes relevant to a claim, enforcement action, dispute, serious complaint or reasonably anticipated legal process. This is often described as a legal hold.

The hold must cover more than the accident form. It may apply to CCTV, emails, maintenance records, training evidence, risk assessments and previous reports involving the same location or hazard. Identify the scope, notify the record owners and prevent routine deletion until the matter is resolved.

This is where centralised records reduce risk. When evidence is mapped to a site, asset, person, contractor and incident, teams can identify related material without searching across multiple folders and systems.

Learn MorePremises & Asset ManagementHow sites and assets sit in one estate structure, so related incident evidence points at the place and kit involved.

Test Whether Your Records Are Genuinely Retrievable

Retention policies look credible on paper until someone needs a complete file at short notice. Run a simple retrieval exercise using a closed incident from the previous year. Ask a manager to produce the initial report, investigation evidence, relevant inspection and risk assessment, action history, completion proof and access history.

If the exercise takes days, relies on named individuals or exposes gaps in the timeline, the retention process needs work. Measure retrieval time, missing attachments, overdue actions and records nearing disposal. Those indicators reveal whether the organisation is retaining usable evidence or merely storing documents.

The most useful accident file is not the largest one. It is the one that lets a competent person see what happened, what was done and what proof supports the organisation’s decisions - calmly, quickly and without reconstruction.