Most age-group triathletes build their week around the run. The swim gets a nod for technique, the run gets the emotional investment, and the bike gets whatever hours are left — usually a long weekend ride with the local group and a midweek spin that drifts into zone 2 by accident.
This is backwards. The bike is 50–60% of your race-day time. It's also the single biggest determinant of how the run goes. Ride it wrong and no amount of run fitness saves you at kilometre 14 of a half-marathon off the bike.
The argument of this piece is simple. The bike leg deserves dedicated, run-protective programming. Not more volume. Different volume, structured for a specific job: delivering you to T2 with your running legs intact and your fuel tank where it needs to be.
Why the bike leg is the pacing lever, not the run
Look at the time splits. In a 70.3, a 5-hour age-group finisher spends roughly 2:45 on the bike and 2:00 on the run. In a full Ironman, an 11-hour athlete spends around 6 hours on the bike and 4 on the run. The bike is not a third of the race. It's more than half.
More importantly, the bike is the only leg where you can give time back to yourself on the run. Every watt you overspend in the first 30 minutes of the bike is a minute you lose in the final 10km of the run, and usually more. John Wakefield, Director of Development at Red Bull-Bora-Hansgrohe, has made this point repeatedly on the Roadman Cycling Podcast about stage racing — the damage done early is paid back with interest late. Triathlon is the same physiology with a run stapled on the end.
The pacing lever sits on the bike because that's where the decisions compound. Pace the swim 5 seconds per 100m too hard and you lose 2–3 minutes. Pace the bike 10 watts too hard and you can lose 15 minutes on the run. The asymmetry is enormous.
This is why serious triathlon bike coaching treats the bike as the race-defining segment, not the filler between swim and run. Programming the bike well is programming the run well by proxy.
The three mistakes that wreck most age-group bike legs
First mistake: too much unstructured endurance. The default age-group bike week is a Saturday group ride with surges, a Tuesday spin, and maybe a Wednesday commute. The intensity distribution is roughly 60% tempo, 20% threshold accidents, 20% easy. Prof. Stephen Seiler's research on polarised training shows that endurance athletes who pile up grey-zone volume get aerobic plateaus, not aerobic ceilings. The bike leg of triathlon is an aerobic ceiling problem.
Second mistake: training in a road position, racing in an aero position. The tri-bike or clip-on position is where your race happens. If you've logged 8 hours a week on the hoods and then rack a 90km 70.3 on aerobars, your hip flexors and lower back break down somewhere around kilometre 50. Your power doesn't drop because your aerobic system is tired. It drops because your position is failing. Dan Bigham has spoken at length about position durability being the limiter for most non-professional TT riders — it's the same for triathletes.
Third mistake: under-fuelling at race intensity. Most age-groupers practise long rides on 40–50g of carbohydrate per hour because that's what their gut tolerates on easy days. Race-day targets for 70.3 and Ironman sit at 70–100g/hr for trained athletes. Tim Spector's work on individual gut response reinforces that carb tolerance is trainable, but only if you train it. A gut that's never seen 80g/hr in a session won't accept it on race day.
Fix these three — intensity structure, position specificity, fuelling under load — and the bike leg changes character before you've added a single hour of training.
What run-protective bike programming actually looks like
Run-protective means the bike block improves bike performance without degrading run performance. That's a narrower target than "get fitter on the bike". It rules out certain sessions and demands others.
A typical week for a 70.3 athlete training 10–12 hours sits at three bike sessions. One long aerobic ride of 2.5–4 hours, ridden at 65–72% of FTP in the aero position for at least 60% of the time. One sustained sub-threshold session — 2x20 minutes or 3x15 minutes at 88–94% of FTP, which is the zone that builds durable aerobic power without the recovery cost of VO2 work. One shorter session that's either race-pace intervals (4x10 minutes at 78–82% of FTP) or a brick.
Notice what's missing. No 30/30s. No all-out VO2 blocks during race-prep phases. Dan Lorang, who coached Jan Frodeno and Gustav Iden through their biggest wins, has spoken on the podcast about why long-course triathlon rewards sub-threshold durability over top-end power. The ability to hold 75% of FTP for 4 hours is worth more than the ability to hit 120% for 5 minutes.
Intensity needs to map to accurate zones. If your last FTP test was in September and you're racing in June, your zones are fiction. Use the FTP zones calculator every 6–8 weeks and re-anchor the week.
Run-protective also means the day after a hard bike session is a run day, not a rest day. If Tuesday threshold bike wrecks Wednesday's run, the bike session was too hard or too late in the week. This is the coaching judgement that separates generic plans from programming built around the athlete — and it's the reason our cycling coaching treats the bike block as a system inside a larger system, not an isolated training silo.
Brick workouts: the bridge most plans neglect
Brick workouts — run immediately off bike — are poorly used by most age-group athletes. The default is a 20-minute shuffle off a three-hour weekend ride, done because the plan says "15min run off bike". This teaches almost nothing beyond the novelty of jelly legs.
Useful bricks fall into two categories. The first is the short-sharp race-rehearsal brick: 60–90 minutes on the bike ending with 15 minutes at race power, straight into a 20–30 minute run starting at 10–15 seconds per km slower than goal pace and building to goal pace by the end. This rehearses the specific moment of T2 — hot legs, high heart rate, needing to find rhythm.
The second is the durability brick: a moderate 2.5–3.5 hour bike at 65–72% of FTP, into a 45–75 minute run at easy aerobic pace. This trains substrate shift and fuelling practice. The run is the point, not an afterthought. The bike sets up a fatigued starting state and the run holds form inside it.
One quality brick every 10–14 days is enough during the specific prep phase. Two a week is too many — the cumulative fatigue chews into run quality elsewhere in the programme.
The common error is running the brick run too hard. If the brick turns into a threshold run off a threshold bike, you've built a session that damages recovery for three days and simulates nothing that happens in a race. Race-pace or slower. Always.
Fuelling practice belongs inside the brick. Take in 70–90g of carbs per hour across the bike portion, continue fuelling through the run, and monitor gut response. Race-day fuelling failures are almost always training-day fuelling omissions.
How to pace the race-day bike leg
Pacing by power is non-negotiable if you have a power meter. Pacing by feel is how 10-watt errors in the first 30 minutes become 15-minute run deficits.
Olympic distance: target 80–88% of FTP as normalised power. Sprint: 88–95%. 70.3: 72–78%. Full Ironman: 68–74%. These are ranges for trained age-group athletes. Newer athletes ride the lower end and still outperform the version of themselves that rode by feel.
The first 20 minutes of the bike are where races are lost. Heart rate is elevated from the swim, adrenaline is high, and perceived effort is a liar. Cap your power 5% below target for the first 15 minutes. Actively hold back. You will pass people. They will come back.
On rolling terrain, let power surge 10–15% above target on climbs lasting under 2 minutes, and drop 10–20% below on descents. Normalised power is what matters, not the number on any given 30-second window. Flat courses demand tighter discipline — variability index below 1.05.
The back half of the bike should be ridden at or below the front half. If your average power for the first half is 205W, the second half should be 200–205W, never 215W. Negative-split bike legs produce positive-split runs, which is the whole objective.
Fuel from minute 10. Don't wait for thirst or hunger. Target 70–90g of carbs per hour for 70.3, 80–100g for Ironman, with 500–750ml of fluid per hour depending on conditions. Take a gel or equivalent on a schedule — every 20 minutes is easier to execute than every 25.
Last 15 minutes: back off 5%. Spin the legs slightly higher cadence. Empty a bottle. You're setting up T2, not claiming a bike split.
Signs your bike block is working
The clearest signal is not a higher FTP number. It's a better run off the same bike effort. If your 90km training ride at 210W used to cost you a 5:15/km run and now costs you a 4:55/km run at the same heart rate, the block is working. The bike didn't get easier in isolation — the whole system got more durable.
Second signal: normalised power holds across the duration. If you can sustain 75% of FTP for 4 hours in the aero position without the last hour dropping off, race-day execution becomes plausible. Most age-groupers can hold 75% for 90 minutes and then bleed watts for the next two hours. That's a durability gap, not a fitness gap.
Third signal: fuelling at 80g/hr feels routine. No gut distress, no flat feeling at hour three, no bonk risk. If race-pace fuelling still feels like an experiment two weeks out from race day, the block didn't address the limiter.
Fourth signal: position is quiet. No neck pain after 90 minutes, no numb hands, no lower back forcing you upright every 15km. Position durability is trainable and measurable, and it's one of the clearest predictors of race-day power retention in the final hour.
Fifth signal: heart rate decoupling stays under 5% on long aerobic rides. If your heart rate is 8–10% higher in hour three than hour one at the same power, aerobic base is still the limiter and more sub-threshold volume is the prescription.
None of these signals require a race to validate. They show up in training if you're looking.
If you're preparing for a 70.3 or Ironman this season and your bike block still looks like a cycling club's training week with a run bolted on, rebuild the structure. Pick one race-pace bike session, one sustained sub-threshold session, one long aerobic ride, and one quality brick per fortnight. Anchor intensities to current FTP zones, practise fuelling at 70g/hr minimum, and ride 60%+ of your weekly bike time in the aero position you'll race in. That's the starting point. The run takes care of itself when the bike is built properly.
