Most 70.3 training plans online start at 10 bike hours a week and climb from there. That number is wrong for roughly 80% of the athletes reading them. It's pulled from professional templates, stretched across a 12-week plan, and handed to someone with a full-time job and two kids.
The real question isn't "what's the maximum I can fit?" It's "what's the minimum dose that delivers the bike split I want without wrecking my run?" Those two numbers are usually closer than athletes expect.
Below are honest ranges by ambition level, and the logic behind where each one tops out.
The honest answer: it depends on what you want
A 70.3 bike leg takes 2:20 to 3:30 for most age-groupers. The training volume needed to ride that duration competently scales with how fast you want to go and how fresh you want to arrive at T2.
If you want to finish: 4–6 hours a week. If you want a strong mid-pack split: 6–8. If you want to podium your age group or chase a Kona 70.3 slot: 8–11. Past 11 hours, for nearly every amateur, the returns collapse.
The second variable is your background. A former club cyclist coming to triathlon needs fewer bike hours because the aerobic engine is already there. A pure runner coming the other way needs more. Training age on the bike matters more than training age overall.
Dan Lorang, who has coached Jan Frodeno and Anne Haug, has said repeatedly that volume is a lever, not the goal. The goal is race-specific fitness. Volume serves it.
Beginner: first 70.3, finish strong
Target: 4–6 bike hours per week across a 16-week build.
Structure looks like this. One long ride, starting at 90 minutes in week one and progressing to 3 hours by week 12. One quality ride of 60–75 minutes with tempo or sweet-spot intervals. One optional easy spin of 45–60 minutes for frequency.
That's it. Three rides. The long ride is non-negotiable because 90km of pedalling is primarily an aerobic durability problem, not a power problem. You cannot fake 3 hours on the bike.
Beginners who push to 8+ hours in their first 70.3 block almost always break down in the run. The bike legs aren't conditioned to absorb that load, and the running gets crowded out. Finish the first one. Build from there.
Intermediate: sub-5:30 bike-run target
Target: 6–8 bike hours per week, with structured intensity.
At this level, the plan gets a third quality touch. One long ride of 2.5–3 hours with race-pace blocks inside it (think 3 x 20 minutes at 70.3 power in the back half). One threshold session of 2 x 15 to 3 x 12 at FTP. One endurance ride of 90 minutes to 2 hours.
Polarised or pyramidal distribution works well here. Roughly 75–80% of bike time sits below aerobic threshold, 15–20% at race pace or tempo, and a small slice at threshold or above. Prof. Stephen Seiler's research on intensity distribution holds up strongly for this group.
The seven-hour athlete who nails this structure will out-ride the nine-hour athlete doing grey-zone tempo every session. I've watched it happen hundreds of times in our triathlon bike coaching programme. Hours are a container; what goes inside them decides the outcome.
Advanced: Kona-qualifying effort
Target: 8–11 bike hours per week, peaking around 11–12 in the biggest weeks.
This is where most age-group podium contenders live. The structure adds a second threshold-or-above session and often a second long ride. A typical week: 3–3.5 hour long ride with race-pace work, 2.5 hour endurance with sweet-spot blocks, 75-minute VO2 or threshold session, and one or two easier rides.
The ceiling exists for a reason. Past 11 hours, run quality starts degrading for athletes not on a pro recovery stack. The bike gets faster and the run gets slower, and 70.3 is won by the athlete who loses the least time on the run.
John Wakefield has talked on the podcast about how even World Tour development riders don't simply maximise hours — they maximise productive hours. Same principle applies at the amateur top end.
Why more hours doesn't always mean faster
Three reasons volume stops paying.
First, diminishing returns on aerobic adaptation. The tenth hour produces a fraction of the adaptation of the fourth. The curve is steep early and flat late.
Second, opportunity cost on the run. Triathlon is three sports fighting for one recovery budget. Every bike hour past your personal threshold comes out of run durability, which is where most 70.3 races are decided.
Third, life load. Job stress, poor sleep, and under-fuelling compress your training ceiling. A 7-hour week executed consistently for 14 weeks beats a 10-hour average that includes two illness write-offs and a missed race.
Joe Friel made this point 20 years ago in The Cyclist's Training Bible: consistency compounds; heroic weeks don't. The athletes who improve year over year are the ones who rarely miss.
How to get the most out of 6, 8, and 10 bike hours
On 6 hours: one long ride (3 hours by peak), one quality session (threshold or sweet-spot), one easy ride. Don't add a fourth session. Protect the long ride even if the weather is bad — move it indoors.
On 8 hours: add a second quality touch and extend the long ride to 3.5 hours. Use race-pace efforts inside the long ride starting eight weeks out. Keep one ride genuinely easy.
On 10 hours: you have room for two quality sessions plus race-specific long rides with structured intervals. The trap at 10 hours is making the easy rides too hard. If your heart rate on endurance rides creeps above 75% of max, you're building fatigue without buying fitness.
Your next step: open your last four weeks of training and count your actual bike hours, not planned ones. If the gap is large, the problem isn't the plan — it's the plan's fit with your life. Build the plan around the hours you'll actually complete.
