You did not train yesterday. You slept about seven hours. Nothing unusual happened at work. But your wearable says your stress is elevated, or your recovery score is poor, or your Body Battery is drained before noon. The sensor is not lying. It is also not telling you the whole story.
Garmin, Fitbit, Samsung Galaxy Watch, Whoop, and Oura all surface some version of this number. Each brand calculates it differently. All of them are reading the same underlying physiological signal and dressing it in a different label.
The question that matters is not what the score is called. It is what the score can and cannot tell you, and why the same reading from one morning to the next can mean very different things.
The signal behind every stress score
Every wearable stress or recovery score is built on one core measurement: how your autonomic nervous system is balanced at any given moment. When the parasympathetic branch is dominant — the branch associated with rest, digestion, and recovery — heart rate variability (HRV) tends to be higher and resting heart rate tends to be lower. When the sympathetic branch is engaged — the branch that drives physical effort, alertness, and acute demand — HRV tends to fall and resting heart rate tends to rise.
Every wearable stress or recovery number, regardless of what it is called on the screen, is a reading of that balance expressed as a score. The HRV explainer covers what HRV actually is, how it is measured, and what affects baseline readings. This article focuses on the harder question: once you have a low score, what does it mean?
Why the same score can mean different things
A wearable stress score cannot solve this problem on its own: the sympathetic nervous system responds to almost any form of demand with a broadly similar physiological signature.
A hard interval session, a tense morning of back-to-back calls, three glasses of wine the night before, a low-grade infection you have not yet noticed, and a week of disrupted sleep can all produce similar-looking data: depressed HRV, elevated resting heart rate, and a wearable that flags elevated stress or poor recovery. The sensor is telling the truth. It just cannot tell you which story the truth belongs to.
This ambiguity is not a failure of the technology. It reflects how the autonomic nervous system actually works. Context is not optional. Without it, the physiological signal is ambiguous by design.
None of the patterns described below are clinical guidance. They describe what wearable data tends to look like in everyday contexts. If a pattern persists without explanation, or concerns you, speak with a healthcare professional.
A practical interpretation matrix
The same combination of low HRV and elevated resting heart rate can point in very different directions, depending on context.
After a hard training session
HRV drops and resting heart rate rises as a direct consequence of muscular load, hormonal response, and inflammation from the session. Within normal limits, this is expected and healthy. The nervous system is appropriately engaged in recovery. If HRV returns toward your personal baseline within 24 to 48 hours, the pattern is consistent with normal adaptation. If it stays depressed for three or more days after a session that did not feel unusual, that is worth noticing. It may indicate accumulated training load.
What to look for: Return to baseline within 48 hours. A slow return after training may indicate load is outpacing recovery.
After alcohol
Alcohol is one of the more reliable HRV suppressors. Even moderate consumption the night before can produce readings that look, on paper, like significant physiological stress. The effect tends to peak during sleep and resolves within 24 hours in most people. The suppression is acute and self-limiting. It does not indicate a problem in the way a sustained pattern would.
What to look for: Single-night drops that resolve completely within 24 hours, consistent with alcohol's short-term autonomic effect.
During illness
Immune activation is metabolically expensive and autonomically demanding. A developing infection may show up in HRV data one or two days before symptoms are obvious. This is not a reliable early-warning system, and it is not a diagnostic signal. It is simply the body running a high-demand process before you notice it consciously. During active illness, both HRV and resting heart rate often worsen significantly.
What to look for: A sustained, unexplained dip in HRV combined with a rising resting heart rate, without a clear training or lifestyle cause. Many people choose not to train hard into this pattern until the trend turns.
During chronic work or life stress
This is the pattern that warrants the most attention, and also the most care in interpretation. Sustained psychological or situational stress activates the sympathetic nervous system in ways that accumulate over days and weeks. Unlike post-training recovery or an alcohol effect, this pattern does not resolve quickly. HRV may run persistently below baseline. Resting heart rate may sit a few beats above your norm for a week or more. Sleep quality often deteriorates, which compounds both signals. See the sleep-score article for how disrupted sleep shows up in wearable data.
The important distinction: this pattern needs a week-level view to be meaningful. A single low reading means almost nothing. Five consecutive below-baseline days, without an obvious physical explanation, is a different picture worth reflecting on.
What to look for: Sustained, multi-day patterns without a clear physical cause. This is the scenario where logging context, what has been happening in your life, transforms ambiguous data into something you can actually act on.
Physiological arousal is not the same as psychological stress
Physiological arousal and psychological stress are not the same thing, and your wearable cannot separate them.
Running a 5K produces a profound stress response in the body. Cortisol rises, heart rate climbs, HRV drops. Nobody would call that harmful. The same nervous-system signatures appear during a tense meeting, after a poor night of sleep, during an infection, or in the hours after a heavy meal. The body's stress response is general-purpose. It responds to demands of all kinds, physical, thermal, infectious, emotional, with a broadly similar cascade.
Your wearable sees a nervous system under demand. That is all it sees. Acute stress responses are, in most cases, entirely normal. The body is designed to mount them, recover from them, and return to baseline. What is worth noticing is when that recovery consistently does not happen.
A week of data tells you more than any single reading
A single low score means very little without the days around it. What is meaningful is direction and duration.
Baseline is personal. HRV numbers vary enormously between individuals. A reading of 45 ms might be strong for one person and low for another. What matters is how your readings behave relative to your own established baseline, not against population averages. Most wearables build that baseline over several weeks of continuous wear, which is why early data tends to be less informative.
Single readings are noise. Week-long patterns are signal. When HRV runs below your baseline and resting heart rate runs above it for five consecutive days, especially without a planned training block to explain it, that pattern is worth paying attention to. Not as a verdict. As a prompt for reflection.
Not all stress responses are problems. The body's capacity to mount and recover from stress responses is part of what keeps it resilient. What tends to be problematic is chronic load without recovery, and that distinction only becomes visible across time.
What different wearables are actually showing you
Garmin's Body Battery and Stress Score draw on HRV measured throughout the day using optical heart-rate sensors. Whoop builds its Recovery score primarily from overnight HRV, respiratory rate, and resting heart rate. Oura uses similar overnight measurements with ring-based sensors. Fitbit and Samsung Galaxy Watch surface stress-adjacent metrics using continuous optical heart-rate tracking.
None of these approaches measures cortisol, psychological state, or emotional experience directly. They all read variations in the autonomic nervous system and translate that signal into a score. The labels (stress, recovery, readiness) are interpretive layers added by the algorithm. The underlying measurement is the same.
Apple Watch records HRV passively during breathing exercises, during sleep in recent watchOS versions, and in the background, and surfaces the data in the Health app. As of this writing, Apple Watch does not offer a dedicated native stress score comparable to Garmin's or Whoop's. HRV and resting heart rate appear as raw metrics rather than a synthesized stress or recovery index. Third-party apps can and do build stress scores from HealthKit data. If your iPhone is showing you a stress score, it is most likely coming from a third-party app or a connected device, not from Apple Watch directly.
In all cases, the medical clearance these devices carry is as wellness tools, not clinical diagnostic devices. The signals they surface are correlational and population-derived. They are useful for building self-awareness over time. They are not diagnostic outputs. A concerning pattern in your data is a reason to speak with a healthcare provider, not a diagnosis in itself.
What to do when the score looks wrong
When a recovery or stress score surprises you, either low without an obvious cause or persistently low across a week, the most useful first step is to ask what context you have not yet recorded.
Did you sleep worse than usual? Did you drink alcohol in the last 24 to 48 hours? Are you in a sustained high-demand period at work or at home? Have you increased training load recently? Are you starting to feel off in a way you have not fully acknowledged?
The score is not wrong. It is incomplete without answers to those questions.
If you cannot find a clear explanation and the pattern persists, that is the kind of signal worth discussing with a healthcare professional who can assess the full picture.
Logging context is what makes the data useful
Wearable data describes the body's state. It does not explain it.
Consider two people with identical HRV traces over a week: depressed on Monday, recovering through Thursday, dropping again over the weekend. For one person, that weekend dip followed two glasses of wine and a late night. For the other, it followed a long, anxious stretch of work they could not switch off from. The physiological signatures look nearly identical. The meaning, and what if anything is worth doing about it, is completely different.
Adding brief daily context to your health data — sleep quality, perceived stress, significant events, alcohol, illness, training load — turns a graph of numbers into something interpretable. Over weeks and months, you start to see your own patterns: that poor sleep reliably precedes a three-day HRV dip for you, or that a demanding travel week shows up in your metrics four days later rather than on the day itself.
That is what Vitanzo is designed to help you develop. The app pulls your HealthKit data (HRV, resting heart rate, sleep stages, activity) and pairs it with the daily context you log yourself. When a low recovery signal appears, you have the surrounding data to interpret it: what you logged, what the trend looked like before, whether this is a familiar pattern or something new. No verdicts. No alarms. Just your data, in context, so the pattern becomes readable.
If you notice persistent changes in your stress or recovery indicators that you cannot account for, or that concern you, speak with a healthcare professional. Wearable data is a starting point for self-observation, not a substitute for clinical assessment.