Mar 31, 2026 9:59:15 AM | Safety Why Safety Raffles Backfire (And What to Do Instead)

You've seen the setup before. Employees go a certain number of days without a recordable incident, and everyone gets entered into a drawing for a gift card, a TV, maybe a weekend getaway. It feels like a win. People seem excited. Leadership is happy.

Then someone gets hurt, and you realize the program didn't actually change anything.

Safety raffles are one of the most common approaches to safety incentives, and one of the most misunderstood. The problem isn't that organizations are trying to motivate their people. The problem is that raffles motivate the wrong thing.

The Hidden Cost of "Safety by Chance"

Here's what actually happens when you tie recognition to incident-free streaks: employees stop reporting.

Not because they don't care about safety. Because they don't want to be the person who costs their team the prize. A near miss goes unlogged. A minor injury gets walked off. A hazard gets noticed and ignored because raising it feels like a risk to the group's streak.

The stakes get higher when the prizes do. Some organizations sweeten the pot with big-ticket items: boats, trucks, cash payouts. The intent is to drive engagement, and it does, just not the kind you want. When a major prize is on the line, the pressure to stay quiet about a near miss, a minor injury, or a potential hazard becomes even more intense. Nobody wants to be the person who kills the team's shot at a new truck. So they stay quiet. And the risks stay hidden.

The result is a program that actively discourages the reporting and transparency your safety culture depends on. You're not building safer behavior. You're building quieter behavior. And quieter behavior is dangerous.

There's also the accountability gap. When recognition is tied to chance, employees have no clear line between what they do and what they earn. Safe behavior doesn't guarantee a reward. Unsafe behavior doesn't necessarily cost them one either. The connection between action and outcome, which is the foundation of any behavior change, simply isn't there.

What OSHA Has to Say About It

This isn't just a culture problem. It's a compliance one. OSHA has been clear that safety incentive programs which discourage injury and illness reporting can create serious liability. A raffle tied to incident-free outcomes can cross that line, even if that was never the intent.

An OSHA-compliant safety recognition program rewards proactive behaviors, not the absence of reported incidents. That distinction matters both for your regulatory standing and for the integrity of your safety data.

What Works Instead

Behavior-based recognition flips the model. Instead of rewarding employees for what doesn't happen, you reward them for what does. PPE compliance. Hazard identification and reporting. Participation in safety training. Safe driving records. Completion of safety observations.

These are behaviors every employee can control. They're visible, they're measurable, and they're directly connected to preventing incidents before they occur.

When an employee knows exactly what they need to do to earn recognition, and knows that recognition is theirs regardless of what anyone else reports or doesn't report, the dynamic shifts. Safety becomes something people actively participate in, not something they hope doesn't catch up with them.

The other piece that gets overlooked is what recognition actually does to culture. When your people feel seen, valued, and appreciated for the specific actions they take to keep themselves and their colleagues safe, safety stops being a compliance exercise. It becomes a source of pride. That's a meaningfully different workplace, and it shows up in your incident rates, your morale numbers, and your workers' comp costs.

The Administrative Reality

One of the reasons raffles persist is that they're simple to run. Drop names in a hat, pull a winner, done.

A well-built behavior-based program doesn't have to be complicated. The right platform handles the tracking, the reporting, and the reward fulfillment, and it integrates with how your team already operates. Safety program administration doesn't have to consume your calendar. When the system is designed well, it can run in as little as 30 minutes a month, and it gives you the reporting you need to demonstrate ROI to leadership, not just anecdotal wins.

The Bottom Line

If your current safety program rewards luck, it's not really a safety program. It's a morale event with a compliance problem attached.

Your people deserve a program that recognizes what they actually do, and your organization deserves the measurable improvement that follows.

See what a behavior-based safety recognition program looks like in practice.