Near miss reporting form template: capture the warning and close the action

A near miss is an event that did not cause injury or ill health but had the potential to do so. Report it while the facts are fresh, make the area safe, identify what could have happened, and assign actions that are checked for effectiveness. A form is useful only when it leads to a safer system of work. Copy the Great Britain form below for workplace events and adapt it to the organisation's incident process.

An ordinary near miss is usually an internal learning event. Some specified high-potential events are reportable dangerous occurrences under RIDDOR, even where nobody is hurt. HSE's dangerous-occurrence guidance points to the Schedule 2 categories. Do not assume “no injury” means “not reportable”, and do not assume every near miss must be sent to HSE. The responsible person should make the RIDDOR decision promptly using current official guidance. This page is a form for facts, triage and action, not a legal determination for a particular incident.

The live Complys incident reporting page is the commercial destination. The existing incident investigation report template, N5-308, owns a fuller investigation after an event. This proposed form is narrower: a fast reporter-friendly record and action follow-through. Do not duplicate the investigation in a long free-text box at the moment someone is trying to make an area safe.

Use the form in the right order

First attend to any person who may be injured or exposed and control an immediate danger. If there is a gas release, unstable structure, live electrical hazard or other serious condition, follow emergency/site procedures and keep people clear. Only then collect enough facts to prevent recurrence. Preserve relevant evidence safely; do not disturb a scene unnecessarily or ask a reporter to re-create a hazardous event for a photograph.

Invite reports from employees, agency workers, subcontractors and others who see a hazard. A useful reporting culture does not require a worker to prove a root cause before submitting a report. Let them state what happened and what they observed, then let a supervisor or investigator assess causes. HSE's incident-investigation workbook distinguishes immediate circumstances from underlying factors. A form that invites blame before facts are gathered can discourage reporting.

Copyable near miss reporting form

Use one event ID. Blank fields must be completed or marked “not known”; do not fill gaps with assumptions. Keep personal information proportionate and protect identities where appropriate.

A. Immediate report and safety action

The first description should be in ordinary words: “A suspended load swung across the pedestrian route; no one was in the route,” rather than “operator negligence”. Do not write “no harm” until the team has checked whether a person was exposed or injured. If an injury or illness did occur, use the relevant accident or exposure process as well; this form should not hide it.

B. Factual event record

Record the potential harm realistically. A dropped small object over an empty exclusion zone may call for a different priority from a load that passed inches from a worker. The absence of injury can be luck or the success of an existing control; investigate which. Avoid speculative injury severity figures presented as official thresholds.

C. Escalation and RIDDOR decision

HSE says only certain work-related events meet RIDDOR reporting conditions; its responsible-person guidance explains who makes the report. A near miss can fit a specified dangerous-occurrence category without an injury. The owner must compare the facts with the current Schedule 2 description, not tick “near miss = no RIDDOR”. Contractual client notice can be separate from statutory reporting. Keep the decision and its rationale with the event file.

D. Causes, controls and learning

Do not stop at “worker failed to follow procedure”. Ask whether the procedure was workable, equipment available, staffing and timing realistic, and the hazard visible to the person doing the work. HSE's learning guidance stresses implementing recommendations, not merely writing them. The appropriate depth of investigation depends on actual and potential consequences. Escalate complex, repeated or high-potential events to a competent investigator and use the separate investigation record.

E. Corrective and preventive action tracker

Prefer changes that control the hazard in the work system: separation, engineering, redesign, reliable isolation or a clearer work sequence. A reminder sign or toolbox talk may support those changes but rarely fixes a missing barrier or defective guard by itself. Assign a named owner and due date, and state what evidence proves the control is in place. Then observe the work or otherwise test the control. “Action raised” is not “risk reduced”.

F. Closure and communication

Tell the reporter what changed. That feedback is part of a credible near-miss process. If a control fails the effectiveness check, reopen the action. Keep the event record and supporting evidence according to the organisation's policy and any statutory/contractual requirements; do not invent one universal retention period for all near-miss reports.

Worked example: vehicle and pedestrian route

A delivery van reverses into a shared loading area. A pedestrian moves behind it but steps back before contact. The supervisor stops vehicle movements and temporarily closes the route. The reporter records the van, time, planned delivery, absence of injury and the layout seen. A review finds that the marked pedestrian route directs people behind vans during peak deliveries. The corrective action is not simply “tell pedestrians to take care”; the site redesigns or segregates the route, agrees the traffic plan with drivers and tests it during the next delivery. A manager reviews whether the event fits any RIDDOR dangerous-occurrence category and records the reasoned answer rather than assuming every near miss is or is not reportable. The reporter receives feedback after the new route is observed working.

Common form failures

• Collecting a long narrative before making the area safe.
• Labelling an event “no injury” without asking whether anyone was exposed or a dangerous occurrence may apply.
• Writing a cause as blame without testing planning, equipment and system factors.
• Leaving an action with no owner, due date or proof of completion.
• Closing a case when a sign is ordered, before the risk control works in practice.
• Failing to share learning with another site where the same hazard exists.
• Discouraging reports because a worker cannot identify the technical root cause.
• Treating software submission as a statutory HSE report.

The Complys incident reporting page is the relevant money page for an incident-record and action workflow. Verify current implementation and terms before claiming automated RIDDOR reporting, investigation or escalation. A platform can help keep a dated record and assigned actions; people must make the site safe, evaluate reportability, investigate proportionately and verify the fix.

Source, claim, owner, product, links and writer-side QA

Terminal writer-side disposition: READY.