What typical training load looks like
in age-group triathlon
What 34,731 training sessions tell us about how age-group triathletes actually train. Not a template. Not a target. A reference point.
You can track your load.
That doesn't mean you can judge it.
Most age-group athletes can see their duration, distance, heart rate, and TSS. What they usually can't see is whether those numbers are low, typical, or high for athletes training for the same kind of racing. This gives you a way to close that gap.
This gives you something most athletes don't have: context. A cohort-based reference point built from uploaded training data — not memory or guesswork.
Long-course changes the weekly picture
Athletes focused on long-course racing accumulated more weekly duration (615 vs 507 min/wk), more distance (171 vs 118 km/wk), and more TSS (574 vs 452/wk). That doesn't just mean more training. It means a different load profile, a different durability demand, and a different recovery conversation.
Coach's Read
If an athlete is targeting 70.3 or Ironman, the weekly ceiling is usually higher. Comparing them with sprint- or Olympic-focused athletes is misleading.
"More is not the signal.
Appropriate is the signal."
Training should not look the same all year
The Specific phase carried the highest load in this cohort: 556 min/wk and around 620 TSS/wk. Load dropped 14% during Taper and 38% in Off-season. That is exactly what you expect if athletes are periodising sensibly rather than training flat all year.
Coach's Read
A high training load is not automatically good. It makes sense only if it appears in the right phase, for the right athlete, with the right recovery around it.
What mattered less than expected in this cohort:
age and sex.
In this dataset, weekly load wasn't meaningfully explained by age or sex. It was explained by what athletes were preparing for — and where they were in the season.
That does not mean those factors never matter. The sample was self-selected, predominantly male, and skewed toward long-course athletes. But the finding is clear: race distance and training phase drove the differences, not demographics.
Average weekly heart rate didn't differ across the factors either. The paper suggests that averaging HR across a week may have hidden meaningful session-level differences — so this should not be taken to mean intensity never changes.
Most athletes did strength work.
Few appeared to treat it as a year-round performance pillar.
Seventy-five percent of respondents reported strength training. Most did it either four or nine months of the year. Sessions averaged 30–50 minutes, twice per week, most often in general preparation.
Coach's Read
Most athletes are doing strength work. Few are treating it as a year-round performance pillar. That may leave performance and durability gains on the table.
Where does 'high volume'
actually sit?
The 90th percentile of this cohort trained 13.7–15.2 hours per week. That's the upper boundary — not the target. Most athletes in the dataset trained considerably less.
High load does not equal high performance. The question is not "how much can I do?" — it's "how much should I do, given everything else in my life right now?"
This changes how you
make decisions.
- You stop guessing whether your load is "enough"
- You stop comparing yourself to the wrong athletes
- You stop treating every phase the same
- You start adjusting load based on context — not habit
Data gives you the reference point. Coaching gives you the decision.
Compare your week to the cohort
The point is not to chase a percentile. The point is to stop interpreting your own load in isolation.
Choose your context, enter your value,
and see where you sit.
Objective Load
The raw measurement — volume, intensity, and density from the FISAAL dataset.
Life Load
Mapping training stress against career, family, sleep, and physiological age.
Coaching Decision
The deliberate coaching decision — informed by the intersection of load and life.
Use these values to sense-check whether an athlete's current load looks broadly low, typical, or high for their race focus and training phase. Then ask the more important question: is this load appropriate for this athlete, right now?
If your week looks high relative to the cohort, that is not automatically a badge of honour. If it looks low, that is not automatically a problem. The useful question is whether your training matches the race you are preparing for, the phase you are in, and the life you are carrying around the training.
What this page does not tell you.
This page does not tell you what your training should be. It does not tell you whether a high TSS week is productive. It does not tell you whether you are recovering well enough to absorb the work. It does not tell you whether your life load is already too high.
The paper is clear: these values are descriptive. They help you compare your training with a relevant cohort. They do not replace coaching judgment, athlete context, or the difference between load completed and load tolerated.
Objective load is useful. Context makes it meaningful.
"Data gives you the reference point.
Coaching gives you the decision."
This study gives you the boundaries: what weekly duration, distance, and TSS looked like in a large age-group cohort. Summit adds the rest: life load, recovery, communication, and the coaching decision that follows.
Leighton Wells
Sport scientist, endurance coach, and founder of Summit Triathlon Coaching
Published research, translated for practice.
Built from a six-month dataset of 95 age-group triathletes using TrainingPeaks, with 34,731 sessions aggregated into 2,177 training weeks across 25 countries. A rare objective reference point for coaches and athletes who want more than guesswork.