Metrics explained
Training load explained: TRIMP, TSS, strain and relative effort
Training load puts a number on how hard a session was, combining duration and intensity. Tracking it over weeks helps you build fitness without overdoing it.
Written by MoveVitals Editorial Collective
Community-authored educational content. Individual clinical review is identified only when a named review is actually recorded.
Editorial standards & corrections
Key takeaways
- TSS sets 1 hour at FTP at 100: below 50 is easy with the next day fine, 100–200 means fatigue for 1–2 days and above 200 takes several days.
- Acute load over the last 7 days reflects fatigue, chronic load over the last 6 weeks reflects fitness, and the balance between them is form.
- Week-to-week jumps of more than about 10–30 % raise injury and illness risk, so increase gradually, often by about 5–10 %, with a lighter week every 3–5 weeks.
- WHOOP strain runs on a 0–21 scale while Polar uses TRIMP and Strava Relative Effort, so devices disagree and you should follow one for trends.
- Heart-rate-based load underestimates strength training, which session RPE (1–10 × minutes) captures better.
A 2-hour easy ride and a 45-minute interval session can be equally demanding. Training load turns each workout into one number so you can compare and add them up.

The main load metrics
| Metric | Used by | Based on |
|---|---|---|
| TRIMP | Polar, research | Duration × heart-rate intensity, weighted exponentially |
| TSS (Training Stress Score) | TrainingPeaks, Wahoo, Zwift, intervals | Power relative to FTP; 1 h at FTP = 100 |
| hrTSS / rTSS | Many platforms | Heart rate or pace versions of TSS |
| Strain | WHOOP | Cardiovascular load on a 0–21 logarithmic scale — see WHOOP strain |
| Training Load / EPOC | Garmin, COROS | Estimated excess post-exercise oxygen consumption |
| Relative Effort | Strava | Heart-rate-zone weighted effort |
| Session RPE | Coaches | RPE (1–10) × minutes |
Typical TSS per session
| TSS | Session | Recovery |
|---|---|---|
| < 50 | Easy / recovery | Next day fine |
| 50–100 | Moderate | Some fatigue next day |
| 100–200 | Hard or long | Fatigue for 1–2 days |
| > 200 | Very hard / race | Several days |
From sessions to trends
The real power of load metrics comes from trends:
- Acute load (last 7 days) reflects fatigue.
- Chronic load (last 6 weeks) reflects fitness.
- The balance between them is "form" — see fitness, fatigue and form.
- Increase weekly load gradually; jumps of more than ~10–30 % week to week raise injury and illness risk.
Load is not recovery
Load tells you what you did, not how you coped. Combine it with HRV, resting heart rate, sleep and how you feel.
In MoveVitals
Workouts from Strava, Garmin, Polar, COROS, WHOOP and Zwift are deduplicated before load is calculated, so a ride recorded by both a bike computer and a watch is not counted twice.
Worked example
Illustrative scenario. Nina logs session load as RPE × minutes. A typical week: 4 sessions averaging 50 minutes at RPE 5 → about 1,000 AU, with a 4-week average of ~950 AU. After a holiday she plans a comeback week at 1,600 AU — an acute:chronic ratio near 1.7. Because big spikes above about 1.5 have been associated with higher injury risk in some team-sport studies, she instead targets ~1,100 AU and increases about 10% a week. The ratio is a rough guide and its predictive value is debated. Numbers are illustrative.
Action steps
- Log every session's duration and RPE (or device load).
- Calculate weekly load and a 4-week rolling average.
- Avoid sudden jumps; increase weekly load gradually (often about 5–10%).
- Plan a lighter week every 3–5 weeks.
- Combine load data with sleep, soreness and mood rather than trusting one number.
Related guides
- Fitness, fatigue and form (CTL, ATL, TSB): the performance management chart
- RPE (rate of perceived exertion): the sensor you always carry
- Deload weeks: why planned easy weeks make you fitter
- Overreaching and overtraining: warning signs and what to do
- Team sports with a wearable: volleyball, rugby, handball and hockey load
FAQ
Why do WHOOP and Garmin give different load for the same ride? Different models and scales. Pick one for trend tracking.
Does strength training count? Heart-rate-based load underestimates it; session RPE captures it better.
Is the acute:chronic ratio reliable? It's a useful rule of thumb, but researchers have questioned its statistical basis, so treat it as a guide, not a prediction.
Do different devices calculate training load the same way? No; brands use different models (heart rate, power, TRIMP), so compare within one platform.
References
- Foster et al. (2001). A New Approach to Monitoring Exercise Training. The Journal of Strength and Conditioning Research. https://doi.org/10.1519/1533-4287%282001%29015%3C0109:anatme%3E2.0.co;2
- Gabbett (2016). The training—injury prevention paradox: should athletes be training smarter and harder?. British Journal of Sports Medicine. https://doi.org/10.1136/bjsports-2015-095788
- Soligard et al. (2016). How much is too much? (Part 1) International Olympic Committee consensus statement on load in sport and risk of injury. British Journal of Sports Medicine. https://doi.org/10.1136/bjsports-2016-096581
For general information only. This is not medical advice — talk to a qualified professional about your health.
Keep reading
Metrics explained
Resting heart rate: normal ranges and what changes it
4 min read
Metrics explained
VO2 max: what it means and how to improve it
4 min read
Sports
Trail running with a watch: heart rate, climbs and pacing by effort
7 min read
Devices & setup
How MoveVitals handles multiple devices: provenance, duplicates and conflicts
5 min read
Metrics explained
Normal heart rate variability (HRV) by age: RMSSD vs SDNN
6 min read
Devices & setup
Strava and MoveVitals: workouts, streams and devices that arrive via Strava
3 min read

