Browse helpHelp centre

How Race Relay and the platform share data

What the workspace sends to the phones and what the phones send back, the one active event per club, and the event group that opens and closes with the event.

OrganiserTimerTechnical DelegateCoachVolunteerSpectatorUpdated 27 October 2026
On this page
  1. What it's for
  2. The chain
  3. What never travels
  4. What success looks like
  5. If something goes wrong
  6. Related

What it's for

Race Relay is not a second system. The event, its races, the lists, the run sheet, the documents and the live timing exist once, in the workspace; the phone shows them for the race it has picked, and a few things the phone does — a coach's claim, a payment tick, a note, the TD's header details — are written straight back. This page is the traffic in both directions.

The chain

  1. One active event per club — Race day › Activate an event (or ⚙︎ › Active event on an admin's phone) makes this event the one the app is live for; the event's group is created, and chats, documents and notes belong to it from then on. → Activate an event · Organiser tools
  2. The event group — one Race Relay group per event, named after it, with the club's standing ROC / Jury, Coaches and Volunteers groups beside it; people join by link or QR, invited timers are its admins, and when the event is archived the group closes and everyone stays on the club's list. → Event access & chat · Clubs and event groups · Race Relay groups & members
  3. Platform → phone: the programme — the run sheet's 📤 Push to comms (ROC / Jury) posts the day; the Program tab shows officials, start times, inspection and forerunner times, and a club admin can ✎ Adjust the day or 🗓 Re-plan the day and Publish to everyone. → Run sheet · Program
  4. Platform → phone: the published list — Publish list to coaches (desk or phone) opens the day's list on Your athletes; 📣 Notify coaches pings the Coaches chat. → Notify coaches and lock the list · Publish to coaches
  5. Phone → platform: claims and answers — + Claim, Racing / Not racing write the green tick on Manage Competitors; + Add a missing athlete lands on the desk with a CHECK. → Claim athletes
  6. Platform → phone: released documents — a released start list, result or DQ list posts into the event's group as a card and onto Docs; a protest lodged on the phone pins the document until an admin resolves it. → Release results · Docs and protests
  7. Platform → phone: live — the Phone live tile on the Timing Desk feeds the Live tab for the race on the race bar, and the live draw wall while the draw runs. → Phone live · Live
  8. Phone → platform: payments — the pay sheet's tick is the same PAID column the organiser sees on Manage Competitors; a coach's card payment on the phone lands on the ledger. → Pay sheet · Coach accounts and the pay sheet
  9. Phone → platform: header details — a club admin or the event's TD fills 📋 Header details on the Program tab; it writes the same Header Info the start lists and results print from. → Header details on the phone · Header info
  10. Phone → chat: notes and the record — a note on a competitor from the Live tab is private until posted to a group; Record & summary pulls the jury trail and the minutes PDF. → Notes · Record
  11. Notifications — messages, documents and start-time changes ping the phone; the level is per group, and a club can be muted. → Notifications
  12. The event is archived — the group closes, its links stop, everyone leaves and stays on the club's list; the next event's chat shows a band to join. → Archive an event

What never travels

  • Timing data is never typed into the phone; a wrong time is fixed on the desk and the phone follows.
  • Documents never reach Public · Spectators; a DQ list goes to the ROC/Jury and Coaches groups only.
  • Another club's chats, lists and documents are never shown.

What success looks like

The club card on Chats names the active event, the race bar reads LIVE while the desk streams, the Program matches the run sheet, a coach's Racing shows as a green tick on the desk within seconds, and the released results are on Docs and as a card in the group.

If something goes wrong

  • The app shows the previous event: it is still the active one; activate the new one.
  • A coach's answer is not on the desk: the day is not published, or the tap did not save (Check your signal).
  • A document is missing from Docs: it was withdrawn, or the phone's race bar is on another race — tap All races.
  • The Program shows old times: the admin did not press Publish to everyone.
Was this helpful?
How Race Relay and the platform share data · Race Bureau Help