Resting Heart Rate, Sleep, and Running Load: What to Watch

Resting heart rate, sleep, and weekly load are the three cheapest signals a runner can track, and they are far more useful together than alone. Read each as a 7-day trend against a 4-week baseline, and change your training when two of the three move in the wrong direction at once.

These three are the inputs most readiness apps combine into one score. Readiness scores explained covers how that combination works. This guide covers how to read each signal on its own and how to make the two-of-three decision by hand.

Why three signals instead of one

Any single marker is easy to misread. Resting heart rate rises after a late dinner, a warm bedroom, or a glass of wine. Sleep duration from a wearable is an estimate with real error. Weekly load looks fine until you notice all seven days were the same intensity. Together, the three describe both what you did and how your body responded.

Buchheit (2014) made the methodological case: much of the contradiction in athlete-monitoring research comes from inconsistent measurement and misinterpretation, not from the markers being uninformative. He also noted that heart rate measures cannot describe every aspect of wellness and recommended pairing them with training logs and simple performance tests.

The rule that falls out is a two-of-three trigger. One signal moving is information. Two signals moving is a decision.

Resting heart rate

Measure it the same way every day. The easiest reliable option is your wearable's overnight or waking resting heart rate from the same device every night. The manual alternative is a 60-second count right after waking, before standing.

Build two references, a 7-day rolling average and a 4-week average, and use these bands.

The last row matters. Plews and colleagues (2013) documented elite athletes whose HRV fell while resting heart rate kept decreasing, which means a low resting heart rate on its own is not proof of recovery.

Sleep

Sleep sets the ceiling on how much training you can turn into fitness. Fullagar and colleagues (2015) reviewed sleep loss in athletes and found that although some maximal and gross motor efforts survive restriction, sport-specific performance tends to decline. They also describe reduced sleep producing autonomic imbalance that resembles overtraining, increases in pro-inflammatory cytokines, and slower, less accurate cognitive performance.

The extension side has evidence too. Mah and colleagues (2011) had 11 collegiate basketball players keep their usual sleep for 2 to 4 weeks, then aim for at least 10 hours in bed for 5 to 7 weeks. Measured nightly sleep rose by about 111 minutes. Sprint times improved from 16.2 to 15.5 seconds, free throw accuracy rose 9 percent, three-point accuracy rose 9.2 percent, and reaction time, sleepiness, and mood all improved.

For a runner:

• Track a 7-day average rather than single nights. One short night is manageable. Five in a row is a training variable.
• If the 7-day average is 60 minutes below your normal, hold volume flat instead of building.
• If it is below six hours, convert hard sessions to easy running until sleep recovers.
• Put the long run after your best sleep opportunity, not after your latest night.
• Treat consistent bed and wake times as part of training. Irregular timing degrades both sleep quality and the reliability of your morning readings.

Load

Planned load and completed load diverge quickly. The simplest internal measure is session RPE, on a 1 to 10 scale, multiplied by duration in minutes and summed weekly.

Foster (1998) followed 25 experienced athletes with this method and derived three values: load as a rolling six-week average, monotony as the daily mean divided by the standard deviation of daily loads, and strain as load multiplied by monotony. Illness clustered when individuals exceeded their own thresholds, mostly of strain.

Monotony is the underappreciated part. Here are two weeks with identical total load.

Week B has wider variation, lower monotony, and therefore lower strain at the same volume. This is the arithmetic behind the advice to make easy days easier and hard days harder, which the easy runs guide covers in detail.

The two-of-three decision table

The response is almost always to hold or reduce rather than to stop. Complete rest is right for illness and for real overreaching. Reflexive rest days in response to one high reading produce a plan that never builds anything.

What these signals cannot tell you

• Tissue-specific risk. Bone stress and tendon irritation develop independently of autonomic markers. A local ache that changes your stride outranks every number here.
• Fueling adequacy. Chronic under-eating suppresses recovery, and its early signs are mood, libido, menstrual changes, and cold intolerance rather than heart rate.
• Absolute fitness. These markers describe state, not capacity. Only a benchmark effort tells you whether the training is working.
• Heat and altitude adaptation. Both raise resting heart rate for days to weeks, so a training camp or a hot spell produces readings that look like overreach.

A weekly submaximal heart rate check

The three signals describe your state. One cheap addition describes your fitness. Pick a flat 10 to 15 minute segment of a route you run often. Once a week, on the same day if possible, run that segment at a fixed easy effort and record average heart rate and average pace. Keep the time of day and the warm-up similar, and skip the week if it is unusually hot or windy.

Over four to six weeks:

• Faster pace at the same heart rate means fitness is improving.
• Same pace at a lower heart rate means fitness is improving.
• Slower pace at the same heart rate means fatigue is accumulating, or heat has arrived.
• Higher heart rate at the same pace with a normal resting heart rate is usually heat, dehydration, or a hard session two days earlier.
• Higher heart rate at the same pace plus a rising resting heart rate means the two-of-three trigger has fired.

Buchheit (2014) names submaximal exercise heart rate, taken as a 30 to 60 second average, as one of the two most useful monitoring tools alongside resting HRV. It works because the route, effort, and time of day are fixed, so most confounds are removed before you look at the number.

Reading the signals across a training block

The same numbers mean different things at different points in a build.

The taper row catches people out. When load drops, your markers improve for reasons that have nothing to do with fitness gained. Treating that as permission to add work undoes the taper's only job.

Building the habit in one week

1. Choose one measurement method for resting heart rate and one for sleep, and do not change devices mid-block.
2. Log session RPE within 30 minutes of finishing each run and multiply by minutes.
3. At the end of each week, write down three numbers: weekly load, 7-day average resting heart rate, and 7-day average sleep.
4. Every four weeks, run the same benchmark effort, such as 20 minutes at threshold on a fixed route, and record pace and average heart rate.
5. Change the plan's structure only at the four-week checkpoint. Change individual sessions freely in between.

Vitadel Run pulls resting heart rate, HRV, and sleep from Apple Health and connected wearables, tracks your training load, and applies the same two-of-three logic to size each day's session. The point of tracking is to notice three days early that the block is drifting, and to make a small correction instead of a large one.