The Find Your Finish blog
Practical guides for choosing a race, training for your next distance, and planning race day, plus resources for organizers setting up their own event.
A weather contingency plan is only useful if it's written down before race week, with specific thresholds and specific people responsible for each decision.
Most volunteer problems on race day trace back to recruitment or briefing gaps from weeks earlier, not anything that happens on the morning itself.
A virtual race removes almost every logistics problem an in-person event has, and trades it for a much harder problem: keeping runners engaged without a shared start line.
A transfer moves a bib to someone else. A deferral moves it to a future edition. Here's how to decide your policy for both.
The right timing method for your race depends almost entirely on field size and how much runners will care about their individual result.
Permits are consistently the longest lead-time item in organising a road race, and the process varies enough by city that general guidance only takes you so far.
Course marshals carry more responsibility than most volunteer roles, since they're often the only person between a runner and a wrong turn or a live traffic lane.
Insurance is one of those items that seems skippable right up until the moment something goes wrong, and by then it's too late to arrange.
Race morning runs smoothly when every task has an explicit time attached to it, not a general sense of when things should probably happen.
The week after a race is when the most useful information about it exists, and it's also when organizers are most likely to skip writing any of it down.
Medical planning for a road race comes down to three decisions: where your medical points go, who staffs them, and how fast a runner in trouble reaches a hospital.
Group registrations are worth setting up deliberately, since a single corporate booking can be worth dozens of individual sign-ups if the process doesn't create friction.
Category pricing works best as a deliberate calculation, not a number picked to match whatever a similar race down the road is charging.
Getting the structure of a corporate running challenge right matters more than the size of the discount you offer.
Runners who feel informed generate far fewer support messages than runners left to guess. A simple communication cadence heads off most of that.
Picking a race date is a constraint-satisfaction problem before it's a marketing decision, and it's worth working through the constraints in a deliberate order.
A visitor deciding whether to register for your race is scanning for specific information, not reading a pitch, and most event pages fail on clarity, not design.
Most registration problems trace back to something left unfinished at launch, not something that goes wrong later. Here's what to lock down first.
Sponsors don't fund events out of goodwill. They fund audiences, and the clearer you are about yours, the easier the conversation gets.
Bib management looks simple until race week, when a poorly planned system turns into one of the most visible sources of runner frustration.
Most registration shortfalls trace back to a handful of fixable issues on the event page itself, not a lack of runner interest in your race.
Organising a road race is mostly a logistics and sequencing problem. Here's the order things actually need to happen in, from permissions to bib collection.