Swap Stars

This template tracks completed shift swaps using the verified action key shift.swap_completed. It counts the number of completed swaps during the contest window and ranks entrants by highest score. Because it uses platform-tracked events, it avoids manual entry and reduces disputes about whether a swap actually happened.

Use it for frontline teams where shift coverage matters, such as retail, hospitality, healthcare support, call centers, and warehouse operations. It works best when employees can opt in and when swap activity is a meaningful sign of flexibility and teamwork. It is not a fit for roles where shift swaps are rare or tightly restricted.

The template is set to 14 days, which matches the natural cadence of a short contest and keeps momentum high. You can repeat it periodically, but it should remain episodic rather than always on. If you run it too often, the novelty fades and the contest starts to feel like a permanent ranking.

This template is designed to recognize individual contributors who actively help cover shifts. Individual ranking makes the behavior visible without forcing a whole team to compete on something that may depend on staffing patterns. If you need a more cooperative format, a team-based contest or threshold-based goal is usually a better fit.

No, the template excludes managers by default. That keeps the contest fair and prevents supervisors from winning on authority or schedule control rather than peer-to-peer flexibility. If your organization needs a different rule set, customize the eligibility carefully so the contest still feels credible to entrants.

This template uses raw event counts, which works when the audience has similar access to swap opportunities. If your sites or departments vary a lot in size or scheduling density, consider whether a per-capita format or a different goal type would be fairer. The key is to make sure the contest measures opportunity-adjusted behavior, not just who has the most chances.

The biggest mistake is running it as an always-on leaderboard instead of a time-boxed contest. Another common issue is using it in a group where shift swaps are controlled by managers or are too rare to create meaningful competition. A third pitfall is rewarding unverified claims instead of only counting completed system events.

Yes. The template already uses points as the prize type and includes suggested points by rank, but you can adjust the reward structure to match your culture. You can also change the copy, eligibility, and announcement language while keeping the verified swap-count scoring intact.

An ad-hoc request depends on memory, visibility, and manager follow-up, so the same people often get asked repeatedly. This contest makes the behavior explicit, measurable, and time-bound, which helps surface the flexible teammates who consistently step up. It also gives you a repeatable way to recognize that behavior without relying on informal praise alone.