After you complete a race that your training plan was targeting, Race Debrief gives you an AI-powered deep dive into how the race went and how your training block prepared you for it. It analyses your race execution, pacing strategy, training compliance, and delivers specific recommendations for next time.
The Race Debrief panel appears on your training plan page once all of these conditions are met:
The race date on your goal has passed.
A race activity from Strava (or manually marked as a race) exists on or near your target race date, at a similar distance.
Race Debrief is for race goals only (not Couch to 5K or distance targets).
When your debrief is available, you will see a "Race Debrief" panel at the bottom of your training plan page with details about your matched race and a "Request Debrief" button.
Clicking "Request Debrief" expands a short form with three prompts. Your answers give the AI crucial subjective context that the numbers alone cannot capture.
Energy levels, leg feel, mental state, when it got hard.
Cramping, pacing errors, stomach issues, course surprises.
Nutrition, sleep, how the taper felt, weather conditions.
After you submit, the AI begins analysing your entire training block and race data. This is a deep analysis that typically takes 30 to 60 seconds. The page updates automatically when it is ready, and you will also receive a notification.
The debrief is structured into five sections, giving you a complete picture of both the race and the training that led to it.
A holistic overview that ties together your training journey and race outcome. This is the section to read first for the big picture.
Did you hit your target? A specific comparison of your goal time/pace versus your actual result, with analysis of why the goal was or was not achieved.
Detailed analysis of how you raced: your pacing strategy (negative, positive, or even splits), heart rate management, and key moments during the race. The AI references your specific per-km split data.
A review of your entire training plan: how volume progressed through phases, which sessions had the most impact, what worked, and what could improve. The AI looks at your weekly compliance scores and volume data across the full training block.
3 to 5 specific, actionable recommendations for your next training block and race. These are grounded in the data from this specific race, not generic running advice.
The debrief draws on a wide range of data to produce a thorough analysis. The more data available, the richer the debrief.
|
Data source
|
What it includes
|
|---|---|
| Race activity | Per-km splits, heart rate zones, terrain, cadence, running power (if FIT data available) |
| Race result | Finish time, pace, distance |
| Race goal | Target time, target pace, course profile (if GPX uploaded) |
| Full training plan | Per-week summaries: planned vs actual volume, session counts, compliance scores, phases |
| Session feedback | Compliance scores from AI session feedback across the training block |
| Plan feedback | Your plan retrospective (rating, what worked, what could improve) if submitted |
| Your input | Race experience, issues, and pre-race notes you provide in the debrief form |
| Race history | Historical performance data at this distance (if 3+ races available) |
| Athlete profile | Experience level, threshold pace, fitness trend, training load |
The AI can only work with the data it has. Here are ways to make sure your debrief is as useful as possible.
Request session feedback on your key training runs. The compliance scores feed directly into the debrief's training block analysis.
Submit plan feedback before requesting the debrief. Your "what worked" and "what could improve" responses give the AI additional context about the plan.
Upload a FIT file for your race activity if you have one. Running dynamics data (power, ground contact time, stride length) adds another layer to the race execution analysis.
Be specific in the form. "My legs felt dead after kilometre 18 and I had to walk through the last aid station" is far more useful than "it was hard." The AI will look for corroborating data in your splits.
Upload a course GPX to your race goal if available. The AI can then analyse how the course elevation affected your pacing.