Everyone Reports One

It tracks verified safety observation reports using the safety.observation_reported action. The contest ends when every entrant on the team has submitted at least one report, so the goal is participation rather than volume. That makes it a good fit for see-something-say-something programs where the behavior you want is reporting, not competition.

Use this for a location-based team where everyone can reasonably observe and report hazards, near misses, or unsafe conditions. It works best when the entrant list reflects the people expected to participate during the contest window. If some roles cannot realistically submit observations, exclude them or split them into a separate contest so the goal stays fair.

A 14-day duration is a natural fit because it gives people enough time to notice issues during normal work without turning the program into a permanent leaderboard. Many teams run it as a short episodic contest, then repeat it later if they want another participation push. Avoid leaving it open-ended, since this template is meant to end when the threshold is reached or the deadline arrives.

No. This template is intentionally cooperative: there are no standings, no public bottom ranks, and no winner-take-all mechanic. The prize is shared by the whole team once everyone has participated, which makes it safer for mixed-skill groups and better aligned with workplace safety culture.

Announce the contest with a clear example of what counts as a valid observation, then show people how to submit one in the system they already use. Managers should reinforce the deadline, but the contest should feel peer-driven rather than top-down. A simple kickoff message, a reminder mid-way, and a final call near the end are usually enough.

The biggest mistake is making the reporting requirement vague, which leads to low-quality or duplicate submissions. Another common issue is using it for a metric the platform already tracks in another way, when the real behavior is a safety observation report. Also avoid rewarding quantity over quality, because the goal is one meaningful report per person, not a flood of low-value entries.

Yes. Because the template is team-scoped by location, you can run separate contests for different plants, warehouses, stores, or shifts. You can also adjust the deadline, prize type, and messaging to match local safety routines while keeping the same threshold-all structure.

An ad-hoc challenge often depends on manual follow-up and can drift into informal recognition with no clear finish line. This template gives you a defined goal, a fixed duration, and a measurable completion rule based on verified reports. That makes it easier to launch, explain, and audit later.

The template is designed to encourage reporting, not to replace formal incident investigation or corrective action. It should be positioned as a participation goal, with a clear reminder that serious hazards still need immediate escalation through normal safety channels. If your site has works-council or labor-relations considerations, keep the format cooperative and avoid individual ranking.