Why your Strava Relative Effort is high on easy rides

Why Relative Effort climbs on an easy ride

Relative Effort scores how much time you spent in each heart-rate zone, weighted so higher zones count for more [Meyer 2018]. A high number means your heart rate sat in higher zones, not that the ride was hard. The two come apart whenever your zones are wrong or your heart rate ran high for a reason unrelated to effort.

The mechanism is purely heart-rate-based. Strava takes your heart-rate stream, slices it into time-in-each-zone using your configured max HR, weights each zone — zone 4 counts for far more per minute than zone 2 — and sums the result [Meyer 2018]. The math is closer to Banister's TRIMP than to a power-based load score [Hellard et al. 2007], which means it measures internal cardiac strain, not mechanical work. A ride where your heart rate averages 145 bpm produces a higher score than one at 130 bpm even if both held the same 165 watts.

That zone-weighting is exactly why an easy ride can outscore a hard one. A 90-minute endurance ride spent entirely in what Strava thinks is zone 3 will out-score a 45-minute interval session that spent 35 of its minutes recovering in zone 1 between efforts. The total time in elevated zones is what drives the number, and a long, steady ride accumulates more of that time than a short, spiky one. The score is doing precisely what it was designed to do — the problem is upstream, in what counts as zone 3 for you.

This is the inverse of the more famous complaint, that Relative Effort under-reports short anaerobic intervals because heart rate lags behind metabolic stress. Here the score over-reports because heart rate, scored against the wrong zones, reads higher than the actual physiological demand. Same root cause, opposite direction: heart-rate-zone load is only as honest as the zone boundaries you feed it.

The max-HR setting that inflates every number

The single most common cause of an inflated Relative Effort is a max heart rate set too low — usually from the 220-age formula, which has a standard error of roughly 10 bpm and can miss an individual by 10-20 [Tanaka et al. 2001]. A max that's 15 bpm low makes your zone 2 read as zone 3, multiplying the weighted score.

The 220-age formula is convenient and statistically weak. Tanaka and colleagues analyzed 351 studies covering 18,712 subjects and found 220-age systematically underestimates max HR in older adults, proposing 208 minus 0.7 times age as a better fit — and even that improved equation carries a standard error of estimate near 10 bpm [Tanaka et al. 2001]. For any one rider, a formula-derived max can sit 10-20 bpm away from their true ceiling. Strava seeds your zones from this kind of estimate unless you've entered a measured max.

Watch what a 15-bpm error does to the zones. Suppose your true max is 190 but Strava has it at 175. Every zone boundary scales down with the max, so a steady aerobic effort that should land mid-zone-2 now reads as low zone 3. Strava weights zone 3 minutes more heavily than zone 2 minutes, so an honest two-hour endurance ride gets scored as if it carried meaningfully more strain than it did. The watts didn't change; the ruler did.

The tell is a pattern, not a single ride. If easy rides keep scoring high while your power numbers and perceived effort say easy, your max HR is the first thing to check and the cheapest thing to fix. Set it from the highest heart rate you've actually seen in a hard, well-warmed-up effort over the last few months — the peak of a 5-minute climb or the last 30 seconds of a maximal sprint — not from a formula. Correcting the max re-scores every future ride and quietly fixes the inflation at its source.

Cardiovascular drift: when a high reading is real but harmless

Even with zones set perfectly, a long or warm ride can post a high Relative Effort because heart rate drifts upward over time at constant power. Coyle and González-Alonso documented this drift at 5-10% over the first 60-90 minutes of moderate work in the heat [Coyle & González-Alonso 2001]. The score is correct; it just isn't telling you the ride got harder.

Cardiovascular drift is well-characterized physiology, not sensor error. As a steady ride goes on — especially in warm conditions — plasma volume drops, core temperature rises, and the heart compensates with a higher rate to maintain the same output, climbing 5-10% over the first hour to ninety minutes without any increase in work rate [Coyle & González-Alonso 2001]. Because Relative Effort sums time-in-zone, that late-ride drift pushes minutes from zone 2 up into zone 3, lifting the final score on a ride your legs experienced as entirely easy.

This is why a three-hour endurance ride on a hot afternoon can post a Relative Effort that rivals a structured interval session. The first hour scores honestly; the back half inflates as drift carries your heart rate upward at unchanged effort. If you have power, you can see this plainly — normalized power flat, heart rate climbing. The body adapted normally; the heart-rate-based score simply can't distinguish drift from a genuine intensity increase, and it isn't designed to.

The right reading is to treat drift-driven Relative Effort as expected on long warm rides and otherwise ignore it. It does not mean you went too hard, lost fitness, or need extra recovery. If anything, a ride long enough to drift is doing exactly the aerobic work a base block is built around. The number is real; the conclusion most riders draw from it is not.

What to do when Relative Effort disagrees with your legs

When an easy ride scores high, do not log it as hard and do not skip tomorrow's quality work off one inflated number. Trust power-based load, perceived exertion, and time-in-zone over a heart-rate score whose inputs you may have wrong. Then fix the upstream cause — almost always the max-HR setting — and commit to one primary load metric for the season.

The training decision is the whole point, and it's the sub-question the broader case for using Strava as a training tool, not a journal, keeps raising: the data layer every cyclist already has only helps if you read it correctly. The pillar's rule for anaerobic intervals — trust power-based TSS when heart rate can't keep up — has a mirror image here. On easy aerobic rides, when heart rate runs high against suspect zones, trust the things that don't depend on those zones: normalized power if you have a meter, Foster's session-RPE if you don't [Haddad et al. 2017], and whether the ride actually felt easy.

Concretely, an inflated Relative Effort on an easy ride should change nothing downstream. Don't reclassify a recovery spin as a hard day in your own log, don't let it talk you out of Tuesday's VO2 session, and don't add a rest day you don't need. One number scored against a possibly-wrong max HR is not evidence of fatigue. Power-based TSS [Allen et al. 2019], a glance at time-in-zone, and a one-to-ten effort rating are three independent checks that will agree with your legs when the heart-rate score doesn't.

Then fix the cause once. Set your max HR from a real observed peak, confirm your zones, and commit to a single load metric across the season rather than comparing a heart-rate-only outdoor ride to a power-based indoor one — those aren't the same units [Allen et al. 2019]. This is where reading the data beats logging it: AdaptCycling reads both your power and heart-rate streams and computes an internal load estimate that doesn't whipsaw when one sensor's configuration is off, so a single mis-set max HR can't quietly rewrite a week of training history.

Quick answers

Sources cited in this guide

1. 01
   Meyer 2018. Quantifying Effort through Heart Rate Data. Strava Engineering.
2. 02
   Tanaka et al. 2001. Age-predicted maximal heart rate revisited. Journal of the American College of Cardiology.
3. 03
   Coyle & González-Alonso 2001. Cardiovascular drift during prolonged exercise: new perspectives. Exercise and Sport Sciences Reviews.
4. 04
   Haddad et al. 2017. Session-RPE Method for Training Load Monitoring: Validity, Ecological Usefulness, and Influencing Factors. Frontiers in Neuroscience.
5. 05
   Hellard et al. 2007. Assessing the limitations of the Banister model in monitoring training. Journal of Sports Sciences.
6. 06
   Allen et al. 2019. Training and Racing with a Power Meter (3rd ed.). VeloPress.

More inside Training with Strava

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

   Relative Effort vs TSS: which to trust by workout

   A per-workout-type rule for when to trust Strava Relative Effort vs power-based TSS, and why they are not the same units.

   →
5. 05

   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.

   →
6. 06

   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.

   →
7. 07

   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.

   →
8. 08

   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.

   →
9. 09

   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.

   →
10. 10

    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.

    →
11. 11

    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.

    →