A technician almost gets burned by a hot line but catches it in time. A ladder nearly slips but doesn't. A refrigerant fitting almost fails under pressure but holds. None of these become incidents. Almost none of them get reported — and that's the problem.
The reluctance to report near-misses is almost never about hiding something — it's that nothing happened, so it doesn't register as worth mentioning. That instinct is exactly what a near-miss log exists to override.
Why near-misses matter more than the incidents that follow them
Every serious incident is usually preceded by near-misses that followed the same pattern, unreported, until eventually the pattern caught up. A near-miss log is how you catch that pattern while it's still just a pattern — before it becomes an injury, a claim, or a fatality.
Why crews don't report near-misses on their own
It's rarely resistance to safety — it's that nothing happened, so it doesn't feel like there's anything to report, and there's no simple, fast way to log it without it feeling like extra paperwork for a non-event. If reporting a near-miss takes as long as reporting an actual incident, it won't happen consistently.
What a usable near-miss log needs
Keep It Fast
- Date, location, and crew member involved
- What almost happened, in a sentence or two — not a full narrative
- What contributed to it (equipment, condition, procedure)
- Corrective action, if any was identified
- Whether it's part of a pattern with prior entries
Turning near-miss data into prevention
The value isn't in any single entry — it's in reviewing the log periodically and looking for repeats. Three near-misses involving the same ladder, the same fitting type, or the same job condition is a signal worth acting on before it becomes a fourth incident that isn't a near-miss anymore.
Why leadership tone matters more than the form itself
A near-miss log only works if crews actually use it, and usage depends heavily on how it's introduced. If near-miss reporting is framed as a way to catch problems early — genuinely useful, not punitive — crews report honestly. If it's introduced alongside blame, or if a reported near-miss triggers a disciplinary conversation, crews stop reporting almost immediately, and you lose the exact visibility the system was built to provide.
The businesses that get real value from near-miss logs are explicit about this upfront: reporting a near-miss is never going to be held against the person reporting it. That single framing decision determines whether the system produces useful data or an empty log nobody trusts.
A concrete example of the pattern this catches
Three separate technicians, over several months, each note a near-miss involving the same brand of extension ladder slipping slightly on a particular surface type. Individually, each entry looks minor — nothing happened, no one was hurt. Reviewed together, it's a clear signal: something about that equipment or that surface condition needs attention before the fourth incident isn't a near-miss. That pattern is only visible if the near-misses were logged in the first place, and only useful if someone's actually reviewing the log periodically rather than letting entries accumulate unread.
Get the HVAC Incident & Risk System
Near-miss logs, incident reports, and corrective action tracking built for how HVAC crews actually work.