You run the same 10 km loop at the same perceived effort, three weeks in a row. Week one your average HR is 138. Week three it's 149. Your pace hasn't changed, your RPE hasn't changed — but your heart is working eleven beats harder to deliver the same output. That gap is cardiac drift, and it is one of the clearest early warnings your body can give you that training load has outpaced recovery. Understanding what drives the drift, where the threshold sits, and when to act on it can save a training block that is quietly going off the rails.
Runners and coaches use "heart rate drift" to describe two related but distinct phenomena. Conflating them leads to the wrong interventions.
Cardiac drift within a single run is the steady, physics-driven rise in HR that occurs during any prolonged effort at constant pace. As you sweat, plasma volume drops. Stroke volume falls. To maintain cardiac output at the same pace, your heart compensates by beating faster. Add a shift from central to peripheral blood flow for thermoregulation, and HR climbs further still. This type of drift is expected and largely unavoidable over runs longer than 60–75 minutes. A well-hydrated runner on a cool day will see 5–8 bpm of rise over the back half of a 90-minute easy run. That is not a warning sign. It is physiology.
Week-over-week training drift is the pattern that should concern you. If your easy-pace HR rises by 5 or more beats per minute across identical or equivalent runs over a 2–3 week window — without a change in heat, altitude, or illness — accumulated training stress is the most likely cause. Your cardiovascular system is no longer recovering fully between sessions. This is the drift that signals you are accumulating fatigue faster than you are absorbing it.
During an aerobic run, cardiac output must match the muscular demand for oxygen. Cardiac output equals heart rate times stroke volume. When stroke volume is suppressed — by plasma depletion, glycogen depletion, or the neuroendocrine effects of unabsorbed training stress — the heart compensates via rate. This is the core mechanism behind every form of cardiac drift.
Accumulated training load adds a second layer. Heavy training stimulates the sympathetic nervous system and suppresses parasympathetic tone. Resting heart rate rises slightly, and the HR response to any given workload increases because the autonomic balance has shifted. HRV falls. Threshold paces feel harder at the same physiological load. If the stimulus is not matched by sufficient recovery, this state persists and worsens. A 5-beat drift week over week is a measurable downstream signal of that imbalance.
Heat amplifies everything. In warm conditions, cutaneous blood flow increases to dissipate heat, further reducing the blood available for working muscles. The heart compensates again with higher rate. A runner moving from spring to summer training will typically see 8–12 bpm of ambient drift from heat alone, independent of fatigue. Separating thermal drift from fatigue drift requires controlling the comparison — same time of day, same course, or using a temperature-corrected baseline.
No single threshold applies to every runner, but a widely used practical guideline among coaches is the 5-beat rule: if easy-pace HR at a standardised effort has risen by 5 or more beats per minute compared to your rested baseline for that course and conditions, treat it as an amber flag. If the drift reaches 10 bpm, treat it as a red flag requiring immediate load reduction.
| HR drift vs baseline (same pace, similar conditions) | Signal | Recommended action |
|---|---|---|
| 0–4 bpm above baseline | Normal variation | Continue as planned |
| 5–9 bpm above baseline | Amber — early fatigue | Drop intensity for 2–3 days; monitor HRV |
| 10+ bpm above baseline | Red — significant under-recovery | Scheduled deload week; no intensity above easy |
| 10+ bpm over 2+ consecutive weeks | Red — overreaching | Extended recovery block (10–14 days), review weekly load |
The baseline matters as much as the threshold. Establish it during a recovery or taper week, on your standard easy route, at the same time of day, in mild weather. That number becomes your reference. Comparing week-three-of-a-build HR against a peak-week measurement from two months ago gives you noise, not signal.
If you want more precision than the 5-beat rule, use aerobic decoupling — the metric Garmin calls "aerobic decoupling" and TrainingPeaks labels "Pa:HR." It quantifies how much your pace-to-HR ratio changed from the first half to the second half of a long run. A well-recovered, well-trained runner shows less than 5% decoupling on a 90-minute easy run. Values between 5–10% are acceptable on long runs exceeding 2 hours. Consistent decoupling above 10% on standard easy runs is an objective marker of cardiovascular strain.
The advantage over raw beat counting is that decoupling normalises for different run lengths and partial-run comparisons. A 60-minute run and a 100-minute run will show different absolute HR drift values at the same recovery state — decoupling percentage makes them comparable.
Get-Split surfaces this metric in your activity detail view alongside lap-by-lap HR data. Track it across three or four weeks of easy long runs and you will have a reliable trend line rather than a single noisy data point.
Track HR drift in Get-Split free →The response should be proportional to the signal. An amber flag (5–9 bpm) calls for a local correction: pull back intensity for 2–3 days, replace any scheduled quality session with easy running or complete rest, and check your HRV trend. If HRV is also suppressed, accelerate toward a full deload. If HRV looks normal, the drift may be heat or a mild hydration deficit rather than accumulated fatigue — hydrate more aggressively and reassess after two easy days.
A red flag (10+ bpm or sustained amber over multiple weeks) requires a scheduled deload week. This means:
The goal is not just to reduce fatigue but to allow supercompensation — the rebound in fitness that comes after a stimulus is absorbed. Runners who push through red-flag drift without adjusting typically see a sharper performance collapse later, not gradual erosion.
The most effective deload is the one you plan, not the one your body enforces. Standard practice among coaches following a periodised structure is to build for 3 weeks and deload for 1, cycling through the mesocycle. At the end of each build phase, reduce volume proactively — even if HR drift is not yet signalling amber.
Specific triggers that should pull a deload forward:
After a well-executed deload, easy-pace HR typically returns toward baseline within 5–7 days. If it does not, extend the deload rather than resuming build. A second week of reduced load costs you very little fitness — the research consistently shows that 7–10 days of reduced volume does not produce meaningful detraining in athletes who have been training for more than 12 months.
Get-Split automatically pulls HR data from Garmin after every synced activity. In the Health dashboard, the HRV trend and resting HR graph sit alongside your training load curve, so you can see the lag relationship directly — training load peaks are typically followed by HRV troughs and resting HR spikes within 24–48 hours. When those signals move together and persist beyond 3 days without recovery, Get-Split flags the pattern as part of its recovery readiness score.
For per-run drift analysis, the Activity detail view shows lap-by-lap HR overlaid with pace. You can visually spot when HR decouples from pace midway through a run, and compare that pattern across your last 4–6 easy runs. Cross-reference it against the weekly mileage and intensity distribution visible in the Training calendar to diagnose whether the drift is volume-driven, intensity-driven, or environmental.
Cardiac drift is the gradual rise in heart rate that occurs during a prolonged run at constant pace, driven primarily by plasma volume loss through sweating and the shift from central to peripheral circulation. A 5–8 beat rise over 60–90 minutes at easy pace is normal. A rise above 10 bpm suggests dehydration or accumulated fatigue.
For a well-trained runner running at true easy pace (conversational, nasal breathing), cardiac drift of 5–8 bpm over the back half of a 60-minute run is within normal range. Drift above 10 bpm at an otherwise comfortable effort usually points to under-recovery, dehydration, heat, or a brewing illness.
Aerobic decoupling (Pa:HR decoupling) measures how much your heart rate rises relative to your pace over a long run. Well-trained runners show less than 5% decoupling on their easy long runs. Rising decoupling week over week — not just in a single run — signals that accumulated fatigue is outpacing your recovery. It is one of the earliest measurable signs of overreaching.
It is a strong early warning, not a definitive diagnosis. Overtraining syndrome (OTS) requires weeks of suppressed performance and symptoms well beyond HR data. But consistently elevated easy-pace HR over 2–3 weeks, combined with declining HRV and flat or dropping pace at perceived effort, should trigger a recovery intervention before OTS develops.
A standard deload week is 5–7 days of reduced volume (40–60% of peak week) and no intensity above easy/Zone 2. Most runners need one deload every 3–4 build weeks. If drift-triggered, extend to 10–14 days: the first week reduces volume, the second confirms HR is trending back toward baseline before resuming structured work.
Yes. In warm or humid conditions, the cardiovascular system routes additional blood to the skin for thermoregulation, pushing HR higher at any given pace. This is thermal cardiac drift, not fatigue drift. The fix is to run by effort (RPE) rather than pace on hot days, or to accept a slower pace at the same HR target. After 10–14 days of heat acclimatisation, plasma volume expands and HR returns toward cooler-weather values.