RaceOSRace operations
Event broadcasts, reminders and two-way support stay inside the event conversation history.
One race. One communication record.
From first message to official result.
RaceOS connects organizer broadcasts, runner replies, timing-mat updates, change requests and supporter cheers without mixing one event’s conversations into another.
RACE COMMUNICATION CONTROLEVENT SCOPED
START10K30KFINISH
MAT UPDATEACCEPTED CROSSINGrunner + followers
FINISHPROVISIONALreview remains open
DECLAREDRESULT + PDFofficial release
Per-event CRMConversations, requests and delivery status remain attached to one race.
Crossing-triggeredUpdates follow an accepted timing-point crossing, not every repeated transponder observation.
Final means officialThe certificate is released after declaration—not merely when a bib touches the finish mat.
Runner message lifecycle
Useful at every stage. Honest at the finish.
The immediate experience stays fast, while the official record stays protected. RaceOS distinguishes an accepted crossing, a provisional finish and a reviewed official result.
Every accepted timing point
The runner—and up to three subscribed loved ones—can receive a crossing update. Repeat observations are consolidated.
Finish is provisional
RaceOS says the runner has finished, while making clear that timing review may still change the result.
Official result
After an official declares the result, RaceOS sends the consolidated timing and can deliver the certificate PDF on WhatsApp.
Organizer workspace
Broadcast, reply and resolve—without losing the race context.
Support teams see event conversations, provider delivery status and runner category-change or upgrade progress in the same communications workspace. Replies retain their channel history; structured requests retain payment or refund state.
A runner conversation, not a ticket number
Support teams see the complete event conversation, registration context and previous updates while they reply.
One workspace for the race team
Runner support, field-team coordination, broadcasts, delivery status and event communication rules sit together without mixing their audiences.
Messages that follow the race
Registration confirmations, reminders, checkpoint updates, provisional finishes, official results and certificates form one continuous journey.
Every delivery is accountable
Sent, delivered and failed messages remain visible so teams can follow up instead of assuming a runner was reached.
Loved ones, connected
A cheer tied to a real place.
From a runner’s public live page, a loved one can follow crossing updates or submit a cheer. They may choose a real timing point so an approved message can appear when that runner reaches it.
- Up to three followers per bib
- Checkpoint cheers are moderated before display
- Messages stay attached to the correct runner and event
- Official result communication follows race declaration
Every audience connected
Runner support and race operations, without losing context.
Organizers communicate with runners, marshals coordinate through their field workspace, and loved ones follow the race through focused experiences built around the same event.