One of the most common questions I get from athletes — especially those stepping up to longer distances — is this:
Should I train by time, or should I train by distance?
It sounds simple, but the answer can have a big impact on your performance, recovery, and long-term progression — especially if you're balancing training with work, family, and life.
Let's break it down properly.
The Traditional Approach: Training by Distance
Most triathletes start here.
- Swim 2,000m
- Ride 60km
- Run 10km
It's neat, structured, and easy to measure. And for race-specific preparation, it absolutely has a place.
Where distance-based training works well:
- Race simulation — e.g., practising a 90km ride for a 70.3
- Confidence building — knowing you've covered the distance
- Benchmark sessions — tracking pace improvements over a set course
But here's the problem…
Distance doesn't account for:
- Fatigue
- Terrain (hills vs flat)
- Weather (wind, heat, humidity)
- Your current fitness or recovery state
A 10km run can be a completely different session depending on the day.
The Smarter Approach: Training by Time
This is where experienced athletes — and most high-level coaches — shift toward.
Instead of saying: "Run 10km"
You say: "Run 60 minutes in Zone 2"
Why Time-Based Training Is More Effective
1. It Controls Training Stress
Your body doesn't know distance — it only knows time under load.
A 60-minute run at the right intensity:
- Builds aerobic fitness
- Limits injury risk
- Keeps recovery predictable
2. It Adapts to Your Daily Condition
Had a poor night's sleep? Hot weather? Fatigue from yesterday?
Time-based training allows you to:
- Adjust pace
- Stay in the correct heart rate zone
- Still get the intended training benefit
3. It Improves Consistency (The Real Secret)
Consistency beats hero sessions every time.
Training by time:
- Removes pressure to "hit numbers"
- Keeps sessions achievable
- Helps you show up day after day
Real-World Example (From My Own Training)
In my Ironman build, most of my key sessions are structured by time:
| Session | Time-Based Approach |
|---|---|
| Long Run | 1h45 → building toward 2h30 (Zone 2) |
| Bike Sessions | 2–4.5 hours based on time, not distance |
| Interval Runs | 4 × 4 minutes at effort, not distance splits |
Why? Because I'm managing:
- Fatigue from work shifts
- Recovery between sessions
- Long-term progression toward race day
And it works — I've gone from my run being my weakest leg to one of the strongest in my age group.
So… Should You Ever Use Distance?
Yes — but strategically.
| Use Distance When… | Use Time For… |
|---|---|
| You're close to race day | 80–90% of your training |
| You want to simulate race conditions | Aerobic base building |
| You're dialling in pacing and nutrition | Recovery sessions |
| Managing fatigue and consistency |
The Hybrid Model (Best of Both Worlds)
The most effective approach?
Train by time, race by distance.
Example week:
- Long ride → 3.5 hours (not 100km)
- Midweek run → 60 minutes Zone 2
- Swim → 45–60 minutes structured intervals
- Race simulation → occasional distance-based session
This gives you:
- ✅ Flexibility
- ✅ Consistency
- ✅ Better recovery
- ✅ Stronger race-day execution
Final Takeaway
If you're serious about improving in triathlon — especially over 40 or balancing a busy life —
Time-based training is the smarter, more sustainable approach.
Distance has its place, but it shouldn't control your training.
Because at the end of the day:
It's not about how far you go in training — it's about how well you arrive on race day.
Want to train smarter? Explore our free resources including the Heart Rate Zone Calculator to dial in your training zones, or check out our structured training plans designed for every distance. Need personalised guidance? Get in touch — I'd love to help.