Every morning your Garmin shows you a number between 1 and 100 and a one-word verdict: Prime, High, Moderate, Low, Poor. It feels authoritative. But most runners glance at it, register “good” or “bad,” and never learn what actually went into it — or what to do when it disagrees with how they feel. This is the full breakdown: what the score is, the six factors behind it, what each band means, how to fix a low one, and the one thing it structurally can’t tell you.
Garmin introduced Training Readiness in 2022 on the Forerunner 955 and has since rolled it out across most higher-end watches. It’s a once-daily score, calculated overnight and shown in your Morning Report, designed to answer one question: is today a good day to train hard, or should you back off?
The score, at a glance
73–100 — Prime / High: well recovered, ready for a demanding session.
34–72 — Moderate: train, but consider holding back the intensity.
1–33 — Low / Poor: accumulated fatigue or poor recovery. Hard training here adds fatigue without producing adaptation.
Garmin’s own 2024 user data put the average score at 60 — squarely in the Moderate band. Most people, most days, are not Prime.
The six factors behind the number
Training Readiness isn’t one measurement — it’s a composite of six, each given its own sub-score, then weighted and normalised to the 0–100 scale. Here’s what feeds in.
| Factor | What it captures | Weighting |
|---|---|---|
| Sleep score | Last night’s duration vs. your sleep need, deep/REM quality, and wake-time consistency. | Heaviest |
| HRV status | Your autonomic nervous system balance against your personal baseline. | High |
| Recovery time | Hours remaining until your body is recovered from recent workouts (from EPOC + fitness). | High |
| Acute load | Your last 7 days of training relative to your 4-week chronic load. | Medium |
| Stress history | Daytime stress trend from HRV over recent days. | Medium |
| Body Battery | How well your energy recharged overnight. | Lower |
Two things matter about this list. First, sleep is weighted most heavily, and the algorithm prioritises acute factors — last night’s sleep, current recovery — over longer-term trends. A single bad night can tank an otherwise strong score. Second, and this is the part Garmin doesn’t advertise: the exact weighting of each factor is undisclosed. You can see which factors are red, orange, or green, but not how much each one moved the final number.
The score tells you what — a number, a colour. It does not tell you why. When it sits in amber after a rough night, you genuinely cannot tell how much is the sleep, how much is yesterday’s session, and how much is the week of work stress.
What each band actually means for your day
Prime (73–100)
Your body is recovered and primed. This is the green light for intervals, a hard tempo, a long run with quality, or a race-pace session. If you have a hard workout on the plan, today is the day to do it. Prime days are also the ones to protect — don’t waste them on a junk-mileage easy run if a key session is coming up.
Moderate (34–72)
The largest and most misread band. Moderate doesn’t mean “don’t train” — it means train with awareness. An easy or steady run is completely fine. A hard session is possible but you should check the factor breakdown first: if the only thing dragging you down is one short night and HRV is still balanced, push on. If recovery time and acute load are both amber, dial the intensity back.
Low / Poor (1–33)
Accumulated fatigue, poor recovery, or both. Hard training in this state compounds fatigue without producing the adaptation you’re chasing. The exception — and it’s an important one — is a deliberate overload block, where a low score may simply be the fatigue you’re intentionally creating. Outside of that, treat Low as a strong nudge toward an easy day or full rest. If it stays Low for 3+ days with no obvious cause, look harder at sleep, stress, or illness.
Training Readiness vs. Training Status vs. Body Battery
Garmin runs three recovery-adjacent metrics and they’re constantly confused. They answer different questions.
| Metric | Question it answers | Time horizon |
|---|---|---|
| Training Readiness | Should I go hard today? | This morning (acute) |
| Training Status | Is my training working over weeks? | Weeks (trend) |
| Body Battery | How much energy do I have right now? | Real-time, all day |
Training Status gives you a label — Productive, Peaking, Maintaining, Strained, Overreaching, Detraining — that describes your trajectory. Body Battery is a live 0–100 gauge that drains as you spend energy and recharges with rest. Training Readiness sits between them: a single morning verdict on whether your body can absorb a hard session today. If you only check one before a workout, it’s Readiness. If you’re planning a training block, it’s Status.
How to fix a Training Readiness score that’s always low
A chronically low score is almost always one of four things. Open the factor breakdown before you do anything else — the number is useless without it.
Read the factor breakdown, not the number.
Tap into the Training Readiness widget and look at the contributing factors. Green is helping, orange and red are dragging you down. This single step tells you what to fix — the headline number on its own tells you nothing actionable.
Fix sleep first — it’s weighted heaviest.
If sleep is red, nothing else you do will lift the score much. Prioritise total duration against your sleep need and a consistent wake time. A fragmented or short night disproportionately drags Readiness down the next morning. (We go deep on this in our guide to how much sleep runners need.)
Cut load if recovery time and acute load are red.
If those two factors are dragging you, you’re training too hard relative to your fitness. Reduce weekly volume 20–30% for two weeks and keep easy days genuinely easy — zone 2, conversational, no exceptions. Many athletes see Readiness jump 15–20 points within a week of real recovery.
Look at life if HRV and stress are red but load is fine.
If training load is moderate but Readiness stays low, the cause is usually off the road: work pressure, poor nutrition, alcohol, illness. Check the stress widget — daytime stress consistently above 50 points to lifestyle, not training. That’s where to intervene.
The accuracy caveats worth knowing
Training Readiness is genuinely useful at the extremes — a Prime reading before a key session, or a Poor reading the morning of a planned long run, are signals worth acting on. But it has real limits, and knowing them makes you better at using it.
It needs three weeks before you trust it
The HRV baseline alone takes at least 19 nights of consistent overnight wear to establish. Until then you’ll see partial scores or none at all. A reading in your first fortnight with a new watch is close to meaningless.
It misses DOMS
Delayed-onset muscle soreness usually peaks around 48 hours after a hard session — but the score has often bounced back by then. You can get a confident Prime reading and still have legs full of cement. The number reads your autonomic and load data, not your quads.
It can’t separate the causes
This is the big one, and it follows directly from the hidden weighting. When your score lands at 48 after a poor night during a hard week, you’re left guessing: is it the sleep? The accumulated load? The work stress? The score collapses all of that into one number and discards the explanation. For day-to-day “hard or easy” decisions that’s often enough. For understanding your own body, it isn’t.
For more on the inputs that feed scores like this, see our beginner’s guide to HRV for runners and how to spot overtraining symptoms before a string of low scores becomes a real problem.
The bottom line
Garmin Training Readiness is a good daily traffic light. Used well — reading the factor breakdown, trusting the extremes, treating Moderate as “check before you commit” — it will keep you from training hard on days your body can’t absorb it. That alone is worth having.
What it won’t do is explain itself. The number arrives every morning with no story attached: no “your HRV is down because dew point was 18°C and your body paid 5 extra beats per minute to thermoregulate,” no “your long runs all followed nights above 7h30 of sleep.” It gives you the verdict and keeps the reasoning. For a lot of runners, that’s the gap between glancing at a score and actually understanding their training.
A score sets the context for the day. It doesn’t tell you the story behind it — and the story is usually the part worth knowing.
Garmin gives you the score. Kovr gives you the reason.
Kovr reads the same data your Garmin does — HRV, sleep, training load, heat, nutrition — and instead of a number, it tells you the story: “Dew point was 18°C, your body paid 5 extra beats to thermoregulate, but your sleep was deep and your nervous system processed the load cleanly.” Garmin asks how that felt. Kovr already knows why.
Join the Kovr waitlistLaunching soon · Garmin, Apple Watch & Oura Ring
Frequently asked questions
What is a good Garmin Training Readiness score?
A score of 73–100 (Prime) means your body is well recovered and ready for a demanding session. 34–72 (Moderate) means train, but at reduced intensity. Below 34 (Low) signals accumulated fatigue or poor recovery — training hard here adds fatigue without producing adaptation. Garmin reports the average user scores around 60.
How is Garmin Training Readiness calculated?
It combines six factors into a single 0–100 score: sleep score, HRV status, recovery time remaining, acute training load, stress history, and Body Battery. Sleep is weighted most heavily, and the algorithm prioritises acute factors like last night’s sleep over longer-term trends. Garmin does not publish the exact weighting of each factor.
Why is my Garmin Training Readiness always low?
The three most common causes are poor or short sleep (the heaviest-weighted factor), too much training load relative to your fitness, and lifestyle stress that suppresses HRV. Open the factor breakdown to see which is red. If training load is moderate but readiness stays low, the cause is usually stress, nutrition, alcohol, or illness rather than training.
What is the difference between Training Readiness and Training Status?
Training Readiness is a daily 0–100 score answering “should I go hard today?” based on acute recovery. Training Status is a longer-term label (Productive, Peaking, Strained, Detraining) answering “is my training working over weeks?” Readiness is about today; Status is about your training trajectory.
Should I skip my workout if Training Readiness is low?
Not necessarily. A low score means avoid hard training, not avoid all training. If you are in a deliberate overload block, a low score may simply reflect the fatigue you are intentionally creating. Check the factor breakdown: if sleep is the only red factor after one bad night, an easy run is usually fine. If recovery time and HRV are both red, move the hard session.
How long does Garmin Training Readiness take to be accurate?
About three weeks of consistent overnight wear. The HRV baseline alone needs at least 19 nights to establish. During this initialisation period you may see partial scores or no score at all. Treat the number as unreliable until the baseline is set.
What can Garmin Training Readiness not tell you?
It tells you a number but not the causal story behind it. Because the factor weighting is hidden, when your score sits in amber after a rough night you cannot tell how much is the sleep versus accumulated load versus stress. It also excludes how you actually feel, and it does not connect a metric like dew point or yesterday’s ride to today’s reading. The score sets context; it does not explain why.
Sources cited
- Garmin. Training Readiness — physiological measurements. View reference
- Garmin Connect 2024 user data, reported via TechRadar. Average Training Readiness score and weekly patterns.
- de Jonge, J. & Taris, T.W. (2025). Sleep Matters: Profiling Sleep Patterns to Predict Sports Injuries in Recreational Runners. Applied Sciences, Vol. 15, No. 19, p. 10814. View study
- Garmin device documentation on HRV Status baseline and initialisation period (19-night minimum).