Race File Analysis Guide: A Complete Post-Race Data Review Process

Why Analyze Race Files?

A race is the final exam for all your training. Regardless of the outcome, race files contain valuable information—they tell you which parts of your training worked, which fell short, and how you can improve for the next race.

Performance analysts on professional teams spend hours analyzing data after every race. As an amateur rider, you don’t need to go that deep, but a systematic analysis process will turn every race into a learning opportunity.

Preparation Before Analysis

Data Collection

Before diving into the numbers, record these subjective notes (ideally within 24 hours after the race):

1. Pre-race status: Sleep quality, nutrition, warm-up feel
2. In-race sensations: When did you feel good/bad?
3. Key moments: Which attacks hurt you? Where did you get dropped or catch back on?
4. Nutrition and fueling: What did you eat, how much did you drink, and at what times?
5. Tactical decisions: What were the decision points? In hindsight, were they right or wrong?

Combining these subjective notes with objective data gives you the complete picture.

Layer 1: Overview Metrics

Open your race file and look at these numbers first:

Basic Metrics Checklist

Metric	Meaning	Questions to Ask Yourself
Total Time	Full race duration	How does it compare to your goal?
NP (Normalized Power)	Normalized power	Is this your best NP for this duration?
AP (Average Power)	Average power	—
IF (Intensity Factor)	Intensity factor	Is it within a sustainable range?
VI (Variability Index)	Variability index	Is your pacing stable?
TSS	Training Stress Score	How does the stress compare to training?
Average Heart Rate	—	Compare to training at the same NP
Max Heart Rate	—	Did you reach your maximum?
Average Cadence	—	Is it in the optimal range?

Race IF Reasonableness Check

Race Duration	Reasonable IF Range	Notes
30 minutes	1.00-1.10	Time trial
1 hour	0.95-1.05	Short road race
2 hours	0.85-0.95	Medium-distance road race
3 hours	0.80-0.90	Long-distance road race
4+ hours	0.70-0.85	Long-distance endurance race

If your IF is above the reasonable range, it suggests you may have paced too aggressively (which could result in a late-race collapse). If it’s below the range, it suggests you may have been too conservative or your fitness didn’t support higher intensity.

Layer 2: Power Distribution Analysis

Time in Power Zones

Categorize your race power data by zones and calculate the time and percentage spent in each:

Example: 2-hour circuit race

Z1 (< 55% FTP):      18 min (15%)  ← Corners, drafting, descents
Z2 (56-75% FTP):     36 min (30%)  ← Group cruising
Z3 (76-90% FTP):     30 min (25%)  ← Surges, riding at the front
Z4 (91-105% FTP):    18 min (15%)  ← Climbs, chasing
Z5 (106-120% FTP):    8 min (7%)   ← Attacks, short climbs
Z6 (121-150% FTP):    6 min (5%)   ← Sprint acceleration
Z7 (> 150% FTP):      4 min (3%)   ← Sprints, attack launches

Analysis Points

1. Z1 time percentage: In road races, your Z1 percentage reflects your position in the group. A higher percentage means more time “hitching a ride” at the back of the bunch
2. Z4-Z5 time: This is where you’re truly “doing the work” in a race. If you spend more time in Z4-Z5 than your rivals, your pacing may not be efficient enough
3. Z6-Z7 time: These are the decisive “race moments”—attacks, reactions, sprints

Layer 3: Time Series Analysis

Power Curve Trends

Plot your power data on a timeline and look for these patterns:

Pattern 1: Positive Split

First half NP: 260W
Second half NP: 230W
Decline: -11.5%

Usually means pacing was too aggressive, burning too much anaerobic reserve in the first half.

Pattern 2: Negative Split

First half NP: 235W
Second half NP: 255W
Increase: +8.5%

The ideal pacing strategy—conservative in the first half, with reserve left to push in the second.

Pattern 3: High Volatility

Power swings dramatically between zones, VI > 1.15.

Possible causes: race rhythm dictated by opponents, varied terrain, tactical riding.

Key Moment Zoom Analysis

Find the decisive moments in the race and zoom in to analyze them on a 1-5 minute scale:

Case study: Getting dropped on lap 5

Attack start time: 1:23:45
Attack duration: 2 min 30 sec
Attack average power: 380W (127% FTP)
Your response power: 340W (113% FTP)
Your NP in the 5 minutes before the attack: 285W (95% FTP)

Analysis: You were already near threshold before the attack, and your anaerobic reserve wasn’t sufficient to follow a 127% FTP attack. Possible solutions: (a) improve anaerobic capacity (b) conserve more energy earlier in the race © anticipate the attack position earlier.

Layer 4: Heart Rate and Power Relationship

Heart Rate Drift Analysis

Heart rate changes at the same power during the race:

Lap 1 @ 250W: Average HR 155 bpm
Lap 5 @ 250W: Average HR 163 bpm
Lap 10 @ 250W: Average HR 170 bpm

Heart rate drift: +9.7%

A heart rate drift above 5% usually indicates:

• Dehydration
• Elevated core body temperature
• Muscle glycogen depletion
• Cumulative fatigue

This information is particularly useful for improving your nutrition and fueling strategy.

Power-Heart Rate Coupling Efficiency

Efficiency Factor (EF) = NP / Average Heart Rate

Comparing EF between races under similar conditions reveals changes in aerobic efficiency. An increase in EF means you can produce more power at the same heart rate—direct evidence of aerobic fitness improvement.

Layer 5: Comparison with the Power Duration Curve

Compare your maximum power across different time segments during the race against your PDC:

Race 5s max: 980W (PDC best: 1050W → 93%)
Race 1min max: 420W (PDC best: 445W → 94%)
Race 5min max: 330W (PDC best: 345W → 96%)
Race 20min max: 285W (PDC best: 300W → 95%)

Interpretation:

• Close to 100% → You were near your limit during the race
• 85-95% → Normal race performance (affected by tactics, fatigue)
• < 85% → You may not have performed to your potential, or tactics didn’t require it

If you set a new PDC record (> 100%) in any time segment, congratulations—the race brought out your best performance.

Building Your Race Analysis Template

Quick Analysis (15 minutes)

Suitable for general training races and practice events:

1. Record subjective feelings
2. Check NP, IF, VI
3. Compare NP between first and second half
4. Analyze one key moment

Full Analysis (45-60 minutes)

Suitable for target events and important races:

1. Complete subjective record
2. All overview metrics
3. Power zone distribution
4. Time series analysis (including 3-5 key moments)
5. Heart rate drift and EF analysis
6. PDC comparison
7. Comparison with the same type of race last time
8. Improvement checklist for the next race

From Analysis to Action

The value of analysis lies in generating actionable improvements. After each analysis, list at least three things:

1. One thing done right: What strategy or ability worked well during the race?
2. One thing to improve: What limited your performance? What is the corresponding training prescription?
3. One thing to try next time: What new strategy is worth trying in the next race?

Conclusion

Race file analysis doesn’t require complex tools or advanced mathematics. What it requires is a systematic process and the ability to ask the right questions. Once you develop the habit of post-race analysis, you’ll find that every race—win or lose—is preparing you for the next one. Data doesn’t lie, and those who learn to listen to data are always on the path of improvement.

Related Reading

• Post-Race Analysis and Goal Setting: Turning Every Race into a Stepping Stone for Progress
• Post-Race Analysis for Swimmers: Finding the Next Training Direction from Race Data
• Power Data Post-Race Analysis Guide: How to Find Room for Improvement in Race Files
• Cycling Post-Race Analysis: Using Strava and TrainingPeaks to Identify Improvement Points