Ask an experienced Health & Safety Manager about the most difficult incident they have dealt with and chances are they will not start by talking about RIDDOR. They will talk about what happened before the report was even considered: the concern that was raised but never escalated, the inspection that found a problem but did not lead to action, or the near miss that seemed minor at the time but later looked like a warning that had been missed.

By the time a serious incident occurs, the story is often already well underway. RIDDOR matters, of course. It sets out what must be reported, who is responsible and when the report needs to be made. But in real operational environments, the harder question is often not “Do we need to report this?” It is “Can we show what happened, what we knew, what we did, and whether the right action was taken afterwards?”

That is where many organisations find the gaps. Not because people do not care. Most teams care deeply about keeping staff, contractors, visitors and members of the public safe. The problem is usually more ordinary than that. Information ends up in different places. Notes are kept in spreadsheets. Photographs are stored in a shared drive. A contractor sends an update by email. A manager records an action somewhere else. Each small decision may make sense at the time, but when an investigation begins weeks or months later, piecing everything together can be far harder than it should be.

“People often focus on whether something is reportable,” says Claire Brooking, Customer Care Director at ANT. “In my experience, the harder question is whether you have the information you need. Can you see what happened, who reviewed it, what decisions were made and what actions followed? That is where organisations often discover the weaknesses in their process.”

The warning signs before the incident

A loose paving slab outside a building might be mentioned several times before someone trips. A faulty gate at a station might be reported as awkward or unreliable long before it becomes a safety concern. A recurring issue during a site visit might look small in isolation, but when similar reports appear across different locations, it starts to tell a different story.

This is why strong incident and near miss reporting matters. The value is not simply in collecting reports. The value is in seeing patterns early enough to act. A near miss is often described as an accident that did not happen, but that undersells its importance. A better way to think of it is as a warning with a bit of luck attached.

Many serious incidents are not complete surprises. They are the final point in a chain of smaller events, delayed actions or missed opportunities. A good reporting process gives organisations the chance to break that chain before somebody is injured.

What RIDDOR actually means

RIDDOR stands for the Reporting of Injuries, Diseases and Dangerous Occurrences Regulations. In simple terms, it requires certain serious workplace incidents to be reported to the relevant enforcing authority, usually the Health and Safety Executive. It covers work-related fatalities, specified injuries, over-seven-day injuries, certain occupational diseases, dangerous occurrences and some incidents involving members of the public.

Not every accident at work is reportable. That is one of the most common areas of confusion. A minor injury may still need to be recorded internally, but that does not automatically make it a RIDDOR incident. Equally, a near miss may not involve an injury at all, but if it falls within the rules for dangerous occurrences, it may still need to be reported.

The distinction matters because organisations can waste time worrying about the wrong thing. RIDDOR is concerned with specific reporting duties. Good health and safety management is concerned with a wider question: what happened here, what does it tell us, and what needs to change?

What is not reportable under RIDDOR?

This is where many organisations get understandably cautious. If someone has been injured, nobody wants to underreact. But reporting every minor event as if it were a RIDDOR incident is not the answer either. It can create confusion, add unnecessary administration and distract from the incidents that genuinely require formal reporting.

Generally, minor accidents that do not meet the reporting threshold are not reportable under RIDDOR. Incidents that are not connected to work activities are also usually outside scope. For example, if someone becomes unwell because of a pre-existing medical condition unrelated to work, that would not normally be a RIDDOR matter. The same applies where a member of the public becomes ill for reasons unrelated to the organisation’s activity.

That does not mean these events should disappear from view. A non-reportable incident may still reveal something useful. It may show that a process is unclear, that a location needs attention, or that staff are unsure how to record concerns. The smartest organisations do not only ask whether something has to be reported. They ask what can be learned from it.

Dangerous occurrences: the near misses that matter most

The phrase “dangerous occurrence” can sound abstract until you put it into a real setting. A piece of lifting equipment fails. A structure partially collapses. An electrical incident could have caused serious harm. Nobody is injured, but the potential was obvious.

This is one of the areas where judgement, records and escalation matter. Dangerous occurrences are not ordinary near misses. They are specified events that may need to be reported because of what could have happened, not just what did happen. That makes accurate reporting especially important. If the people reviewing the incident do not have enough information, it becomes harder to decide whether the threshold has been met.

The practical lesson is simple enough. If something could have caused serious harm, it deserves proper attention, even if the outcome was fortunate. A lucky escape is still information. In some organisations, it is the most useful information they will receive all month.

The part after the report

Many articles about RIDDOR stop once they have explained what is reportable and how quickly reports should be made. That is useful, but it is not the full picture. For Health & Safety Managers, the real work often starts after the initial report has been made internally.

An organisation may need to gather photographs, witness statements, inspection records, maintenance information, contractor notes, CCTV details and evidence of previous reports. It may also need to assign actions, monitor whether they have been completed and show that lessons were learned. If that information is scattered across emails, paper forms and spreadsheets, the process quickly becomes messy.

This is why many organisations introduce structured accident management processes. It is not about making reporting more complicated. It is about making sure incidents, investigations, evidence and follow-up actions sit together in a way that can still be understood later.

Claire Brooking puts it plainly: “The incident report is only the start. If an action comes out of that investigation, someone needs to know who owns it, when it is due and whether it has actually been completed. Otherwise, the same issue can sit there waiting to happen again.”

Due diligence is not just a phrase

Due diligence is one of those terms that appears regularly in health and safety conversations, but it only really means something when an organisation has to prove it. It is the ability to show that reasonable steps were taken. Not claimed. Not assumed. Shown.

That might include evidence of inspections, records of reported concerns, completed actions, risk reviews, investigation notes and communication between teams. The problem is not always that organisations fail to do these things. The problem is that the evidence is often fragmented. One department has part of the story, another team has another part, and nobody has the full picture in one place.

This is where systems such as iSafety Suite become relevant. For organisations managing incidents, actions and compliance activity across different sites, teams or departments, visibility is not a nice-to-have. It is what allows people to understand whether the process is working.

A strong audit trail does not remove the need for judgement. It supports it. It gives managers, safety teams and senior leaders a clearer view of what was reported, what was reviewed and what happened next.

Why audits and inspections still do the heavy lifting

RIDDOR is often associated with what happens after an incident, but many of the best safety improvements happen before that point. That is where inspections, audits and checks still do much of the heavy lifting.

A missed inspection can leave a defect unnoticed. A recurring issue can sit unresolved if actions are not tracked properly. A site visit can identify a risk, but if that information does not go anywhere useful, the organisation gains very little from the inspection itself.

Regular audits, assessments and checks help organisations spot weaknesses before they become incidents. They also give leaders evidence that risks are being reviewed, actions are being assigned and standards are being monitored over time. That matters in almost every operational environment, but particularly where the public, contractors or multiple teams are involved.

A single issue may not seem significant. Twenty similar issues across different locations tell a different story. The value comes from being able to see both.

Where organisations commonly get caught out

Most RIDDOR-related problems are not dramatic. They are ordinary process failures that become serious when pressure arrives. Someone assumes another person has reported the incident. A manager believes Health & Safety has already been informed. A contractor sends details to one contact, but the information never reaches the person responsible for reviewing it.

Another common problem is weak follow-up. An incident is recorded, an investigation starts, an action is agreed, and then the trail goes cold. Nobody deliberately ignores it. It just slips down the list as other priorities take over. Months later, when someone asks whether the issue was resolved, the answer is not immediately clear.

There is also the problem of poor first reports. If the original record is vague, the investigation starts on shaky ground. Missing timings, missing photographs, missing witness details and unclear descriptions can all create problems later. The first report does not need to be perfect, but it does need to be useful.

What this looks like in real organisations

The value of better reporting is easiest to understand when you look at organisations that have had to manage these challenges in live operational environments. At Enfield Council, improving the way incidents were recorded and managed helped create greater visibility and consistency across the organisation. The Enfield Council case study shows how structured reporting can support better oversight in a complex local authority setting.

Rail environments bring their own pressures. Multiple locations, high passenger volumes, contractors, operational teams and safety-critical processes all make reporting more challenging. The MTR Elizabeth Line case study demonstrates how better reporting processes can give management teams clearer information and more meaningful insight across a busy network.

The point is not that every organisation needs the same setup. They do not. A council, rail operator, airport and facilities management provider will all have different risks and reporting pressures. The shared requirement is visibility. Without it, the same problems appear again and again: slow escalation, incomplete records, missed trends and actions that are difficult to evidence.

RIDDOR in public-facing environments

RIDDOR can be especially challenging in environments where the public interacts with the organisation every day. Councils, schools, rail operators, airports and facilities teams all have to think beyond employees. They may also need to consider contractors, visitors, passengers, pupils, service users and members of the public.

That adds complexity. A person injured on site may not be an employee. They may not understand the organisation’s reporting process. The first person they speak to may not be part of the Health & Safety team. Information may need to move quickly between frontline staff, managers and administrators before anyone can make a sensible decision about what happens next.

In these settings, the strength of the process matters as much as the knowledge of the regulation. If people do not know how to report an incident, or if the report does not reach the right person, the organisation is already on the back foot.

Questions worth asking before the next incident

No system can prevent every accident. No process removes the need for professional judgement. But organisations can ask better questions before the next serious incident tests their process.

Can staff report concerns quickly and clearly? Can managers see issues as they arise? Are actions tracked to completion? Can evidence be found without searching through emails and folders? Can recurring issues be identified across more than one site? If someone asks six months from now what happened and what was done, will the answer be easy to prove?

These are not abstract questions. They are the difference between a process that looks fine on paper and one that works under pressure.

Frequently asked questions about RIDDOR

Does every workplace accident need to be reported under RIDDOR?

No. Many workplace accidents should be recorded internally but do not meet the threshold for RIDDOR reporting. The key is understanding the difference between internal recording and formal reporting.

Who decides whether an incident is reportable?

The duty normally sits with the employer, the person in control of the premises or another responsible person. Frontline staff should be encouraged to report what happened, but the final decision should sit with someone who understands the reporting requirements.

Are near misses reportable?

Most near misses are not reportable under RIDDOR, but some dangerous occurrences are. Even when a near miss is not reportable, it may still be extremely valuable from a risk management point of view.

Why does record keeping matter?

Good records help organisations investigate incidents, track actions, identify trends and demonstrate due diligence. Poor records make all of those things harder.

Can digital reporting decide whether something is RIDDOR reportable?

No. That decision remains with the organisation and the responsible person. Digital reporting can support the process by helping teams capture information, review incidents, track actions and maintain a clearer audit trail.

Final thoughts

RIDDOR is often treated as a formality that appears after something serious has happened. In practice, it sits within a much wider picture. Reporting, investigation, evidence, action tracking, inspections and due diligence all matter because they help organisations understand what happened and reduce the chance of it happening again.

The best organisations do not only ask whether an incident is reportable. They ask what the incident reveals. Was there a warning sign? Was an action missed? Was a trend overlooked? Did the right people have the right information at the right time?

Good reporting will never remove every risk. But it does give organisations a better chance of seeing problems earlier, acting faster and proving what was done afterwards. For any Health & Safety Manager, that is where the real value lies.