← All articles
Recovery

Your Watch Says Recovery Is Low. Should You Train?

The honest answer is almost always yes, but differently. A decision tree for turning a bad recovery score into a modified session rather than a skipped day — and the three situations where you genuinely should rest.

OnlyGains Editorial··5 min read
The short version
  • A low score is a reason to change the session, not to delete the day.
  • A dip the morning after a hard session is the system working, not a warning.
  • Rest fully for only three reasons: illness, pain, or several consecutive days below baseline.
  • Modify by cutting intensity first and volume second — keep the movement.
  • If the warm-up feels fine after ten minutes, override the score and train.

You wake up, reach for your phone, and the app has already decided how your day is going. Recovery: 31%. Red.

And now a decision that should take two seconds takes twenty minutes, because you have been handed a number with no instructions attached.

Here is the instruction set.

First: what the score is not

A recovery score is not a verdict on whether you are allowed to train. It is a summary of how much total load your body is currently carrying — from training, yes, but equally from alcohol, a late meal, a short night, a hot room, a stressful week, an oncoming cold, or a flight.

It cannot tell those apart. It reports the sum.

This matters because the correct response to "I am fatigued from Tuesday's intervals" and "I slept badly because my kid was up at 3am" are completely different, and your watch shows you the same red number for both.

You have context the device does not. Use it.

Second: expect the dip after hard work

This is the most common misreading, and it quietly costs people their training.

A genuinely hard session is supposed to suppress your recovery metrics the following night. Your heart rate variability drops, your resting heart rate rises, and the score goes red. That is the physiological signature of a training stimulus. If a hard session never moved those numbers, it was not a hard session.

So the morning after intervals or a heavy lower-body day, a red score carries almost no information beyond "you trained yesterday, and it counted."

Treating that as a reason to back off creates a loop with an obvious endpoint: train hard → score drops → take it easy → score recovers → train hard → score drops. You end up alternating between hard days and unplanned rest days, never accumulating a training block, with a device that congratulates you for it.

The decision tree

Work down the list. Stop at the first row that matches.

1. Do you have a fever, a sore throat, swollen glands, or a chest infection?Rest. No score, session or streak is worth this. Return when symptoms are above the neck and improving.

2. Do you have sharp, localised, or worsening pain — as opposed to general soreness?Rest that area, and get it looked at if it persists beyond a few days. A recovery score has nothing to say about a tendon.

3. Have you been below your baseline for five or more consecutive days, with training unchanged?Take a deload week. Cut volume by roughly a third and keep some intensity. This is genuine under-recovery, and it is the one case where the wearable is telling you something you might otherwise have missed.

4. Did you do something hard yesterday?Train as planned. This dip is expected. Do the warm-up before deciding anything.

5. Did you drink, eat late, sleep badly, or have a brutal day at work?Train, but modify. The fatigue is real, but it is not training fatigue and it will clear faster.

6. None of the above, score just low?Warm up for ten minutes, then decide. This is the single most reliable diagnostic anyone has, and it costs ten minutes.

The ten-minute rule

Wearable data is a prediction. How you actually feel once you are moving is a measurement.

Do the warm-up. Ten minutes of easy movement, then the first working set or the first kilometre. Then ask honestly:

  • It feels normal or good. Train as planned. Whatever the score picked up on has not translated into anything that matters today. This happens constantly.
  • It feels heavy but manageable. Modify — see below.
  • It feels genuinely wrong. Warm-up hurts, coordination is off, heart rate is 20 beats high at easy pace. Go home. This is rare, and when it happens you will know.

Most red-score days resolve at the first option. The score was reading your dinner.

How to modify without wasting the day

When you do need to scale back, the order matters. Cut intensity first, volume second, and movement never.

Planned sessionModified version
IntervalsSame duration, all at easy aerobic pace
Threshold runEasy run, 20% shorter
Heavy 5×5Same lifts, 3×5 at 75% of the planned load
Long runTwo-thirds the distance, easy
Full-body liftTop sets only, drop the accessories

Notice that nothing is deleted. You keep the movement pattern, the blood flow, the habit and the day. You remove the part that requires you to be fresh.

This matters more than it sounds. The cost of a skipped day is rarely the lost training — it is that skipping gets easier every time you do it.

The case for handing off the decision

The awkward truth is that this decision is hardest to make well at exactly the moment you have to make it: half-awake, before coffee, with a number in front of you and a session you were already slightly dreading.

Which is why readiness is more useful as an input to a plan than as a notification. OnlyGains takes the readiness signal from Apple Health, WHOOP, Oura or Fitbit and reshapes the day's session against it — so what you open is a modified workout rather than a colour and a decision.

The summary

Low recovery scores mean train differently far more often than they mean do not train.

Rest completely for illness, for pain, and for a sustained downward trend. For everything else — warm up, see how it feels, and scale the intensity rather than cancelling the day.

Your watch is a useful instrument with no idea what you did last night. You do.

Questions people ask

Short answers to the things this article gets asked most.

Should I train when my recovery score is red?

Usually yes, differently. Rest completely for illness, for sharp or localised pain, and for a sustained five-day downward trend with training unchanged. For everything else, warm up for ten minutes and then decide — most red-score days resolve into a normal session, because the score was reading your dinner rather than your training.

How accurate are recovery scores?

They accurately summarise total load, but they cannot tell you its source. Training fatigue, alcohol, a late meal, a short night, a hot room, a stressful week, an oncoming cold and a flight all produce the same red number. The device reports the sum; you have the context it does not.

What should you do on a low recovery day?

Cut intensity first, volume second, and movement never. Intervals become the same duration at easy aerobic pace; a threshold run becomes an easy run 20% shorter; a heavy 5×5 becomes 3×5 at 75%; a long run becomes two-thirds the distance. Nothing is deleted — you keep the movement pattern and the habit and remove only the part that requires you to be fresh.

Does a low recovery score mean you are overtrained?

Rarely. A genuinely hard session is supposed to suppress your recovery metrics the following night — that dip is the physiological signature of a training stimulus, and a hard session that never moved the numbers was not hard. Sustained suppression across five or more consecutive days with training unchanged is the pattern that actually indicates under-recovery.

Can you improve your recovery score in one day?

Partly, since much of what these scores capture is same-day input rather than accumulated training load — sleep duration, alcohol, late meals, room temperature and stress all move the number overnight. But chasing the score is the wrong goal. Reacting to every red day creates a loop of hard day, red score, unplanned rest day, where you never accumulate a training block.

recovery scoreWHOOPreadinesstraining decisionsautoregulationwearables

Keep reading