Safety Days Without Incident
A location-vs-location contest for tracking incident-free days from your OSHA 300 log. Use it to turn a safety streak into a clear race for bragging rights and a badge.
Trusted by frontline teams 15 years of frontline software
Built for: Manufacturing · Warehousing & Logistics · Construction · Retail · Facilities Management
Overview
Safety Days Without Incident is a location-based contest template for tracking incident-free streaks as a race to a fixed milestone. Each entrant is a site, branch, plant, or crew, and the organizer updates the standings using verified safety records such as the OSHA 300 log. The first location to reach the target value, set here at 90 days, wins a badge and bragging rights.
Use this template when you want a simple, visible safety challenge that encourages attention without turning into a permanent leaderboard. It works best for teams that already record incidents consistently and can agree on what counts as a reset. Because the scoring is manual, it is meant for verified external records rather than actions the platform already tracks.
Do not use this format if the goal is to rank individuals, reward the lowest incident count publicly, or create pressure to underreport. It is also a poor fit for sites that cannot maintain a reliable incident definition or update cadence. For those cases, fix the reporting process first, then run the contest. The strongest version of this template is transparent, time-bound, and cooperative: everyone can see the streak, everyone knows the rule, and the finish line is clear.
Standards & compliance context
- Use this template as an engagement layer only; it does not replace OSHA recordkeeping, incident reporting, or any required safety documentation.
- Base updates on verified records so the contest reinforces accurate reporting rather than discouraging it.
- Avoid any rule that rewards hiding incidents or delays a required report, since that can conflict with safety compliance obligations.
- If works-council or employee-representation rules apply, keep the format transparent, non-punitive, and clearly tied to cooperative safety improvement.
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 rules by confirming what counts as an incident, which locations are eligible, and how the 90-day target will be measured from your verified safety records.
- Assign one organizer to review the OSHA 300 log or equivalent source on a fixed cadence and post each location’s current incident-free streak in the standings.
- Start the contest with all participating locations at their current streak values, then reset only the site that has a verified incident and document the reason for the reset.
- Run the contest until one location reaches the target value or the 120-day window closes, keeping updates visible so entrants can see progress without guessing.
- Close the contest by naming the winning location, awarding the badge, and reviewing any reporting gaps, rule confusion, or data delays before the next round.
Best practices
- Use verified incident records only, and never let the contest depend on informal reports or manager memory.
- Define the reset rule before launch so every site knows exactly what breaks the streak.
- Keep the contest at the location level when the goal is shared safety behavior, because individual ranking can create avoidable pressure.
- Publish standings on a fixed schedule so the race feels fair and predictable.
- Treat the badge as recognition, not punishment, and avoid public shaming of sites that fall behind.
- If sites differ in size or risk profile, consider whether a per-capita format or a different goal type would be fairer before using this template.
- Use a short pilot window first if your incident definitions or reporting workflow are still being refined.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this template actually track?
It tracks each location’s current incident-free streak in days, using a manual unit of "days incident-free." The organizer updates the standings from the OSHA 300 log or another verified safety record. The contest ends when one location reaches the target value, which is set here to 90 days.
Is this a team contest or an individual contest?
This template is set up as a team contest with location-level standings. That makes it better for site safety programs, plants, warehouses, branches, or crews where the goal is shared behavior rather than individual ranking. It is not designed for opt-in individual competition.
How often should the standings be updated?
Update them on a regular cadence that matches your safety reporting process, such as daily or after each shift change. The key is consistency, because the streak only works if everyone trusts the same source of truth. If a site has an incident, reset that site’s streak immediately and document the reason.
Who should run this contest?
A safety manager, EHS lead, site leader, or HR partner can run it, as long as they can verify the incident data. The organizer should own the updates, confirm resets, and publish the standings. If multiple locations participate, one central owner should keep the rules consistent across sites.
Can this be used for compliance reporting?
It can support awareness and engagement, but it does not replace OSHA recordkeeping or any required reporting process. Use verified incident data from your normal compliance workflow, and keep the contest separate from official regulatory filings. The template should encourage accurate reporting, not pressure people to hide incidents.
What is the biggest mistake to avoid with a safety streak contest?
The biggest mistake is turning it into a punishment board or using it to shame the site with the most incidents. That creates bad incentives and can discourage reporting. Keep the format cooperative and transparent, and make the prize about recognition, not blame.
Can I customize the target or duration?
Yes. The template is set to a 90-day target and a 120-day duration, but you can adjust both to fit your site’s risk profile and reporting cadence. Many teams choose a shorter target for a pilot, then extend it once the process is working.
How is this different from a permanent leaderboard?
This is a time-bound contest with a clear finish line, not an always-on ranking. That matters because episodic contests are easier to understand and less likely to become background noise. Once a site wins or the window closes, you can reset and run the next round.
What should I pair this with during rollout?
Pair it with a short rule card, a clear definition of what counts as an incident, and a simple update schedule. If you want stronger participation, add a recognition post or a small badge for the winning location. You can also link it to a safety meeting or toolbox talk so the contest supports the broader program.
Related templates
Go deeper on the topic
-
A daily huddle is a brief (10–15 minute) standing meeting held at the start of a shift or workday to align the team on priorities, surface issues, and...
-
A deskless worker is any employee whose job happens without a desk, a company laptop, or a fixed workstation. They're roughly 80% of the global workforce —...
-
A frontline employee app is a phone-first application that gives hourly, field, and deskless workers access to their schedule, pay, announcements, training,...
-
A frontline worker is any employee whose job happens away from a desk — on a production floor, in a patient room, behind a store counter, in a customer's...
-
Artificial intelligence in the workplace: boost productivity, streamline tasks, and empower employees with smarter, more meaningful work.
-
Intranet file naming conventions that improve search, reduce clutter, and help employees find the right document fast.
-
Discover why manufacturing teams need mobile tools — from real-time safety alerts to on-the-go training and frontline recognition. See how MangoApps helps.
-
Discover 7 common intranet platform failures that exclude frontline workers—and the specific capabilities that close the gap for deskless teams.
Ready to use this template?
Get started with MangoApps and use Safety Days Without Incident with your team — pricing built for small business.
