July 2026
The medal goes in a drawer. The finish line photo gets posted and buried within 48 hours. What felt visceral on Sunday morning becomes a blur by Wednesday.
Race memories fade fast unless something holds onto them. Most races do: a finisher photo, a results email, sometimes a recap video for the field as a whole. Rarely is any of it built around the one race a runner actually remembers: their own.
The Story Ends Too Soon
Race directors pour months into building an experience. Then the last finisher crosses, the timing mats come up, and the story stops.
What runners get afterward is a results page: a finish time, maybe a split at mile 13 and another at mile 20. For a runner who spent five months training, who hit the wall at mile 22 and fought through it, who ran their best second half in three years, a spreadsheet row doesn't capture what happened.
Runners know something significant happened out there. Most races hand them a number and move on.
What Runners Are Actually Looking For
Ask a runner what they do in the days after a race and a pattern emerges. They pull up their splits, compare the back half to last year, and spend the next conversation trying to explain what mile 22 actually felt like to someone who wasn't there.
They're not looking for raw data. What they want is their race told back to them in a way that makes sense. A pace chart shows numbers. A narrative shows a runner who held steady through the hardest miles, negative split the back half, and crossed twelve minutes ahead of last year's time. That's something worth sharing.
The most specific memories are usually the smallest ones: the voice message from a friend right before the hill at mile 13, the sign from a runner's kids cheering at mile 20. Runners don't forget who showed up for them mid-race. They don't always have an easy way to sit with it again once they've caught their breath.
Where AI Recaps Fit
The challenge has always been scale. A race with 10,000 finishers can't produce 10,000 individual race stories by hand, and no one expects a race director to try. What's changed is the level of detail available to build from when using Laurel: checkpoint splits, pace history, field position at every point on the course, a full performance arc from start to finish. That density of data, captured automatically for every finisher, is new. Turning it into something a runner actually wants to read is the harder problem, and it's the one Laurel built its recaps to solve.
Laurel's AI-driven post-race recaps do exactly that. Each recap pulls from a runner's full data set and builds a narrative around their specific race: where they gained ground, where they slowed, how their effort unfolded mile by mile. Every finisher gets one on their results page, and the last-place runner gets the same treatment as the winner. Today, that means a personalized recap once the race is over. There’s no telling what other options could be available down the line.
Runners can also revisit every shout-out they received mid-race: messages typed by supporters and read aloud in the app, and the ones recorded in an actual voice. In 2025, runners received over 155,000 shout-outs across Laurel-timed races, and just under 16,000 of them were audio: a supporter's actual voice, not just text read aloud.
Why Race Directors Should Care
For race directors, giving runners a story instead of a spreadsheet row changes what happens after Sunday. A runner who gets a real account of their race, not just a number, keeps talking about it: to their training group, to a friend who ran their first half marathon and is still deciding whether a marathon is next. That's what drives return registrations and referrals. It starts with what a runner has to remember the race by.
The finish line is a beginning for most runners. Giving them something worth reading and worth sharing is how a race stays in the conversation long after the course closes.
The race ends at the finish line. The story doesn't have to.
0