> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nexrex.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Group competitions

> Run official team competitions, choose how teams are scored, and keep standings up to date.

A group competition pits two or more teams against each other on a shared
activity metric. NexRex totals every entrant's qualifying activities within the
competition dates and ranks the teams. Athletes see the same official standings
in the app.

Use a group competition when you want to motivate a club or squad with
friendly rivalry, for example a monthly distance battle between training
groups.

## Before you start

* Create at least two [groups](/coaches/group-plans#create-a-group). Each
  selected group becomes a team.
* Only active members of your organization can be entrants.

## Create a competition

Open **Challenges** and click **New Challenge**. The wizard has four steps:
**Type**, **Basics & Rules**, **Groups & Registration**, and **Review &
Publish**. Enter a name at any point to save your progress with **Save Draft**.

<Steps>
  <Step title="Choose the type">
    Select **Group Battle**.
  </Step>

  <Step title="Set the basics and rules">
    Enter a name, an optional description, and the start and end dates. The
    start and end date can be the same day.

    Pick the **Battle Metric** and **Scoring Method**. See
    [Metrics](#metrics) and [Scoring](#scoring) below.

    Optionally, set the **Competition timezone** using a timezone name such as
    `Asia/Taipei`. Activities count by their completion date in this timezone.
    Leave it blank to use your organization's timezone.
  </Step>

  <Step title="Select the teams">
    Select at least two groups to compete.
  </Step>

  <Step title="Review the roster and publish">
    When you continue to **Review & Publish**, NexRex saves the competition as a
    draft and freezes the team roster from the current group members. Review the
    team assignments, then click **Publish Challenge**.
  </Step>
</Steps>

### How the roster is frozen

The competition roster is separate from your club groups:

* Each team starts with the members of its group at the moment you reach the
  review step.
* If an athlete belongs to more than one selected group, they stay on the
  first selected team.
* Later changes to the groups themselves don't change the competition roster.
  To move, add, or remove entrants, [edit the competition](#edit-a-published-competition).

<Note>
  If the draft changed in another browser tab, NexRex asks you to click
  **Reload latest draft** before saving. Your inputs stay visible until you
  reload.
</Note>

## Metrics

Every entrant's qualifying activities are summed for the chosen metric:

| Metric             | What counts                            | Unit                                                          |
| ------------------ | -------------------------------------- | ------------------------------------------------------------- |
| **Total distance** | Activities with a recorded distance    | Kilometres (shown in miles for athletes using imperial units) |
| **Total duration** | Activities with a recorded duration    | Hours                                                         |
| **Training load**  | Activities with a NexRex training load | Training load (TL)                                            |
| **Activity count** | Every activity                         | Activities                                                    |

Only activities completed between the start and end dates, inclusive, in the
competition timezone count.

## Scoring

Choose how teams are ranked:

* **Team Total**: teams are ranked by the sum of all their entrants' values.
* **Team Average** (per member): teams are ranked by their total divided by
  the team's size. Use it when team sizes differ.

### How per-member scoring works

NexRex divides the team total by the full roster count for that team. The
count includes entrants with no qualifying activities. NexRex rounds the result
to two decimals.

For example, a team of four runs 10 km, 8 km, 7 km, and 0 km. Its per-member
score is 25 km ÷ 4 = 6.25 km.

### Ranks and ties

* Teams with the same score share a rank. The next team skips ranks
  accordingly, so two teams tied for first are followed by a team in third.
* Teams with a score of zero are still ranked.
* Teams with no entrants appear in the standings but are left unranked.

## Edit a published competition

Open the competition from **Challenges** and click **Edit competition**. You can
change:

* The name and description.
* The metric and scoring method.
* The start date, end date, and competition timezone.
* The teams in the competition. At least two teams must remain. Removing a
  team also removes its entrants.
* The roster. Move an entrant to another team, remove an entrant, or add an
  active organization member to a team.

When you change the roster, teams, metric, scoring, dates, or timezone, the
save button reads **Save and recalculate**. NexRex recalculates the entire
competition period. Each entrant's activities count only for their current
team.

When you change only the name or description, the button reads **Save
details**. The current results stay as they are.

### Resolve an edit conflict

If another coach saved changes after you opened the editor, your save fails
with a conflict. Your edits stay on screen. Click **Reload latest rules**,
review the latest version, then reapply your changes and save again.

## How results refresh

NexRex calculates official standings:

* When you publish the competition.
* Automatically as new activities sync, including corrected or removed
  activities.
* When a coach who manages the competition requests a rebuild.

NexRex also checks active competitions on a regular schedule, so results catch
up even if an update was missed.

Click **Check for updates** below the standings to load the latest results.
The standings show when they were last updated and one of these states:

| State          | What it means                                                         |
| -------------- | --------------------------------------------------------------------- |
| **Pending**    | An update is queued. NexRex shows "Waiting to update standings."      |
| **Rebuilding** | NexRex is calculating standings. Check again shortly.                 |
| **Current**    | The standings reflect the latest rules and synced activities.         |
| **Stale**      | The rules changed and the standings need updating.                    |
| **Error**      | The update failed. NexRex retries automatically. Check again shortly. |

While an update runs or after it fails, NexRex keeps showing the last
completed standings when they still match the competition's rules.