| Point | Marshal | Status | Seen |
|---|
Marshals get a big "Call race control" button that rings this number, with this name on it.
What every marshal and crew member sees under Info on their phone: start time, where to meet, what to wear, and a link to the briefing document if you have one.
Three ways, use any mix. Everything lands in the list below to check before saving.
Columns for name, mobile and (optionally) point, team and role (e.g. "team leader").
Copy the list or messages and paste. Names and numbers are picked out.
Everyone on this race, plus anyone you've just added (marked new). Pick each marshal's point, or a crew role (lead, tail…) for people who move with the race. Change anything here and press Save marshal list: links already sent keep working. Points come from the race's key points on the setup page.
| Name | Mobile | Point | Team (optional) | Role |
|---|
Texts each person a link with big YES / NO buttons (texts can't be replied to, so the link is how they answer). Answers appear here as they come in.
Who gets asked: the marshals saved in step 3 (or anyone still waiting in the step 3 list, e.g. last year's list loaded from the organisation).
| Name | Mobile | Answer | Note |
|---|
Each marshal has a personal link: no app, no password. Send it by text or WhatsApp.
| Point | Marshal | Team | Role | Tracker (crew) | Link | Texted |
|---|
Checking…
Split the course into sections, each with a section leader who sees only their stretch on their phone and can message it. Race control then sees a summary per section. Marshals with the same team (e.g. "Water station 3") share a team leader who can check the whole team in at once.
| Section | From km | To km | Section leader | Marshals |
|---|
How this service appears to marshals: on their screen, the YES/NO page, and at the end of texts. Leave blank for RaceControl.
Save this race's marshal list to the organiser's account. Next year, load it back in one click.