What goes wrong
On many busy construction sites the person responsible for health and safety, often a graduate engineer or site manager, is asked to juggle programme pressure, material deliveries and daily briefings. In that environment the distinction between a reportable incident and a routine injury can become blurred. Workers may mention a slip, a near-miss or a piece of plant that failed, and the site engineer simply notes it in a daily diary without checking statutory thresholds. The result is that incidents that fall within the Reporting of Injuries, Diseases and Dangerous Occurrences Regulations are never formally logged, leaving the organisation exposed to regulatory enforcement.
The consequences of under-reporting extend far beyond immediate administrative oversight. Health and Safety Executive inspections can be triggered, leading to formal improvement notices, prohibition notices and substantial fines, as well as prosecution of duty holders under the Health and Safety at Work etc. Act. Beyond the legal exposure, the absence of a proper record means that systemic trends remain invisible. A pattern of recurring equipment defects or minor trench collapses may go unnoticed until a catastrophic failure occurs, eroding safety culture on site and undermining trust across the workforce.
Commonly missed events include non-fatal injuries that result in more than seven consecutive days of incapacitation, specified injuries such as confirmed fractures other than to fingers, thumbs or toes, and dangerous occurrences where no person was hurt. A scaffold collapse, an uncontrolled crane failure or an unpredicted contact with an underground high-voltage electrical cable are all statutory dangerous occurrences. The confusion often stems from site staff assuming that if nobody required an ambulance or took immediate time off, the event does not require statutory notification.
The commercial and practical impact on the project is severe. Unreported incidents that come to light during an HSE audit or insurance claim can halt work entirely while retrospective investigations take place. Subcontractors may face suspension, contractual disputes arise over delay responsibilities, and the principal contractor suffers significant reputational damage that impairs prequalification for future civil engineering contracts. Treating statutory reporting as a secondary paperwork exercise exposes the entire project team to unnecessary operational and legal jeopardy.
Why it happens
A primary cause is inadequate site-level training regarding the scope and definitions within the Reporting of Injuries, Diseases and Dangerous Occurrences Regulations. New graduates and operational supervisors often receive only high-level health and safety inductions that gloss over the specific criteria distinguishing a minor first-aid event from a specified injury or a statutory dangerous occurrence. Without formal guidance on the regulations, staff rely on personal intuition rather than legal criteria.
Construction design and management arrangements under the CDM Regulations frequently fail to establish an unambiguous incident escalation protocol between site management and head-office safety advisors. When the pre-construction information and construction phase plan lack clear flowcharts for reporting thresholds, site engineers assume someone else in corporate management has made the determination, resulting in incidents slipping through the gaps between project tiers.
Programme pressure and commercial targets create an environment where admitting to an incident is subconsciously discouraged. When an operative sustains an injury, the commercial drive to protect site safety statistics and avoid delays can lead to informal arrangements, such as placing the worker on light desk duties without recording that they are incapacitated from their normal work. This directly obscures the seven-day incapacitation threshold defined by the regulator.
Communication breakdowns across multi-tiered subcontract packages severely compound the issue. Trade contractors frequently treat internal injuries or equipment breakdowns as proprietary matters, resolving them within their own teams and failing to inform the principal contractor. The site manager remains unaware that an operative has been signed off work or that a piece of temporary lifting equipment suffered a structural mechanical failure.
The wording of the regulations themselves can be misconstrued by site staff without legal or compliance training. Terms such as dangerous occurrence encompass specific engineering events, including the failure of temporary works, overturning of lifting equipment or unintended contact with overhead power lines. Without immediate access to standard reference tables on site, supervisors frequently default to the assumption that zero harm equates to zero reporting obligations.
- Inadequate operational training on statutory reporting thresholds
- Poorly defined escalation pathways in the construction phase plan
- Programme pressure encouraging informal management of injuries
- Breakdown of communication between trade subcontractors and the main contractor
- Misinterpretation of technical definitions such as dangerous occurrences
- Failure to track worker incapacitation beyond the initial shift
- Assumption by site personnel that corporate teams have already notified authorities
Where JobEng helps
Compliance: certificates, inductions, audits and documents with expiry tracking, next to the QA/QC and incident records of the project. JobEng is an app for UK engineering and construction, on iPhone and Android with the same account on the web. Engineers use it to find work and manage their applications.
How to spot it
The earliest indicator of a reporting breakdown is a persistent divergence between the site first-aid treatment log and the statutory incident register. If first-aid entries record puncture wounds, suspected hairline fractures, eye injuries requiring specialist irrigation or joint dislocations, but no corresponding incident evaluation exists, the site has almost certainly failed to apply the correct classification process. Weekly cross-checks between first-aid records and the safety log are essential to identify these discrepancies.
Another clear warning sign is the informal reassignment of injured operatives to non-manual tasks. When a groundworker, carpenter or steel fixer is suddenly assigned to store management, gateman duties or general paperwork following an incident, the engineer must immediately investigate. If the operative cannot carry out the full range of their normal contractual duties for more than seven consecutive calendar days, not counting the day of the incident, statutory reporting is required.
Reviewing minutes from site subcontractor coordination meetings and daily shift briefings often exposes unrecorded dangerous occurrences. Casual references to plant strikes against trench boxes, temporary propping displacements, dropped structural components arrested by safety netting or flashovers during excavation indicate reportable events that site teams have treated as routine site hiccups rather than dangerous occurrences.
Supervisors should regularly inspect temporary works and plant logs for unrecorded structural distress. A mobile elevated work platform that tilted during tracking, a crane hoist rope that jumped a sheave, or an excavation wall that slipped into a trench box all represent reportable dangerous occurrences under the regulations, regardless of whether operations paused for only a few minutes.
A simple internal compliance audit involves running realistic scenarios during management meetings, such as a concrete skip failure or an operative off work over a weekend following a back strain. Assessing how supervisors categorize these events immediately exposes gaps in understanding, allowing site leadership to correct faulty reporting practices before an external inspection takes place.
- Cross-reference first-aid log entries against the statutory incident register weekly
- Identify workers reassigned to modified or light duties following an injury
- Inspect plant maintenance and breakdown logs for structural or mechanical failures
- Check daily supervisor shift diaries for references to near-miss plant strikes
- Review subcontractor progress meetings for mentions of dropped loads or falsework movement
- Verify whether injured personnel have returned to full duties within seven days
Standard fixes and their limits
The immediate action following any incident is to halt works in the affected area, ensure medical care is provided, and make the location secure. If there has been a structural failure, trench collapse, scaffold movement or plant overturning, all plant and personnel must stand down immediately. Do not attempt to clear debris or right equipment until the scene is fully assessed, as disturbing the site can destroy evidence required by investigators and potentially trigger secondary collapses.
Once the area is safe, gather primary evidence immediately. The site engineer must take date-stamped photographs from multiple angles, record weather and ground conditions, note plant serial numbers and preserve any failed mechanical components or broken rigging. Take written, signed statements from all direct witnesses and supervisors while recollections are fresh, establishing an indisputable factual record before external parties intervene.
The designated competent person, usually the health and safety manager in consultation with the project manager, must determine whether the incident meets statutory reporting criteria. Use official guidance to verify the specific classification, whether it is a specified fracture, an occupational disease, an over-seven-day incapacitation or a defined dangerous occurrence. If ambiguity remains after reviewing the criteria, professional prudence dictates consulting legal or corporate safety advisors rather than choosing not to report.
Submit the formal notification to the Health and Safety Executive via the approved online reporting system within statutory timeframes. Fatalities and specified injuries must be notified without delay, with full written reports submitted within ten days, while over-seven-day incapacitation injuries must be reported within fifteen days of the incident date. Retain the official confirmation receipt and reference number within the site health and safety file.
Recognise the limits of administrative reporting; submitting a form does not resolve the physical or organizational failure that caused the event. If the incident involved temporary works movement, retaining wall instability or plant foundation settlement, the temporary works coordinator and structural designer must inspect the works, carry out fresh calculations, and issue a formal redesign or revised method statement before work resumes.
- Cease work immediately, secure the perimeter, and make the incident area safe
- Preserve all physical evidence, take comprehensive photographs, and record witness statements
- Evaluate the incident against statutory criteria with the designated competent safety manager
- Submit the statutory notification through the approved HSE portal within legal time limits
- File the official submission receipt and reference number in the construction phase plan records
- Instruct the structural designer or temporary works coordinator to review any structural failures
- Conduct a formal investigation to rectify procedural flaws and prevent recurrence
Innovative solutions
Integrating the statutory incident register with a BIM model creates a single source of truth for health and safety data. When a report is entered, the location is automatically linked to the 3‑D element, allowing supervisors to visualise exposure zones and to cross‑reference design drawings. This reduces transcription errors and ensures that any corrective action is visible to the whole project team. The approach works well on sites already using BIM for coordination; it requires a modest investment in software licences and training, and a clear data‑management protocol.
Wearable proximity sensors linked to a cloud‑based dashboard give real‑time alerts when a worker enters a high‑risk zone, such as beneath an active crane hook or adjacent to a trench with temporary shoring. The devices record the time, location and duration of exposure, automatically populating the incident register if a threshold is breached. This technology directly tackles the cause of missed reports by capturing events that might otherwise go unnoticed. It is proven on large infrastructure projects, while smaller firms can start with a limited fleet of devices and a simple mobile app, scaling up as confidence grows.
After a dangerous occurrence, drone surveys equipped with high‑resolution cameras and LiDAR can rapidly map the affected area without exposing personnel to further risk. The generated point cloud is overlaid onto the BIM model, highlighting any deformation or loss of material that may not be evident from a visual inspection alone. This method shortens the time between incident and accurate assessment, supporting timely reporting under RIDDOR. Drones are now widely accepted for site inspections; the limitation lies in weather conditions and the need for a qualified operator under the Civil Aviation Authority regulations.
Artificial intelligence applied to historic incident logs can identify patterns that human reviewers might miss, such as a cluster of minor injuries linked to a specific temporary work platform. By flagging these trends early, the system prompts a review of the associated risk assessment before a serious event occurs. The technology is still emerging in the construction sector, but pilot projects have demonstrated its ability to reduce repeat incidents. Implementation requires clean, structured data and collaboration with an AI specialist, making it more suitable for firms that already maintain digital records.
Modular prefabrication of structural and services elements reduces the amount of on‑site manual work, directly lowering the exposure to hazards that trigger RIDDOR reporting. Factory‑built components arrive with documented quality and safety data, enabling the site team to focus on assembly rather than fabrication. While the approach is proven for hospitals, schools and residential blocks, it may be limited by transport logistics and the need for early design coordination. A small contractor can start by specifying off‑site fabricated wall panels or pre‑tested concrete slabs for a single building segment, gaining experience before scaling up.
Embedding RIDDOR compliance clauses into contract milestones ties payment to the timely submission of incident reports and corrective actions. This contractual lever encourages the principal contractor and subcontractors to maintain up‑to‑date registers and to act swiftly when a dangerous occurrence is identified. The mechanism is straightforward to include in standard JCT or NEC contracts, but it relies on diligent monitoring by the client’s health and safety advisor. For firms with limited legal resources, a simple template amendment can be adopted across multiple projects to embed the requirement without extensive bespoke drafting.
Virtual‑reality (VR) based safety inductions allow new workers to experience simulated hazardous scenarios, reinforcing the distinction between reportable incidents and routine first‑aid events. By immersing trainees in a controlled environment, the training highlights the exact triggers for RIDDOR reporting, such as a near‑miss involving a falling object or a structural movement exceeding a defined threshold. The technology is mature for training purposes, though the initial hardware cost can be a barrier for smaller firms. Starting with a shared VR suite at a regional training centre or leasing equipment can provide the benefits without a large capital outlay.
- BIM‑linked digital incident register
- Wearable proximity sensors with cloud alerts
- Drone LiDAR surveys for post‑incident mapping
- AI analysis of historic incident data
- Modular prefabrication to reduce on‑site hazards
- Contractual RIDDOR compliance milestones
- VR safety inductions for clear reporting triggers
A worked example
On a mixed‑use development in the north of England, a scaffold erected for façade work suffered a sudden shift when a wind gust exceeded the design load. The site manager halted work and called the scaffold contractor, but the junior engineer recorded the event only as a ‘minor movement’ in the daily log, assuming it did not meet the RIDDOR definition of a dangerous occurrence. The first‑aid register showed a few bruises, yet the statutory incident register remained empty, creating a discrepancy that later surfaced during the HSE audit.
The HSE inspector highlighted that any unexpected movement of a temporary structure that could have caused injury qualifies as a dangerous occurrence, regardless of whether injury actually occurred. Realising the oversight, the site team consulted the principal contractor’s health and safety advisor, who recommended retro‑fitting the scaffold with tilt sensors that feed data into a cloud dashboard. The incident was then logged as a dangerous occurrence, triggering the required notification within the eight‑hour window. This corrective action also prompted a review of the scaffold design against BS EN 12811, revealing that the original wind‑load calculations were based on outdated assumptions.
The integration of the tilt‑sensor data with the project’s BIM model allowed the engineer to visualise the exact points where the scaffold exceeded its design angle, correlating the movement with the wind‑speed records from the on‑site weather station. This evidence supported a rapid redesign of the bracing system, which was prefabricated off‑site and installed within two days, minimising further disruption. The use of the sensor system also provided an automatic trigger for future RIDDOR reporting: any reading beyond the set threshold generates an alert and a pre‑filled incident form, ensuring compliance without manual interpretation.
The incident taught the team that relying solely on manual logs can miss reportable events, especially when the perceived severity is low. By adopting digital monitoring and linking it to the statutory register, the site achieved a clear audit trail and reduced the risk of regulatory breach. The experience also reinforced the need to involve the structural engineer early when temporary works are designed, ensuring that wind‑load assumptions are current and that appropriate monitoring is specified. The project now uses the sensor‑BIM workflow on all temporary structures, embedding the lesson into the standard operating procedure.
How to prevent it next time
During the design phase, embed a RIDDOR risk register within the overall project risk register, clearly defining the thresholds that trigger a report, such as any unintended movement of temporary works, a near‑miss involving falling objects, or a medical treatment beyond first‑aid. Reference the HSE guidance on dangerous occurrences and align the register with the CDM 2015 duty‑holder matrix. By allocating responsibility for each trigger to a specific role—site manager, temporary works coordinator or health and safety adviser—the team knows who must act and record the event, preventing ambiguity later on.
Specify in the contract documents that the incident register must be a digital platform with audit‑trail capability, preferably linked to the BIM model. The specification should cite relevant guidance such as the HSE’s “Reporting Injuries and Dangerous Occurrences” and require that any entry automatically timestamps, records the reporter, and attaches supporting evidence like photos or sensor data. This ensures consistency and provides a clear evidential basis should an inspection occur. For firms without an existing system, a cloud‑based spreadsheet with controlled access can meet the requirement while a more sophisticated solution is being sourced.
Develop method statements that embed explicit RIDDOR trigger points, describing the exact actions to be taken when a threshold is reached. For example, a method statement for trench shoring should state that any observed movement beyond five millimetres, or any loss of support, requires immediate cessation of work, notification to the temporary works coordinator, and entry into the digital register. Cross‑reference these statements with the site‑specific risk assessment and ensure they are reviewed during the daily toolbox talk. This creates a clear, repeatable process that aligns daily practice with statutory obligations.
Introduce regular inspection hold points that specifically verify the completeness and accuracy of the incident register. During these checks, the health and safety adviser should confirm that all near‑misses, dangerous occurrences and medical treatments beyond first‑aid have been recorded, and that supporting documentation is attached. Any gaps must be escalated to the site manager and, if unresolved, to the principal contractor’s HSE representative. Documenting these inspections creates a paper trail that demonstrates due diligence, which is valuable during HSE audits or insurance reviews.
Capture lessons learned in a central repository after each incident, summarising the cause, the effectiveness of the response, and any improvements to the reporting process. Share these summaries in the monthly safety meeting and update the relevant method statements and risk registers accordingly. By feeding the experience back into the project’s knowledge base, the team builds a culture of continuous improvement and reduces the likelihood of repeat reporting failures. This systematic approach aligns with CIRIA’s guidance on learning from incidents and supports the long‑term safety performance of the organisation.
- Include RIDDOR triggers in design risk register
- Use digital BIM‑linked incident register
- Write method statements with explicit reporting steps
- Conduct daily toolbox talks on reporting criteria
- Perform hold‑point inspections of the register
- Store lessons learned in a central database
- Embed contractual RIDDOR compliance milestones
Who to involve and when to stop
The decision on whether an event must be reported under RIDDOR rests with the duty‑holder who has overall control of the work, typically the principal contractor or the client’s appointed health and safety coordinator under CDM 2015. They must be informed immediately when a dangerous occurrence is identified, and the temporary works coordinator should halt the activity until the cause is investigated and corrective measures are in place. If the incident involves a structural failure, a collapse, or an uncontrolled release of hazardous material, the site manager must stop work instantly and raise the matter to the structural or geotechnical engineer for assessment.
The HSE requires that any reportable incident be notified to the enforcing authority within the statutory time‑frames; failure to do so is a prosecutable offence. Therefore, once a dangerous occurrence is confirmed, the site manager must ensure the notification is sent to the local authority or HSE, copy the client’s health and safety adviser, and document the action in the digital register. If there is any doubt about the classification of an event, the safest course is to notify the authority and seek clarification, rather than risk a breach of the regulation.
How to start
- Download JobEng free from the App Store (iPhone) or Google Play (Android).
- Create your free account as an engineer, technician, graduate or student.
- Open JobEng and start with: compliance: certificates, inductions, audits and documents with expiry tracking, next to the QA/QC and incident records of the project.
Download JobEng free
Free for engineers, technicians, graduates and students. On iPhone and Android, with the same account on the web.
Frequently asked questions
When does a near‑miss need to be reported under RIDDOR?
A near‑miss that could have resulted in injury or damage, such as an uncontrolled fall of an object or a temporary structure moving beyond its design limit, must be reported. If the event meets the definition of a dangerous occurrence in the HSE guidance, it should be logged and notified within the required time‑frame.
Who is responsible for entering incidents into the register?
The person who first becomes aware of the event—usually the site manager, supervisor or temporary works coordinator—must enter the details. The duty‑holder with overall control, often the principal contractor, ensures the entry is completed and that any required notifications are sent.
What evidence should be attached to a RIDDOR report?
Attach photographs, sensor data, witness statements and any relevant drawings or calculations that illustrate the occurrence. Supporting documents help demonstrate that the incident meets the reporting criteria and provide a clear record for any subsequent investigation.
How long should records be kept?
Incident records, including supporting evidence, should be retained for at least ten years in line with the HSE’s record‑keeping guidance. This period covers the typical limitation for health and safety prosecutions and allows for future reference during audits.
Can digital tools replace the statutory register?
Digital tools can enhance the register by providing audit trails, timestamps and integration with BIM, but they must still meet the statutory requirement of a complete, accessible record. The system used must be approved by the duty‑holder and capable of producing the information in the format required by the HSE.
JobEng is free to download on iPhone and Android. Firms can ask about a free month of the full platform.
Questions about the product or your data? See support and the privacy policy.