Home → Guides → Near-miss reporting: what to report and why it matters
Incident management

Near-miss reporting: what to report and why it matters

A near miss is an event that did not cause injury or ill health but had the potential to do so. A falling object that lands beside a worker, or a vehicle that narrowly misses a pedestrian, may reveal a control failure before a person is harmed. This guide uses HSE guidance and RIDDOR for Great Britain; Northern Ireland has a separate reporting regime. HSE's incident investigation guidance uses near-miss information as a route to prevention. The useful question is not whether the event was lucky enough to avoid harm, but what allowed it to happen and what might happen next time.

Near miss, accident and dangerous occurrence

An accident has caused harm or loss. A near miss has not, but could have. A dangerous occurrence is a specific type of high-potential incident listed in RIDDOR Schedule 2. Some dangerous occurrences may look like near misses in ordinary language, yet they are reportable to HSE if the legal criteria are met. Most ordinary near misses are not automatically RIDDOR-reportable. Never use a label in an internal app as the legal determination. Check the facts against HSE's dangerous-occurrence guidance and use the RIDDOR checker only as an aid, not a regulator decision.

The existing RIDDOR explanation and accident-book comparison own those statutory reporting questions. This guide owns the general workplace learning process. The pharmacy dispensing near-miss guide addresses a specific sector workflow and should remain separate.

Make reporting usable

Ask for the date, place, task, what happened, potential harm, immediate controls and people who can clarify the facts. Allow a worker to report quickly before details fade. A manager can follow up for fuller information. Reports should focus on work conditions, equipment, supervision and interfaces, not simply blame the person nearest the event. Explain how the organization uses reports and when it shares feedback. If people never hear what changed, reporting will dry up.

Provide a way to report hazards as well as events. A missing guard found before a machine is used may be a hazard observation rather than a near miss. That classification is less important than ensuring the guard is fixed and any similar machines are checked. Avoid incentives that reward low report numbers, because an apparent decline may mean people have stopped speaking up.

Investigate and act proportionately

First make the area safe and provide help if anyone was injured. Preserve useful evidence. For a high-potential event, investigate promptly, including whether a RIDDOR notification is required. Ask what barriers failed and whether the risk exists elsewhere. Assign corrective actions, owners and dates. Confirm completion in the field, not just in the report record. Review repeated near misses by location, task or contractor to find a pattern that an isolated report misses.

An investigation should be proportionate to potential severity and learning value. A dropped screw and a suspended load falling beside a person do not require identical response. Workers and safety representatives often know why a procedure is difficult to follow; involve them in designing workable controls. Recheck later whether the change prevented recurrence.

Records and commercial route

Keep records that support action, trend review and statutory decisions where relevant. Sensitive names and health details should be limited to those with a need to know. A record may show that a RIDDOR check was made, but the actual report, if required, must be submitted through HSE's official route. The incident reporting software page is the commercial destination for evaluating how to organize reports. This article does not claim that Complys makes automatic RIDDOR determinations, submits reports to HSE, offers anonymous reporting, or captures reports on a specific mobile device.

Capture and learn from near misses

Complys gives you a structured way to record near misses, actions and trends. Deciding what is statutorily reportable stays with you and your competent person.

Explore incident reporting software →

General information, not legal advice. Verify current requirements against the primary sources linked above.