Discipline X Games
scoring·3 min read

How to score a team fitness challenge without arguments

Four steps to settle the scoring before a challenge starts: choose the unit of measurement, convert by time, handle missing data, and publish the rules where the whole team can see them.

By Discipline X Games Editorial Team·Published 2026-11-02

Most team activity challenges fail in the same place: the scoring rules are settled after the competition has already started. This article describes how to settle them in advance, so that every argument happens at the design stage rather than at the results announcement.

Step 1: Pick a single unit of measurement

Do not add “number of sessions” to “number of kilometres”. Choose one base unit and convert everything into it. Two options are common:

  • Weighted activity minutes — easy for participants to understand, and no equipment required.
  • Converted points — more flexible when a team covers many different activities, but the conversion factors have to be published.

For most workplaces, weighted activity minutes are the safer choice, because participants can check their own number without having to trust a conversion table they cannot verify.

Step 2: Convert by time, not by distance

Distance depends on terrain, weather and the measuring device, so two people making the same effort can produce very different numbers. Activity time is the steadier variable.

There is a public basis for an intensity scale. The World Health Organization’s guidance separates moderate from vigorous intensity; its fact sheet cites at least 150 minutes of moderate-intensity activity per week. The Compendium of Physical Activities lists MET values (metabolic equivalents) per activity, which is a way to set conversion factors from published numbers instead of from taste. The factors in the table below follow it: each is the activity’s MET value divided by the MET value of brisk walking.

A conversion table with brisk walking as the 1.0 baseline, using the Compendium’s MET values (accessed 31 October 2026), rounded to one decimal:

Activity Factor (proposed) Note
Brisk walking 1.0 Baseline: 4.8 METs (3.5 to 3.9 mph, level, brisk)
Running 1.8 8.5 METs at 5.0 to 5.2 mph, which is 1.77 times brisk walking; faster running scores higher (9.3 METs at 6 to 6.3 mph is 1.94 times)
Cycling 1.4 6.8 METs at 10 to 11.9 mph (leisure, slow), which is 1.42 times; slow riding under 10 mph is 4.0 METs, 0.83 times

These factors are derived from the Compendium’s MET values, but the speed bands are our choice, and an organiser should publish the bands they use. Swimming and strength sessions are left out of the table because we did not check their Compendium entries; add them only from the Compendium, with the band and the MET value written beside the factor. What matters is not absolute precision but that the number is published in advance and applied to everybody in the same way.

Step 3: Write the rules for missing data in advance

Three situations often come up and can cause argument if no rule exists:

  1. A session was not recorded. Allow a late entry within 72 hours, confirmed by a teammate.
  2. The device did not sync. Use manually entered figures if the device cannot export data; never add both sources together.
  3. Activity outside the list. Participants propose it first, the organisers settle the factor within 24 hours, and it applies from the next time.

Rule 3 is easy to skip and can cause argument. If you can only settle one thing, settle this one.

Step 4: Publish first, do not edit mid-run

Before the opening day, post a worked example scorecard for a hypothetical week. Participants can check the arithmetic themselves and see the consequences in advance. Once the challenge starts, the factors are frozen; any change has to be written up as “week N adjustment” and applies only to the following week. A correction of a technical error (for example a wrong unit) may be applied retroactively, announced with the corrected scores and recorded in the change log.

One common mistake

A common error is rewarding volume instead of consistency (our observation). When every team has someone running 100 km a week, the scorecard is decided by three people and the other twenty lose motivation. The cheapest fix: score on an average with a per-member cap, for example a maximum of 300 points per week per person, then add whatever exceeds the cap to the team’s shared point pool.

Sources


Sources

AI assistance recorded as: AI draft, not edited