Communicating Event Updates to Registered Runners
Runners who feel informed generate far fewer support messages than runners left to guess, whether the news is routine or a last-minute change. Setting up a simple communication cadence early avoids most of the scramble that happens when there's suddenly something urgent to say.
A basic communication cadence
| Timing | What to send |
|---|---|
| At registration | Confirmation with category, amount paid, and a link to the event page |
| 2 to 3 weeks out | Logistics reminder: bib collection details, venue, transport, weather-appropriate guidance |
| Week of the event | Final details: exact start time, any road closures affecting access, what to bring, support contact |
| Day before or morning of | Only if something has changed, don't send a routine message just to fill the slot |
What's worth communicating
Focus on what a runner needs to act on: schedule changes, route changes, weather contingency plans, category cutoffs, and bib collection logistics. Filling the inbox with generic hype emails between these makes it easier for the one message that actually matters to get lost or ignored.
It also helps to separate excitement-building content, countdown posts, sponsor shoutouts, training tips, from operational content that a runner genuinely needs to act on. Both have a place, but they shouldn't compete for the same inbox slot in the final week, when operational clarity matters more than momentum. If you're building out a fuller content calendar around your event, keeping that distinction in mind from the start avoids diluting the messages that actually need attention.
Not every update needs to go to everyone
A change affecting only one category, for instance a cutoff time adjustment for the full marathon, doesn't need to go to 10K entrants who aren't affected by it. Segmenting communication by category or wave, where your registration system allows it, keeps messages relevant and reduces the chance that runners start skimming past your emails because too many of them don't apply to them.
This matters more as an event grows. A small race can get away with one message to everyone; a large event with multiple distances, waves, and start times benefits from treating each group as its own audience with its own relevant details, even if the underlying template stays largely the same.
Choosing which channel to rely on
Email remains the default for most events because it's easy to keep a record of and doesn't require a runner to opt into anything beyond registering. Adding SMS or WhatsApp for genuinely urgent, same-day updates is worth considering for larger events, but only if you can commit to keeping the number or list current, since an unreliable secondary channel is worse than not offering one at all.
Whatever channels you choose, state them clearly during registration, something as simple as noting that important updates come by email and that runners should check their spam folder closer to the event, since first-time senders sometimes land there. That single line prevents a surprising share of 'I never got the email' complaints after the fact.
Handling last-minute changes
- Send changes through the channel runners already expect. Don't introduce a new channel the week of the event.
- Lead with the change itself in the first line, not buried under a friendly preamble.
- State what stays the same alongside what's changing. Runners often assume the worst about anything left unmentioned.
- Update the event page itself, not just the email, since not everyone reads every message before race morning.
- If you don't yet have a dedicated support inbox, even routing changes through your contact page consistently is better than switching channels mid-event.
Setting this up early
This is easiest to get right when it's decided before registration opens, not improvised once questions start arriving. See race registration checklist for what else should be locked down at that stage. If you're unsure how much detail your event page currently gives runners, how to increase marathon registrations covers what a clear, well-structured page does for conversion and trust alike.
Don't stop at the start line
A short post-event message, results, photos if available, a thank-you, and a note on what's next, closes the loop and keeps runners engaged for your next edition. It doesn't need to be elaborate, but skipping it entirely wastes the goodwill built over an otherwise well-run communication cadence. Runners who feel like the relationship ended cleanly are more likely to register again without needing to be re-convinced from scratch.
List your event and manage registrations, updates and runner communication in one dashboard.
List your eventWorking with organizers on the platform, the pattern that stands out is how much a single, clearly timed pre-race email cuts down on support questions compared to events that go quiet after registration and reappear only with a last-minute change. My honest read is that runners forgive a change far more easily than they forgive silence followed by a surprise.
Frequently asked questions
How often should I email registered runners before the event?
A handful of purposeful messages, at registration, roughly two to three weeks out, and race week, covers most events well. More frequent than that risks runners tuning out the one message that actually matters.
Should I always send an email if there's a route or schedule change?
Yes, and update the event page at the same time. Treat any change that affects what a runner needs to do differently as urgent enough to send immediately, not batched into the next scheduled update.
What if I don't have anything new to say close to race day?
It's fine to skip a message rather than send something just to check a box. A final logistics reminder the week of the event still has real value even without new information.
Is SMS or WhatsApp better than email for urgent updates?
For genuinely urgent, same-day changes, a channel runners are likely to see quickly matters more than which one it is. Use whichever channel you've told runners to expect, and be consistent about it.