Heart Rate Drift Is Telling You Something. Your Wearable Isn't Listening.

Your heart rate climbs during long steady efforts even when pace stays flat. That drift is one of the most useful signals in endurance training, and most wearables ignore it completely.

Cardiac drift is the gradual increase in heart rate during prolonged exercise at a constant workload. Run at 6:00/km for 60 minutes and your heart rate in the first 10 minutes might average 140. By the final 10 minutes it might be 155. Same pace. Same perceived effort at the start. Fifteen beats of drift.

This happens because your body is losing plasma volume through sweat, reducing stroke volume (the amount of blood pumped per heartbeat). To maintain the same cardiac output, heart rate has to increase. Add in rising core temperature, which dilates blood vessels and further reduces effective blood volume, and you get a steady upward creep in heart rate that has nothing to do with running harder.

Why Drift Rate Matters

The magnitude of cardiac drift during a standard effort is a proxy for several things that matter to athletes.

Hydration status. More dehydrated means faster drift. If your drift on the same 60 minute route was 8 beats last week and 15 beats this week at the same temperature, something changed. Probably your hydration going in.

Heat adaptation. Athletes who are heat acclimated show less cardiac drift at the same temperature. Track your drift over the first few weeks of summer and you’ll watch it gradually decrease as your body learns to manage thermoregulation more efficiently.

Aerobic fitness. A fitter cardiovascular system maintains stroke volume more effectively under fatigue. Over months of consistent aerobic base building, cardiac drift at the same effort level decreases. This is a training adaptation signal that’s more granular than VO2 max estimates.

Fatigue state. Accumulated training fatigue increases cardiac drift. If you’re in a heavy training block and your drift on easy runs starts climbing, your body is telling you it’s losing the ability to regulate cardiovascular function efficiently. That’s an overreaching signal.

What Your Wearable Does With This

Almost nothing.

Your watch records heart rate continuously. It could calculate drift on any effort longer than 30 minutes at a steady pace. It could track drift trends over weeks and months. It could flag when drift increases suddenly as a hydration, heat, or fatigue warning.

Instead, it gives you an average heart rate for the session and maybe a chart showing the climb. The analysis is left entirely to you.

Garmin gives you average heart rate by lap if you set up auto laps. You can manually compare early laps to late laps. But this is data extraction, not interpretation. You have to know what drift means, know that it matters, and do the comparison yourself.

Whoop tracks strain using heart rate data but doesn’t isolate drift as a distinct metric. Your strain score goes up because your heart rate was higher for longer. It doesn’t distinguish between “heart rate was high because you ran hard” and “heart rate was high because you were dehydrating and drifting.”

How Athletes Actually Use Drift

Experienced coaches have used cardiac drift as a training tool for decades. The Aerobic Threshold test (also called the MAF drift test) is built entirely on this concept. Run at a fixed heart rate for 60 minutes on a flat course and measure pace decline. If your pace drops by more than 5% from the first half to the second half, you’re above your aerobic threshold.

This is a field test that requires no lab, no lactate meter, no gas exchange analysis. Just a heart rate monitor and a flat road. It’s been used in endurance coaching since Phil Maffetone popularised it in the 1990s.

The data to automate this test exists on every wearable with GPS and heart rate. No platform automates it.

Drift as a Daily Check In

Here’s a practical application. Every time you do an easy run of 40 minutes or longer, note the heart rate in the first 10 minutes and the last 10 minutes at the same pace. Track that gap over time.

On well recovered days the gap will be small, maybe 5 to 8 beats. On days when you’re carrying fatigue, dehydrated, or sleep deprived, the gap will widen to 12 to 18 beats.

This single metric, tracked consistently, tells you more about your recovery state than most recovery scores. It’s a direct physiological measurement of how well your cardiovascular system is coping, taken during actual exercise rather than estimated from overnight data.

If your drift has been climbing for three consecutive runs, something in your recovery stack is failing. Sleep, hydration, nutrition, or training load. Start investigating before your recovery score catches up two days later.

The Temperature Variable

Cardiac drift is highly sensitive to ambient temperature. A 10 degree Celsius increase in temperature can add 5 to 10 beats of additional drift on the same effort. This is normal and expected.

The problem is that most wearable platforms don’t factor temperature into their analysis at all. Your Garmin connect chart shows your heart rate climbing during a hot run. It doesn’t note that the drift was temperature expected. It doesn’t compare today’s drift against similar temperature sessions in your history.

For athletes in climates with significant seasonal variation (like Sydney, where a winter easy run at 12 degrees and a summer easy run at 32 degrees are both common), temperature adjusted drift would be enormously valuable. It would separate the signal (fitness changes, fatigue accumulation) from the noise (it was just hot today).

The weather data exists. Your phone knows the temperature. The connection to your heart rate data doesn’t happen.

Training Applications

Drift data informs three practical training decisions.

First, pacing strategy for long events. If your drift in training is 12 beats per hour at race pace, you know your heart rate at km 30 of a marathon will be roughly 24 beats higher than at km 5. Knowing this lets you set a starting heart rate that keeps you in the right zone at the end, not just at the start.

Second, hydration planning. Athletes who track drift against fluid intake can find their personal hydration sweet spot. Too little fluid and drift climbs. Too much and you’re stopping for bathroom breaks and dealing with GI distress. The drift data tells you whether your hydration strategy is working in real time.

Third, recovery monitoring. Weekly drift trends on equivalent sessions are a sensitive early warning system for overreaching. More sensitive than resting HRV in many cases because drift captures cardiovascular function under load, not at rest. You can have a decent resting HRV and still show elevated drift if your cardiovascular system is fatigued at working intensity.

The Synthesis Gap

Cardiac drift connects heart rate, hydration, temperature, fatigue, and fitness into a single measurable signal. It’s one of the best examples of a metric that emerges from the intersection of data streams rather than from any single data point.

Your wearable has the raw data to calculate it. The heart rate trace exists. The GPS data exists. The time stamps exist. What’s missing is the layer that says “your drift is trending up, here’s what that probably means given your recent training load, sleep data, and local temperature.”

That’s the synthesis layer. It turns data into decisions. And it’s still not built into any platform most athletes use.