RIDDOR Reporting: 7 Mistakes That Distort Safety Data
RIDDOR reporting protects workers only when leaders use it to classify risk clearly, preserve evidence, and correct weak controls before patterns repeat.
Principais conclusões
- 01Separate internal recordkeeping from RIDDOR reportability so managers do not mistake a logged event for a legally assessed reporting decision.
- 02Classify severity early because over-seven-day timing does not replace prompt review of specified injuries, fatalities, and dangerous occurrences.
- 03Assign the responsible person before incidents happen, especially where contractors, agency workers, self-employed workers, or shared premises are involved.
- 04Protect investigation evidence in parallel with RIDDOR notification so the form does not replace learning, control review, or first-hour discipline.
- 05Use Andreza Araujo's safety culture diagnostic to test whether reporting routines reveal real risk or only produce compliant records.
RIDDOR reporting is the United Kingdom duty to report certain work-related deaths, specified injuries, over-seven-day injuries, occupational diseases, dangerous occurrences, and gas incidents under the Reporting of Injuries, Diseases and Dangerous Occurrences Regulations 2013. The legal requirement matters, but the bigger leadership question is whether the organization uses the report to see risk earlier or only to satisfy an external form.
The Health and Safety Executive updated its RIDDOR reporting guidance on 20 January 2026 and launched a public consultation on 7 April 2026 to review parts of the 2013 regulations. HSE named under-reporting and over-reporting as longstanding challenges, which is exactly why EHS leaders should treat RIDDOR quality as a management signal rather than a clerical task.
Why RIDDOR reporting mistakes distort safety decisions
RIDDOR mistakes distort safety decisions because they change what leaders believe happened, how severe the exposure was, and whether a control failure deserves escalation. A late or misclassified report may still look tidy in a file, although the management team has already lost the first chance to preserve evidence and challenge the operating system.
As Andreza Araujo argues in Safety Culture: From Theory to Practice, declared culture and operated culture separate when the organization says safety is central but treats incident data as administration. RIDDOR is one place where that split becomes visible because the record can either reveal risk or bury it under procedural language.
The thesis here is practical. RIDDOR reporting should not be reduced to a legal yes-or-no exercise. It should force leaders to ask whether the event shows weak control design, poor supervision, unclear ownership, or a risk pattern that the ordinary dashboard has failed to show.
1. Confusing internal recordable cases with RIDDOR reportable events
Internal recordkeeping and RIDDOR reporting serve different purposes, even when the same incident appears in both systems. A company may record first aid cases, medical treatment, restricted work, near misses, property damage, and environmental events internally, while RIDDOR applies only to defined categories under the 2013 regulations.
This confusion is common in global companies because EHS teams move between OSHA, HSE, ISO 45001, and corporate reporting taxonomies. A case that belongs in a local accident book may not be RIDDOR reportable, and a dangerous occurrence may be RIDDOR reportable even without an injury. The same distinction appears in OSHA 300 logs, where legal recordability and leadership evidence are related but not identical.
The practical fix is a two-column triage. The first column asks whether the event meets the legal reporting threshold. The second asks what the event reveals about exposure, controls, supervision, contractor management, or design. When only the first column exists, leaders may comply with the rule while missing the risk.
2. Waiting for absence duration while ignoring immediate severity
RIDDOR classification fails when the team waits to see how many days the worker is absent while ignoring whether the injury was already specified or fatality-linked. HSE's online reporting form states that over-seven-day worker injuries must be reported within 15 days of the accident, but that timeline does not replace the need to classify serious injuries promptly.
A fractured bone, an amputation, a loss of consciousness caused by head injury, or another specified injury should not sit in a calendar watch while the site debates absence duration. The reportability question changes with the facts, and the investigation rhythm should change with it as well.
Across 25+ years leading EHS at multinationals, Andreza Araujo identifies a repeated weakness in serious-event response. Teams often keep the language mild during the first hours because they fear escalation, and that mild language shapes every later decision, from evidence preservation to executive notification.
3. Letting the wrong person own the report
RIDDOR reports should be submitted by the responsible person, not by whichever employee first notices the event. HSE guidance updated in 2026 identifies responsible people as employers, some self-employed people, and people in control of work premises when a reportable event has occurred.
Ownership matters because the person who reports usually controls the quality of the facts submitted. If a contractor, agency worker, visitor, or self-employed person is involved, the site must decide who controls the premises, who controls the work, and who has the duty to notify. When that decision is vague, the report may be delayed while each party assumes another party is handling it.
The control point is simple enough to audit. Every site should define the responsible-person rule before the incident happens, including contractors and shared premises. That rule belongs in the incident response plan, the contractor onboarding package, and the manager's first-hour checklist.
4. Treating dangerous occurrences as optional near misses
Dangerous occurrences are reportable because some high-potential events expose serious control failure even when no one is injured. This is where many organizations weaken RIDDOR because they have trained people to think only injuries create reporting duties.
A collapse, explosion, lifting failure, electrical incident, uncontrolled release, or other high-potential event may deserve legal reporting and immediate control review. Calling it a near miss is not enough if the event fits a defined dangerous occurrence. The same leadership trap appears in near-miss reporting, where the organization celebrates volume while failing to separate ordinary observations from events that nearly reached fatal energy.
James Reason's work on defenses and latent conditions helps leaders avoid this mistake. The absence of injury does not prove the system worked, because a final barrier may have held by chance while upstream defenses had already failed. RIDDOR forces the organization to notice that distinction when the dangerous occurrence category is applied with discipline.
5. Reporting to the regulator while losing investigation evidence
A RIDDOR report is not a substitute for evidence preservation, and the first hour after a serious event still belongs to control of the scene, witness separation, photographs, equipment status, documents, and exposure reconstruction. A legally submitted form cannot repair evidence that was overwritten by cleanup, restart pressure, or informal storytelling.
In more than 250 cultural transformation projects, Andreza Araujo observes that organizations often rush to declare whether an event is reportable before they have stabilized the evidence needed to understand it. That sequence protects the file more than it protects learning.
The better sequence is parallel. One person manages RIDDOR classification and notification duties while another protects the investigation process. The site should preserve the scene, secure logs, record witness availability, and capture control status, using the same discipline described in incident evidence preservation.
6. Over-reporting to avoid judgment instead of improving judgment
Over-reporting can look cautious, but it often hides weak classification skill and sends noisy data into the regulator and the company dashboard. HSE's 7 April 2026 consultation specifically named the need to reduce unnecessary administrative burden while improving the usefulness of workplace injury and illness reporting.
The answer is not to report less. The answer is to decide better. A site that reports everything because managers cannot interpret reportability is still exposed, because the same leaders may fail to identify the event that should trigger shutdown, engineering review, or board attention.
Build a classification review that takes 10 minutes and uses a fixed decision tree. What happened? Was anyone killed or physically injured? Was the injury specified? Did routine work become impossible for more than seven consecutive days? Was there a dangerous occurrence, occupational disease, exposure to a listed agent, or gas event? A short disciplined review beats both panic reporting and casual dismissal.
7. Leaving RIDDOR out of the executive safety dashboard
RIDDOR data should inform the executive dashboard because reportable events reveal severity, classification quality, and the maturity of management response. If RIDDOR is visible only to EHS and legal, senior leaders may never see the pattern that should change funding, staffing, maintenance, or contractor decisions.
This is especially important where reported cases are too clean. A site with difficult work, old assets, high contractor activity, and no reportable events may be excellent, but it may also be hiding weak reporting thresholds. That is why underreporting in safety should be reviewed next to RIDDOR classifications, not after a regulator asks questions.
The executive dashboard should show reportable events by category, time to classification, repeated activity involved, control failure, overdue investigation actions, and decisions triggered. The logic should match an executive safety dashboard that governs severe risk, not one that only counts injuries after the month closes.
Each month in which RIDDOR data stays outside leadership review allows reporting quality, serious-risk exposure, and control failure to remain technically documented but strategically invisible.
RIDDOR reporting checks leaders should apply
| Decision point | Weak practice | Stronger leadership question |
|---|---|---|
| Reportability | Ask only whether the incident was recorded internally | Does the event meet a RIDDOR category under the 2013 regulations? |
| Severity | Wait for absence duration before classifying the event | Is the injury already specified, fatality-linked, or linked to serious exposure? |
| Ownership | Let EHS submit without clarifying legal duty | Who is the responsible person for this worker, premises, or activity? |
| Near miss | Call every no-injury event a near miss | Does the event fit a dangerous occurrence category or reveal failed critical controls? |
| Learning | Close the report when the form is submitted | What control, decision, or operating condition changed because the report was made? |
RIDDOR reporting is strongest when it forces classification, evidence, ownership, and corrective action into the same management conversation. The form is the legal output, but the leadership value sits in the decisions the report triggers.
Conclusion
RIDDOR reporting should help leaders see serious work-related harm and dangerous occurrences with enough clarity to act before the pattern repeats. When it becomes only a compliance upload, the organization may satisfy the regulator while weakening its own ability to learn.
If your company needs to connect reporting duties, investigation quality, dashboards, and culture diagnostics into one management system, request a diagnostic through Andreza Araujo.
Perguntas frequentes
What is RIDDOR reporting?
Who is responsible for making a RIDDOR report?
When must an over-seven-day injury be reported under RIDDOR?
Is every near miss reportable under RIDDOR?
How should leaders use RIDDOR data?
Sobre a autora
Andreza Araujo
Global Safety Culture Specialist
Andreza Araujo is an international reference in EHS, safety culture and safe behavior, with 25+ years leading cultural transformation programs in multinational companies and impacting employees in more than 30 countries. Recognized as a LinkedIn Top Voice, she contributes to the public conversation on leadership, safety culture and prevention for a global professional audience. Civil engineer and occupational safety engineer from Unicamp, with a master's degree in Environmental Diplomacy from the University of Geneva. Author of 16 books on safety culture, leadership and SIF prevention, and host of the Headline Podcast.
- Civil Engineer (Unicamp)
- Occupational Safety Engineer (Unicamp)
- Master in Environmental Diplomacy (University of Geneva)