How to Read a Power File After a Hard Ride

Your ride is done. Your legs are cooked. Before you close the app and forget about it, spend ten minutes with the power file. That ten minutes is where the training value compounds.

This chapter walks through a repeatable process for post-ride power file review — what to look at, in what order, and what questions to ask at each step.

Start With the Summary Numbers

Open the ride and look at the headline figures first. These give you a quick orientation before you zoom into any details.

Average power tells you the mean across the entire ride, including coasting and soft-pedaling. On its own it undersells the physiological cost of anything with surges, climbs, or attacks.

Normalized power (NP) corrects for that. It weights harder efforts more heavily to give a better estimate of the metabolic cost. A large gap between average power and NP means the ride was physiologically expensive relative to its raw average — think criteriums, punchy road races, or interval sessions with full recoveries. See the glossary entry on NP for the calculation.

Variability Index (VI) is simply NP divided by average power. A VI close to 1.00 means a steady, controlled effort — a long tempo block or a time trial. A VI above 1.10 signals a highly variable ride. Neither is inherently good or bad; it depends on the goal of the session.

Intensity Factor (IF) compares NP to your FTP. An IF above 1.00 means the normalized effort exceeded threshold — possible in short, very hard races or test efforts. IF is a quick gut-check on how hard the ride actually was relative to your current fitness.

Training Stress Score (TSS) combines duration and IF into a single fatigue estimate. It tells you roughly how much recovery this ride demands. TSS is explained in detail here.

Check the Power Curve

The power-duration curve (sometimes called the mean maximal power curve) plots your best average power for every duration across the ride — from a few seconds out to the full ride length.

Look for:

New peaks — did you set a best-ever number at any duration? Most platforms flag these automatically. Note which durations and under what conditions.
Shape of the curve — a strong short end (under two minutes) with a weak long end suggests a rider skewed toward anaerobic capacity. The reverse points toward aerobic endurance. Neither is a problem; it tells you where you are.
Where the curve drops off sharply — a sudden dip at a specific duration can reveal a limiter. If your curve holds well to five minutes then collapses, your VO2max ceiling may be constraining longer efforts.

Compare this ride's curve against your rolling baseline. Most platforms let you overlay the current ride against a 90-day or season-best curve. If you underperformed at a duration you targeted, that's a useful signal.

Audit Your Pacing

This is where you learn whether your execution matched the plan.

Zoom into the power trace and look at the shape:

Even distribution — power stays roughly in a band for the target effort. Good for time trials, tempo blocks, and threshold intervals.
Positive split — power starts high and fades. Common in races and hard group rides. Expensive metabolically. If this was unintentional, it signals you went out too hard.
Negative split — power builds through the effort. Efficient and controlled. Harder to achieve, particularly in races.
Spiky profile — power swings widely throughout. Expected in criteriums or technical courses. Check VI to quantify it.

For interval sessions specifically, pull up each rep individually. Compare the power you hit on rep one versus rep four or five. If rep five was significantly lower, you either started too hard, carried too much fatigue into the session, or your FTP estimate needs revisiting with the FTP estimator.

Count Your Matches

"Burning a match" refers to a hard anaerobic effort that depletes your finite high-end energy reserves. After a race or hard group ride, count how many efforts exceeded a threshold you care about — often set above VO2max power — and for how long.

Some platforms call this "matches burned" or show it as time in zone six or seven. Others let you set a custom wattage ceiling and count crossings.

Ask:

How many matches did you burn, and when in the ride did they happen?
Did you have matches available at the end, or were you empty when it mattered?
Were the efforts forced (responding to attacks, covering gaps) or tactical (your own initiative)?

This informs both race tactics and training priorities. If you consistently run out of matches in the final third of a race, you either need to conserve better earlier or build more anaerobic capacity.

Look at Heart Rate Alongside Power

Power tells you what you did. Heart rate tells you the cost.

Cardiac decoupling — the relationship between power and heart rate drifting apart over time — is a key endurance metric. If you held steady power but your heart rate climbed continuously, aerobic drift occurred. This is normal on long rides in heat or when you're fatigued, but high decoupling on what should have been an easy day is a warning sign.

Power-to-HR ratio at the end of a long effort compared to the start gives you a rough read on aerobic efficiency. Holding the same ratio across several hours indicates solid aerobic fitness and adequate fueling.

If heart rate was abnormally high for the power output throughout — not just at the end — consider: poor sleep, heat, illness, or being in a deeper fatigue hole than you realized.

Flag Segments That Need Attention

Before you close the file, mark anything worth returning to:

A climb where you faded unexpectedly
An interval where the power dropped mid-effort
A sprint that underdelivered relative to your expectation
A sustained section where you felt worse than the numbers suggest

Most platforms allow notes or segments. Use them. When you review training blocks every few weeks, flagged efforts are far more useful than raw data you have to reconstruct from memory.

Build a Short Post-Ride Habit

The review doesn't need to be exhaustive every time. A structured five-to-ten minute process is more useful than an occasional deep dive.

A repeatable checklist:

Note TSS and IF — does it match the session intent?
Check NP vs. average power — how variable was the ride?
Scan the power curve for peaks or unexpected drops
Audit pacing on the key effort(s)
Count matches burned and note timing
Review HR decoupling on long aerobic work
Flag anything worth noting

This habit closes the feedback loop between execution and planning. Over weeks and months, you build a detailed picture of how your fitness is responding, where your limiters are, and which sessions are actually producing adaptation.

The data is only useful if you read it. Start with this structure, then adapt it to what you find yourself caring about most in your own file.