Training with Strava

Relative Effort vs TSS: which to trust for each workout type

Relative Effort and TSS are not two readings of the same thing. Relative Effort is a heart-rate-zone score, closer to Eric Banister's TRIMP than to a power meter's output [Meyer 2018, Hellard et al. 2007]. TSS is mechanical work, scaled so one hour at threshold equals 100 [Allen et al. 2019]. They answer different questions on different rulers, which is why no single number is right for every ride. The rule that holds across workout types: trust power-based TSS when heart rate cannot keep up with the effort, and Relative Effort when the work is steady and aerobic enough for heart rate to settle into the zone it belongs in.

By Jim Camut · Former pro & ex-Bruyneel Academy racer

Updated Jun 1, 20264 chapters7 citations

01 / 04

What each metric actually measures

Relative Effort sums weighted time-in-heart-rate-zone against your max HR; TSS scales normalized power against your FTP [Meyer 2018, Allen et al. 2019]. One counts heartbeats, the other counts watts. Neither is a corrected version of the other, and there is no conversion factor between them.

Relative Effort sums weighted time-in-heart-rate-zone against your configured max HR, then scales it so efforts across sports stay comparable. The math descends from Banister's TRIMP, an exponential weighting of heart-rate reserve [Hellard et al. 2007]. TSS does something structurally different: it takes normalized power, scales it against your FTP, and multiplies by duration, calibrated so 60 minutes at threshold returns exactly 100 [Allen et al. 2019]. One counts heartbeats; the other counts watts.

The split matters because heart rate is a lagging, capacity-bounded signal and power is an instantaneous, unbounded one. Heart rate takes 30 to 90 seconds to climb to the level an effort demands, and it cannot exceed your maximum no matter how hard you push past it. Power registers a 700-watt surge the instant your legs produce it. On steady work the lag washes out and the two signals track each other closely. On short, sharp work the lag is the whole story, and a metric built on heart rate systematically under-counts the stress [García-Ramos et al. 2015].

This is the practical core of using Strava as a training tool rather than a journal: the data layer every cyclist already has only helps if you read each ride with the metric that fits it. The parent pillar gives the rule of thumb in one line. Below is the full per-workout-type version, because the right metric flips depending on what the session was built to do.

02 / 04

A decision table by workout type

The right metric flips with the session. Either works for steady endurance; power edges sweet-spot and threshold; power is the only honest read for anaerobic and VO2 work; and long or hot rides need a discount on Relative Effort for cardiovascular drift [García-Ramos et al. 2015, Coyle & González-Alonso 2001].

Steady zone 2 endurance: either metric is honest, and Relative Effort is genuinely useful because heart rate has hours to settle into the aerobic zone the ride lives in. Two 90-minute endurance rides at 165 and 180 watts post different Relative Efforts, and the gap reflects real internal strain [Meyer 2018]. The one caveat is duration: past about 90 minutes, cardiovascular drift lifts heart rate 5 to 10 percent at unchanged power [Coyle & González-Alonso 2001], so a long ride's Relative Effort runs high for a reason that is not extra training stress.

Sweet-spot and tempo: both work, with a slight edge to power. These efforts sit just below threshold, sustained for 8 to 20 minutes, long enough that heart rate reaches the right zone, so Relative Effort tracks them sensibly. But sweet-spot is precisely the zone where small power differences matter most to adaptation, and heart rate is too blunt to distinguish 88 percent of FTP from 94 percent. If you have a meter, read the watts [Allen et al. 2019].

Threshold intervals over 5 minutes: power, clearly, but Relative Effort is not useless. A 3-by-12-minute set holds heart rate near its ceiling long enough to capture most of the work. The problem is the recovery valleys: the classic TRIMP method that Relative Effort descends from does not separate work from recovery, and a modified version that does runs about 9 percent higher on interval sessions, with the gap widening as intensity climbs [García-Ramos et al. 2015]. Power-based TSS counts each interval at its true intensity and is not fooled by the rests.

Anaerobic and VO2 max work: Relative Effort breaks here, and the only honest answer is power. Thirty-second on, thirty-second off repeated for 8 minutes produces enormous metabolic stress and almost no time in the top heart-rate zone, because heart rate cannot climb and fall fast enough to register the spikes. The TRIMP lineage under-counts interval stress structurally, not occasionally [García-Ramos et al. 2015]. If a session has efforts under two minutes or anything above threshold, trust TSS. Long or hot rides are the mirror case: read Relative Effort with a discount, since drift inflates it on a ride your legs found easy [Coyle & González-Alonso 2001].

03 / 04

Why you cannot compare a Relative Effort number to a TSS number

Comparing the two numbers directly is meaningless. A Relative Effort of 140 and a TSS of 95 are no more comparable than 140 pounds and 95 kilograms, except there is no conversion at all [Meyer 2018, Allen et al. 2019]. The error compounds when Strava splices both into one Fitness curve.

A rider sees a Relative Effort of 140 on Saturday's group ride and a TSS of 95 on Tuesday's trainer session and concludes Saturday was harder. That comparison is meaningless. The numbers are not on the same axis, because the two metrics are scaled to different physiology with no conversion between them [Meyer 2018, Allen et al. 2019].

The error compounds in Strava's Fitness curve. Strava feeds Relative Effort into the chart when a ride has no power and a TSS-equivalent when it does, then averages both into one exponentially-weighted line [Meyer 2018]. A month of HR-only outdoor rides followed by a month of indoor power rides produces a step that no change in fitness created. Each ride is scored honestly on its own ruler; the trend is the lie, because the trend splices two rulers together — the failure mode our companion piece on mixing power and heart rate in the Strava chart walks through in detail.

This is also why chasing the bigger number is a trap. Relative Effort rewards long steady volume and under-rewards short intensity [García-Ramos et al. 2015], so a rider optimizing for the higher score drifts toward more tempo and less of the hard, brief work that drives top-end adaptation. The metric quietly nudges your training toward what it happens to measure well, which is the opposite of what a structured plan needs [Seiler 2010].

04 / 04

Pick one primary metric and hold it

Accuracy on any single ride matters less than consistency of input across the season [Allen et al. 2019]. Pick the metric you can apply to most rides and feed your fitness trend only that one. If heart rate is primary, pair it with session-RPE to cover its anaerobic blind spot [Haddad et al. 2017].

Pick the metric you can apply to most of your rides and feed your fitness trend only that one. If you have power on more than half your rides, make TSS primary and estimate it for the heart-rate-only rides rather than letting Relative Effort into the same curve [Allen et al. 2019]. If you are mostly outdoors on heart rate, make Relative Effort primary, set your max HR from a real observed peak, and accept the known blind spot on anaerobic work [Meyer 2018].

If heart rate is your primary metric, pair it with a one-to-ten effort rating after every ride. Carl Foster's session-RPE method is validated across continuous and interval work alike and costs nothing [Haddad et al. 2017], and it catches exactly the sessions Relative Effort under-counts. The hard 40-minute interval session that posts a modest Relative Effort will post a 9 on the effort scale, and that disagreement is the signal. Two independent reads beat one read you already know is blind in places.

Common questions

Quick answers

Can I convert Relative Effort to TSS or compare the two numbers?

Not interchangeably, no. TSS is power-based, scaled so an hour at threshold equals 100 [Allen et al. 2019]. Relative Effort is a heart-rate-zone score descended from Banister's TRIMP [Meyer 2018, Hellard et al. 2007]. They are scaled to different physiology with no conversion factor between them. Compare each metric only to its own past values, and never read a Relative Effort number as if it were a TSS number.

Which should I trust for VO2 max and anaerobic intervals?

Power-based TSS, every time. Anaerobic and VO2 efforts spike metabolic stress faster than heart rate can climb, so the heart-rate-zone score that Relative Effort uses misses most of the load. The classic TRIMP method it descends from averages work and recovery together and under-counts interval sessions, running about 9 percent low versus a method that separates them [García-Ramos et al. 2015]. If the session has efforts under two minutes or anything above threshold, read the watts.

Is Relative Effort accurate for easy endurance rides?

For steady aerobic work, yes, with one caveat. On a zone 2 ride heart rate has time to settle into the right zone, so Relative Effort reflects real internal strain and tracks power closely [Meyer 2018]. The caveat is duration: past about 90 minutes, cardiovascular drift lifts heart rate 5 to 10 percent at unchanged power [Coyle & González-Alonso 2001], so a long or hot ride's score runs high for reasons unrelated to training stress.

Why does my Relative Effort look higher than my TSS?

Because they are different units. A Relative Effort of 140 and a TSS of 95 are no more comparable than 140 pounds and 95 kilograms, except there is no conversion between them at all [Meyer 2018, Allen et al. 2019]. One counts weighted heartbeats, the other counts normalized watts against your FTP. Track each against its own history; the only meaningless comparison is one metric's number against the other's.

Which metric should I make primary for tracking fitness over a season?

Whichever you can apply consistently to most of your rides. Consistency of input beats accuracy on any single ride, because your fitness trend is an exponentially-weighted average that assumes every day is on the same scale [Allen et al. 2019]. If most rides have power, make TSS primary; if most are heart-rate-only outdoors, make Relative Effort primary and pair it with session-RPE on your hard days to cover its anaerobic blind spot [Haddad et al. 2017].
References

Sources cited in this guide

  1. 01
    Meyer 2018. Quantifying Effort through Heart Rate Data. Strava Engineering.
  2. 02
  3. 03
    Hellard et al. 2007. Assessing the limitations of the Banister model in monitoring training. Journal of Sports Sciences.
  4. 04
  5. 05
  6. 06
    Coyle & González-Alonso 2001. Cardiovascular drift during prolonged exercise: new perspectives. Exercise and Sport Sciences Reviews.
  7. 07
    Seiler 2010. What is best practice for training intensity and duration distribution in endurance athletes?. International Journal of Sports Physiology and Performance.
In this series

More inside Training with Strava

Start here · Foundational guide

Training with Strava: a self-coached cyclist's guide

How to use Strava as a training tool — what its metrics actually tell you, where it fails, and how to structure training around it without a coach.

Read the full guide

Other articles in this series

  1. 01

    What your Strava Fitness number means (and if yours is good)

    Strava Fitness is CTL — a 42-day weighted load average. What the number means, why it is personal, and the decisions to make from it.

  2. 02

    Apps that connect to Strava: read vs display

    How to tell which training apps actually read your Strava data and adapt versus the ones that only display your rides.

  3. 03

    Is Strava Premium worth it for a self-coached cyclist?

    What Strava Premium gives a training-focused rider, what it doesn't (no coaching), and when the free Intervals.icu chart beats paying.

  4. 04

    How to set up Strava for training: one-time configuration

    Configure Strava once for training: real FTP and max HR, honest zones, one sensor stack, and feed privacy that protects your plan.

  5. 05

    Strava segments as fitness tests: map efforts to tests

    Use Strava segments as scheduled benchmark tests: which profiles map to which test, how to schedule every 4-6 weeks, and controlling variables.

  6. 06

    What to look at on Strava after a ride: 4 metrics

    A 30-second post-ride routine: the four Strava metrics that matter after every ride, the ones to ignore, and why.

  7. 07

    Strava Fitness going down while training hard: the decay math

    Why your Strava Fitness (CTL) drops even when you train hard: the 42-day EWMA decay math, the real causes, and when a falling line is correct.

  8. 08

    Strava indoor power vs outdoor HR: Fitness chart jumps

    Mixing power-based TSS and HR-based Relative Effort splices incompatible units into your Strava Fitness chart. Why it jumps and how to fix it.

  9. 09

    Heart rate drift on long rides at same power: what it means

    Why heart rate climbs at flat power on long rides — cardiovascular drift, aerobic decoupling (Pw:HR) as a durability signal, and what to do.

  10. 10

    Strava heart rate zones wrong: the whole-dashboard cascade

    How a wrong max HR in Strava cascades into bad zones, Relative Effort, and Fitness — and how to set zones from real data.

  11. 11

    Why your Strava Relative Effort is high on easy rides

    Relative Effort can spike on a genuinely easy ride — usually a mis-set max HR, not lost fitness. What inflates it on Strava and what to do.

Free 14-day trial · No card · ~3 minutes

Try the adaptive coach yourself.

Connect Strava, tell us your goal and weekly hours, and your first training week is ready in minutes.

Free 14-day trial. No credit card required.