You're Tracking Three Sports But Managing One Training Load. That's the Problem.

One Number Does Not Describe Three Sports

Open Strava after a big training week. You'll see a single training load number - maybe a Relative Effort score, maybe an estimated TSS. It tells you that you trained hard. It does not tell you that 80% of that load came from cycling and your run volume was dangerously low relative to what you're about to ask your legs to do on race day.

This is the core problem with how most triathletes track training. They manage one aggregate number when they're actually training three distinct physiological systems with three distinct fatigue profiles and three distinct injury risk curves.

A triathlete doing 12 hours per week split 2/7/3 across swim/bike/run has a completely different body than one doing 12 hours split 4/4/4. Their overall "load" might look identical on any dashboard. Their readiness to race - and their injury risk - could not be more different.

TSS Is Not Fungible Across Disciplines

Training Stress Score was originally designed for cycling power data. It works well for that. The problem starts when you try to use it as a universal currency across sports.

100 TSS on the bike means you did roughly a one-hour ride at threshold. Your cardiovascular system took a hit, your quads accumulated some fatigue, and you burned through glycogen. You'll feel it tomorrow, but you could probably run the next day without much issue.

100 TSS on the run means something very different. Running generates 3-5x the eccentric muscle damage per unit of effort compared to cycling. The impact forces, the stretch-shortening cycle loading on tendons, the neural fatigue pattern - none of this maps cleanly onto cycling stress. A 100 TSS run leaves your musculoskeletal system significantly more damaged than a 100 TSS ride, even though the number is identical.

Research from Mujika (2017) in the International Journal of Sports Physiology and Performance showed that the relationship between training load metrics and performance outcomes differs substantially across endurance disciplines. The dose-response curve is sport-specific. Treating all load as equivalent is like adding dollars and euros because they're both "money."

Swimming makes this even messier. A 60-minute masters swim session might generate modest cardiovascular stress and almost no musculoskeletal damage compared to running. But it creates significant shoulder fatigue that won't show up in any heart rate-based load metric. Your CTL doesn't know about your rotator cuff.

The Bike-Run Interference Problem

Every triathlete knows the feeling: you had a massive bike week, your total training load looks great, and then your Thursday run feels like you're dragging sandbags. Your legs are heavy, your pace is off, and your Garmin helpfully tells you your VO2 Max is declining.

This isn't a mystery. It's bike-run interference, and it's one of the most under-tracked phenomena in triathlon training.

Heavy cycling volume, particularly sessions with lots of time above threshold, creates significant quadriceps fatigue. When you then try to run, those same quads need to absorb impact forces on every stride. Fatigued quads mean altered running mechanics - shorter stride, more braking force, compensatory loading on calves and Achilles tendons. A 2021 study in the Journal of Sports Sciences found that cycling-induced fatigue significantly altered running kinematics in triathletes, increasing ground contact time and reducing running economy.

The insidious part: your aggregate training load might look perfectly managed. Your acute-to-chronic ratio is 1.1, right in the sweet spot. But that ratio is being calculated across all three sports. Your cycling-specific acute load might be spiking at 1.5 while your running load sits at 0.7 - and then you wonder why your Achilles hurts when you try to ramp up run volume three weeks before race day.

Swim Load: The Neglected Third

Most triathletes under-track swim load for a simple reason: swimming doesn't hurt the same way. You get out of the pool feeling tired but not wrecked. Your legs feel fine. Your heart rate data from swimming is unreliable (wrist-based optical sensors struggle in water). And since most triathlon training platforms weight load by cardiovascular stress, swimming often looks like a minor contributor.

This creates two problems.

First, shoulder health. Swim volume accumulates stress on the rotator cuff, and that stress is invisible to every mainstream load metric. Triathletes who ramp swim volume for an Ironman build frequently develop shoulder issues that "come out of nowhere" - except they don't. The load was accumulating; nothing was tracking it.

Second, swim fitness gets deprioritized because the numbers don't scream at you. A triathlete who skips a bike session sees their CTL drop noticeably. Skip a swim session and the dashboard barely moves. This creates a feedback loop where athletes unconsciously shift volume toward bike and run - which is exactly backwards for most age-groupers whose biggest time gains are in the water.

Acute-to-Chronic Ratio Needs Per-Sport Tracking

The acute-to-chronic workload ratio (ACWR) is one of the most useful injury prediction tools in endurance sport. When your recent training load spikes above 1.3-1.5x your chronic baseline, injury risk increases significantly. Research by Gabbett (2016) in the British Journal of Sports Medicine established this framework, and subsequent work has refined it for endurance athletes.

But the ACWR only works if you're calculating it at the right resolution. An aggregate ACWR across swim, bike, and run can mask dangerous spikes in individual disciplines.

Here's a scenario that plays out constantly in Ironman training blocks: an athlete maintains steady total volume but shifts their distribution. They cut swim sessions to add more bike volume as they approach a long-course race. Their aggregate ACWR looks stable at 1.0-1.1. But their cycling ACWR jumped to 1.4 in two weeks, and when they try to maintain run volume alongside the increased bike load, their run quality collapses and their injury risk spikes.

Per-sport ACWR tracking catches this immediately. Aggregate tracking misses it entirely.

What Actually Works

The fix isn't complicated in theory. You need:

Separate load tracking per discipline. Your weekly training load should be three numbers, not one. You should know your swim, bike, and run load independently, tracked over time with their own acute-to-chronic ratios.

Cross-sport fatigue modeling. Bike load affects run quality. Run load affects bike leg freshness. These interactions need to be visible, not buried in an aggregate number. When your cycling load spikes, something should flag that your run sessions might need to back off even if your "run load" looks fine.

Shoulder-specific swim tracking. Heart rate-based load metrics miss the primary injury risk in swimming. Volume and intensity in the water need separate attention, particularly during build phases.

Distribution awareness. Not just "how much did I train" but "how was that training distributed across disciplines, and does that distribution match what my race demands?"

Most triathletes try to do this manually - a spreadsheet here, a TrainingPeaks chart there, some mental math about how Tuesday's ride will affect Thursday's run. It works until it doesn't, usually at the worst possible time in a training block.

Connecting the Data You Already Have

The frustrating thing is that the data exists. Strava has your bike and run files. Your swim watch logs every session. Garmin or WHOOP tracks your recovery. The problem isn't collection - it's integration and interpretation.

This is what athletedata.health is built to do. It pulls from Strava, Garmin, WHOOP, and Oura simultaneously, so your AI coach sees all three sports as distinct load channels. When your cycling ACWR spikes, it flags the run interference risk. When your swim volume drops for two weeks, it notices. When you're three weeks out from race day and your per-sport load distribution doesn't match your race demands, it tells you.

No single training platform does this well because they all default to aggregate metrics. A coaching layer that understands the three-sport interaction - that cycling fatigue suppresses run quality, that swim load is invisible to heart rate metrics, that TSS is not a universal currency - gives you the visibility that one number never will.

Stop Managing One Number

Triathlon is three sports pretending to be one. Your training load tracking should reflect that. If you're looking at a single aggregate number and making decisions from it, you're missing the sport-specific signals that actually predict performance and injury.

Track three loads. Watch three ratios. Understand the cross-sport interactions. That's how you train for three sports without letting one of them quietly wreck the other two.

Want per-sport load tracking with cross-discipline fatigue modeling? Start your free trial.