How should you pace an Ironman bike leg?

What is Intensity Factor and why does it matter?

Intensity Factor is a concept introduced by Andrew Coggan in the early 2000s as part of the same framework that produced TSS, Normalized Power, and the FTP-based zone system. IF is defined as Normalized Power divided by Functional Threshold Power, expressed as a decimal. An IF of 1.0 means you rode the entire ride at your FTP. An IF of 0.70 means you rode at 70 percent of FTP, normalized. The metric exists to answer a specific practical question: how hard, relative to your own ceiling, was this ride?

For Ironman pacing, IF is the single most useful number. Average power is contaminated by coasting, stop lights, and variable terrain. Normalized Power accounts for the physiological cost of surges by weighting brief hard efforts more heavily than their time suggests. IF then normalizes that weighted power to your own FTP, which lets you compare intensity across athletes, courses, and seasons on a single scale.

The critical insight from Coggan's original work is that sustainable IF decreases predictably with event duration. A 5-minute effort can be held at IF 1.15 to 1.25. A 1-hour time trial is, by definition, close to IF 1.00. A half-marathon bike leg (70.3 Ironman) sits around IF 0.80 to 0.85 for well-trained athletes. A full Ironman bike leg — 112 miles, 4.5 to 7 hours of riding — drops to IF 0.65 to 0.78 depending on the athlete's ability and fitness. Beyond that, both the cardiovascular system and the muscular glycogen stores start to fail, and the marathon becomes a different and much darker event.

Coggan originally published IF ranges for long-course triathlon suggesting 0.70 to 0.78 as the realistic window for well-trained athletes in a full Ironman. Twenty years of race data have validated this range almost unchanged. The ceiling is a physiological limit, not a training limit.

What Intensity Factor should you actually target by finish-time goal?

The target IF scales with finish-time ambition, fitness, and experience, but the ranges are remarkably consistent across thousands of power files.

• First-time Ironman, 13 to 15+ hour finish goal: IF 0.62 to 0.68. The priority is finishing the marathon, not optimizing the bike split. An easy bike is almost always the right answer — pushing harder compounds into a walking marathon.
• Intermediate athlete, 11 to 13 hour finish goal: IF 0.65 to 0.72. This is the most common amateur range. The sweet spot is usually IF 0.68 to 0.70 for most athletes in this band, which produces a controlled bike leg and a runnable marathon.
• Competitive amateur, 9 to 11 hour finish goal: IF 0.70 to 0.76. Athletes at this level have both the fitness and the bike handling to sit in a higher intensity, and the fueling capacity to support it. Still rarely above 0.76.
• Elite / professional, sub-9 hour finish goal: IF 0.74 to 0.78. Even at the top of the sport, IF rarely exceeds 0.78 for the full 112 miles. Kristian Blummenfelt's sub-7-hour Ironman in 2022 was ridden at approximately IF 0.80 on a completely flat course with ideal conditions — and it's notable precisely because it sits right at the edge of what the model allows.
• Hilly or hot course correction: subtract 0.02 to 0.04 from the target. Courses like Nice, Lanzarote, St. George, and Kona in a hot year punish aggressive pacing disproportionately. A cautious IF on a hard course consistently beats an aggressive IF.

The 'I'll just push a little harder' instinct is why most Ironman bike legs end badly. Adding 10 watts to a 4-hour 30-minute ride at 200W saves about 5 to 8 minutes on the bike and loses about 15 to 40 minutes on the run. That's a losing trade for almost every athlete.

What is Variability Index and why is it as important as IF?

Variability Index is Normalized Power divided by Average Power. It measures how smooth or variable your ride was. VI of 1.00 means the ride was perfectly steady. VI of 1.10 means the ride had significant surging (climbs, accelerations, passing efforts). VI of 1.20 means the ride was all over the place — hard on climbs, easy on descents, inconsistent throughout.

For Ironman pacing, VI should stay under 1.05, and ideally under 1.03 on flat courses. The reason is glycogen economics: every surge above IF 0.85 for more than a few seconds forces the body to burn glycogen at a much higher rate than fat-driven Zone 2 effort. Glycogen is the fuel that runs the marathon. Every unnecessary surge on the bike is glycogen you do not have available for mile 18 of the run.

A rider with IF 0.70 and VI 1.03 has produced a near-perfect Ironman bike leg. The same rider with IF 0.70 and VI 1.15 has probably ridden the same average power but in a much more costly way — punchy on every climb, coasting on descents, reaching briefly into Zone 4 and 5 dozens of times. The fatigue bill at mile 80 of the marathon is much higher for the second rider, even though the power file looks 'the same' on average.

The practical implication is that on hilly Ironman courses, the steady rider gives up a little time on the climbs by refusing to push above target IF on steep sections, and gains it back on descents and flats. On flat courses, the steady rider holds a near-constant wattage for 112 miles. On both, the steady rider runs a better marathon.

How do you pace an Ironman bike leg by heart rate or RPE instead?

Not every athlete races with a power meter, and even athletes who do should have a backup plan in case the head unit fails or the power data becomes unreliable. Heart rate and RPE can do most of the same work as power, if the athlete is calibrated and the conditions are friendly.

For heart rate, the target is typically 75 to 82 percent of threshold HR for most amateurs, and 78 to 85 percent for competitive amateurs and pros. The caveat is that heart rate drifts upward over the course of a long ride due to cardiovascular drift, heat, and fatigue — so a reasonable target is to start at the bottom of the range (say, 75 percent) and allow drift to the top of the range (82 percent) by hours 3 to 4 of the ride. Do not chase heart rate in the first hour; it will settle below target and then rise.

For RPE on a 10-point Borg CR10 scale, Ironman bike pacing should feel like a 4 to 5 out of 10 in the first half and drift to 5 to 6 out of 10 by hours 3 to 4. Anything above 6 is too hard. If the effort feels moderately hard in the first 90 minutes, you are certainly overcooking the pace, regardless of what the power meter says. The 'this feels easy' sensation in the first 90 minutes is not optimism — it's the correct pacing signature of a well-executed Ironman bike.

The best long-course triathletes describe the first 90 minutes of the bike as 'easier than I think it should be' and the final 90 minutes as 'harder than I think it should be, but at the same power'. That's the correct shape of the ride. If it ever feels the opposite, the pacing is wrong.

How does fueling interact with bike pacing?

The bike pacing target and the fueling target are linked in a way that most first-time Ironman athletes don't realize. At IF 0.68, most athletes can absorb 80 to 100 grams of carbs per hour and still tolerate the gut — because blood flow to the digestive system is preserved at lower intensities. At IF 0.78, the same athlete often cannot absorb more than 60 to 70 grams per hour because splanchnic blood flow has dropped and gastric emptying has slowed.

This is why pushing the bike pace harder doesn't just cost glycogen directly — it costs the ability to replace glycogen by eating. An Ironman athlete at IF 0.70 taking in 90 grams per hour for 5 hours has absorbed 450 grams of carbs, which is enough to run a functional marathon. The same athlete at IF 0.78 is more likely to take in 350 to 400 grams over the same duration because the gut couldn't handle more, and the fuel deficit compounds during the run.

The practical rule is that the bike pace and the fueling rate must both be planned together. An aggressive bike plan requires a gut that has been specifically trained for high-carb intake under the higher intensity — and even then, the ceiling is lower than at moderate effort. For most amateurs, the 'take it easy on the bike so you can eat on the bike' approach is the right one.

How do you break the 112 miles into segments?

A well-executed Ironman bike leg has a deliberate segment-by-segment plan rather than a single average target. The structure lets the athlete ease in, hold the middle, and resist the temptation to push hard at the end.

• Miles 0 to 20 (Hour 1): Target IF 0.62 to 0.65. This is the discipline phase. Resting athletes who just finished the swim feel strong, and the race is still full of other athletes passing them. The job is to hold below the target IF no matter how many people go past. Every watt spent in the first 20 miles is more expensive than later watts.
• Miles 20 to 60 (Hours 2 to 3): Target IF at the goal. Settle into race pace. Fuel consistently. Stay aero. Ignore surges. This is where most of the ride happens and where the steady discipline is built.
• Miles 60 to 90 (Hours 3 to 4.5): Hold target. Do not increase. Fatigue starts to become real here, and the temptation is to 'push while I still feel okay'. The right move is to hold steady and continue fueling aggressively, knowing the last hour is where the tax gets paid if you overcook now.
• Miles 90 to 112 (Hours 4.5 to 6): Allow a small drop in IF if needed. Normalized Power often declines in the last hour by a few watts for all but the most experienced athletes. Fighting this is usually a mistake. Protect the legs, finish the fueling plan, and save mental bandwidth for the run. A 2 to 5 watt drop in the last hour costs less than 90 seconds on the bike split and saves the marathon.

What are the five most common Ironman bike pacing mistakes?

These mistakes appear in power files from every Ironman race, at every level, and they are the reason amateur marathon splits are usually 30 to 90 minutes slower than the athlete's standalone marathon fitness suggests.

• Starting too hard in the first 20 miles. The fresh legs, the adrenaline, and the other athletes passing create an almost irresistible pull to ride above target early. The first hour should feel almost disappointingly easy. If it doesn't, the race is already slipping.
• Pushing hard on climbs without easing on descents. Surging on every climb while free-wheeling on descents drives VI above 1.10 and wastes glycogen on segments where the time savings are trivial. The correct move on climbs is to hold IF steady — typically losing a few seconds to stronger climbers — and make it back on flats and descents.
• Chasing passes. Passing another athlete requires a brief effort above target. Being passed does not. Let strong cyclists go, let weaker athletes catch you, and ignore the individual battles. The marathon is where places are made in Ironman, not the bike.
• Ignoring fueling because the bike feels easy. Athletes who start comfortably often don't feel hungry and skip their planned carbs in the first hour. This is a fatal error — the fuel debt cannot be made up later, especially at higher intensities where the gut closes down. Eat on schedule from the start, regardless of how you feel.
• Confusing 'fit enough to ride harder' with 'should ride harder'. An athlete whose bike fitness allows IF 0.78 can still benefit from racing at IF 0.72 if it produces a better marathon. The goal of the bike in an Ironman is not to produce the best bike split — it's to produce the best overall finish time, and for almost every amateur, the best overall finish time comes from a conservative bike.

How do you use race data to refine your pacing for next time?

Every Ironman power file is a piece of evidence for the next one. After a race, the athlete should look at four specific numbers: average power, Normalized Power, IF, and VI. Those four numbers, compared to the bike split and the marathon split, tell the story of what actually happened.

If IF was at target, VI was under 1.05, and the marathon was slower than expected anyway, the issue is probably fueling, fitness, or heat — not bike pacing. If IF was above target or VI was above 1.05, and the marathon collapsed, the bike is the primary suspect. If IF was below target and the marathon still went badly, the issue is almost never the bike at all.

The practical lesson is that Ironman bike pacing should become more conservative, not less, with experience. Every year of experience tends to show an athlete how much they lose on the marathon by pushing the bike, and experienced Ironman athletes generally race at lower IF than first-timers — because they've learned the hard way that the bike is a fuel preservation exercise, not a power display.