Why is my recovery score low? A troubleshooting decision tree

This is a troubleshooting guide, not a product explainer — for how the recovery score itself is built, see that page. Here we're working backward from "my score is low" to "here's why, and here's what to do."

Step 1: is this one bad day, or a pattern?

Before anything else, pull up your last 7–14 days of scores. This single check determines which half of this guide applies to you.

If you're not sure what your "usual range" is, look at your 30-day average rather than any single past score — nightly recovery is noisy enough that the 30-day view is the only fair comparison.

If it's one bad day: five usual suspects

Work through these in order — the first two explain the large majority of single-day dips.

1. Alcohol the night before. Even one or two drinks measurably suppresses overnight HRV and elevates resting heart rate; it's the single most common cause of a "why is my recovery red after a normal night" surprise. Effect is largest the same night, mostly gone by the second night after.
2. A late or heavy meal. Digestion running late into the night keeps your heart rate elevated when it should be dropping, which shows up directly in tonight's recovery inputs.
3. Yesterday's training load. A hard session suppressing tonight's recovery is the system working as intended — recovery scores are partly a strain-response measurement, not a bug.
4. Heat, travel, or a disrupted room. A hot bedroom, a new bed, jet lag, or unfamiliar noise all measurably lower overnight HRV independent of anything else you did right.
5. Stress from the day. Psychological load registers in your autonomic nervous system the same way physical load does — a stressful evening before bed can suppress recovery even with a full night's sleep hours logged.

If one of these matches and it's genuinely one day, no action is needed beyond noting it — a single low score with a known cause is data, not a diagnosis. Train at a moderate intensity, or ease off slightly, and expect it to normalize within a night or two.

If it's 3+ days in a row: a step-by-step protocol

A multi-day slide needs a different kind of check than a single bad day. Work through these steps in order:

1. Check your training log for the last 10–14 days. Has intensity or volume climbed without an easy day in between? Stacking hard sessions on top of unresolved fatigue is the most common cause of a multi-day slide, and it's the first thing to rule out because it's the easiest to fix — insert 2–3 lower-intensity days and watch whether recovery rebounds within a week.
2. Check life load outside of training. New job stress, poor sleep from a life event, jet lag from travel, or a stretch of late nights all suppress recovery for as long as they're active — the score isn't wrong, it's accurately reporting an input you may not be tracking as "load."
3. Check whether HRV and resting heart rate are moving together. If HRV is trending down and resting heart rate is trending up over the same days, treat it as a stronger signal than either alone — this combination is the classic early pattern before a cold or flu shows up, sometimes 24–48 hours before you feel anything.
4. Rule out the obvious lifestyle explanations before assuming illness. Dehydration, a run of poor-sleep nights, or a period of heavier drinking than usual can produce the same multi-day pattern as illness. If you can identify and remove one of these, give it 3–5 days before re-checking.
5. If none of the above fits, treat it as a signal worth respecting. Back off training intensity, prioritize sleep, and watch for symptoms over the next few days. Bodies often show physiological strain in HRV and resting heart rate before symptoms are noticeable.

The inputs behind the number

If you want to know which lever moved, it helps to know what's actually feeding the score:

• HRV — usually the most heavily weighted input; a drop below your baseline is the strongest single flag.
• Resting heart rate — moves inversely to HRV in most stress scenarios; rising RHR alongside falling HRV is more informative than either alone.
• Sleep — both duration relative to what your body needed and sleep quality (time in deep/REM, disruptions) factor in.
• Respiratory rate (on devices that track it) — usually stable night to night; a sustained shift is one of the earlier illness tells, often showing up before you notice any symptoms.

None of these numbers are diagnostic on their own — they're a readout of physiological strain, and strain has dozens of ordinary causes. The pattern across days is what carries the information, not any single night.

When it's a medical signal, not a lifestyle one

Most low recovery scores resolve on their own once the obvious cause (alcohol, training load, a stressful week) passes. Treat it as worth a doctor's visit, not just a rest day, if you notice:

• Resting heart rate staying elevated (10+ bpm above your normal) for a week or more with no clear cause
• Low recovery accompanied by fever, chest pain, unusual shortness of breath, or persistent unexplained fatigue
• A recovery slide that doesn't respond at all to a week of good sleep, no alcohol, and reduced training load
• Any recovery pattern change alongside other new symptoms you'd otherwise dismiss

A wearable-derived score is a screening signal, not a diagnosis — it's genuinely useful for catching something early, but it can't tell you what's happening, only that something is.

How to respond without overreacting

The practical response scales with the pattern, not the number on any single day:

• One low day, known cause: train as planned or slightly easier; no other change needed.
• One low day, no obvious cause: treat it as a mild yellow flag — go easier today, watch tomorrow.
• 3+ low days, training-explained: insert real rest days, not just "easier" ones, and don't add new hard sessions until the trend turns.
• 3+ low days, no explanation: prioritize sleep and hydration, cut alcohol, and watch for symptoms over the next few days before deciding it's nothing.

This is exactly the kind of pattern-over-single-number judgment that's hard to do by eye across four separate metrics — it's why Vita's AI coach is built to read your HRV, resting heart rate, and sleep trends together and flag when they're moving in a way worth a second look, rather than leaving you to eyeball four separate charts. And because Vita computes a recovery-style score from Apple Watch HRV and resting heart rate alone, you can run this same troubleshooting logic even without a WHOOP band.