Races: the control panel from publication to the protocol

After creation, everything about the race runs from the “Race management” screen. At the top is the “Race readiness” block: what’s set up, what needs attention, how many participants.

1. Team: add a moderator — they’ll review documents and confirm payments (or do it yourself), a co-organizer, and marshals for the checkpoints.
2. Participants and admission: spot counters per class, payment status (paid / needs review / unpaid), and the “Document review” button.
3. Race day prep: GPS tracks, checkpoints, the start list, and results. The hints list what’s missing — “Tracks not uploaded for 2 of 5 classes”, “3 checkpoints without a marshal”.
4. On race day: the “Live map” with participants’ positions and “Checkpoint GPS check-ins”; after the finish — “Reference compliance” and “Final standings”. While a rider has cuts you have not decided on, the results show “under review” for them; accept or reject the cuts (one by one or all at once) and the badge turns into the reference percentage. Off-track excursions need no decision and do not affect the badge.
5. Statuses: “Finish event” closes registration and edits; “Cancel” notifies participants with an entry and those who tapped “Remind me”; moving the start date also reaches them as a notification; only a canceled event can be deleted.