Weekly MVP voting

Weekly MVP voting is a recurring, group-wide award: each week, members of a group vote for the standout performer, and the tally resets and starts fresh. This guide covers how the weekly cycle works, the scoring options, and who can see tallies, history, and the vote-by-vote audit trail.

Scope: per group, per week#

Weekly MVP voting is scoped per member group (identified by a tag). Every person casts one vote per week per group. If someone belongs to more than one group, they get one weekly vote in each.

Contrast this with the per-game event MVP covered in Events & squads: that award is tied to the players selected for a single match, whereas weekly MVP is a rolling, group-wide vote that doesn't depend on any one event.

The weekly reset#

Voting resets weekly at Monday 00:00 UTC. At that moment the previous week closes and a new week begins with a clean tally. Keep the UTC boundary in mind if your group spans time zones — the reset happens at the same absolute time everywhere, which may fall mid-day locally.

Scoring scheme#

Choose how votes translate into a result:

• Single pick — each voter names one person, and that's one vote.
• Weighted 3-2-1 — each voter ranks up to three people: three points to first, two to second, one to third.

Points and rank are stored and snapshotted, so the recorded result is preserved exactly as cast even if the scheme configuration changes later.

Results visibility#

Whether members can watch the tally as it builds is an organization setting:

• Show live tallies — members see standings update as votes come in.
• Hide until the week ends — standings stay concealed until the weekly window closes, then the result is revealed.

Choose based on whether you want an open race or an impartial end-of-week reveal.

Turnout and closing early#

Turnout is shown so you can see how many eligible members have voted. If everyone who's going to vote has voted, you can close voting early rather than waiting for the Monday reset.

Leaderboards, history, and the audit trail#

Access to historical and voter-level data is permission-gated. This keeps casual results open while protecting who-voted-for-whom.

• Leaderboards and history let you look across past weeks to spot trends and recurring winners. They require the mvp:view-history permission.
• The audit trail — the record of exactly which voter picked which candidate — is owner-only, gated behind mvp:view-audit-trail. This is deliberately the most restricted view, since it deanonymizes individual ballots.

For how these permissions are assigned to roles and groups, see Members, roles & groups.

Weekly vs per-game MVP at a glance#

Related#

• Events & squads
• Members, roles & groups
• Running hackathons