- Report every near miss to your supervisor, no matter how minor it seems.
- Use the site near miss reporting system and complete the form honestly and promptly.
- Describe what happened, where, when, and what could have occurred if circumstances differed.
- Investigate every near miss to identify the root cause, not just the immediate trigger.
- Implement corrective actions promptly and check they are effective in preventing recurrence.
- Provide feedback to the reporter so they know their near miss was taken seriously.
- Analyse near miss data regularly to identify trends and patterns across the project.
- Share lessons learned from near misses with all teams through toolbox talks and alerts.
- Encourage colleagues to report near misses and support them when they do.
- Recognise and thank workers who report near misses — it takes courage to speak up.
|
- DON'T dismiss near misses as unimportant — they are warnings of future serious incidents.
- DON'T make the reporting process so complicated that people do not bother completing it.
- DON'T exaggerate or minimise what happened — report the facts honestly and accurately.
- DON'T close a near miss report without investigating the root cause properly.
- DON'T delay implementing corrective actions — the same near miss could become an injury tomorrow.
- DON'T fail to give feedback — reporters who hear nothing will stop reporting in future.
- DON'T ignore repeated near misses — they indicate a systemic problem needing urgent attention.
- DON'T keep lessons learned to yourself — share them so other teams benefit too.
- DON'T blame or punish workers for reporting near misses — this destroys the reporting culture.
- DON'T treat near miss data as a negative — high reporting rates indicate a healthy safety culture.
See also: Accident and Incident Reporting (RIDDOR) | Incident Investigation Process
|