The timing call comes in at six to eight weeks to race day. The course is already certified, the schedule is locked, the permit is filed. Now someone needs timing solved and a results page live by race morning.
At that point, the conversation becomes transactional. How many checkpoints? What's the price? When can you be on site?
That conversation skips nearly everything that matters.
Booked and built aren't two timing strategies. They're two mindsets. One treats timing as a backend function. The other treats it as the foundation of the entire race-day experience, for runners, spectators, and everyone watching from outside it. One produces a results page. The other produces a race that grows.
Timing Is a Course Design Decision
Mapping checkpoint locations shapes everything downstream: what a race director can see while the event is moving, how accessibly spectators can follow participants, and how confidently road reopening calls can be made.
Those decisions require the course. They also require buffer time to think through and operationalize.
A timing partner brought in at week eight is working with what's available. A timing partner brought in at month four is helping design something. The distinction shows up on race day in ways that are hard to backfill.
The Decisions That Can't Wait
Checkpoint placement is the first conversation worth having early. Especially the density strategy: how frequently the race needs reads, where the critical windows are, how terrain affects deployment across the full course. These are conversations that benefit from multiple passes.
Spectator communication is the second. The tracking experience that participants and fans have depends on what is configured before registration closes. Live tracking pages, text alert checkpoints, and shout-out features don't improve under deadline pressure. They get set up quickly and launched as-is.
Safety data feeds are the third. Sweep vehicles establish where the back of the pack ends. They don't show how runners are distributed across the final miles, or which of them stopped moving ten minutes ago. Back-of-pack thresholds, not-moving alerts, and the information being handed to city partners and police liaisons all need to be agreed on with enough runway to brief the people who will be relying on them. Race morning is not the moment to explain a new system to a city operations chief.
How Late Decisions Spread
When timing planning gets rushed, the fallout rarely stays contained to timing.
A checkpoint placement finalized at week four may conflict with a sponsor activation confirmed at week six. A road reopening protocol built around live course data is now being used by a city team that had two days to learn it. The spectator tracking page went live without being stress-tested under real traffic.
None of these are race-ending on their own. Together, they create an event that's harder to manage than it needed to be, with a post-race debrief that runs longer than expected and a list of fixes that could have been caught in March.
What Early Planning Looks Like in Practice
Races that run well at scale treat timing as part of event architecture, not a line item to address after everything else is settled. The timing conversation begins while the course is being finalized. The spectator experience gets built into the marketing calendar. City partners are briefed on what data they'll have access to before they're depending on it.
That kind of preparation doesn't require more budget or a larger team. It requires earlier decisions. Some race directors treat timing and the spectator experience the way they treat road closures, permitting, and volunteer coordination. They end up with a race that grows year over year. App downloads, live tracking users, shout-outs sent, return registrations. Those numbers are the product of decisions made months before race day, not the morning of.
Every Woman's Marathon began planning its race-day experience with Laurel months before the gun went off. By race morning, the tracking platform was configured, spectator features were live, and fans knew how to find their runners. This led to five people for every runner using the live tracking page and sending over 34,000 shout-outs. San Antonio Marathon did the same and reached nearly 60,000 users between their app and live tracking. That kind of reach doesn't come together in the final weeks. It comes from treating the spectator experience as part of the event, not an afterthought to the timing contract.
Booking gets timing solved. Building gets a race that grows year over year. The difference is what gets created along the way: a tracking experience spectators actually use, shout-outs that turn into return visits, data that makes next year's planning faster instead of starting over. None of that comes from the vendor relationship. It comes from treating timing as part of the race's architecture from the start, which is the partnership Laurel is built for.
Three Questions Worth Asking Your Timing Partner Early
- How does your checkpoint deployment strategy adapt to our specific course terrain?
- What does the race director dashboard show in real time, and who on our team needs to be trained on it before race day?
- What information will city partners and police liaisons see, and how far out do they need to be briefed?
0