A near miss report records an event that could have caused injury or damage but did not. What a near miss report should include, how to keep a near miss log that leads to action, and how to get people to report.
A near miss report records an unplanned event that did not result in injury, illness or damage — but could have. A dropped tool landing a metre from someone, a forklift reversing past a pedestrian who stepped back in time, a gas cylinder found unsecured. Near misses happen far more often than injuries, and they share the same causes, which makes them the cheapest source of safety information an organisation has. The point of a near miss report is not the record; it is the fix that prevents the next one from becoming an incident.
Never measure teams on having fewer near miss reports. A falling count usually means people stopped reporting, not that the site became safer.
An incident report covers events where harm or damage actually occurred and often carries legal reporting obligations. A near miss report covers the event that stopped short. Both should feed the same system, use the same cause categories and lead to the same corrective action process — the only difference is luck. High-potential near misses deserve the same root cause analysis as incidents, and the findings belong in the job safety analysis for that task.
Reporting rates depend on what happens after someone reports. If reports disappear, or lead to blame, they stop. Ettex Forms makes the report itself easy — a short mobile form with photo upload and an anonymous option, sent straight to the safety lead with the location attached — so the remaining work is the part that matters: acknowledging, fixing and feeding back. Share closed near misses in toolbox talks so crews see that reporting changes things.
Any unplanned event that did not cause injury, illness or damage but had the potential to. Unsafe conditions spotted before anything happens are often logged as hazard observations rather than near misses.
Allowing anonymous reports increases reporting, especially early on. Named reports make follow-up questions easier, so most programmes offer both.
Usually not, but certain dangerous occurrences — such as collapses, explosions or failures of lifting equipment — are reportable in many jurisdictions even when nobody is hurt.
A job safety analysis breaks a task into steps, identifies the hazards in each, and sets the controls before work starts. How to run a JSA, a worked example, and how it relates to a job hazard analysis and a risk assessment.
A commissioning checklist confirms that installed systems are complete, safe and working as designed before handover. What to check at each stage, a sample structure for HVAC and electrical systems, and how to track sign-off.
A software request form lets staff ask for new tools while IT checks security, cost and overlap first. The fields that matter, the approval route, and what to record after purchase.