Quiz Bowl

This template sets up a team-based learning contest for departments, with a highest_score goal, per-capita scoring, and a 14-day duration. It uses the verified action quiz.passed, so standings are based on completed quizzes rather than self-reported activity. The prize type is points, with suggested rank payouts already defined.

Quiz Bowl fits HR, L&D, enablement, safety, or department leaders who want to drive knowledge checks without turning the contest into a popularity contest. It works well when you want participation across mixed-size departments and need a fair way for a small team to compete against a large one. It is especially useful when the learning content is already available in your system.

The template is designed for a two-week sprint, which is long enough for people to complete a few quizzes but short enough to keep momentum. It can be repeated quarterly, tied to a training rollout, or used as a one-off campaign after policy updates or onboarding. Avoid leaving it open-ended, since that turns it into a leaderboard instead of a contest.

Per-capita scoring makes the contest fair for departments of different sizes, so a five-person team can compete with a fifty-person team. Without that adjustment, larger groups usually win by volume alone, which weakens participation from smaller teams. This template is built to reward engagement and completion, not headcount.

Yes. You can swap in your own quiz topics, set the contest around a specific training module, and adjust the prize to match your culture. The template already uses points as the prize type, but you can pair points with a badge or bragging rights if that fits your rollout. Keep the scoring tied to verified quiz passes so the contest stays clean and easy to explain.

Quiz Bowl depends on a system that can record quiz.passed events, such as a learning platform or internal training workflow. If quizzes are already tracked in your app, the contest can score them automatically without manual entry. That reduces admin work and avoids the common mistake of manually scoring a metric the platform already knows.

The biggest mistake is using raw totals without per-capita adjustment, which favors large departments and discourages smaller ones. Another common issue is making the quiz too broad, so the contest feels disconnected from the actual learning goal. It also helps to define the quiz window clearly and avoid mixing in subjective judging, since this template is meant to score verified completions.

Yes, because the template gives you a repeatable structure: team scope, scoring mode, duration, and prize logic are already defined. That makes it easier to launch quickly, explain the rules, and compare results across departments. Ad-hoc challenges often fail when the scoring rules are vague or when people do not understand how winners are determined.