Recovery scores explained, and why your devices disagree

In one night at a Central Queensland University sleep lab, Miller and colleagues (2022) fitted 53 adults with six consumer wearables plus an electrocardiogram and compared every device's heart rate variability with the ECG. WHOOP 3.0 read 4.5 ms low on average. Apple Watch Series 6 read 9.6 ms low. A Garmin Forerunner 245, which took its reading from a short sample near the start of the night, read 22.4 ms low. Those gaps exist before any scoring formula touches the data. Stack a different baseline, a different set of extra inputs and a different scale on top, and the same person can wake up to a 7 out of 10, a 64 percent and a 38 on three screens.

None of those numbers has to be wrong. Each answers a slightly different question. This article covers what WHOOP, Oura, Garmin and Apple say about their scores, how Titan's Recovery score works down to the weights with three nights calculated in full, what the research supports, and what to change on a Low, Moderate or High day. The wearable data quality guide covers how accurate the inputs are before any score is built from them.

01What every score starts from

Every major recovery or readiness score draws on heart rate variability, and most pair it with overnight resting heart rate. Each company compares those signals with your own history instead of a population norm. The differences between products come later, in which extra inputs they add, how long a history they compare against, and how they turn the comparison into a number.

Heart rate variability

HRV is the beat-to-beat variation in the interval between heartbeats. At rest most of the fast variation comes from the vagus nerve, the parasympathetic brake on the heart, so HRV above your usual level generally means a rested system. RMSSD, the root mean square of successive differences between beats, tracks vagal activity closely. SDNN, the standard deviation of all intervals in a recording, reflects a broader mix of influences. WHOOP reports RMSSD. Apple Watch stores HRV in Apple Health as SDNN, as the WHOOP support and Recovery settings articles document.

The raw millisecond value says little on its own. Age, genetics, fitness, breathing rate and the measurement window all shift it, so 45 ms can be a great morning for one person and a poor one for another. Plews and colleagues (2013) argued that only monitoring over time reveals each athlete's individual HRV pattern, which is why every serious score compares you with yourself.

Resting heart rate

Resting heart rate usually moves opposite to HRV. Heat, dehydration, alcohol, a late meal, illness and accumulated training fatigue tend to raise overnight heart rate and lower HRV. HRV reacts faster and noisier, and resting heart rate is steadier night to night, so when both move against you on the same morning the signal is harder to dismiss. Plews and colleagues (2013, IJSPP) found that a single day's resting heart rate correlated weakly to moderately with training gains in 10 runners, and a one-week average correlated strongly. The same was true, more sharply, for HRV.

02How WHOOP, Oura, Garmin and Apple build their numbers

Each summary below uses only what the manufacturer publishes about its own score. None of the four publishes its weights. Some publish band cutoffs and some do not.

WHOOP Recovery

WHOOP's developer documentation describes Recovery as "a daily measure of how prepared your body is to perform," calculated when you wake as a percentage from 0 to 100. The higher the score, the more ready WHOOP considers you to take on Strain that day. The documentation lists the objective measurements that factored into the score as resting heart rate, HRV as RMSSD and, on WHOOP 4.0, blood oxygen and skin temperature. Its data model includes a user_calibrating flag for the period while WHOOP is still learning your baseline, and a score state of "UNSCORABLE" when there is not enough data.

The documentation publishes no weights or band cutoffs, and I could not reach a WHOOP page that states them, so this article quotes none. WHOOP also does not write HRV to Apple Health, so a WHOOP band alone cannot give Titan the overnight HRV its Recovery score is built on, as the WHOOP support article explains.

Oura Readiness

Oura's Readiness Score runs from 0 to 100 with published bands. At 85 or higher Oura calls it "Optimal, you're ready for action!" From 70 to 84 it is "Good, you've recovered well enough." Under 70 it is "Pay attention, you're not fully recovered." Oura groups its contributors into three pillars and lists them by name.

• Sleep and Sleep Balance, covering last night and the past two weeks
• Previous Day Activity and Activity Balance, covering yesterday and recent load
• Resting Heart Rate, HRV Balance, Body Temperature and Recovery Index, which Oura groups as body stress

Recovery Index asks how many hours of sleep you got after your heart rate reached its overnight low. Oura's page states that the contributors sum to the score, emphasizes contributors based on multiple days, and says that "100s are designed to be rare rather than regular." Oura's Readiness therefore folds sleep and activity directly into the number. A short night or an unusually active yesterday can lower Readiness even when HRV and resting heart rate look normal.

Garmin Training Readiness and Body Battery

Garmin ships two related numbers. Training Readiness is the morning-facing one. Garmin names last night's sleep and the recovery time left from recent activities as the primary drivers, followed by acute training load, HRV status, sleep history before last night and stress history from the past three waking days. Its HRV status reads as balanced when your 7-day average HRV sits within your personal baseline range. Recent activities count fully toward acute load when recorded, and their effect expires over the next 10 days. Garmin classifies readiness in five levels, "from poor to prime with low, moderate, and high in between," and updates it through the day as recovery time runs down or a new workout lands. Garmin's page does not give numeric cutoffs for those levels, and it says Training Readiness is not designed to predict race performance.

Body Battery answers a different question. Garmin describes it as a running estimate of energy reserves built from heart rate, HRV and movement, fullest when you wake, drained by activity and stress, and recharged by rest and sleep. The two can disagree on the same morning because Training Readiness looks back across 10 days of load and several nights of sleep, while Body Battery tracks the current day.

Apple Readiness and Vitals

Apple added a Readiness score with Apple Watch Series 12 and Ultra 4, announced on September 9, 2026. Apple says it analyzes recent activity, training load, vitals and sleep score, and returns a single score from 0 to 10 with one of four recommendations, Recover, Pace Yourself, Ready or Go For It. Readiness updates through the day, for example after an intense workout, and shows which factors are driving the score. Apple has not published the score ranges behind each recommendation.

The Vitals app remains the per-metric view. Apple's announcement says overnight vitals now include a recovery HRV measurement analyzed against your personal baseline, labeled in words such as "Typical" and "Favorable," and adds a daytime view. The Apple Watch HRV that Titan reads from Apple Health is SDNN.

The five scores side by side

Oura, Garmin and Apple put sleep and training load inside the number. WHOOP and Titan stay close to the cardiac signals and leave training load to separate scores. That design choice is the first place to look when two devices disagree.

03How Titan's Recovery score works

The Recovery score and baselines help articles describe the same model from inside the app. This section gives the constants behind it.

The two inputs

Recovery scores the night you just slept, and the score belongs to the day you woke up. Titan reads two values from that night.

Overnight HRV is the geometric mean of every HRV reading inside your main sleep session. Titan takes the natural logarithm of each reading, averages those, and converts the average back to milliseconds. A geometric mean gives one unusually high reading less pull than a plain average would.

Sleeping heart rate is the lowest 30-minute rolling average of heart rate during the same sleep. On a night with too few heart rate readings to fill a 30-minute stretch, Titan uses the 10th percentile of the readings instead.

Both values come from one device. Titan prefers the device that recorded the sleep, so a watch and a ring never get mixed inside one night. If no sleep session was saved, Titan reads the readings between 10 PM and 10 AM and labels the score Partial night. No setting changes which readings count. A Mindfulness session that falls inside the window adds one HRV reading to the night, the same as any other reading.

The baseline, in usual steps

Your baseline is the median of your measured nights before the night being scored, drawn from the Recovery window, which is 60 nights by default. A measured night is one with both overnight HRV and sleeping heart rate. Only earlier nights count, so tonight never changes a score Titan has already given an earlier night.

Titan measures how far last night sits from that median in units of your own night-to-night spread. The spread is the median absolute deviation, or MAD, the median of how far each night in the window sits from the median. Titan multiplies the MAD by 1.4826, the factor that makes it match a standard deviation when the data are normally distributed. The result is one usual step, and the help articles use that name. A distance measured this way is called z.

HRV is handled on a logarithmic scale, so its distances are proportional. A 10 percent drop is the same distance whether your baseline is 30 ms or 90 ms. Two floors keep a run of near-identical nights from making a tiny change look enormous. The HRV step is never smaller than about 4 percent, and the sleeping heart rate step is never smaller than 1 bpm. Each z is capped at 3 steps in either direction, so one broken reading cannot pin the score.

A baseline needs at least 7 measured nights, and they have to cover at least a quarter of the window. On the default 60-night window that means 15 measured nights. Until then the Recovery screen says Not enough nights for a baseline.

One fixed curve

Titan combines the two distances in one line and passes it through a logistic curve, the S-shaped function 1 / (1 + e^−x), which returns a value between 0 and 1.

x = 0.25 + 1.5 × zHRV − 0.75 × zHR

Recovery = 100 × 1 / (1 + e^−x), rounded to a whole number

The curve itself never changes, which gives the scale fixed landmarks.

The bands are Low 0 to 39, Moderate 40 to 74 and High 75 to 100. With sleeping heart rate at baseline, HRV about 0.45 of a step below its median is enough to reach Low, and about 0.55 of a step above reaches High. The same night always gets the same score, however often you open Titan.

Three nights, worked through

Take an Apple Watch user on the default 60-night window. Her overnight HRV baseline is 62 ms. Her nights typically sit about 10 percent from that median, so the MAD on the log scale is 0.10 and one usual step is 0.148, about 16 percent. One step above her baseline is 72 ms and one step below is 53 ms. Her sleeping heart rate baseline is 52 bpm with a MAD of 1.5 bpm, so one step is 2.22 bpm.

Check Night B by hand. 60 ms is about 3 percent below 62 ms, and ln(60 ÷ 62) is −0.033. Divided by the 0.148 step, that is 0.22 steps below baseline. Multiplying by 1.5 gives −0.33, and adding the 0.25 constant gives −0.08. The logistic of −0.08 is 1 ÷ (1 + e^0.08), which is 0.48, so the score reads 48.

What the arithmetic shows

HRV carries twice the weight of sleeping heart rate for each step. On Night A, HRV 1.45 steps below baseline took 2.18 off x, and a heart rate 1.35 steps above baseline took another 1.01. Both moved against her on the same night, which is the pattern the research below treats as the strongest warning.

Your spread decides how much a given drop matters. Take three athletes with the same 62 ms baseline who all wake to 57 ms with sleeping heart rate at baseline. If their nights usually sit 5 percent from the median, 57 ms is 1.13 steps down and Recovery reads 19. At 10 percent it is 0.57 steps and Recovery reads 35. At 15 percent it is 0.38 steps and Recovery reads 42. The same 5 ms drop lands in the Low band for all three, at very different depths.

The logistic curve flattens at both ends. Once x passes about ±4.6 the score sits within 1 point of 0 or 100, so a very bad night and an extremely bad night read almost the same. The middle of the scale, where most nights land, is where small changes in HRV and heart rate move the score most.

Titan stores the inputs for SDNN and RMSSD separately. Turning Use RMSSD for HRV on or off under Settings > Recovery & Sleep rebuilds Recovery history with the new method automatically, so every baseline night and every scored night use the same formula.

Estimated scores

Some nights lack an input. Titan still gives a score, marks it Estimated, and shows the reason under the ring. Only nights with both overnight HRV and sleeping heart rate feed your baseline.

A night with sleeping heart rate and no HRV reads Estimated with the reason No HRV recorded overnight. Titan carries HRV forward from your last 7 measured nights, weighting recent nights more, and moves the carried value 30 percent of the way back toward your baseline for each night since the last measured one. Your sleeping heart rate, breathing rate, sleep length and sleep efficiency can shift it by at most a quarter of a usual step. Titan then scores the night on the same curve.

A night with no usable data follows your recent measured scores. Titan starts from your last 30 nights of measured scores, which need at least 7, and pulls the estimate toward their median for each night you miss. Your first HRV reading after waking and your Apple Health resting heart rate before 10 AM can each move it an eighth of the way toward the score they point to, a quarter at most with both.

A Partial night is scored on the same curve as a full one. When heart rate covers less than 6 hours of the 10 PM to 10 AM window, Titan moves the score toward your usual score in proportion.

When a score is final

A night's score becomes final at noon on the day you wake. Before noon, a late watch sync can still update it. After noon it stays fixed, even if more readings arrive. Later readings can still reach the baselines of future nights.

04What the evidence supports

Three questions matter. Do HRV trends track training adaptation, does adjusting training to HRV beat a fixed plan, and do consumer sensors measure the signal well enough to begin with?

HRV trends track adaptation, with caveats

Plews and colleagues (2013, Sports Medicine) reviewed HRV monitoring in elite endurance athletes and found the picture messier than a simple rule. Both increases and decreases in HRV have accompanied poor adaptation in elites, and fitness gains have sometimes arrived with an unexpected fall in HRV. Their fixes were methodological. Average across days, use indices that suit highly trained athletes, and learn each athlete's pattern over time.

The averaging point has direct evidence. In 10 runners over a 9-week block, a single day's log-transformed RMSSD had a trivial correlation with the change in maximal aerobic speed (r = −0.06), while the one-week average correlated strongly (r = 0.72) (Plews et al., 2013, IJSPP). A follow-up in triathletes found that at least 3 valid readings per week were needed to match the full weekly average (Plews et al., 2014). Titan's Recovery follows the same logic. It averages every HRV reading across the night and compares that average with a median of many earlier nights.

Buchheit (2014) argued that most contradictory findings in this field come from methodological inconsistency and misinterpretation, and that any change should be judged against the measurement's error and the smallest worthwhile change, in the context of the current training phase. He also recommended pairing heart rate measures with training logs, questionnaires and simple performance tests, since no single marker captures every kind of fatigue.

Bellenger and colleagues (2016) pooled 24 studies in endurance athletes. Training that improved performance produced a small rise in resting RMSSD (standardized mean difference 0.58). Training that left athletes overreached and slower also produced a small rise (0.26). Their conclusion was that resting HRV is largely unaffected by overreaching. A single morning's HRV cannot tell you whether a hard block is working or digging a hole. The pattern over days, alongside how you feel and perform, carries more information.

On variability, the evidence is thin and points in more than one direction. In a two-athlete case study over 77 days, Plews and colleagues (2012) watched the 7-day average of log RMSSD fall steadily in the triathlete who became non-functionally overreached, while the coefficient of variation of that average also fell. The control athlete stayed stable on both. Two athletes cannot settle which direction matters. Titan's Recovery has no variability term. Your night-to-night spread only sets the size of one usual step, so a more erratic history makes each departure from baseline count for less.

HRV-guided training in controlled trials

Kiviniemi and colleagues (2007) randomized 26 moderately fit men to a predefined plan, an HRV-guided plan or a control group for 4 weeks. The HRV group trained hard when morning HRV held steady or rose, and trained easy or rested when HRV fell below a reference derived from the previous 10 days or declined for 2 days in a row. VO2 peak rose from 56 to 60 ml/kg/min in the HRV group and did not change significantly in the predefined group, 54 to 55. Maximal running speed improved more in the HRV group. The between-group difference in VO2 peak change was not significant.

Vesterinen and colleagues (2016) ran 40 recreational runners through 8 weeks of intensive training. The HRV-guided group scheduled moderate and hard sessions only when morning HRV sat within an individual smallest worthwhile change, and ended up doing fewer of them, 13.2 against 17.7. Their 3,000 m running performance improved by 2.1 percent, a significant change, while the predefined group's 1.1 percent improvement was not. VO2 max improved in both groups.

Javaloyes and colleagues (2019) did the same with 17 well-trained cyclists over 8 weeks. The HRV-guided group improved peak power output by 5.1 percent, power at the second ventilatory threshold by 13.9 percent and a 40-minute time trial by 7.3 percent. The traditional group did not improve significantly, although the direct between-group comparison was not significant either.

Düking and colleagues (2021) pooled 8 studies with 198 participants. HRV-guided training had a significant positive effect on submaximal physiological markers (Hedges' g = 0.296) and small, non-significant effects on performance (g = 0.079) and VO2 peak (g = 0.171). HRV-guided plans usually contained fewer moderate and hard sessions, and they produced fewer non-responders.

Read together, these trials support a modest claim. Using morning HRV to decide when to go hard produces results at least as good as a fixed plan, often with fewer hard sessions and fewer athletes who fail to improve. The samples are small, dozens of participants per trial, and none of them tested a consumer composite score. They tested the practice of adjusting intensity to a personal HRV trend, a form of auto-regulation, which is what a recovery score is for.

How accurate the sensors are

Miller and colleagues (2022) is the clearest head-to-head. Against ECG, intraclass correlations for HRV were 0.99 for WHOOP 3.0, 0.67 for Apple Watch Series 6, 0.65 for Polar Vantage V, 0.63 for Oura Gen 2 and 0.24 for Garmin Forerunner 245. For heart rate the figures were 0.99, 0.96, 0.93, 0.85 and 0.41. Two caveats apply. The research group receives funding and equipment from WHOOP, and WHOOP supplied raw beat-to-beat data where the other devices were read from their apps. The Garmin HRV came from a 3-minute window near sleep onset, so its low agreement partly reflects when it measured.

Dial and colleagues (2025), with no declared conflicts, tracked 13 adults over 536 nights. Lin's concordance with ECG for overnight HRV was 0.99 for Oura Gen 4, 0.97 for Oura Gen 3, 0.94 for WHOOP 4.0, 0.87 for Garmin Fenix 6 and 0.82 for Polar Grit X Pro. Resting heart rate concordance was 0.98 and 0.97 for the two Oura rings, 0.91 for WHOOP and 0.86 for Polar. The two studies used different hardware generations and statistics, so compare devices within a study, not across them. Both show that two wearables on the same body report different HRV on the same night before any scoring model runs.

05Why your number disagrees with another device or another person

Another person

A friend's Recovery of 80 and your 45 say nothing about who is fitter or healthier. Each score measures distance from that person's own history. Titan's fixed curve makes this explicit, since a 56 means a night at your own baseline and a 56 for your friend means a night at theirs. The raw HRV values behind the scores are not comparable either, for the reasons in the HRV section above.

Another device

When two devices disagree on the same morning, the causes stack in a predictable order.

1. Measurement. The devices may record different HRV statistics, SDNN on Apple Watch and RMSSD on WHOOP, over different windows, a whole night, a sleep phase, or a short morning reading. Sensor agreement with ECG also differs, as Miller and Dial showed.
2. Inputs. Oura, Garmin and Apple fold sleep and training load into readiness. Titan and WHOOP stay close to the cardiac signals. A poor night of sleep with normal HRV will lower Oura's or Garmin's number more than Titan's.
3. Baseline length. Garmin's HRV status compares a 7-day average with a personal range. Oura's balance contributors look back two weeks or more. Titan compares last night with the median of your measured nights in a 60-night window by default. A longer window treats a rough training week as a real drop, and a short one absorbs it.
4. Scaling. Titan maps the distance from your baseline onto a fixed curve. Oura uses a 0 to 100 scale with fixed bands. Apple uses 0 to 10 and four labels. Garmin uses five named levels.
5. Timing. Apple and Garmin update readiness through the day. Titan's Recovery belongs to the night you slept and becomes final at noon on the day you wake. Before noon, a late watch sync can still update it.

The window length alone changes what a hard week looks like.

Titan's Recovery window is 60 nights by default, the long end of that range. The baselines article covers how the window is filled.

Another screen inside Titan

Titan's own numbers use different baselines too. Recovery compares last night with the median of your measured nights in the Recovery window. Stress and Battery compare each 5 minutes of the day with fixed 60-day medians of your daily average HRV and your daily Apple Health resting heart rate. A Low Recovery can sit beside a calm Stress day, because one reads the night against your earlier nights and the other reads waking hours against daily averages. The Apple Watch app shows the Recovery score your iPhone synced.

Yesterday's score changed

A night's Recovery is final at noon on the day you wake, and its baseline only uses nights before it, so later nights never rescore it. Past scores change when Titan rebuilds history, for example after you turn Use RMSSD for HRV on or off, or after Clear Recovery Cache. The why past scores changed article lists every cause.

06What to do on a low, moderate or high day

A recovery score is an input to a training decision. The research above supports adjusting intensity to a personal trend, so the useful questions are what today's band says and whether the pattern has held for more than one morning.

Low day

Titan's calendar legend sums up a Low score, 0 to 39, as "Favor easy work, sleep and nutrition." Keep the session and lower the ceiling. Swap intervals for easy aerobic volume, cut the top sets from a strength session, or make it a rest day if the week has been heavy. Several Low days inside a hard block are a reason to bring a deload week forward.

One Low morning after a hard session is expected. A run of them deserves more weight. Titan does not use a fixed millisecond or percentage HRV threshold. For a rule of thumb that works with any wearable, use this one. A morning HRV more than one median absolute deviation below your baseline median for two or more consecutive days, with resting heart rate above baseline, is a signal to reduce training intensity. The Recovery score and baselines articles show where to find your baseline. Kiviniemi's protocol also acted on a two-day decline, and the averaging studies above show why a single reading is too noisy to act on.

Moderate day

The legend sums up the Moderate band, 40 to 74, as "Train, but keep an eye on intensity." Moderate is where most ordinary training days land. Run the planned session and watch how the hard efforts feel against their usual heart rate or pace.

Moderate days are where the weekly view helps most. The Training balance chart in Trends plots a 7-day rolling average of Exertion times 10 minus Recovery, with a reference line at zero. Above zero, exertion is outpacing recovery. Below zero, recovery is running ahead of exertion. A string of Moderate mornings is fine while that line hovers near zero. A string of Moderate mornings with the line climbing well above zero is the pattern to act on.

High day

The legend sums up the High band, 75 to 100, as "Ready for quality training." Put the key interval session or heavy lift here when the plan allows. Keep in mind what the score measures. A High score says last night's overnight HRV and sleeping heart rate together sat well on the good side of your baseline. It does not see a sore hamstring, a sore throat, a long-haul flight or a poorly healed injury. Any of those overrides the number.

07When the number is missing or wrong

Some bad scores are data problems. The Recovery missing or looks wrong article covers each cause in order.

• The baseline is still filling. Until the window holds 7 measured nights covering a quarter of its length, 15 nights on the default 60-night window, the Recovery screen says Not enough nights for a baseline.
• The score says Estimated. Last night was missing HRV, heart rate or a sleep session, and the line under the ring names which. Wear the watch to sleep and check Health permissions for both types. HRV not showing covers the HRV side.
• The score changed during the morning. A watch that synced late can update the night's score until noon. After noon it stays fixed.
• You switched to RMSSD. Titan then needs the Heartbeat Series permission, and without it HRV can go blank. Titan rebuilds Recovery history with the new method on its own.
• Past scores look stale. Clear Recovery Cache under Settings > Health & Connected Apps recalculates Recovery, Sleep, Stress and Battery history from Apple Health.

08The Recovery detail screen on Today

Tap the Recovery card on Today to see your own inputs, baselines and history. The top shows your score in a ring and the band label. Under it is the time your sleep ended, or, for an estimated score, the reason it is estimated. The "What shapes your score" section has two rows, Overnight HRV and Sleeping heart rate, each beside your Recovery baseline with the difference in ms or bpm. Tap either row for the baseline window length, the percent change from baseline and a daily chart. Titan notes that these comparisons are not exact contributions to the score. The "Recovery history" section has a 7, 30 and 60 day picker, the average for that period, a daily bar chart, and a comparison of your last 7 days with the 7 before once each week has 4 scored days. The Recovery score article documents the full screen.

09References

• Bellenger CR, et al. (2016). Monitoring athletic training status through autonomic heart rate regulation: a systematic review and meta-analysis. Sports Medicine, 46(10), 1461-1486. doi.org/10.1007/s40279-016-0484-2
• Buchheit M. (2014). Monitoring training status with HR measures: do all roads lead to Rome? Frontiers in Physiology, 5, 73. doi.org/10.3389/fphys.2014.00073
• Dial MB, et al. (2025). Validation of nocturnal resting heart rate and heart rate variability in consumer wearables. Physiological Reports, 13(16), e70527. doi.org/10.14814/phy2.70527
• Düking P, et al. (2021). Monitoring and adapting endurance training on the basis of heart rate variability monitored by wearable technologies: a systematic review with meta-analysis. Journal of Science and Medicine in Sport, 24(11), 1180-1192. doi.org/10.1016/j.jsams.2021.04.012
• Javaloyes A, et al. (2019). Training prescription guided by heart-rate variability in cycling. International Journal of Sports Physiology and Performance, 14(1), 23-32. doi.org/10.1123/ijspp.2018-0122
• Kiviniemi AM, et al. (2007). Endurance training guided individually by daily heart rate variability measurements. European Journal of Applied Physiology, 101(6), 743-751. doi.org/10.1007/s00421-007-0552-2
• Miller DJ, et al. (2022). A validation of six wearable devices for estimating sleep, heart rate and heart rate variability in healthy adults. Sensors, 22(16), 6317. doi.org/10.3390/s22166317
• Plews DJ, et al. (2012). Heart rate variability in elite triathletes, is variation in variability the key to effective training? A case comparison. European Journal of Applied Physiology, 112(11), 3729-3741. doi.org/10.1007/s00421-012-2354-4
• Plews DJ, et al. (2013). Training adaptation and heart rate variability in elite endurance athletes: opening the door to effective monitoring. Sports Medicine, 43(9), 773-781. doi.org/10.1007/s40279-013-0071-8
• Plews DJ, et al. (2013). Evaluating training adaptation with heart-rate measures: a methodological comparison. International Journal of Sports Physiology and Performance, 8(6), 688-691. doi.org/10.1123/ijspp.8.6.688
• Plews DJ, et al. (2014). Monitoring training with heart rate-variability: how much compliance is needed for valid assessment? International Journal of Sports Physiology and Performance, 9(5), 783-790. doi.org/10.1123/ijspp.2013-0455
• Vesterinen V, et al. (2016). Individual endurance training prescription with heart rate variability. Medicine & Science in Sports & Exercise, 48(7), 1347-1354. doi.org/10.1249/MSS.0000000000000910
• Apple (2026). Introducing Apple Watch Series 12, with the all-new Health Sensing System. Apple Newsroom. apple.com/newsroom
• Garmin (2024). Training Readiness. Garmin Technology. garmin.com
• Garmin (n.d.). Body Battery. Garmin Technology. garmin.com
• Oura (2026). Your Oura Readiness Score. Oura blog. ouraring.com
• WHOOP (n.d.). Recovery. WHOOP for Developers. developer.whoop.com