Race configuration

Each event contains one or more races. A race represents a single competition — for example, a sprint triathlon, an Olympic-distance race, or a relay.

The race list

Open the event from the events list. The event detail page shows three top tabs (Races / Users / Chats / Documents) with the Races tab as the landing view. Each race is a card with its name, gender category, start date/time, distances (swim / bike / run), drafting status, and an icon strip on the right for editing, viewing race log, and starting / stopping the race. The + Add Race button bottom-right opens the wizard for a new race.

Creating or editing a race

For a new race, tap + Add Race — a wizard steps through Basics → Distances → Start → Options → Course map → Numbers. For an existing race, tap the pencil icon on its row — the same fields are presented as tabs in a dialog so you can jump straight to the one you need.

Basics

The race name (e.g. "Elite Men Sprint") and gender category (Female / Male / Open / Relay). The category drives validation for athlete number entries downstream.

Options — race rules

The Options tab is where the rules that govern penalties and officiating live. The screenshot below is the Sprint Elite (Drafting) race in the demo event.

• Tracking enabled — when on, officials' device locations are visible on the race map.
• Drafting allowed — whether drafting is permitted in this race. When off (e.g. the Non-Drafting age-group race), drafting violations are not counted and the drafting penalty type is available.
• Reduce push notifications to users — when on, the race only sends critical pushes (penalties, race start, results). Routine status pings to officials and athletes are suppressed.
• Ready check — enable a pre-race ready check for this race. When on, officials can ask everyone who can submit penalties or incidents to confirm they're ready before the start. See the Ready check guide for how officials run it.
• TO assignments — enable technical-official role assignments per race (e.g. Chief Bike, Bike 1, Penalty Box).
• Stop & go — make stop-and-go penalties available as an alternative to time penalties. Stop & go and the run penalty box are mutually exclusive — turning one on turns the other off, so a run-leg penalty is always either served in the box or as stop-and-go.
• Run penalty box / Bike penalty box — enable the run leg or bike leg penalty box. When the bike box is on, configure how many positions are available (a small dropdown next to the toggle).
• Standard penalty (s) — the time penalty (in seconds) served in the penalty box for a standard violation.
• Drafting devices — enable drafting device integration for this race (only available when drafting is allowed).
• Penalty/Incident Sync — when enabled, penalties and incidents for this race are synchronised with connected external systems.

Course map

The Course map tab is where you upload a GeoJSON course file. The default state shows a venue-area map with a single pin and an Upload course map button.

Once a course file is uploaded, the same tab renders the route in colour-coded swim / bike / run segments.

Numbers — number series

The Numbers tab configures athlete number ranges for the race. Each row is a minimum/maximum pair; tap + Add range to add additional non-contiguous ranges (e.g. 1–99 and 200–299). Numbers are used for validation when officials enter athlete numbers during penalty and incident submission.

When multiple races share an event, each race carries its own number series. The series can also be linked to specific gender categories.

Merging and splitting races

Races can be merged when multiple races run simultaneously on the same course (e.g. elite men and elite women). Merging combines the penalty and incident views so officials see everything in one list. In the web race list, a merged race is labelled with a readable name derived from the races you combined — the wording they share, or their names joined together — so it's easy to recognise at a glance.

Merged races can be split back into separate races if needed.

Locking after first penalty or incident

Once a race receives its first penalty or incident, most configuration options are locked and can no longer be changed. This protects the integrity of the data — changing rules mid-race would invalidate existing records.

Plan your race configuration carefully before the race starts. If you need to make changes after data has been recorded, contact your organisation admin.

Starting and stopping a race

Officials with the right permissions (typically Head Referee or Technical Delegate) can start and stop races from the race view. Starting a race activates real-time features like location tracking and notifications.