Near-Miss Cup
Near-Miss Cup is a 2-week team contest for safety observations reported per person, so smaller sites can win on a fair, per-capita basis. It turns near-miss reporting into a focused sprint with clear standings and points prizes.
Trusted by frontline teams 15 years of frontline software
Built for: Manufacturing · Warehousing · Construction · Logistics · Utilities
Overview
Near-Miss Cup is a team-based safety contest template built around one verified action: safety.observation_reported. It ranks locations by per-capita reporting over a 14-day window, which makes it a better fit for mixed-size sites than a raw-count challenge. The template is designed to surface near misses, unsafe conditions, and hazard observations before they turn into incidents, while keeping the scoring simple enough for frontline teams to understand.
Use this template when you want a short, visible push to increase reporting and sharpen hazard awareness across one or more locations. It works well for warehouses, plants, yards, and field operations where leaders want more eyes on the floor and a fair way to compare sites. Because the contest is episodic and ends after two weeks, it creates urgency without becoming a permanent leaderboard.
Do not use this template if you need to rank individual workers publicly, if your program depends on manual tallies, or if the behavior you want to reward is not a verified system event. It is also not the right format for incident rates, lost-time metrics, or compliance reporting itself. The contest should encourage quality observations and follow-up action, not replace investigation or corrective-action workflows.
Standards & compliance context
- This template supports proactive hazard reporting, but it does not replace required incident investigation or regulatory recordkeeping.
- Use verified observations only so the contest does not incentivize unsubstantiated reports or paperwork inflation.
- If your workplace has a safety committee or works-council process, share the contest rules in advance and keep the format cooperative rather than punitive.
- Do not use the contest to discourage reporting of injuries, unsafe conditions, or stop-work concerns; those must remain available outside the contest.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
How to use this template
- Set the contest duration to 14 days and confirm the scoring is based on the safety.observation_reported metric action.
- Assign the contest to location teams so each site competes as a unit rather than as individual workers.
- Explain the per-capita rule before launch so smaller sites understand they can win fairly against larger sites.
- Open the contest, then have supervisors remind crews to submit verified near-miss and hazard observations during the two-week window.
- Review the standings during the contest and close with the points prize, then capture any follow-up actions from the observations collected.
Best practices
- Define what counts as a reportable near miss before launch so teams do not guess at the standard.
- Use per-capita scoring whenever locations differ in headcount, shift count, or site size.
- Keep the contest short and time-boxed so it feels like a campaign, not a permanent leaderboard.
- Require verified observations only, and do not count duplicates or vague reports that cannot be acted on.
- Pair the contest with a quick feedback loop so people see that reported hazards lead to fixes.
- Recognize the top sites publicly, but avoid shaming low performers or publishing bottom rankings.
- Give supervisors a simple script for encouraging reporting without pressuring people to invent observations.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does the Near-Miss Cup template actually track?
It tracks verified safety observations reported by each location and ranks teams by per-capita performance. The scoring mode is metric-based, using the safety.observation_reported action. That makes it a fit for programs that want more near-miss reporting without relying on manual entry or subjective judging.
Is this contest meant for individuals or teams?
This template is designed for teams, with team_scope set to location. Because it uses per-capita scoring, a smaller site can compete fairly against a larger one. It is not meant to rank individual workers publicly.
How long should the contest run?
The template is set to 14 days, which matches a short safety push better than an always-on leaderboard. That duration is long enough to create momentum and short enough to keep reporting focused. If you extend it too far, the contest can start to feel like routine tracking instead of a campaign.
Who should run this contest?
A safety manager, EHS lead, or site leader usually owns the setup and review. Supervisors can encourage participation, but the scoring should stay tied to verified system actions rather than informal tallies. That keeps the contest easy to explain and consistent across locations.
Can this be used for compliance reporting or incident reduction goals?
It can support a broader safety program, but it is not a substitute for formal incident investigation or regulatory reporting. Near-miss reporting is useful because it surfaces hazards early, before they become recordable events. The contest should encourage reporting quality, not replace required safety processes.
What is a common mistake when using a safety contest like this?
A common mistake is rewarding raw volume without per-capita fairness, which lets large sites dominate by size alone. Another pitfall is counting unverified reports or duplicate entries, which weakens trust in the standings. Keep the scoring tied to confirmed observations and explain what counts before launch.
How can we customize the prize or recognition?
The template uses points as the prize type, so you can map the win to internal points, badges, or bragging rights. Many teams pair the cup with a short recognition moment at the end of the two weeks. If you want, you can also customize the copy to match your site language or safety campaign theme.
Does this integrate with our existing safety workflow?
Yes, as long as your workflow can record the safety.observation_reported action. The template is built around verified system events, which makes it easier to connect to existing safety reporting or mobile inspection tools. That also reduces the need for manual scorekeeping.
How is this different from an always-on leaderboard?
A contest has a clear start and end date, while a leaderboard runs continuously. This template is episodic by design, which is better for engagement and easier to promote around a specific safety theme. It also avoids the fatigue and fairness issues that come with permanent ranking.
Related templates
Ready to use this template?
Get started with MangoApps and use Near-Miss Cup with your team — pricing built for small business.
