Race File Analysis for Cycling: Find Attacks and Burned Matches

Why race file analysis matters

Good race file analysis for cycling starts with a problem every racer recognizes: the average rarely explains the result.

A race can look controlled in the summary while being brutally selective in the pedals. Average power may sit near a sustainable number, but the file can hide repeated accelerations, short recoveries, long periods of pressure and the exact moment your race became harder than it needed to be.

That is why post-race analysis should not start with 'Was my average power good?' Better questions are more useful:

• Where did the race become selective?
• Which surges forced a real response?
• How much recovery did you get before the next hard effort?
• Did you miss the move because of fitness, position or timing?
• What should change in training and execution before the next race?

The point is not to admire big numbers. It is to connect the numbers to the decisions that created them.

What averages hide in a race file

Average power smooths the race into one number, which is useful for broad context but weak for explaining selection. Racing is uneven by nature. Corners, rises, crosswinds, attacks, braking, gaps and position fights create repeated changes in demand.

Two riders can finish with similar average power and have very different races. One may have stayed near the front, followed wheels efficiently and spent effort only when the field was actually splitting. Another may have drifted back, braked into corners and sprinted back onto the wheel every time the road narrowed.

The summary can make those rides look similar because it compresses the entire race into a single workload. The file explains why one rider spent less to get the same outcome.

Normalized power helps because it gives more weight to harder efforts and better reflects the cost of variable racing. But it is still a summary metric. It can tell you the race was costly. It cannot tell you whether the cost came from smart commitment, poor positioning or chasing the wrong moves.

To get that answer, zoom into the moments where the race changed.

Locate the selection points

The first job is to find the moments that mattered. Do not start by hunting for your highest power. Start by finding the sections where the field split, the pace changed or your outcome shifted.

Selection often appears as a sequence rather than a single spike. The decisive move might include the first acceleration, a short hesitation, a second surge, a bridge across, then several minutes of pressure while everyone tries to make the move stick.

Look for patterns such as:

• A sharp power increase followed by sustained pressure
• Multiple spikes with little soft-pedaling between them
• A speed increase that lines up with a power surge
• A cadence jump that suggests an acceleration rather than a grind
• Heart rate continuing to rise after power drops, which points to delayed physiological cost

The useful question is not only 'How hard was the surge?' It is 'What did the surge force you to do next?'

A hard acceleration followed by full recovery may look dramatic without changing the race. A slightly lower effort that comes after several previous surges, with no real recovery before or after, may be the one that decides whether you stay in the front group.

This is a common mistake in cycling power analysis. Riders focus on the highest peak, but the decisive effort is often the one performed after the legs are already loaded.

Race file analysis for cycling: the post-race workflow

Use the same workflow after every race so the file becomes actionable instead of just interesting.

1. Mark the selection points

Open the file and scroll through the power trace with speed, cadence, heart rate and elevation visible. Mark the places where the race situation changed:

• The field split
• A move went clear
• You had to bridge
• You lost contact
• The pace changed before key terrain
• The race became lined out after a corner, climb, wind section or technical feature

Name each marker in plain language, such as 'field split after corner', 'bridge to front group' or 'lost wheel before climb'.

2. Create laps or segments around each surge

For every marked point, create a lap or segment that includes the effort and the immediate lead-in and recovery. Do not isolate only the spike. Include what happened before and after, because that is where the real cost often appears.

A useful segment should answer:

• What was the load before the surge?
• How hard was the surge itself?
• Did you recover afterward or stay under pressure?
• Did the effort improve your race position or only repair earlier damage?

3. Compare power, cadence, heart rate and speed before and after

For each segment, compare the channels on both sides of the surge:

• Power: Was the effort a short spike, a sustained push or repeated accelerations?
• Cadence: Did you accelerate fluidly, grind, or lose pedaling rhythm?
• Heart rate: Did it stabilize, keep rising, or stay elevated into the next effort?
• Speed: Did the effort actually move you with the race, or were you spending power with little change in speed?

This comparison separates the move itself from the cost it created.

4. Label the cause

Every major effort should get a cause label. Keep the labels simple:

• Required by the race situation
• Chosen attack or bridge
• Forced by another rider's move
• Caused by poor positioning
• Caused by braking or cornering loss
• Wasted due to impatience or uncertainty

This step prevents the default conclusion that every failed response was a fitness problem. Sometimes it was. Often the file shows that the hard effort was created earlier by position, timing or hesitation.

5. Convert the finding into two targets

Finish with one training target and one race execution target.

If the file shows you could follow the first move but faded when the pressure repeated, the training target might be repeatability under incomplete recovery. The race execution target might be staying closer to the first ten wheels before the circuit's decisive corner.

If the file shows most hard efforts were solo gap closes, the training target may still include anaerobic repeatability, but the execution target matters more: stop entering technical sections too far back.

One physiological target plus one tactical target keeps the lesson specific enough to use.

Worked example: repeated corner gaps versus one decisive bridge

The numbers below are hypothetical. They are not benchmarks. They show how the same summary can hide two very different tactical stories.

Rider A and Rider B finish the same race with similar average power and both feel they were at their limit.

Rider A's file shows this pattern across several technical laps:

• Before each corner, power drops as the rider brakes and loses position
• After each corner, there is a short high-power acceleration to close a small gap
• Cadence jumps sharply, speed rises only after a delay, and heart rate keeps drifting upward
• The pattern repeats until the rider cannot close the final gap

The cause label is not simply 'could not handle the power'. It is more specific: repeated corner exits forced by poor position and braking. The physiological cost came from having to re-accelerate again and again with incomplete recovery.

A useful training target would be repeat accelerations with short recovery. A useful execution target would be entering the technical section farther forward and carrying speed through the corner so fewer matches are spent getting back onto the wheel.

Rider B's file shows a different pattern:

• The rider stays sheltered before the key move
• A sharp surge appears when the front group accelerates
• Power stays elevated while bridging across
• Cadence remains controlled, speed increases with the move, and heart rate rises but stabilizes after the bridge

That effort was expensive, but it was tied to the race outcome. The cause label is 'chosen bridge to decisive group', not wasted effort.

For Rider B, the training target might be holding selection-level power after a hard acceleration. The execution target might be committing earlier when the right riders move, rather than waiting until the gap is larger.

The difference matters. Rider A needs to reduce avoidable cost before the selection. Rider B needs to improve the ability to finish the selection once the right move goes.

Classify the cost: necessary matches versus wasted matches

A burned match is not just any hard effort. It is a hard effort that reduces your ability to respond later.

That distinction is important because racing requires matches. Following the decisive move, bridging before a split forms or holding position before key terrain can all be worth the cost. The problem is spending the same physiological currency on avoidable repairs.

When reviewing the race, group your major efforts into categories:

• Attacks you initiated
• Attacks you followed
• Bridges you chose
• Gaps you closed after drifting back
• Positioning surges before key terrain
• Accelerations after corners or technical sections
• Pulls that did not improve your tactical situation

Then look at the recovery between them. If power dropped and stayed low enough for breathing and leg tension to settle, the match cost was limited. If each surge fed directly into the next, the cost compounded even if no single effort was your highest peak.

The file is useful because memory tends to justify effort. In the moment, closing a gap can feel mandatory. Afterward, the data may show the gap only existed because you entered the previous section too far back.

The goal is not to avoid hard efforts. It is to spend them where the race demands them, not where impatience, hesitation or poor position creates extra work.

Interpret the supporting channels

Power is the foundation, but power alone can mislead. Cadence, heart rate and speed explain how the effort happened and whether it changed the race.

Cadence helps identify the type of demand. A high-cadence jump often points to an acceleration out of a corner or a response to an attack. A lower-cadence high-power section may suggest a climb, wind pressure, an overgeared effort or a grind from poor momentum. The same power can carry a different cost depending on how it is produced.

Heart rate adds delayed context. It will not capture the immediate cost of a short acceleration as cleanly as power, but it can show accumulated strain. If heart rate keeps rising across repeated surges while power peaks fade, the limiter is likely fatigue accumulating faster than you can recover.

Speed helps show whether the effort changed your race position. A high-power spike with little speed change may mean you were fighting wind, gradient, poor positioning or a closing gap. A power spike paired with a speed increase and a stretched field suggests the group actually accelerated.

Read the channels together. A power surge before a climb, a cadence jump out of a corner and a speed increase as the field lines out are different tactical situations. The same wattage can be smart, necessary or wasteful depending on why it happened.

Use summary metrics after the tactical review

Once you have identified and labeled the decisive sections, zoom back out and look at the summary metrics.

Normalized power is useful because it captures the cost of variable intensity better than average power. If normalized power sits well above average power, the race likely involved repeated accelerations or uneven pacing. The important question is whether that variability came from the race's decisive moments or from avoidable work.

Variability index adds another layer because it compares normalized power with average power. A steadier race will show less separation. A more stochastic race will show more separation. Do not chase a specific value. Ask what created the variability.

Peak efforts help define the event demands only when they are tied to the race situation. A peak effort used to bridge to the front group tells you something different from a peak effort spent closing a gap after drifting too far back.

For broader context, an FTP estimator can help frame sustainable power from hard efforts. But race files are messy by design. The mess is where the tactical information lives.

Separate tactical mistakes from fitness limitations

A fitness limitation usually appears when the race demands a repeatable pattern and your response degrades. You can follow early, then the same type of effort becomes harder to reproduce. Power fades, cadence loses fluidity, heart rate remains elevated and recovery between surges becomes incomplete.

A tactical mistake often has a different signature. The power is high, but the reason for the effort was avoidable. You were too far back before a narrow section. You let a gap open because you were inattentive. You chased alone when cooperation was available. You pulled hard when the move had little value. You reacted to every acceleration instead of identifying which riders and sections actually mattered.

Fitness determines what you can do. Tactics determine how often you are forced to do it.

Use the labels from your workflow to make the distinction:

• If most hard efforts were required by the race situation, train repeatability, durability and recovery under pressure
• If most hard efforts repaired avoidable mistakes, prioritize positioning, timing and restraint
• If the decisive effort was possible once but not repeatable, train the ability to surge, settle and surge again
• If you made the selection but could not follow the next move, train selection-level power after prior load

This is where analysis becomes useful. The same file might point one rider toward harder anaerobic repeatability work and another toward better corner positioning.

Turn the file into training and race execution

The final step is translation. A race file should leave you with a training decision and a race decision.

If the file shows repeated short spikes with limited recovery, train surge repeatability. Build sessions around hard accelerations, incomplete recovery and the ability to settle back into pressure rather than fully reset.

If the decisive move came after a long period of fatigue, train durability. The limiter was not fresh power. It was the ability to produce the power required to follow the decisive move after sustained load.

If you made the front group but could not contribute or follow the next acceleration, train over-under control and recovery under pressure. Many riders can surge once. Fewer can surge, recover while still riding hard, then surge again.

If cadence collapsed late, be careful with the conclusion. It may point toward force production under fatigue, but it can also reflect poor gearing, bad positioning, too many earlier matches or simply accumulated fatigue.

If normalized power was high and your tactical labels show wasted efforts, do not solve the problem by adding intensity first. Reduce the unnecessary cost. Better positioning is often the cheapest way to make the same fitness go further.

Conclusion

Race file analysis for cycling is most useful when it connects physiology to tactics.

Average power gives workload context. Normalized power shows more of the cost. Peak efforts show what you produced. But the real value comes from identifying where the pressure happened, why you had to respond, how much recovery you had and whether each effort moved you closer to the result you wanted.

Mark the selection points. Build laps around the surges. Compare power, cadence, heart rate and speed before and after. Label the cause. Then turn the file into one training target and one race execution target.

That is how a race file becomes more than a record of effort. It becomes a plan for racing better next time.