Why single-sport coaches fail triathletes

Most coaching tools were built for one sport. Runna for running. TrainingPeaks for cyclists (initially) and then everyone. Intervals.icu assumes you’ll know which charts to combine. For athletes who train two or three disciplines, this single-sport origin is a silent problem: the tool treats your training as three parallel plans, but your body experiences one combined load. The gap between those two models is where injuries and stagnation hide.

Failure mode one — combined monotony is invisible

A triathlete does an easy swim Monday, an easy ride Tuesday, an easy run Wednesday, an easy swim Thursday, an easy ride Friday. Each sport’s dashboard shows healthy variety — Monday was 40 TSS of swim, nothing else; Tuesday was 55 of ride, nothing else. Per-sport Foster monotony looks fine.

But the combineddaily stress is 40, 55, 45, 50, 60 — evenly distributed, never zero, no real rest day. Combined monotony is 3.2. Foster’s research says this pattern elevates illness risk the following week. The single-sport tools never show the combined number, so the warning never fires.

This is the most common failure mode we see in beta. Athletes come in describing “unexplained fatigue” and “always getting sick right before races”. The explanation is usually on the combined-load chart their previous tool didn’t have.

Failure mode two — per-sport TSS hides the shape of the week

“Weekly swim: 120 TSS, weekly ride: 320 TSS, weekly run: 180 TSS. Total 620 TSS.” This is how most triathlete spreadsheets look. It’s not wrong, but it’s dangerously coarse. A 620-TSS week with two rest days and two long days is productive. A 620-TSS week with seven moderate-load days — because each sport has a “consistency” plan — is a stress fracture waiting to happen.

Only a combined daily-TSS view shows the shape of the week. That’s the number that predicts training outcomes, and single-sport tools fundamentally can’t compute it because they don’t cross the boundary between sports.

Failure mode three — cross-sport load adds are invisible

You had a big swim week and still executed your scheduled run intervals. Your run coach sees your running load — fine, on-plan. Your swim coach sees your swimming load — heavy but progressing. Neither sees that the combined stress on your body exceeded safe ramp. The injury looks “random” a month later; the chart that would have shown the problem didn’t exist.

ZoneTwo’s rule engine has an explicit check for this pattern: CROSS_SPORT_LOAD_ADD. It fires when per-sport loads look safe individually but combined weekly TSS exceeds the safe ramp by more than 40%. A single-sport tool can’t fire this rule because it’s structurally unaware of the other sports.

What combined-load modeling actually changes

Three concrete shifts once you model all sports as one athlete:

• TSB is computed on combined daily TSS. Form is the gap between total fitness and total fatigue, not a per-sport average. Race-day readiness reflects the whole body.
• Monotony is combined. Rest days become visible as real zeros, and the evenness trap is caught. This alone changes how athletes plan their weeks.
• The weekly review narrates across sports. “Your swim volume climbed 25% while run mileage held — shift one easy run to give the shoulders recovery room.” A single-sport coach can’t write that sentence.

Who this matters for

Pure runners, pure cyclists, or pure swimmers: this doesn’t apply to you. Single-sport tools match your reality.

Duathletes (run + ride), aquathletes, and especially triathletes: combined-load modeling isn’t a nice-to-have. It’s the difference between a coach who sees your week and one who sees three unrelated weeks. If you’re serious about training across sports, use a tool that computes combined load natively — ours, or someone else’s. Just not one that treats each sport in isolation.

Read more on the metrics behind this: training monotony, CTL, ATL, TSB, and the multi-sport feature that implements all of this.