HRV Explained: The Daily Training Signal ACWR Misses
HRV Explained: The Daily Training Signal Your Load Metrics Miss¶
Your Garmin says 34. Your Whoop says Recovery 42%. Your body feels fine. You have a 10×1K workout scheduled in two hours. Do you run it?
Most articles about heart rate variability answer that question with a shrug and a link to buy a strap. This one gives you a decision.
HRV is the closest thing runners have to a daily readout of nervous system status. It is not magic. It is not "cellular recovery." It is a number that trends up when you are absorbing training and trends down when you are not. The question is what to do with the number on a Tuesday morning when the workout is already on the calendar.
What you will learn:
- What RMSSD actually is — and why the absolute number is meaningless without your baseline
- The gap between ACWR (week-level) and HRV (day-level) and why you need both
- A four-state decision matrix for acting on a suppressed score
- The convergent signals that tell you when to trust a low reading
- The modification menu — what to run instead, not just whether to run
- The honest limitations of the VO2max research
What Your Readiness Score Actually Measures¶
Garmin's "HRV Status." Whoop's "Recovery Score." Oura's "Readiness." Different labels, same underlying metric: RMSSD — root mean square of successive differences between heartbeats.
Here is the plain-English version. Your heart does not beat like a metronome. The gap between beat 1 and beat 2 is slightly different from the gap between beat 2 and beat 3. RMSSD measures how different those gaps are. More variation means your parasympathetic nervous system — the "rest and digest" branch — is running the show. That is what recovery looks like on a chart.
Less variation means your sympathetic system is still elevated. Training load, poor sleep, alcohol, a stressful week — the body does not distinguish the source. All of it flattens the number.
One thing to settle immediately: the absolute value does not matter. A runner sitting at RMSSD 28 is not less recovered than one at 82. Age, genetics, fitness, and measurement device all shift the number. Your personal baseline, established over four to six weeks of consistent morning tracking, is the only benchmark that means anything. Every proprietary "readiness score" is just a translation of your recent RMSSD against your own history.
Where ACWR Stops and HRV Starts¶
Acute-to-chronic workload ratio is a week-level tool. It tells you whether the load you are stacking is progressing safely against your four-week average. Useful. Necessary. But it says nothing about whether Tuesday is the right day for the 10×1K or whether you should push it to Thursday.
ACWR operates on a seven-to-28-day rolling window. HRV operates on this morning.
That is the gap. Load metrics answer: "Is this training block sustainable?" HRV answers: "Is my nervous system ready to absorb today's session?" Both questions matter. Only one of them gets asked at 6 a.m. with running shoes in your hand.
ACWR is the monthly budget. HRV is the daily spending check. A budget in good shape does not mean every individual purchase is wise.
The Decision Matrix¶
Stop reading the daily number in isolation. Read the trend against your seven-day baseline. Four states, four responses.
| HRV Trend State | What It Means | What To Do |
|---|---|---|
| At or above 7-day baseline | Full autonomic recovery | Train as planned |
| 5–10% below baseline (single day) | Mild suppression — likely noise | Check convergent signals; proceed if RHR and mood look normal |
| 5–10% below baseline (2+ consecutive days) | Pattern — sustained nervous system load | Modify session: drop volume 20–30% or reduce intensity one zone |
| >10% below baseline | Meaningful suppression | Replace quality work with easy running or rest |
Two rules make this table work. First, single-day dips are noise more often than not. Second, patterns are signal. Two consecutive days trending the same direction means something. Do not modify a workout off one bad reading. Do not ignore three in a row.
Convergent Signals: When to Trust a Suppressed Score¶
HRV alone is not a diagnosis. HRV plus confirming signals is. Check four things before cutting the session:
Sleep quality and duration. Under six hours or fragmented sleep drops HRV regardless of training status. If sleep tanked, the suppression has a name.
Resting heart rate. A 4–5 bpm elevation over your personal norm, measured at the same time and posture each morning, corroborates a real autonomic load. RHR elevated and HRV suppressed together is a stronger signal than either alone.
Whole-body fatigue. Not localized soreness — legs always feel like legs after a long run. Whole-body drag, low mood, sluggishness in the first five minutes of warmup. That is the nervous system talking, not the quads.
Training phase position. Week three of a hard overreach block is a different context from a random Tuesday off a rest week. Suppression in a build week is expected. Suppression after a recovery week is a warning.
When two or more of these line up with a low HRV reading, act on the number. When none of them do, treat the HRV as noise and run the session.
NavRun's injury alert system watches your load automatically from Strava and flags the training phases where a suppressed HRV day is most likely to matter. Connect your account to see your load context alongside your daily metrics.
When to Ignore a Suppressed Score¶
HRV picks up things that have nothing to do with training readiness. Ignore the reading when you can name the cause:
Alcohol. Even one drink suppresses HRV for 24–36 hours. Two to three drinks can flatten it for up to 72 hours. This is not moralizing — it is arithmetic. If you had wine with dinner, this morning's number is measuring the wine, not your training capacity.
Late meal timing. Eating within two hours of bed elevates overnight sympathetic activity and drops RMSSD. A large dinner at 9 p.m. contaminates the next morning's reading.
Illness onset. Rare, but real. A sharp HRV drop with no other explanation, followed by symptoms 24 hours later, is one of the few cases where HRV works as an early warning. The acute drop is larger than a training dip and outside your normal range — not just below baseline.
Heat and dehydration from the previous day. A summer long run in 90°F that was not properly rehydrated will echo in the next morning's HRV. Drink water. Sleep. The number will recover.
If the suppression has a clear cause and your other signals look normal, run the session. Context always overrides a number without context.
Chronic vs. Acute HRV Patterns¶
This is where HRV becomes genuinely useful — not as a daily gating signal, but as a multi-week pattern.
An acute dip after a hard session is expected and benign. Expect HRV to drop one to three days after quality workouts, race efforts, and threshold blocks. It should recover to baseline within 48–72 hours. If it does, the training stimulus was absorbed correctly.
Chronic suppression — HRV sitting below baseline for seven to 14 days without recovery — is the alarm. This is the same distinction as ACWR: single-week spikes are recoverable; sustained overreaching is not. Persistent HRV depression often precedes overtraining syndrome by two to three weeks, appearing before the performance drops, mood changes, or injury signals that trigger attention.
A 2026 perspective piece in Frontiers in Sports and Active Living by Bourdillon and Millet — "Taking heart rate variability to the next level in sports: towards a multi-signal integration" — argues that single-metric HRV read in isolation is insufficient for training decisions. Trend plus context is the minimum requirement. That matches what runners find in practice. The alarm is not "one low Tuesday." The alarm is "two weeks of low Tuesdays with no recovery bounce."
The Modification Menu¶
When the number and the context agree that something needs to change, the question is not whether to run — it is what to run instead. Most runners freeze here. They see a low HRV and either grind through the planned session or cancel the day entirely. Both choices are usually wrong.
| Original Session | Level 1 Modification (Mild Suppression) | Level 2 Modification (Meaningful Suppression) |
|---|---|---|
| 10×1K at 5K pace | 6×1K at 10K pace | Easy 45-minute run |
| 20-mile long run | 15-mile at easy pace | 10–12 miles easy |
| Tempo 6 miles | 4 miles at marathon pace | Easy 30–40 minutes |
| Track workout | Drop last 2 reps, one zone easier | Skip; cross-train or rest |
| Back-to-back long runs | Day 1 as planned; shorten Day 2 | Full rest Day 2 |
The goal is to protect the training block, not abandon sessions. A modified workout keeps the aerobic pattern intact and keeps the week's training stress in range. A skipped day costs the stimulus entirely. When in doubt, drop intensity before volume — an easy run at suppressed HRV is almost never wrong.
The Science, With Honest Caveats¶
The most-cited evidence for HRV-guided training is PMC8001752 — a 2021 NIH-indexed study that assigned 16 adolescent middle- and long-distance runners to either a fixed training plan or an HRV-guided plan during a two-week altitude camp at roughly 1,900 meters. The HRV group modified daily sessions based on morning readings.
Results:
- HRV-guided group: +4.27% VO2max (+2.8 mL·kg⁻¹·min⁻¹, p=0.002)
- Fixed-plan control: +1.26% (+0.8 mL·kg⁻¹·min⁻¹)
That is a meaningful gap. It is also a study with real limitations. Altitude amplifies every autonomic signal — the HRV responses at 1,900 meters are larger and more reliable than at sea level. The subjects were adolescents, who adapt more rapidly than trained adult runners. N=16 is small. Two weeks is a short window.
The honest summary: HRV-guided training has a coherent mechanism and encouraging evidence. It is not a guaranteed 4% VO2max bonus. It is a systematic way to match training intensity to nervous system readiness, which should, over time, produce better absorption of training and fewer forced rest days from cumulative overload. That is the realistic return.
HRV Plus NavRun¶
ACWR, training monotony, and ramp rate are week-level signals NavRun surfaces automatically from your Strava data. When load is drifting into high-risk territory, the injury alert fires before you feel it. That is the week-level layer.
HRV is the day-level layer sitting on top. When NavRun's deviation detection flags a session that came in slower than planned, a suppressed HRV reading from that morning usually explains why — the stimulus was there, but the nervous system was not ready to absorb it cleanly. When AI feedback notes that recent tempo runs are trending harder at the same pace, the HRV trend often shows the same pattern from a different angle.
Neither layer replaces the other. Load context tells you the training block is sound. Daily HRV tells you the session is timed correctly. Connect Strava, see both layers, and stop guessing about which bad Tuesday actually matters.
FAQ¶
Q: What's a normal HRV for a runner?¶
There is no universal normal. RMSSD varies with age, genetics, fitness, measurement device, and time of day. A 25-year-old might baseline around 90 ms; a 55-year-old might baseline at 35 ms — and both can be fully recovered for the same workout intensity. Track your own reading at the same time each morning for four to six weeks. That personal baseline is the only comparison that means anything.
Q: Garmin, Whoop, and Oura show different numbers. Which should I use?¶
Pick one platform and stay with it. Each device uses proprietary scaling — Whoop reports a 0–100 recovery score, Garmin shows milliseconds, Oura blends multiple signals into a readiness index. The underlying signal is similar across platforms, but the outputs are not comparable. Switching platforms mid-training block resets your baseline and wastes weeks of tracking.
Q: Should I cancel a race if my HRV is suppressed race morning?¶
Almost never. Pre-race adrenaline and anticipation reliably suppress HRV for most runners — sometimes dramatically. A low reading on race morning often reflects nervous activation, not fatigue. If the two weeks leading into the race looked normal and the taper was executed correctly, run the race. Race-morning HRV is the wrong data point to make that call on.
Q: How long does alcohol suppress HRV?¶
Moderate drinking — one to two drinks — suppresses HRV for 24–36 hours. Heavier consumption can flatten it for up to 72 hours. This is one of the largest and most consistent effects in the HRV literature. If you drank last night, this morning's readiness score is not about your training status.
Q: Is HRV more useful than perceived exertion?¶
They are complementary, not competing. HRV catches what you would rationalize away — subtle autonomic strain accumulating underneath sessions you convince yourself feel fine. Perceived exertion catches what HRV misses — mechanical fatigue, gut issues, weather stress, pace-specific heaviness. Use both. When they agree, act. When they disagree, ask which one has a better explanation for today.
Q: Should I track HRV during a taper?¶
Yes. HRV typically rises during a correct taper as cumulative fatigue dissipates and the parasympathetic system rebounds. A trend that lifts steadily in the two to three weeks before a goal race is a strong positive sign. A trend that stays flat or falls during a supposed taper suggests the training block ran too long and the taper needs to be extended or deepened.
Back to the Workout¶
Your Garmin says 34. Your Whoop says 42%. RHR is on trend. You slept seven and a half hours. No alcohol the night before. No pattern of suppression over the past week. You are in week two of a build, not week five of an overreach.
You run the 10×1K.
That is the point. Not to chase the number up. Not to panic when it dips. To know — specifically, on this Tuesday morning, with this context — whether the signal is telling you something real or telling you nothing.
The decision framework is the tool. The number is just the starting point.