Task Race to 100
Task Race to 100 is a department-vs-department contest where the first team to reach 100 verified completed tasks wins. It is built for short, high-energy sprints that reward fast execution, not guesswork.
Trusted by frontline teams 15 years of frontline software
Built for: Operations · Customer Support · Logistics · Shared Services
Overview
Task Race to 100 is a department-level contest template for a simple operational sprint: the first team to reach 100 verified task.completed events wins. It is designed for situations where the work is already captured in your system and you want a clean finish line that rewards speed, coordination, and follow-through.
Use this template when you need a short burst of execution around a measurable workload, such as closing tickets, finishing checklists, completing follow-up actions, or clearing a backlog. Because the contest ends the instant a department crosses the target, it creates urgency without requiring complex scoring rules. The structure is team-based, not individual, and it is best when departments are similar enough in size and workload to compete on a raw-number target.
Do not use this template for external KPIs that are not tracked as task.completed events, and do not use it when fairness depends on per-capita scoring or most_improved handicapping. It is also a poor fit for open-ended leaderboards, because the value comes from a fixed duration and a clear race to a finish line. If your audience needs cooperative recognition rather than competition, or if the work is safety-sensitive and should not be gamified as a race, choose a different format. This template works best when the rules are simple, the data is verified, and the team can see progress toward one shared target.
Standards & compliance context
- This template uses verified system events, which supports auditability and reduces the risk of subjective scoring.
- If tasks involve regulated work, confirm that the contest does not pressure employees to skip required checks or documentation.
- For unionized or works-council environments, keep the format cooperative and transparent, and avoid punitive public ranking of individuals.
- If task completion is tied to safety, quality, or compliance workflows, ensure the contest does not conflict with mandatory procedures or escalation rules.
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
- 1. Define exactly which task.completed events count and write the rule in plain language before the contest starts.
- 2. Confirm that each department has access to the same task source so the standings reflect verified work, not manual claims.
- 3. Set the target at 100 completed tasks and keep the duration at 14 days unless your workload cadence clearly requires a different sprint length.
- 4. Launch the contest with department standings visible so teams can see who is leading and how close each group is to the finish line.
- 5. Monitor the event feed for duplicate, misclassified, or late-entered tasks and correct issues quickly so the race stays trusted.
- 6. End the contest the moment a department crosses 100, publish the winner, and review what helped the team move fastest.
Best practices
- Count only verified task.completed events so the contest rewards real execution instead of self-reported activity.
- Keep the target fixed and public from day one so teams do not feel the finish line moving mid-race.
- Use department-level standings when the goal is shared throughput, not individual heroics.
- Choose a 14-day window for a sprint-like pace unless your operational cycle clearly runs shorter or longer.
- Define what does not count, such as reopened tasks or duplicate completions, to prevent disputes.
- Make the task definition narrow enough that every entrant understands the same behavior is being rewarded.
- Review the data source before launch so missing integrations or delayed syncs do not distort the race.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What kind of tasks does this template count?
It counts verified task.completed events, so it works best for work already tracked in your system. Use it for operational tasks like ticket closures, checklist items, follow-up actions, or other completed work events. It is not meant for manual entry of external numbers like sales or steps. If the task is not a real system event, this template is probably not the right fit.
Is this a team contest or an individual contest?
This template is set up as a department-level team contest. That makes it a good fit when you want one shared finish line and a clear winner across groups. It is not designed as an opt-in individual leaderboard. If you need individual competition, you would clone and reframe the structure before launch.
How often should we run a Task Race to 100?
This template is designed as an episodic contest with a 14-day duration. That cadence is long enough for teams to build momentum but short enough to keep urgency high. It is usually better as a periodic sprint than an always-on leaderboard. Once the race ends, reset the target and start a new round if needed.
Who should run the contest?
An operations lead, team manager, or program owner should run it and monitor the standings. The organizer should confirm that the task.completed events are being captured correctly and that each department understands what counts. If there is any ambiguity about task definitions, resolve it before launch. Clear rules matter more than frequent reminders.
How does this avoid unfair competition between large and small departments?
It does not use per-capita scoring, so it is a raw-number race. That makes it best when departments have similar capacity or when the goal is to create a straight sprint to a shared target. If team sizes vary widely, consider a per-capita format or a most_improved contest instead. Raw targets are fair only when the audience can realistically compete on the same footing.
Can we use this for safety, training, or recognition work instead of tasks?
Only if the underlying action is still task.completed in your system and the contest rules are clear. For safety or learning, a more specific template is usually better if you want to count safety.inspection_completed, course.completed, or recognition.given. This template is intentionally narrow so the finish line stays simple. If the work type changes, the template should change with it.
What are the most common mistakes when launching this contest?
The biggest mistake is counting vague or unverified work instead of real completed tasks. Another common issue is setting the target too high for the 14-day window, which turns the race into a slog. Teams also get confused when the organizer changes what qualifies after launch. Lock the rules, verify the data source, and keep the finish line visible.
Can we customize the prize or ranking logic?
Yes. The template uses points as the prize type, but you can adapt the reward structure to fit your program. The ranking logic is fixed around first_to_target, so the first department to hit 100 wins outright. If you want second and third place recognition, you can still use the suggested points by rank as a fallback for reporting or secondary awards.
How is this different from an ad-hoc team challenge?
An ad-hoc challenge usually lacks a fixed target, a defined end date, and a clear scoring rule. This template gives you all three, plus a verified metric source and a simple win condition. That makes it easier to explain, easier to track, and easier to repeat. It also reduces disputes because the contest ends the moment a team crosses the line.
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 Task Race to 100 with your team — pricing built for small business.
