Most first-timers can finish a 70.3 on 8 to 12 hours a week. The bigger surprise: in a study of 209 half-Ironman finishers, weekly hours didn’t separate the fast from the slow. Hours are a ticket to the start line, not a speed dial.
Do More Hours Really Mean a Faster 70.3 Training Plan?
Researchers surveyed 209 half-Ironman finishers and split them into fast, mid and slow groups. Average training time was 13.9 ± 5.4 hours a week, and it did not differ between groups (J Sci Med Sport, 2014). What did predict finish time: age, previous best half time, goal time and how much the goal mattered. Together those four explained 58% of the variance.
In short: who you are and what you’ve done beat how many hours you logged.
Faster finishers had raced more halves and took fewer rest days in training. That points to experience and consistency, not raw volume. The same pattern showed up at Ironman distance. In 184 recreational men training 13.9 ± 5.0 hours a week, personal-best marathon and Olympic-distance times predicted race time better than volume (Knechtle group, 2015). That’s a longer race, so treat it with care.
Think of weekly hours like the size of your fuel tank. A bigger tank helps only if you can fill it every week. A smaller tank you fill reliably beats a huge one you fill twice.
Plans disagree by 5 hours at the peak. That’s your first clue that no single number is correct.
6, 8 or 10-12 Hours: What Each Level Buys You
Triathlete puts an average 70.3 week at 8:30 to 11:00 and a peak week at 11:00 to 14:00. Rouvy and Purple Patch both say 8 to 12 hours works for most athletes. Translation: the middle of the pack lands near 9 or 10.
| Weekly hours | Realistic goal | Plan length | Main trade-off |
|---|---|---|---|
| 6 | Finish, if you already train about 3 h/week | 18-24 weeks | Little room for a second quality session |
| 8 | Finish comfortably | 16-18 weeks | Long ride and long run take most of the week |
| 10-12 | Finish strong, or chase a time goal | 16 weeks | More fatigue, more life to protect |
The 6-hour row is an editorial judgment. No source gives a proven minimum. The nearest anchor is the Finalsurge beginner plan, which starts at 5:50 and assumes you already exercise 3+ hours a week. A Mindset Endurance plan runs 4 to 9 hours across 16 weeks.
Hours are also a time-goal tool. One forum poster aiming for sub-5:00 averaged about 17 hours a week, and faster age-groupers post 14 to 22. That’s anecdote, not data. Still, it says finishing and racing are different questions.
Want the 8-hour layout day by day? See this 8-hour week for a full-time job. This post helps you choose the tier first.
How Hours Ramp Across the Build
You don’t train 12 hours from day one. A 24-week commercial plan shows the shape: base 6.0 to 9.0 hours, build 9.5 to 12.0, peak 11.0 to 13.5. The TrainingPeaks beginner plan averages 9 hours over 16 weeks, with a 12-hour peak week and a 5-hour recovery week. Finalsurge climbs from 5:50 to 8:32 over 18 weeks.
The pattern is a staircase. Start where you are, step up a little each phase, and drop back every few weeks. Peak weeks tend to land 4 to 6 weeks before race day, then the taper takes over.
Pick your top tier, then work backward. If your peak is 8, start near 6. If your peak is 12, start near 8 or 9.
Build the base first. Add speed later.
Swim, Bike, Run: Splitting the Hours
Triathlete’s average week splits roughly as swim 1:30 to 2:00, bike 4:00 to 5:00 and run 3:00 to 4:00. Using midpoints, my own arithmetic gives about 18% swim, 46% bike and 36% run. Strength and mobility add 30 minutes to 2 hours.
In short: nearly half your hours go on the bike. Run gets a bit over a third.
Bricks live inside those bike and run hours, not on top of them. How often and how long to do bricks is covered separately.
Ramping Without Getting Hurt
Injury data in triathletes is thin. In 37 amateurs doing a 12-week Ironman build at 10.5 ± 2.8 hours a week, 65% had an injury and 89% of those were overuse. Even so, low, moderate and high load groups did not differ significantly in injury or illness (UCT thesis, 2019). Older work did link higher weekly hours with muscle-tendon injuries (p = 0.014).
A 2025 study of 5,205 runners and more than 500,000 runs found single-run spikes mattered. Jumping 10 to 30% above your longest run in the past 30 days raised overuse injury risk by 64%. Weekly mileage change did little. Those are runners, not triathletes.
Translation: the big single session bites harder than the slow weekly climb. Keep your long run near its recent size.
A Case Study: Priya Picks Her Tier
Priya, 36, signed up for her first 70.3 with 20 weeks to go. She had finished a sprint and an Olympic race. She wanted 12 hours because a forum said so. Her real week held 7 to 9.
She picked an 8-hour peak, an 18-week plan and a 6-hour start. Illustrative numbers only. She held steady, hit most sessions, and dropped back to 5 hours every fourth week. She finished comfortably.
The plan she could repeat beat the plan she could brag about.
What to Do When Life Breaks the Plan
Most plans ignore reality. You’ll miss sessions. You’ll travel, sleep badly or catch a cold. The research says consistency, with fewer rest days, tracks with faster finishes. So the skill isn’t a perfect week. It’s a quick fix after a bad one.
AthleteOS builds your training plan around the weekly hours you give it, whether that’s 6, 8, 10 or 12. When life interrupts, the AI coach re-plans the rest of the week and the Adaptation Log explains each change, so you can approve or decline it. Start the 14-day trial and set your hours first.
A Quick Checklist for Choosing Your Hours
- Can you repeat this week 16 to 18 times in a row?
- Do you already train about 3 hours a week?
- Is your goal a finish or a time?
- Does your fuel plan hold up on long days? Use this hour-by-hour fuelling plan.
- Will your easy days stay easy? Zone 2 builds that base.
If you answered yes to the first two, start at 8. Move up only when the week feels boring.