Ironman training is unique among endurance events in one critical way: the load comes from three separate sports, each stressing different tissues, different energy systems, and different musculoskeletal structures. A week that looks manageable on paper — 3 swims, 4 bikes, 4 runs — can hide a total stress burden that exceeds what the body can absorb. Most Ironman DNS (did not start) and DNF (did not finish) outcomes trace back to load mismanagement in the months before race day, not fitness shortfalls on race day itself.
Why Single-Sport Load Metrics Fail Triathletes
A runner who tracks weekly kilometres has a single, consistent metric. A cyclist who tracks kilojoules or TSS (Training Stress Score) can compare any two weeks directly. A triathlete doing both — plus swimming — faces a load aggregation problem: how do you add 15,000 metres of swimming, 250km of cycling, and 60km of running into a single number that tells you whether you're in the safe zone or approaching breakdown?
The most common mistake: triathlete athletes track each sport separately and conclude each is "within reasonable limits" while the cumulative stress across all three exceeds recovery capacity. The injury doesn't come from the run or the bike — it comes from the total.
The TSS Framework for Multi-Sport Load
Training Stress Score (TSS), developed by Andrew Coggan for cycling with a power meter, has been extended to running (rTSS) and swimming (sTSS) to allow cross-sport load aggregation. The calculation differs by sport but the output is comparable:
- Cycling TSS: Based on power output relative to Functional Threshold Power (FTP). A 1-hour ride at exactly FTP = 100 TSS.
- Running TSS (rTSS): Based on pace or heart rate relative to threshold. A 1-hour run at threshold pace = 100 rTSS.
- Swimming TSS (sTSS): Based on pace relative to threshold pace (T-pace). Lower TSS per hour than bike or run — swimming places minimal musculoskeletal load, which matters for injury risk even if the cardiovascular stress is equivalent.
Total weekly TSS = cycling TSS + running TSS + swimming TSS. This single number can be tracked over time to monitor the Acute:Chronic Workload Ratio (ACWR) and identify when you're loading faster than your body is adapting.
The Acute:Chronic Workload Ratio in Ironman Training
ACWR compares your training load over the past 7 days (acute load) to your average load over the past 28 days (chronic load). The research-supported safe zone is 0.8–1.3. Above 1.5, injury risk roughly doubles.
In Ironman training, ACWR violations typically occur at three points:
- Early build phase: Athletes feeling good after base training increase volume across all three sports simultaneously. Each individual sport increase seems modest; the aggregate ACWR spikes.
- After a recovery week: Chronic load has dropped during the easy week. Returning to normal training creates a higher ACWR than expected. The recovery week lowers your chronic load baseline — don't return to full volume on Monday.
- Final long block: 8–12 weeks from race day, athletes push their longest weeks. These are often the highest ACWR weeks of the entire build — and the timing is the worst, because injury at this stage eliminates months of preparation.
Sport-Specific Load Priority
Not all three sports carry equal injury risk for equal training stress:
Running: Highest Injury Risk per Hour
Running generates ground reaction forces of 2–3× body weight per stride. It is the sport responsible for the majority of Ironman training injuries — stress fractures, IT band syndrome, plantar fasciitis, Achilles tendinopathy. Running mileage should be increased most conservatively of the three sports, particularly in the first 12 weeks of a build.
Practical rule: When adding volume in a given week, prioritise adding swim or bike volume before run volume. Running load should be the last variable increased and the first reduced when accumulated fatigue signals appear.
Cycling: Moderate Injury Risk, High Cardiovascular Stress
Cycling places minimal musculoskeletal impact load but generates substantial cardiovascular and metabolic stress. Long rides (4–7 hours in Ironman prep) contribute enormous TSS that the body must absorb through recovery. Knee overuse injuries (IT band friction, patellofemoral) are the primary cycling-related risk, often from saddle height errors rather than volume alone.
Cycling is also the discipline where most Ironman time is spent on race day (5–8 hours for most athletes). Volume in cycling can be higher than running without equivalent injury risk, but the cardiovascular accumulation still contributes to overall fatigue.
Swimming: Lowest Injury Risk, High Recovery Value
Swimming places almost no axial load on the musculoskeletal system and can often be maintained or even increased during periods when running must be reduced due to fatigue or minor injury. Shoulder overuse injuries occur with poor technique or very high volume, but are rare in athletes swimming fewer than 20,000 metres per week with reasonable stroke mechanics.
Swimming can be used strategically as "active recovery" — moderate swim sessions on the day after long bikes or runs help flush metabolic waste without adding meaningful musculoskeletal stress.
Periodisation Across a 30-Week Ironman Build
A well-structured Ironman build follows a periodised progression across phases, with weekly TSS targets that reflect the ACWR safe zone:
Phase 1 — Base (Weeks 1–10)
Focus: aerobic base in all three sports; establish weekly routine; introduce brick workouts. TSS builds gradually from baseline to approximately 600–800/week by end of phase. No week-on-week TSS increase exceeds 10–15%.
Phase 2 — Build (Weeks 11–22)
Focus: sport-specific intensity; long bike and long run distances approach race distances; weekly TSS reaches 800–1,000+ by peak weeks. Brick sessions become longer and more race-specific. Recovery weeks every 3–4 weeks reduce TSS by 40–50%.
Phase 3 — Peak and Taper (Weeks 23–30)
Weeks 23–26: highest volume weeks of the build. One final long ride (160–180km) and long run (28–32km). TSS may reach 900–1,100 in peak week. Weeks 27–30: progressive taper. Volume reduces by 30–40% per week. Intensity maintained. By race week, TSS is 40–50% of peak-week levels.
Brick Workouts and Cumulative Load
Brick sessions — training two sports back-to-back, most commonly bike followed immediately by run — create a compound load that single-sport TSS calculations underestimate. The physiological transition between sports generates additional neuromuscular stress beyond what the individual sessions would suggest.
Account for bricks in your load calculations by treating the combined session as 10–15% higher TSS than the sum of the individual components. And schedule bricks carefully — they require a full recovery day on either side, not just "an easy session."
Using Load Tracking Tools
Manual ACWR tracking is feasible but time-consuming. Use the NorthLine Training Load Calculator to input weekly training data across all three sports and monitor your acute:chronic workload ratio in real time. Pair this with the Cycling Power Zones Calculator to establish your FTP-based TSS baseline for cycling — the most accurate way to quantify cycling load in your weekly total.
Platforms like Intervals.icu and TrainingPeaks automate this across all three sports if your devices upload to them, giving you a continuous performance management chart without manual calculation.
The Simple Rule When in Doubt
If you feel uncertain whether you're overloading in a given week, default to this: add volume to swimming before cycling, and cycling before running. The injury risk hierarchy makes this the safest path through the build. A slightly undertrained swimmer who arrives at the run start healthy is infinitely better positioned than an overtrained runner who arrives with a compromised Achilles.
Topics