How to Use HRV and Readiness to Adjust Running Workouts

Heart rate variability is most useful to a runner as a three-state daily decision: near your baseline means run the session as written, moderately below means cut the hard part, and clearly below for two days running means go easy or rest. The number is only meaningful against your own history, which takes two to four weeks of consistent measurement to establish.

What does HRV actually measure?

Heart rate variability describes the small differences in time between consecutive heartbeats. When your parasympathetic nervous system is dominant, those intervals vary more. When sympathetic drive rises with hard training, illness, sleep debt, alcohol, or stress, they vary less. RMSSD, the root mean square of successive differences, is the index most often used for daily monitoring because it mostly tracks parasympathetic activity and stabilizes within a short recording. Many apps report a log-transformed version, ln RMSSD, which spreads the values into a more even scale.

The practical point is narrow. HRV is a state marker, not a fitness score. Buchheit (2014) argues that most of the conflicting HRV findings in the literature come from methodological inconsistency and misreading of individual data, not from the measure being useless. Read as a personal trend with a known error range, it answers one question well: is my autonomic system where it usually is today?

How long does a baseline take to build?

Plan on two weeks minimum and four weeks for confidence. During that window, measure the same way every day and record the value without acting on it. Then compute two things: a 7-day rolling average, and the standard deviation of your daily readings across the whole baseline window.

Those two numbers define your zones. Kiviniemi and colleagues (2007) used a reference built from a 10-day mean minus one standard deviation, and prescribed low intensity or rest when the morning value dropped below it or trended down for two days. Vesterinen and colleagues (2016) used an individually determined smallest worthwhile change around the baseline for the same purpose. Both approaches share the same logic: the threshold belongs to you, not to a population.

Two habits protect the baseline. Keep the measurement conditions identical, and keep the window rolling so it tracks fitness changes. As aerobic fitness improves, resting HRV often drifts upward and resting heart rate drifts down, so a baseline frozen in January will misjudge you in April.

What do green, yellow, and red days mean?

The value of a three-state system is that it produces a decision instead of a feeling. Here is a workable mapping once your baseline exists.

Two details make this work in practice. First, yellow days should modify a session rather than delete it, because deleting sessions repeatedly erodes the aerobic base that made the plan possible. Second, red days need a rule for what replaces the workout, decided in advance. A 35-minute conversational run is a better default than an open-ended decision made while tired.

How do you move a hard session without wrecking the week?

Hard sessions are the scarce resource in a training week, so the goal is to reschedule rather than discard. Three rules cover most cases.

• Swap, do not stack. If Tuesday's intervals move to Wednesday, Wednesday's easy run moves to Tuesday. Never place two hard days back to back to catch up.
• Protect the long run. If both a quality session and the long run are threatened in the same week, keep the long run and shorten the quality session. Aerobic durability builds slowly and is expensive to rebuild.
• Cap the weekly count. Most recreational runners hold two hard sessions per week, sometimes three during a peak block. If readiness has pushed a session late in the week, drop it rather than compress three hard days into four calendar days.

Vesterinen and colleagues (2016) illustrate why this is not a loss. Their HRV-guided group completed roughly four fewer hard sessions over eight weeks than the fixed-plan group and still improved 3000 m performance, while the fixed group did not improve significantly during the same block. Placement mattered more than count. Javaloyes and colleagues (2019) reported a similar pattern in trained cyclists, where an HRV-guided group improved peak power output and a 40-minute time trial while a traditional periodization group did not.

What HRV cannot see

Readiness scores are blind to several things that decide whether your season goes well.

• Tissue tolerance. Bone, tendon, and fascia load histories do not show up in beat-to-beat intervals. A stress reaction in the tibia can develop while HRV looks excellent.
• Mechanical change. A limp, an altered cadence, or a sore spot that appears only during push-off is a stronger signal than any number.
• Fueling status. Under-eating suppresses recovery and performance in ways HRV reports only late and indirectly.
• Heat and altitude. Both shift heart rate and HRV for reasons unrelated to training stress, so an unfamiliar climate will produce a week of confusing readings.
• Absolute fitness. A high HRV does not mean you can hold threshold pace today. Fitness comes from the training history; HRV comments on the state you bring to it.

There is also a specific trap in well-trained runners. Plews and colleagues (2013) describe HRV saturation, where HRV falls or plateaus even as resting heart rate keeps dropping and fitness improves. In that context, an unusually high reading can accompany accumulated fatigue rather than freshness. When the number and your body disagree at the extremes, follow your body.

How to measure so the number means something

Measurement error is the main reason people give up on HRV.

1. Fix the time. Immediately on waking, before standing, before caffeine, or use an overnight average from the same device every night.
2. Fix the position. Supine or seated, chosen once and never mixed.
3. Fix the breathing. Breathe normally rather than performing slow paced breathing, which inflates HRV substantially.
4. Fix the duration. One to five minutes is sufficient for RMSSD-based indices, and Buchheit (2014) notes 5-minute resting recordings are enough for most monitoring purposes.
5. Note the context. Alcohol, late meals, illness, travel, and hard evening sessions all move the number, and a one-line note prevents you from misreading a normal response as a problem.

Vitadel Run builds this baseline from Apple Health sleep, HRV, and heart rate data and turns it into a readiness state, then reshapes the day's VDOT-based session around it, so the daily decision is already made when you open the app.

What a readiness-aware week looks like

A four-session week for a runner training for a 10K might look like this. The plan sets the intent; readiness decides the shape.

Over a month, this produces a plan that is roughly 80 percent as aggressive as the paper version on paper and considerably more consistent in practice, because the sessions you do complete land on days when your body can absorb them.

When to ignore your readiness score

Override the number in four situations. Ignore a green reading when you have local pain that changes your gait, when you are ill with fever or chest symptoms, when you have slept under five hours, or when perceived effort at easy pace is clearly higher for a third day. Ignore a red reading when the cause is obvious and transient, such as one late night or one glass of wine, and you feel fine after a warm-up. In that case, start the session, run the first repetition, and decide from how it feels rather than from the morning number.

The habit that matters most is the one that costs nothing: measure daily, act on trends, and write down what changed. A readiness system earns its keep over months, when you look back and find that your hard sessions landed on your better days.