5 Best Practices for a Hazard and Observation Program Employees Actually Use

Key Takeaway

• Make hazard reporting quick and simple so employees are more likely to participate.
• Remove unnecessary barriers by focusing on the observation, not the reporting category.
• Build trust by following up and showing employees their reports lead to action.
• Track reporting trends alongside incidents to measure engagement and uncover risks.
• Connect every report to a corrective action, training opportunity, or safety improvement.

Want More Hazard Reports? Start Here

Every EHS team wants more hazard and observation reports. They’re not short on hazards, they're short on people willing to document what they see. The gap between the two is where most safety programs quietly stall.

Here's what separates programs that get real participation from ones that collect dust.

1. Make reporting fast, or it won't happen

If submitting a report takes multiple minutes and multiple screens, most employees won't bother, especially for something that seems minor at the time. Kay Yoder, SVP of EHS at Southern Glazer's Wine and Spirits, has pointed to this directly: streamlining reporting tools so participation takes minimal effort is one of the two things that keep a safety program engaging. Mobile-first reporting, a photo instead of a form, a QR code instead of a login screen, isn't a nice-to-have. It's the difference between a hazard getting documented or getting forgotten by lunch.

2. Stop making employees guess which category their observation belongs in

One approach worth borrowing from safety leaders who've solved this well: combine near misses, unsafe conditions, and general suggestions into a single reporting category, rather than forcing employees to pick the "right" one. Doing this removes a barrier that most programs don't even realize exists. The reasoning is simple, combining categories tells employees the organization wants their knowledge, whatever form it takes. If someone has to stop and think about which of five forms applies before they even start, you've already lost some of them.

3. Close the loop, every time

Collecting a report is half the job. The follow-up sequence, review, investigate, correct, and then tell the person who reported it what happened, is where trust in the system actually gets built. Skip that last step and reporting quietly drops off, because employees stop believing anything happens when they speak up. It doesn't need to be an all-hands announcement. Something as simple as a notification confirming an action was taken is often enough.

4. Watch the trend, not just the count

A rising number of near misses and observations isn't necessarily bad news, it's usually a sign employees trust the system enough to use it. The reverse is worth paying attention to as well: a sudden drop in reports doesn't automatically mean things have gotten safer. It can just as easily mean people have quietly stopped engaging. Comparing observation volume against incident rates over time is what tells you which situation you're seeing.

5. Give every report somewhere to go

A hazard report that sits in a queue with no visible next step teaches employees not to bother next time. The stronger model connects reporting to action: a corrective action with an owner and a due date, training assigned when the root cause points to a skill gap, or a toolbox talk built around the real example that was just reported. A single observation, handled this way, can end up protecting far more people than just the one who reported it.

The throughline

None of these five practices work in isolation. Fast reporting without follow-through breeds cynicism. Follow-through without fast reporting means most hazards never make it into the system in the first place. The organizations getting real value out of hazard and observation programs are the ones treating all five as one connected system, not five separate initiatives.