Garmin Training Readiness: Real Score Ranges Explained

Garmin describes Training Readiness as "a score and a short message that helps you determine how ready you are for training each day." Simple enough — except most pages explaining it publish the wrong score ranges, and the number runners actually care about is their own, the one sitting stubbornly in the red. This guide does two things: it gives you the official ranges straight from Garmin's manuals, and it tells you what to do when yours is low.

The official score ranges (most sites publish them wrong)

There are five tiers, not three or four, and Prime starts at 95 — not 80. These come from Garmin's own device manuals, where the levels, colors and descriptions are identical from model to model.

Score	Level	Color	Garmin's description
95-100	Prime	Purple	Best possible
75-94	High	Blue	Ready for challenges
50-74	Moderate	Green	Good to go
25-49	Low	Orange	Time to slow down
1-24	Poor	Red	Let your body recover

The second error worth knowing: Body Battery is not one of the inputs. Two separate Garmin sources list the six factors and Body Battery is not among them — and Garmin's own user forums have even carried a feature request asking for it to be added — not something anyone requests for a feature that already exists.

The six inputs, and which ones actually move the score

Garmin lists six:

• Sleep score — last night only.
• Recovery time — the countdown left over from recent sessions.
• HRV status — whether your 7-day average heart rate variability sits inside your personal baseline range.
• Acute load — recent training, whose effects "gradually expire over the next 10-day period."
• Sleep history — the last 3 nights.
• Stress history — your waking stress over the last 3 days.

They are not equal, and Garmin says so: "the primary drivers ... are how well you slept last night and residual recovery demands of recent activities." That is the shape of the whole thing — last night's sleep, plus what you have not recovered from yet. What Garmin has never published is a weighting. No percentages, no formula. Any site handing you a percentage split invented it.

Two time windows explain most confusing scores. Acute load does not clear overnight, so a hard weekend keeps pressing on the number for days; you can see that tail directly in your acute training load. And HRV status needs history before it means anything — Garmin's guidance is to record HRV every night for three weeks before there is a sensible baseline to compare against.

One input catches people out. Sleep history is not only about sleeping badly: an unusually long stretch awake — Garmin's example is 20 hours — drags the score down by itself, and one good night "does not fully erase" the nights before it.

Low score, but you feel fine

This is the question the score actually raises, and it has three different answers. Open the score and read the factor breakdown first — which answer applies is usually visible there.

1. A factor explains it

Acute load high, recovery time still counting down, HRV outside your baseline: the watch is telling you something you already had reason to know. The low score is arithmetic, not a verdict, and the ordinary training answer applies — take the easy day, and make it genuinely easy rather than a grey-zone slog. If you are not sure where that ceiling sits, your heart rate zones will put a number on it.

2. Low score, nothing explains it, and you feel fine

Move the session. Do not skip it, and do not force it. Your own read on your body is real data: a 2016 systematic review in the British Journal of Sports Medicine found that "subjective measures reflected acute and chronic training loads with superior sensitivity and consistency than objective measures."

But "I feel fine" is one reading on one morning, and it can lag. One runner on a popular training forum posted a readiness of 1, felt fine, trained as planned — and came down with a fever the next day, eventually moving the workout to the weekend. Garmin lands in the same place: "listen to your body, consider the data together with how you feel and adjust your plans and expectations accordingly." Pushing a hard session back a day costs you almost nothing, and a recovery planner turns that into a scheduling decision instead of a coin flip.

3. Every factor is green, or the score never moves at all

Then it is a calibration problem, not a physiology problem, and the troubleshooting section below is where to go. A score pinned at the same value for days is still data — just data about your watch.

Three situations where the score stops meaning anything

A watch you have worn for less than three weeks

HRV status is one of the six inputs, and the official guidance is to record HRV every night for three weeks before a usable baseline exists. Until then that input is missing or provisional. A brand-new watch producing strange readiness numbers in week one is not broken — it is still collecting.

You run a lot

Acute load carries a 10-day tail. Train hard most days and it never fully drains, so the score sits low permanently. The algorithm is working; the output has stopped carrying information, because a number that reads Low every single day cannot tell your heaviest week from your easiest. Garmin's answer for deliberate high-load blocks is not to ignore the score but to read which factor is driving it: acute load or recovery time driving a low score is expected, whereas sleep or stress driving it "might be reason to re-evaluate your approach."

You narrowed your sleep window

A trick that circulates in Garmin's forums: set your sleep window to seven hours instead of eight and your scores improve. It does work, and that is exactly the problem. Nothing about your recovery changed — you lowered the pass mark. The honest version is to change the sleep rather than the window, which is slower and covered in our sleep and recovery guide.

What the trial evidence says about training by HRV

The principle underneath Training Readiness — that day-to-day HRV should steer what you do that day — has direct trial support, with one large caveat. A 2019 randomized controlled trial compared HRV-guided training against a predetermined program and found the HRV-guided group improved 5 km time by 17.5 plus or minus 5.6%, against 14 plus or minus 4.7% for the fixed program, a moderate between-group effect size. The caveat: the participants were 36 untrained women, so the finding should not be stretched to trained runners. It supports the idea of steering by daily readiness. It does not validate the specific number on your wrist.

Stuck at 1, or not showing up at all

Before concluding that your body is broken, rule out the data. Roughly in the order worth checking:

1. Stop charging overnight. Sleep score, sleep history and HRV are all measured while you sleep, and that is the only window in which they can be collected. Charge in the shower instead.
2. Give a new watch three weeks. As above — the HRV baseline is not there yet.
3. Check your sleep window setting. If the watch is looking for sleep at the wrong hours, last night's sleep score comes back missing or wrong, and one of the two primary drivers has nothing to hand over. Our sleep recovery calculator is a useful sanity check on what your window should be.
4. Confirm your watch has the feature at all. Not every Garmin does, and this catches more people than it should.

On that last point: Training Readiness ships on the Forerunner 265, 955 and 965, fenix 7 and fenix 8, epix (Gen 2), Enduro 2, MARQ Gen 2, tactix 7 and Descent G2. It is not on the fenix 6, and — the one that surprises people — not on the Venu 3, although the Venu 4 has it. Garmin's own instruction is to check the product page rather than assume a recent watch qualifies, and that is still the right move: the list changes as models are added.