Readiness scores compress heart rate variability, resting heart rate, and sleep data into a single daily number, which makes them a useful physiological snapshot rather than a verdict. Overriding a low score is reasonable when the dip has a clear one-off explanation, your subjective feel is genuinely fine, and there are no illness signs. It becomes risky when a low score persists across several days, comes with elevated resting heart rate, or coincides with symptoms of illness. Treat the number as one input to weigh, not the decision itself.
By Emily Harrison
Who This Matters Most For
This guide is for anyone who wears a device that produces a daily readiness, recovery, or training-readiness number, Oura, Whoop, Garmin, and similar platforms all do some version of this, and who has ever stared at a low score and wondered whether to train anyway. It’s written for recreational and competitive athletes, weekend racers, strength trainees, and the coaches who work with them. It assumes you already understand the basics of what heart rate variability and resting heart rate are; the focus here is judgment, not definitions. It is not written for people managing a diagnosed cardiac condition, an eating disorder, or another condition where a clinician has already given specific monitoring instructions, those instructions should always take priority over anything in this article or in an app.
How Readiness Scores Are Actually Calculated
Most consumer readiness scores are built from the same three raw ingredients: heart rate variability (the beat-to-beat variation in your heart rhythm, largely governed by your autonomic nervous system), resting heart rate, and sleep data (duration, timing, and how much it deviates from your usual pattern). Some platforms add secondary signals, body temperature, breathing rate, or recent training load, as supporting context.
Oura’s publicly described methodology is a useful, concrete example of how this works in practice. According to Oura’s own explanation of its Readiness Score, the 0-100 number is built from seven separate daily contributors grouped into three pillars: sleep (how last night compares with your normal pattern, and whether you’ve been getting enough sleep over the past two weeks), activity (yesterday’s activity balance and the cumulative load your body is carrying), and body stress (resting heart rate changes, HRV trends, body temperature variation, and how quickly your heart rate settles after activity). Oura frames scores of 85 and above as optimal readiness, 70 to 84 as good recovery, and anything below 70 as a signal that recovery may be insufficient.
The detail worth remembering is that these scores are almost always calibrated against your own rolling baseline, typically a two-week personal average, rather than against a population norm. That’s why a score of 72 might be an ordinary Tuesday for one person and a genuine red flag for another. It also means the score is only as good as the baseline period behind it: someone coming off a rough month of poor sleep will have a baseline that reflects that rough month, quietly lowering the bar for what counts as “normal.”
What These Scores Capture Well
Readiness scores are genuinely good at one specific job: flagging shifts in autonomic and cardiovascular status over time. Research on elite endurance athletes by Plews, Laursen, Stanley, Kilding, and Buchheit, published in Sports Medicine in 2013, showed that tracking an individual athlete’s own HRV pattern over weeks and months can reveal a physiological fingerprint, with rises and falls in HRV tracking changes in fitness and freshness for that specific athlete. Used this way, as a longitudinal trend rather than a single-day snapshot, HRV-derived scores can pick up on accumulating fatigue before it becomes obvious in performance.
Sports scientist Martin Buchheit, writing in a 2014 Frontiers in Physiology paper on heart-rate-based monitoring, made a similar point: when measurement protocols are standardized (same time of day, same body position, same conditions), resting HRV and related heart rate measures do a solid job of tracking positive aerobic adaptation and acute training responses. That’s the score’s real strength, it is sensitive to the physiological cost of training load, disrupted sleep, and the early stages of illness, and it does this consistently and without requiring you to think about it.
Resting heart rate elevation in particular is one of the more reliable early markers of brewing illness or accumulated fatigue, often showing up a day or two before you feel noticeably unwell. A composite score that weights this signal heavily is doing real work, even on the days when it’s wrong about everything else.
What These Scores Miss
The blind spots are just as important as the strengths, and they’re where most bad decisions happen. A readiness score has no way to know that you have a job interview at 2 p.m., that your kid was up sick all night, that you’re nervous about a work presentation, or that today is the race you’ve been building toward for six months. It measures your body’s overnight physiology; it cannot measure your circumstances.
This gap shows up clearly in a 2016 systematic review by Saw, Main, and Gastin published in the British Journal of Sports Medicine, which compared subjective self-report measures (soreness, mood, stress, perceived recovery) against objective markers like HRV and blood-based biomarkers across 56 studies. The review found that subjective measures “reflected acute and chronic training loads with superior sensitivity and consistency than objective measures.” In plain terms, how you actually feel about your training and your life often picks up meaningful change faster and more reliably than your heart rate variability does. A readiness score built purely on physiology is, by design, missing the input that turns out to matter most.
Buchheit’s 2014 paper makes the same point from a different angle, noting plainly that “measures of heart rate cannot inform on all aspects of wellness, fatigue, and performance,” and arguing for complementary tools alongside heart-rate-based monitoring, including psychometric questionnaires, training logs, and simple performance tests. Motivation is a particularly large blind spot: the adrenaline and focus that show up on race day or during a meaningful test aren’t part of any overnight physiological signal, yet they measurably change how a session goes.
Single-night noise is the other major gap. One glass of wine, a late dinner, an unfamiliar hotel bed, a hot bedroom, or a stressful phone call before bed can all dent HRV and resting heart rate for one night without reflecting anything meaningful about your actual training capacity the next day.
What the Score Sees vs. What It Misses
What it sees
- Overnight HRV trend
- Resting heart rate shifts
- Sleep duration and timing
- Body temperature deviation
- Breathing rate changes
- Recent training load
What it misses
- Work or family stress
- Motivation and race-day adrenaline
- One-off events like travel or alcohol
- Illness before it’s measurable
- Why a session matters to your plan
- Emotional state and mindset
When Overriding a Low Score Is Reasonable vs. Risky
Overriding a low readiness score is not automatically reckless, and treating the score as absolute is its own mistake. The question is whether you’re overriding it with information, or overriding it with wishful thinking.
Reasonable to override when:
The dip has one clear, explainable cause (a hard session two days ago, a single late flight, one poor night’s sleep); your subjective soreness, mood, and motivation are genuinely fine; you have no sore throat, fever, or unusual fatigue; and the session ahead is meaningfully important to your plan, a race, a key test, a session you’ve built toward.
Risky to override when:
The score has been low or falling for several consecutive days; resting heart rate is elevated alongside it; you notice any illness symptoms, however mild; or overriding has become automatic, something you do every single day regardless of the number, which quietly defeats the entire point of tracking it.
Halson’s 2014 review in Sports Medicine on monitoring training load makes a point worth carrying into this decision: no single marker, heart rate variability included, has strong enough standalone evidence to serve as a definitive stop-or-go signal. She writes plainly that “there is yet to be a single, definitive marker described in the literature.” That’s not a reason to distrust the score; it’s a reason to treat it as one vote among several, alongside how you feel and what today actually requires of you.
Building Your Own Cross-Check Habits
The practical fix for all of this is a habit, not a rule. A few small routines make the difference between a score you react to and a score you actually use.
Keep a sixty-second subjective log next to the app. Rating soreness, mood, and motivation on a simple 1-to-5 scale each morning, right alongside the device’s number, gives you two data streams instead of one. Saw, Main, and Gastin’s review specifically recommends this combination: frequent, brief subjective ratings paired with periodic objective testing, rather than leaning on either alone. Over a few weeks, the pattern between your subjective log and your readiness score becomes far more informative than either one on its own.
Look at the seven-to-fourteen day trend line before reacting to any single morning. Most apps show this graph somewhere; if yours doesn’t, jot the number down daily. A score that dropped once and bounced back is noise. A score that’s been drifting down for a week and a half is a signal.
Tag context when it’s unusual, travel, alcohol, a late meal, a stressful day, the start of a cold. A month of tagged data turns a mysterious low score into an explainable one, and over time you’ll start to see your own personal patterns, how much a poor night’s sleep actually costs you, how long travel disruption tends to last, whether your score dips before or after you notice you’re getting sick.
Finally, revisit your assumptions periodically. A baseline built during a stretch of altitude training, a new medication, a change in caffeine intake, or a major life event will not describe “normal” the same way it did a few months earlier. Treat your own thresholds as something to update, not something fixed at setup.
Scenarios: Low Score, Different Contexts, Different Responses
The same low number can call for very different responses depending on what’s around it. Here’s how that plays out in practice.
Checklist: Before You Override a Low Readiness Score
- Check the trend over the past seven to fourteen days, not just this morning’s number
- Ask honestly: any sore throat, fever, chills, or unusual fatigue right now?
- Rate your own soreness, mood, and motivation out of five, out loud or on paper
- Identify one specific, one-off explanation for the dip, and write it down
- Look at the underlying resting heart rate or HRV trend if your app shows it, not just the composite score
- Confirm the session ahead is important enough to justify pushing through a borderline day
- Set a fallback plan to scale down mid-session if it starts feeling wrong
- Log what you decided and how it turned out, so the next call is easier
Worked Example: Maria’s Two Low-Score Mornings
Maria is a 34-year-old recreational runner training for a fall marathon. On a Saturday morning with a scheduled 16-mile long run, her readiness score reads 61, well into the yellow zone, down from a weekly average of 78.
Before deciding anything, she runs through her checklist. The trend shows one clear dip, not a slide. Her subjective log reads soreness 2 out of 5, mood 4 out of 5, motivation high, she’s genuinely looking forward to the run. Context: she flew home from a work trip two nights earlier, slept poorly the first night back, but slept well last night. No sore throat, no fever, nothing that reads as illness. Her decision: run as planned, but with a slightly easier pace target than originally written, and an agreement with herself to cut the run short at mile eight if anything feels off. It doesn’t; the run goes fine, and her score is back near baseline the next morning.
Three weeks later, her score reads 58 for the third straight day, and her resting heart rate is six beats per minute above normal. Her subjective log shows heaviness in her legs and a scratchy feeling in her throat that she’d been ignoring. This time the checklist points the other way: multiple consecutive low days, a real physiological shift, and an early symptom she can’t explain away with travel or a hard session. She swaps the scheduled tempo run for an easy walk and an early night. By the next morning she’s clearly sick with a cold. The two decisions, made with the same checklist a few weeks apart, land in opposite places for good reason.
Common Mistakes
What Sports Scientists Say
The published research on HRV-based monitoring is more cautious about single-number interpretation than most marketing copy suggests. Plews, Laursen, Stanley, Kilding, and Buchheit, in their 2013 Sports Medicine paper on elite endurance athletes, point out a genuinely counterintuitive finding: “in elite athletes, studies have revealed both increases and decreases in HRV to be associated with negative adaptation.” In other words, at the highest levels of fitness, a rising number and a falling number can both signal a problem, which is exactly the kind of nuance a simple 0-to-100 score can’t convey on its own.
Saw, Main, and Gastin’s 2016 review reaches a conclusion that should reorder most people’s trust hierarchy: subjective self-report measures “reflected acute and chronic training loads with superior sensitivity and consistency than objective measures.” That’s a systematic review of 56 studies concluding that how you rate your own soreness and mood tends to outperform your wearable’s physiological score at detecting real changes in training response.
Buchheit’s 2014 review lands on a practical middle ground: heart-rate-based measures are cheap, fast, and genuinely useful when standardized, but they need company. Halson’s 2014 review goes further, noting that despite years of research into fatigue markers, “very few of these markers have strong scientific evidence supporting their use, and there is yet to be a single, definitive marker described in the literature.” Interestingly, her review of monitoring practices across Australian and New Zealand sport programs found that 91 percent used some form of athlete monitoring, and self-report questionnaires, used by 84 percent of programs, were more common than any objective test, including heart rate variability.
Taken together, the research doesn’t argue against readiness scores. It argues against using them alone.
Safety and Scope Notes
This article is general educational information about interpreting consumer wearable data, not medical advice, and it is not a substitute for guidance from a qualified clinician or coach who knows your history.
Persistent low readiness across many consecutive days, any symptoms of illness (fever, sore throat, unusual fatigue, gastrointestinal upset), or signs of injury should always take priority over a training plan, no matter how important the session feels. When in doubt, rest and consider medical evaluation rather than pushing through.
Key Takeaways
- Readiness scores combine HRV, resting heart rate, and sleep data into one number; they are a physiological snapshot, not a full picture of your day
- They’re calibrated against your own rolling baseline, not a population norm, so comparing scores between people rarely means anything
- Subjective measures, soreness, mood, motivation, often catch real changes that objective scores miss, according to published research
- Judge trends over a week or two rather than reacting to any single morning’s number
- Reasonable overrides pair a low score with a clear, one-off explanation and genuinely normal subjective feel
- Illness symptoms and persistent low readiness should always outrank a training plan
- The most useful habit is a simple, repeatable cross-check routine, not blind trust in the number or blanket dismissal of it
Frequently Asked Questions
Is it ever okay to train hard on a low readiness score day?
Yes, when the dip has a clear one-off explanation, such as travel or a hard session two days earlier, your subjective feel is good, and you have no illness symptoms. Treat the low score as a caution flag to monitor, not an automatic stop sign.
How many low-readiness days in a row should trigger a real pullback?
There’s no universal number, but several consecutive low or declining days, especially alongside an elevated resting heart rate, is a far stronger signal than one low morning, and generally warrants easier training or an extra rest day.
Can a readiness score warn me that I’m getting sick before I feel it?
It can sometimes flag early physiological changes, like a rising resting heart rate, before symptoms appear, but it is not a diagnostic tool. Treat an unexplained drop as a prompt to pay closer attention to how you feel, not as a diagnosis.
Why does my score differ from a training partner’s even after a similar session?
These scores are calibrated against your own rolling personal baseline rather than a shared population scale, so identical numbers can mean different things for different people. Comparing raw scores between people generally isn’t meaningful.
Should I ignore my readiness score on days I feel great?
Not automatically. A mismatch between how you feel and what the score shows is worth noting rather than dismissing outright. Check the recent trend and look for an explainable context, like alcohol or a late meal, before deciding it’s just noise.
Does stress from work or family life show up in a readiness score?
Only indirectly, if it’s disrupting your sleep or elevating your resting heart rate. Psychological stress and motivation aren’t measured directly by any of these platforms, which is one of the more significant blind spots to account for yourself.
What should I track alongside my readiness score?
A short daily log of soreness, mood, and motivation, plus notable context like travel, alcohol, illness signs, or big life events, turns a single number into a far more useful picture after a few weeks of data.
Should coaches let athletes override a low readiness score on their own?
Many effective programs build in structured autoregulation, letting athletes adjust a session within agreed limits based on both the score and how they feel, rather than treating the number as either irrelevant or absolute.
References
- Oura. “Readiness Score.” Oura Ring Blog. https://ouraring.com/blog/readiness-score/
- Plews DJ, Laursen PB, Stanley J, Kilding AE, Buchheit M. “Training Adaptation and Heart Rate Variability in Elite Endurance Athletes: Opening the Door to Effective Monitoring.” Sports Medicine, 2013;43(9). https://link.springer.com/article/10.1007/s40279-013-0071-8
- Saw AE, Main LC, Gastin PB. “Monitoring the Athlete Training Response: Subjective Self-Reported Measures Trump Commonly Used Objective Measures: A Systematic Review.” British Journal of Sports Medicine, 2016;50(5):281-291. https://bjsm.bmj.com/content/50/5/281
- Buchheit M. “Monitoring Training Status With HR Measures: Do All Roads Lead to Rome?” Frontiers in Physiology, 2014;5:73. https://www.frontiersin.org/journals/physiology/articles/10.3389/fphys.2014.00073/full
- Halson SL. “Monitoring Training Load to Understand Fatigue in Athletes.” Sports Medicine, 2014;44(Suppl 2):139-147. https://link.springer.com/article/10.1007/s40279-014-0253-z
