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.

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 meaningful error. Weekly load looks fine until you notice all seven days were the same intensity. Combined, the three describe both the input and the response.

Buchheit (2014) makes the methodological case: much of the contradiction in the athlete-monitoring literature comes from inconsistent measurement and misinterpretation, not from the markers being uninformative. He also notes that heart rate measures cannot describe all aspects of wellness, fatigue, and performance, and recommends pairing them with training logs, questionnaires, and simple performance tests.

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

Resting heart rate: what to measure and what counts

Measure it the same way every day. The easiest reliable option is your wearable's overnight or waking resting heart rate, provided you use the same device nightly. The manual alternative is a 60-second count immediately on waking, before standing.

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

That last row matters. Plews and colleagues (2013) documented elite athletes whose HRV fell while resting heart rate continued to decrease, showing that low resting heart rate alone is not proof of recovery.

Sleep: the input that sets your ceiling

Sleep determines how much training you can convert into fitness. Fullagar and colleagues (2015) reviewed sleep loss in athletes and found that although some maximal and gross motor efforts persist after restriction, sport-specific performance tends to decline. They also describe reduced sleep quality and quantity producing autonomic imbalance that resembles overtraining symptoms, 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 maintain habitual sleep for 2 to 4 weeks, then aim for a minimum of 10 hours in bed for 5 to 7 weeks. Objective nightly sleep increased 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.

Running-specific translation:

• Track a 7-day average rather than single nights. One short night is manageable; five in a row is a training variable.
• Below your normal average by 60 minutes for a week, hold volume flat instead of building.
• Below six hours average, 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, because irregular timing degrades both sleep quality and the reliability of your morning readings.

Load: measure the training you actually did

Planned load and completed load diverge quickly. The simplest internal measure is session RPE multiplied by duration in minutes, summed weekly.

Foster (1998) followed 25 experienced athletes using this method and calculated three derived 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 episodes clustered when individuals exceeded personal thresholds, mostly related to strain.

Monotony is the underappreciated part. Consider 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.

The two-of-three decision table

Notice that the response is almost always to hold or reduce rather than to stop entirely. Complete rest is the correct answer for illness and for genuine overreaching, but reflexive rest days in response to a single high reading produce an inconsistent plan that never builds anything.

What these three signals cannot tell you

• Tissue-specific risk. Bone stress and tendon irritation develop independently of autonomic markers. A localized ache that changes your gait outranks every number here.
• Fueling adequacy. Chronic under-eating suppresses recovery, and its early signs are often 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 will produce readings that look like overreach.

Adding a submaximal heart rate check

The three signals above describe your state. One cheap addition describes your fitness, and it costs nothing extra: a weekly submaximal heart rate check.

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. Run it at the same time of day, after a similar warm-up, and skip the week if conditions are unusually hot or windy.

Interpretation over four to six weeks:

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

Buchheit (2014) specifically identifies submaximal exercise heart rate, taken as a 30 to 60 second average, as one of the two most useful monitoring tools alongside resting heart rate variability. The reason it works is control: 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 is worth stating plainly, because it catches people out. When load drops, your markers improve for reasons that have nothing to do with fitness gained, and 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, on a 1 to 10 scale, 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, for example 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 assembles resting heart rate, HRV, and sleep from Apple Health into a single readiness state and resizes the day's session against it, which is the same two-of-three logic applied automatically.

The point of tracking is not to accumulate charts. It is to notice, three days early, that the block is drifting, and to make a small correction instead of a large one.