Heart rate variability has gone from a research metric to a number on everyone's wrist. Wearables give it a score every morning, and a lot of people are making training decisions around it. Some of that is useful. A lot of it is over-interpretation. Here's how we think about HRV in the clinic, and how we'd suggest you use it.
What HRV actually measures
HRV is the beat-to-beat variation in the time between heartbeats. A resting heart rate of 60 doesn't mean one beat every second. It means intervals that fluctuate, maybe 920 ms, then 1,060, then 980. That variation is the output of the autonomic nervous system continuously adjusting the sinoatrial node: vagal (parasympathetic) input slows the heart quickly, while sympathetic input acts more slowly.
Most consumer devices report one of two things:
RMSSD: the root mean square of successive differences between intervals. It's weighted toward fast, vagally mediated changes, which is why it's the most common metric for short resting measurements.
SDNN: the standard deviation of all intervals. It reflects overall variability, including slower influences like circadian rhythm and respiration.
These aren't interchangeable, and absolute values vary a lot between people, devices and algorithms. A higher number is not automatically better, and your number is not comparable to your training partner's.
Why it moves
HRV is sensitive to a long list of inputs, and that's both its appeal and its problem. Training load, sleep, alcohol, illness, psychological stress, travel, caffeine, hydration, time of day, body position and breathing pattern all shift it. A low reading tells you something was different. It doesn't tell you what.
On the training side, the general pattern is that heavy loading or accumulated fatigue tends to suppress HRV and a good recovery period tends to restore or raise it. But the relationship is individual and noisy, and the day-to-day swings are often larger than the training signal you're hoping to detect.
Where it's useful
Trends, not single readings. The most defensible use is a rolling baseline, typically a 7-day average compared against your longer-term range, with attention to the day-to-day coefficient of variation. A single low morning is rarely actionable. A sustained downward drift alongside rising soreness, worse sleep and declining performance is more informative than any one of them alone.
A flag, not a verdict. HRV works best as one input that prompts a question: how am I sleeping, what changed in my training, am I getting sick, what's going on outside the gym? It can support a decision to back off a session, but it shouldn't be the only reason.
Consistent measurement conditions. If you're going to track it, standardize it. Same time of day, same position, same device, ideally on waking and before caffeine. Overnight averages from a wearable are convenient and reasonably consistent, but they're still a proxy, and wrist-based optical measurement is less accurate than a chest strap with ECG-grade R-R detection, particularly with movement.
Where it falls short
It doesn't diagnose. HRV can't tell you whether a tissue is ready to be loaded, whether a tendon is irritable, or whether you're ready to return to sport. It says nothing about local tissue capacity. A post-surgical knee or a reactive tendon can have perfectly normal HRV and still not tolerate a given load, and the reverse is also true.
Evidence for guiding training is mixed. Several studies suggest that HRV-guided programming can produce comparable or modestly better outcomes than fixed programming in some populations, but effects are small, protocols differ, and results aren't consistent across athletes. It's a reasonable tool to experiment with, not an established standard.
It can create its own problem. Some people start to feel the number before they feel their body. A poor score at 6 a.m. becomes an expectation of a bad day, which can influence perceived effort and sleep. If checking your score increases anxiety or leads you to cancel sessions you'd otherwise have handled fine, it's costing more than it's giving.
Scores are proprietary. "Readiness," "recovery" and "body battery" are composites built from HRV plus other inputs using algorithms you can't inspect. They may be useful, but they're not the same thing as measured HRV.
Pain, sensitization and the nervous system
Because HRV reflects autonomic balance, it's tempting to link it to persistent pain and central sensitization. Some research does show lower vagally mediated HRV in people with chronic pain conditions, but the findings are correlational and heterogeneous. HRV is not a measure of sensitization, and a low number is not evidence that someone's nervous system is "stuck" in a threat state. What we can say is that sleep, stress load and activity levels influence both HRV and pain experience, which is a good reason to address those regardless of what the score says.
How we'd use it
If you already track HRV and find it helpful:
Establish a baseline over at least two to four weeks before drawing conclusions.
Look at the trend and your normal range, not the daily number.
Pair it with how you feel, sleep quality, resting heart rate and training performance.
Use it to ask better questions, not to override how you're actually moving and recovering.
If it's making you more anxious or more rigid, stop looking at it.
If you don't track it, you're not missing a critical piece. Sleep consistency, progressive loading, adequate fueling and honest attention to how you feel will do most of the work.
The bottom line
HRV is a window into how your body is responding to the total load of your life, not just your training. That makes it a useful, imperfect context tool. It can't replace objective testing, a clinical exam, or good coaching, and it should never be the thing that tells you whether you're ready to load a healing tissue or return to sport.
If you're dealing with an injury, a plateau, or a return-to-sport timeline and want help sorting out what the data actually means, that's what we do at MVMT Evanston. Get in touch and we'll take a look.
