Recognition Rally

It tracks verified recognition events in the platform, specifically recognition.given and recognition.received. The contest scores departments by event count and normalizes results per person, so larger teams do not have an automatic advantage. It is designed to reward visible appreciation, not subjective judging.

This template is set up as a team contest with department-level standings. That makes it a good fit when you want shared momentum and cross-functional participation instead of a single winner. If you need individual recognition, you would clone and reconfigure the structure rather than use this template as-is.

The template is built for a 14-day duration, which fits the natural cadence of a short culture campaign. That window is long enough for people to notice good work and post recognition without turning it into a permanent leaderboard. If you run it too often, the behavior can start to feel forced.

HR, People Ops, internal communications, or department leaders can run it, depending on who owns culture programs in your organization. The organizer should seed the contest, monitor participation, and close it on time so the standings feel like a true event. It works best when leadership participates without trying to game the outcome.

The template is designed around verified system actions, which helps avoid manual scoring disputes and Goodhart-style gaming. Because it uses per-capita team standings, it is fairer for mixed-size departments than a raw total would be. If your workplace has works-council or employee-relations sensitivities, keep it cooperative and avoid public bottom-rank shaming.

The biggest mistake is treating it like an always-on leaderboard instead of a time-boxed contest. Another common issue is rewarding volume without encouraging meaningful recognition, which can lead to spammy posts. It also helps to avoid mixing in unrelated metrics, because that makes the standings harder to understand.

Yes. The template uses bragging rights as the default prize, but you can pair it with badges, team shout-outs, or a small non-cash reward if your policy allows it. You can also adjust the audience, department scope, and communication plan while keeping the core per-capita recognition contest intact.

An ad-hoc drive usually depends on reminders and manual tracking, which makes it harder to compare teams fairly. Recognition Rally gives you a defined duration, verified scoring actions, and clear standings from the start. That structure makes participation easier to explain and easier to repeat.

Yes, as long as your recognition program records events the platform can count. The template is meant to sit on top of existing recognition behavior rather than replace your program. If your current process is mostly informal, you may want to standardize how recognition is posted before launching the contest.