Post-Race Analysis: Using Strava and TrainingPeaks to Find Improvement Points

Introduction

Post-race data analysis is the most overlooked yet most valuable step for amateur athletes. Many riders treat the finish line as the end of the race, but for those with a drive to improve, the race is just the beginning: every race leaves behind a detailed record of physiological and mechanical data, waiting to be interpreted and applied.

Modern sports technology gives amateur athletes access to the same quality of data as professionals. Platforms like Strava, TrainingPeaks, and Garmin Connect offer a wealth of analytical tools. The problem isn’t a lack of data—it’s how to extract meaningful insights from the sheer volume of numbers.

The Three-Tier Framework for Post-Race Analysis

Tier 1: Immediate Subjective Notes (1–2 hours post-race)

Before looking at the numbers, record your subjective feelings. While the memory is still fresh, note:

• Which section felt the easiest/most painful?
• Was nutrition sufficient? Any gastrointestinal discomfort?
• Was your position in the pack ideal? Were there moments where energy was wasted?
• Compared to your expected result, what caused you to exceed or fall short?

Cross-referencing these subjective notes with objective data often reveals the most critical issues.

Tier 2: Interpreting Strava Data

Strava’s Segment feature is especially useful for climbing races. By breaking the race course into multiple Strava segments and analyzing speed and heart rate for each, you can pinpoint exactly where you expended too much energy or where you held back too much.

Tier 3: In-Depth Analysis with TrainingPeaks

TrainingPeaks offers more advanced analytical tools, particularly the Power-Duration Curve and Training Status (TSB) tracking:

• Power Curve: Compare post-race against your personal best power curve to see whether peak power across various durations was at its optimal level
• Training Status (TSB/Form): Was your TSB on race day within the optimal range (typically +5 to +20)? Too high may indicate insufficient tapering; too low may indicate overtraining before the race
• Race Analysis: A TrainingPeaks Premium feature that generates detailed race segment reports

Specific Analysis Case Studies

Case 1: Collapse in the Second Half of a Climbing Race

Symptoms: Heart rate dropped in the second half of the race, but speed also dropped; finish time was 15% slower than expected.

Data interpretation steps:

1. Review the Power vs. Time chart to confirm the magnitude of power decline in the second half
2. Compare the Power/Heart Rate ratio (Efficiency Factor) between the first and second halves; a significant drop in EF in the second half indicates fatigue onset
3. Cross-check nutrition logs to confirm whether there were overly long gaps between feedings before fatigue set in

Improvement direction: If insufficient nutrition is confirmed, adjust feeding frequency for the next race; if the initial pace was too high, set a power ceiling alert.

Case 2: Analyzing the Moment of Getting Dropped from the Pack

Symptoms: Fell off the pack at a specific section, then rode solo for the remainder.

Data interpretation: Locate the exact drop-off point and examine:

• Was the 5-minute power before getting dropped far above target? (Indicating the pack attacked on that section)
• Was there insufficient nutrition before getting dropped? (High heart rate but low power)
• Compare speed with riders in the same group on Strava to determine whether the pack accelerated as a whole or whether it was a personal capability issue

Practical Recommendations

1. Create a post-race record template: Design a standardized post-race log and fill it out after every race. Accumulating this data enables longitudinal comparisons
2. Link to training goals: Each issue identified through analysis should correspond to a specific training prescription; only then does the analysis become meaningful
3. Free tools are sufficient: Strava’s basic version, Garmin Connect, and Intervals.icu (free and powerful) are enough for most analytical needs—no need to rush into paid software
4. Compare across seasons: Comparing data from the same race each year against the previous year is the most objective way to measure annual progress
5. Identify your recurring weakness pattern: Athletes typically have recurring weaknesses (e.g., insufficient nutrition in the second half, poor positioning before climbs). Finding this pattern and focusing on improving it yields significant results

Conclusion

Post-race analysis turns every race from a result into a learning opportunity. Behind every data point lies a story waiting for you to discover and interpret. Through systematic post-race analysis, you’re not just improving your next race result—you’re deepening your understanding of your own body, and that awareness is an invaluable asset that no training plan can directly teach you.

Related Reading

• Post-Race Analysis and Goal Setting: Turning Every Race into a Stepping Stone for Progress
• Methods for Post-Race Analysis in Cycling: How to Find Improvement Points from Race Data
• How to Properly Read Strava Data: Making Data Your Tool for Improvement
• Post-Race Analysis for Swimmers: Finding Next Training Directions from Race Data