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. Tap a participant’s start number to change it: the new number must be within the class range and unused; the participant is notified. The class can be changed the same way, by tapping its name on the card: the list shows free spots, a new number is assigned in the new class, and payment and documents are kept.
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”. “Checkpoint scanners” opens any scanner for you: race and qualification separately, each checkpoint with its marshal and classes.
4. Start list for day 1 is built from qualification: the rider’s last finished attempt counts (time plus penalties); riders without a result go to the end of their class by number. Only admitted riders with an issued start number are included (the “issued” mark on the moderator screen); if you don’t track number issue in the app, all admitted riders are. If someone is still on the qualification track you get a warning before building. On publish every rider gets a notification with their qualification result and start position. Default class order is strongest first: Master, Pro, Gold, Silver, Bronze, Novice, then Electro, Juniors, Ladies; reorder with the arrows in the list settings. Lines are cut by overall position, so a line at a class boundary may be mixed — that’s expected. Formats: “Mass start”, “By lines” (N riders per line, interval between lines), “Live queue”. The interval gives each line a planned start time (race start + line number × interval) — shown in the list, to the rider and in the notification; the official time is still set by the marshal. The day 2 list is built from day 1 results.
5. Line starts on the scanner. With a published “by lines” or “live queue” list, the start marshal sees the current line with its riders and a countdown to its start, and starts the whole line with one button (riders not present are unchecked with a tap and start later by number). Entering a number from a later line asks for confirmation; if confirmed, the results show a note “started from line 3 instead of own line 7” with a zero penalty — whether to penalize is your call.
6. Marshals and scanners. Qualification and race are timed with separate scanners: a marshal’s “My checkpoints” list shows “Race start”, “Qualification finish” and so on, the part of the day running now is on top, the other one is dimmed and opens only after a confirmation. If a mark still goes to the wrong scanner, the app offers to move it with its original time; an extra tap on a rider who has already finished just says so, without an error. After qualification, “Race control” has “Remove marshals from qualification” — they keep race checkpoints only.
7. On race day: the “Live map” with participants’ positions and “Checkpoint GPS check-ins”; after the finish — “Marks vs GPS”, “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.
8. Reference check per lap. If a class has more than one lap, the track is checked against the reference lap by lap — a cut on any lap is visible even if the other laps are clean. Sections that most riders don’t ride (the reference drifted from the marked course) are ignored. A penalty is suggested per lap with a missed section: the median time other riders in the class need for that section × 1.5, at least a minute — cutting must not pay off. Sections from 200 m, or from 40 s of riders’ time, count; smaller gaps are GPS noise. “Accept all” skips cuts computed from an incomplete track (the rider hasn’t stopped recording yet) — decide those by hand. Record the reference as one clean lap from finish to finish: on import the app warns if start and end don’t meet or there are many stops.
9. Marks vs GPS. The screen compares the marshal’s finish marks with finish passes found in riders’ tracks. Red — a pass without a mark: “Add” puts a mark at the GPS pass time. Yellow — a mark GPS doesn’t confirm, or off by more than a minute — check with the marshal, “Use GPS” moves the time. Grey — an extra lap after the finish, not an error. Marks the server rejected (wrong scanner, rider without a start) sit on the results screen under “Unaccepted marshal marks” — accept or dismiss them.
10. Editing laps. In an expanded result, tap any mark for “Change time” or “Delete mark”; under the attempt — “Add finish pass” (HH:MM:SS). After an edit laps are renumbered by time, the finish is the class’s last lap, total and status are recomputed; your “DNF” and “DSQ” are kept. Every edit is logged. If the counted time exceeds the class time limit, the row shows “over limit N min” and a “Over limit → DNF” button — you change the status, it’s never set automatically.
11. 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.