Near Miss Reporting Toolbox Talk Template
A near miss is an event that could have caused harm but did not. A dropped item that narrowly misses someone, a vehicle reversing across a pedestrian path or a scaffold component falling into an empty zone can reveal a failed control. Reporting lets the team remove the immediate danger, understand why it happened and prevent a more serious event. A toolbox talk should show the actual reporting route and follow-up, not merely ask workers to “be careful”. HSE says near misses should not be ignored because they reveal how well safety risks are being managed. HSE near-miss book.
Report the warning before it becomes an injury
Important legal distinction: Not every near miss is reportable to HSE under RIDDOR. Some specified “dangerous occurrences” are reportable; the responsible person must apply the current Schedule 2 criteria. All near misses relevant to safety should still be dealt with through the employer's internal process. HSE dangerous occurrences.
Copyable briefing card
| Field | Complete for this site/team |
|---|---|
| Site/team, date and briefing lead | [ ] |
| What counts as an internal near miss here | [ ] |
| Immediate stop/isolate/make-safe route | [ ] |
| Where to submit a report, including offline alternative | [ ] |
| Supervisor/contact and response time | [ ] |
| Who screens RIDDOR dangerous-occurrence criteria | [ ] |
| Feedback route to the reporting worker/team | [ ] |
| Action owner and closure evidence | [ ] |
Opening script: “If something nearly injures someone today, report it even if no one was hurt. First make the area safe without putting yourself in danger. Tell [contact] and use [form/channel]. Say what happened, where, when, what could have happened, and what is still unsafe. The supervisor will decide what needs investigation or statutory reporting; you do not need to know a RIDDOR category before telling us.”
Demonstrate the process
Recognise and protect. Use a real example from the site, such as a reversing plant near miss or a tool dropped from height. Ask workers what immediate protection is needed: stop movement, establish an exclusion, isolate damaged equipment or arrange first aid if someone was in fact harmed. Do not send someone into a live danger to collect photos.
Record facts promptly. The basic report should identify the location, date/time, people or activities involved, the event sequence and immediate controls. Avoid a blame statement such as “worker careless” instead of describing conditions. Keep personal data limited to what the investigation requires. A photograph may help but is not mandatory if taking it would delay control.
Separate internal learning from legal notification. The supervisor or appointed responsible person should screen serious events against the current RIDDOR criteria. HSE lists certain specified dangerous occurrences, such as particular failures of lifting equipment or electrical incidents; the legal decision depends on the detailed facts. A generic near-miss label cannot decide it. If anyone was injured, use the incident and first-aid process and consider the separate reportable-injury rules. HSE RIDDOR incident types.
Close the loop. Assign a corrective action, owner and due date. Check whether the control works, then tell the team what changed. A “number of near misses logged” target can discourage accurate reporting if it turns into performance pressure. Encourage early reports and visible action.
Ask workers
- What near miss could occur in today's work and how would you stop it from recurring immediately?
- Who do you tell if the usual app or network is unavailable?
- What facts would you record without guessing a cause?
- Who decides whether an event meets RIDDOR dangerous-occurrence criteria?
- How will you know your report led to a real change?
Ask one person to show the actual reporting route. If workers do not have access, fix the process before relying on it.
Talk record and action log
| Name/role | Reporting route understood | Question/action | Acknowledgement |
|---|---|---|---|
| [ ] | [ ] | [ ] | [ ] |
Action: [hazard/control], owner [ ], due [ ], checked [ ], feedback to team [ ]. Keep an actual incident record in the employer's designated system, not only this attendance card.
Example: dropped spanner
A spanner falls from a platform and lands in an empty passage. No one is injured. The team stops overhead work, isolates the passage, reports the event and checks tool securing, edge protection and who could have entered below. The supervisor decides whether any legal reporting threshold applies, records the finding, then explains the changed control to the crew. “Nobody was underneath” is not a reason to ignore the event.
Common mistakes
- Assuming all near misses must be sent to HSE under RIDDOR.
- Failing to control an active hazard before filling out a form.
- Recording blame instead of the task, conditions and controls.
- Leaving reports open without action or feedback.
- Making the reporting tool the only route when workers may lack access.
Source, ownership and writer-side QA
Primary sources: HSE near-miss book; HSE dangerous occurrences; HSE reportable incident types. Reviewed 6 October 2026. RIDDOR distinction is explicit; no universal notification instruction. Ownership: No near-miss-reporting topic in the observed live Complys toolbox hub; existing incident/near-miss reporting guidance or form serves recording/process intent, while this is the live briefing card. Final repo collision check remains. Link/product: Parent toolbox-talk hub is a candidate after whole-page route/product QA. Do not imply Complys automatically decides RIDDOR reportability or guarantees action closure. Disposition: READY writer-side; employer process, legal escalation and implementation gates remain.