1
Incident Occurs
Incident Occurs: A worker on a construction site is struck by a falling object (dropped bolt from scaffolding) and sustains a cut requiring 5 stitches. Supervisor immediately initiates first aid and begins incident documentation.
RIDDOR (Reporting of Injuries, Diseases and Dangerous Occurrences Regulations 2013) is the UK legislative framework mandating that employers report specified workplace incidents to the Health and Safety Executive (HSE...
A practical sequence teams can use to standardize adoption and reduce risk.
1
Incident Occurs: A worker on a construction site is struck by a falling object (dropped bolt from scaffolding) and sustains a cut requiring 5 stitches. Supervisor immediately initiates first aid and begins incident documentation.
2
Initial Assessment - Immediate or Serious? The supervisor consults the RIDDOR Serious Injury list. The injury is a laceration (not on the serious list). However, if the worker is admitted to hospital for observation or treatment beyond primary care, RIDDOR triggers. In this case, no hospitalisation, so not immediately reportable under serious injury criteria.
3
Monitor Work Absence: The worker is off-site for medical treatment. The supervisor tracks the absence: Day 1 (incident day), off-site; Day 2, Day 3 (weekend, not counted), Day 4, off-site medical review; Day 5, returns to modified duties. Total 2 days off work (not exceeding 7 calendar days).
4
Absence Exceeds 7 Days Threshold: Suppose the worker's infection requires extended care, and absence extends to 8 calendar days (including weekends/rest days, counted consecutively from date of incident). The "over-7-day" threshold is breached. RIDDOR becomes mandatory.
5
Report Submission: Within 15 days of the accident date, the organisation must submit a RIDDOR report (Form F2508H or online via HSE's RIDDOR Portal). The form captures:
6
Incident date/time
These are the areas where mature teams typically see measurable gains.
01
RIDDOR compliance is non-negotiable. A missed reporting deadline is itself a regulatory breach; HSE will pursue enforcement action even if the underlying incident was properly managed. HSSE teams must maintain incident classification decision trees (written protocols: "If injured worker hospitalised >24 hours, report RIDDOR") to ensure decisions are consistent and defensible. RIDDOR data also serves as a key performance indicator: organisations monitoring their own RIDDOR rate can identify trends (e.g., "Most serious injuries involve MEWPs-upgrade MEWP training and competency standards"). RIDDOR reporting demonstrates duty of care to workers and courts in compensation claims.
02
RIDDOR creates a continuous reporting obligation, generating incident data that flows into investigation logs, corrective action registers, and compliance dashboards. Digital HSSE systems track incident-to-report timelines, flag approaching deadlines, and enforce mandatory fields. Integration with Dockt enables verification that personnel involved in incidents held required competency credentials at time of incident-e.g., "RIDDOR report filed; was the MEWP operator IPAF-certified?" If certification was missing, this triggers compounded liability (incident + competency breach). Post-incident, Dockt flags that the affected worker must complete retraining before reassignment.
Deep Dive
A concise reference focused on implementation, governance, and day-to-day execution.
RIDDOR (Reporting of Injuries, Diseases and Dangerous Occurrences Regulations 2013) is the UK legislative framework mandating that employers report specified workplace incidents to the Health and Safety Executive (HSE). Unlike COSHH (which is preventive) or OHSAS/ISO 45001 (which are management systems), RIDDOR is purely incident notification-a statutory duty to log what happened and inform regulators, enabling HSE to identify trends, investigate serious cases, and pursue enforcement action.
RIDDOR applies to all workplace incidents meeting defined severity thresholds:
RIDDOR reporting is a no-blame legal obligation-non-compliance itself is a breach, separate from the underlying incident. HSE can issue Improvement Notices (requiring corrective action) or Prosecution Notices if patterns of incidents suggest systemic control failure. Data from RIDDOR reports feeds HSE's national injury statistics, informing regulatory priorities and safety guidance.
Also Known As: Incident Reporting Regulations, RIDDOR 2013
Regulatory Standard / Framework: RIDDOR 2013 (SI 2013/1471), Health and Safety at Work etc. Act 1974 Section 28, HSE RIDDOR Guidance (L73)
RIDDOR Incident Classification & Reporting Process - 7-Step Real-World Example:
RIDDOR Severity Hierarchy: Severity Level 1 (Immediate 24h Report) ├─ Deaths ├─ Serious Injuries (fracture, amputation, >24h hospitalisation, loss of consciousness) └─ Dangerous Occurrences (structural collapse, load loss on MEWP, uncontrolled fire)
Severity Level 2 (15-Day Report) └─ Over-7-Day Injuries (inability to perform normal duties >7 calendar days)
Severity Level 3 (10-Day Report) └─ Occupational Diseases (asbestosis, silicosis, occupational dermatitis)
Non-Reportable (Record Only) ├─ Injuries requiring First Aid only (minor cuts, bruises) ├─ Injuries with <7 days absence └─ Pre-existing conditions unrelated to work
RIDDOR compliance is non-negotiable. A missed reporting deadline is itself a regulatory breach; HSE will pursue enforcement action even if the underlying incident was properly managed. HSSE teams must maintain incident classification decision trees (written protocols: "If injured worker hospitalised >24 hours, report RIDDOR") to ensure decisions are consistent and defensible. RIDDOR data also serves as a key performance indicator: organisations monitoring their own RIDDOR rate can identify trends (e.g., "Most serious injuries involve MEWPs-upgrade MEWP training and competency standards"). RIDDOR reporting demonstrates duty of care to workers and courts in compensation claims.
RIDDOR creates a continuous reporting obligation, generating incident data that flows into investigation logs, corrective action registers, and compliance dashboards. Digital HSSE systems track incident-to-report timelines, flag approaching deadlines, and enforce mandatory fields. Integration with Dockt enables verification that personnel involved in incidents held required competency credentials at time of incident-e.g., "RIDDOR report filed; was the MEWP operator IPAF-certified?" If certification was missing, this triggers compounded liability (incident + competency breach). Post-incident, Dockt flags that the affected worker must complete retraining before reassignment.
According to the Health and Safety Executive (2023), the UK construction industry reported 37,000 RIDDOR over-7-day injuries annually, with a rate of 1,565 per 100,000 workers-approximately 5 times higher than the all-sector average. Fatal injuries in construction: 43 deaths in 2022-23. In dredging and maritime, RIDDOR data is sparser (fewer workers), but serious injury rates are comparable to construction. HSE prosecution rates: approximately 2-3% of major incident reports (deaths, serious injuries) result in criminal prosecution, typically resulting in fines of £100k-£500k+ and custodial sentences for gross negligence manslaughter cases.
Manual Legacy Approach: Historically, site supervisors reported serious incidents verbally to a site manager or HSSE advisor, who would handwrite an incident form and file it away. Many organisations failed to systematically apply the RIDDOR severity criteria-incidents were classified informally ("It looked serious"), without written decision trails. Reporting deadlines were tracked informally; some incidents were missed entirely. Post-incident investigation was often superficial (no root cause analysis, no documented corrective actions). If HSE inspected and requested RIDDOR records, organisations scrambled to gather scattered incident files and retrospectively complete missing reports.
Transition to Digital RIDDOR Management: Modern HSSE platforms automate incident reporting workflows. When an incident is logged (e.g., via mobile app or web portal by site supervisor), the system applies RIDDOR classification logic: Is the worker hospitalised? Yes to Serious Injury to 24-hour reporting deadline triggered. Is absence >7 days? Yes to Over-7-day injury to 15-day deadline triggered. Digital checklists guide investigators through root cause analysis (5 Why, Bow-Tie, Fishbone). Corrective actions are assigned to owners with due dates. On a dashboard, HSSE leadership sees: "5 incidents logged this month; 3 reportable RIDDOR; all reported on time; 2 corrective actions overdue."
Integration with Dockt & Competency Validation: Dockt's competency platform validates whether personnel involved in incidents were properly certified at time of incident. Post-incident investigation can query: "Was the injured MEWP operator IPAF-certified? When did their certification expire?" If certification was missing or lapsed, this is documented in the incident investigation, informing corrective actions (e.g., "Mandatory IPAF refresher for all operators within 30 days"). Future incident prevention is improved: Dockt flags that any new MEWP operators assigned to the site must have current IPAF certification.
Benefits of Digital RIDDOR + Dockt Integration:
Serious injuries (fractures, amputations, hospitalisations >24 hours, loss of consciousness) are reported immediately (within 24 hours). Over-7-day injuries are any work-related incident causing absence from normal duties exceeding 7 calendar days; they are reported within 15 days. An injury can be both (e.g., a fracture causing 10 days absence)-in that case, both reporting routes apply, but the 24-hour serious injury deadline takes precedence.
Explore connected concepts often applied alongside this term.
Read term
Explore this related glossary concept.
Explore ->
Read term
Explore this related glossary concept.
Explore ->
Read term
Explore this related glossary concept.
Explore ->
Dockt helps teams move from manual credential tracking to proactive, audit-ready competence management.