Every endurance athlete eventually runs into the same problem: how do you compare a two-hour easy ride with a one-hour interval session? One feels easy and takes twice as long. The other is brutal but short. Which one cost you more? Which one should you recover from?
Training Stress Score — TSS — exists to answer exactly that question. It's the most important load metric in endurance training, and once you understand it, you stop guessing what you can handle next week.
What does TSS actually measure?
Training Stress Score, introduced by Andrew Coggan, is a single number that represents the total physiological load of a workout. It combines how hard you went and how long you went for, weighted so that harder efforts count disproportionately more than easy ones — which is exactly how your body perceives training stress.
The anchor point is simple and worth memorizing: one hour ridden at exactly your FTP equals 100 TSS. From that anchor, everything else scales. A two-hour easy ride at 65% FTP might land around 85 TSS. A one-hour ride with hard intervals can hit 110 TSS. A five-hour endurance ride can clear 250 TSS even though none of it felt desperate.
How is TSS calculated?
The classic cycling formula uses three inputs: Normalized Power (NP), Intensity Factor (IF), and duration.
- Normalized Power (NP) is an average power that accounts for the fact that variable efforts are harder on the body than steady ones. Stop-and-go criterium racing with the same average power as a flat time trial feels much worse — NP captures that.
- Intensity Factor (IF) is simply NP ÷ FTP. An IF of 1.0 means you rode at exactly your FTP average. A tempo ride might sit at IF 0.82. A recovery spin at IF 0.55.
- Duration is in seconds, and the final formula is: TSS = (duration × NP × IF) ÷ (FTP × 3600) × 100.
In practice, you never compute this by hand. Every training platform — CoreRise included — calculates TSS automatically from every ride file you upload. What matters is understanding what the number means, not the arithmetic.
Does TSS work for running and swimming?
Yes, with small adaptations. The language stays the same, the anchor stays the same, only the intensity input changes.
- Running TSS (rTSS) uses Normalized Graded Pace instead of power — pace adjusted for the energy cost of hills. Your threshold pace plays the role FTP plays on the bike.
- Running TSS from power (using a running power meter like Stryd) is calculated exactly like cycling TSS, with running FTP as the anchor. This is increasingly the default for serious runners.
- Swimming TSS (sTSS) is anchored to CSS (Critical Swim Speed) and uses pace rather than power.
- hrTSS — heart rate TSS — exists as a fallback when you have no power meter. It's noisier but usable for endurance zones.
The important insight: once your sport-specific anchor is set, TSS is sport-agnostic. A 70-TSS run and a 70-TSS ride impose a comparable physiological load. That's what makes it powerful for triathletes.
What do weekly TSS numbers mean?
Weekly TSS is the most actionable version of the metric. It tells you whether you're building, maintaining, or coasting. Broad ranges that work for most athletes:
- 300–450 weekly TSS — recreational endurance training. Healthy, sustainable, good for general fitness and amateur goals.
- 450–650 weekly TSS — committed amateur level. Base phase for half-marathon, 70.3 triathlon, or serious gran fondo preparation.
- 650–900 weekly TSS — hard amateur or elite-level training. Typical of Ironman preparation or elite road racers in build phases.
- 900+ weekly TSS — professional territory. Rare and requires world-class recovery, nutrition, and sleep infrastructure.
These are ranges, not targets. Your number depends on your sport, training age, and recovery capacity. A 45-year-old runner balancing a job and family will get more from 350 quality TSS than 600 forced ones.
What is the Performance Management Chart?
TSS becomes genuinely powerful when you track it over time in a Performance Management Chart (PMC). The PMC plots three derived numbers, all in TSS units, calculated as exponentially weighted averages of your daily TSS history.
- CTL — Chronic Training Load (42-day exponential average). Think of it as your fitness. It moves slowly and represents the load you've been absorbing over the last month and a half.
- ATL — Acute Training Load (7-day exponential average). This is your fatigue. It rises fast after a hard week and drops fast with rest.
- TSB — Training Stress Balance = CTL − ATL. This is your freshness. Positive TSB means you're rested relative to your fitness; negative TSB means you're loaded up.
How do you use TSS to plan a training week?
The practical workflow most coaches use — and the one CoreRise applies automatically — follows three rules.
- Progress weekly TSS gradually. A week-over-week jump of more than ~10% is where overuse injuries and burnout start appearing. Three build weeks followed by one recovery week at 60–70% of peak is the classic pattern.
- Watch your CTL, not your individual workouts. A single 150 TSS session looks scary. A CTL that climbs from 50 to 75 over eight weeks is what actually makes you fitter.
- Arrive at race day with positive TSB. Most endurance races are executed best with a TSB between +10 and +25 on race morning. Below 0 and you're tired; above +30 and you're losing fitness.
What are the common mistakes with TSS?
TSS is the best planning tool you have — until you start using it as a video game score. Three traps catch almost everyone.
- Chasing the number instead of the training. Padding TSS with junk miles — long, aimless Zone 2 rides added just to hit a weekly target — inflates the number without adding meaningful adaptation.
- Testing with heart rate and power mixed. If half your rides use power-based TSS and half use hrTSS, your PMC becomes noise. Pick one anchor per sport and stick to it.
- Ignoring life stress. TSS only measures training load. A 600-TSS week on top of a brutal work schedule or broken sleep is physiologically not the same as 600 TSS on a calm week. The body doesn't distinguish between training stress and any other kind.
How does TSS differ from other load metrics?
You'll encounter other acronyms in training platforms. They are cousins of TSS, not replacements.
- TRIMP (Training Impulse) is an older heart-rate-based load metric. It weights time in each HR zone and produces a load number. Useful as a heart-rate fallback, less precise than power-based TSS.
- Suffer Score (Strava) is a simplified, heart-rate-based effort score. Good for gamification, not useful for structured planning.
- Load (Garmin) is Garmin's proprietary version of TSS-style acute and chronic load, calculated from EPOC-based internal load. Close in spirit to CTL/ATL but not directly comparable across platforms.
Key takeaways
- TSS is a single number that represents total workout load, anchored so that one hour at FTP equals 100 TSS.
- The formula combines duration, Normalized Power, and Intensity Factor — platforms calculate it for you automatically.
- TSS works across cycling, running (rTSS), and swimming (sTSS) once a sport-specific threshold anchor is set.
- Weekly TSS ranges are sustainable bands, not targets. Quality beats volume every time.
- The Performance Management Chart (CTL, ATL, TSB) turns TSS history into a picture of fitness, fatigue, and freshness.
- Progress load gradually, watch CTL trend, and arrive at races with positive TSB.
- TSS measures training stress only — life stress is invisible to it, but your body still pays for it.
Frequently asked questions
How is TSS different from calories burned?
Calories measure energy expenditure. TSS measures physiological stress relative to your own fitness. A five-hour easy ride burns a huge amount of calories but imposes moderate stress. A one-hour hard interval ride burns fewer calories but imposes far more stress. For training planning, TSS is vastly more useful than calorie totals.
What's a good daily TSS?
There's no universal daily number — it depends on your weekly plan and your recovery. A rough heuristic: most recreational athletes sit between 50 and 150 TSS per training day, with easier days around 50–80 and quality sessions between 90 and 150. The number you should care about is weekly TSS and CTL trend, not any single day.
Can I compare TSS across sports?
Approximately, yes — that's the whole point. A 70 TSS ride and a 70 TSS run impose comparable load once each sport has an accurate threshold anchor. But running is more impact-intensive than cycling, so 100 TSS of running damages your musculoskeletal system more than 100 TSS of cycling. TSS captures cardiovascular load better than structural load.
What happens if my FTP is wrong?
Your TSS becomes systematically biased. If your FTP is overstated, your TSS will be underreported — every ride looks easier than it is, and you'll plan too much load. If your FTP is understated, TSS is inflated and you'll look like you're training harder than you really are. Retest every 4–6 weeks so the anchor stays honest.
Should I target a TSS number every day?
No. Daily TSS targets turn training into a number-chasing exercise and invite junk miles. Target weekly TSS and progression of your CTL. Individual workouts should be prescribed by purpose (endurance, threshold, VO2max, recovery), not by a TSS quota.
Does TSS account for heat, altitude, or life stress?
Not directly. TSS only sees duration and intensity. A hot, humid, dehydrated ride at 70 TSS is physiologically far harder than 70 TSS in cool conditions. A night of bad sleep on top of hard training multiplies the cost. Good training platforms — including CoreRise — let your coach factor these in when adjusting the plan.
How CoreRise uses TSS to manage your training
Every workout you complete — whether it comes from Apple Health, Garmin, or a manually logged session — is automatically converted into TSS inside CoreRise, using the right anchor for the sport (FTP for the bike, threshold pace or running power for running, CSS for swimming). Your weekly load, CTL, ATL, and TSB are calculated and updated continuously.
That data becomes context for your coach. When you ask 'can I handle a big weekend?', the answer is grounded in your real fatigue, not a guess. When the coach builds or adapts a plan, it ramps your weekly TSS inside a safe zone. When you sleep badly or report a hard week at work, your coach factors that in and scales the next block.
- Automatic TSS calculation from Garmin, Apple Health, and manually logged workouts.
- Weekly load targets that progress inside a sustainable 5–10% build range.
- Your coach reads your CTL, ATL, and TSB before every plan adjustment.
- Recovery weeks are planned, not improvised after you crash.