In the back half of a long run, heart rate rises at unchanged pace. The phenomenon is predictable, and it changes which number deserves your attention.
- Cardiac drift appears in any prolonged effort held at a steady intensity, usually after the first ten or twenty minutes.
- The heart speeds up because each beat moves less blood: heat, flow redirected to the skin, and fluid loss all shrink the available volume.
- It’s physiological when it climbs slowly and your pace holds. It needs correcting when it arrives early, rises steeply, and your pace gives way.
- On long runs, you steer by pace and breathing, treating heart rate as a guardrail instead of a target.
Same Pace, Ten Beats More
Mile ten of a long run, flat road, pace identical to the one you were holding half an hour earlier. The watch reads 152 where it read 144. Two instincts follow: slow down to drop back into the zone you’d set for yourself, or write the day off as proof that your fitness has gone somewhere. Both come from the same assumption, that the number measures how hard you’re running.
It measures something else: what it costs you, at this moment, to run at that speed. Cardiac drift is the gradual rise in heart rate that shows up during any prolonged effort held at a constant intensity, typically starting after the first ten or twenty minutes. The meaning of the number shifts while the run goes on, and knowing which direction it shifts changes how you handle the next two hours.
What Happens to Blood and Temperature
Your heart speeds up because each contraction sends less blood into circulation than it did earlier, and it makes up the difference by beating more often. The amount of blood reaching the muscles every minute stays where the effort demands, delivered now through more beats and less volume per beat.
Heat sits behind all of it. Running produces far more of it than the body can hold onto, and to shed the excess, part of the flow gets rerouted to the skin, where blood hands its temperature off to the air. That blood is subtracted from central circulation. If you’re also sweating heavily and replacing little, plasma volume falls too, and less blood arrives to fill the heart in the interval between two beats. The volume ejected with each contraction, what physiologists call stroke volume, drops accordingly.
Picture filling a bathtub by carrying water in a bucket. If the bucket shows up three-quarters full, you’ll need more trips to raise the level at the same rate. The tub asks for the same water. It’s the bucket that brings less of it each time around.
That’s the most intuitive explanation, and a second one exists: the rise in heart rate may originate in increased sympathetic nervous system activity, which shortens the filling time between beats and reduces ejected volume on its own. The two hypotheses are still being debated, and for runners it changes little, since the phenomenon stays regular and predictable even without a settled mechanism. How pronounced it gets depends instead on variables you already know: air temperature, humidity, hydration status at the start, duration of the run, and how fast you covered the opening miles. At ninety degrees in humid air, drift arrives sooner and climbs higher, which is the same reason running slower in summer has a physiological explanation.
When Drift Tells You Something and When It Doesn’t
To work out which of the two cases you’re in, look at three things together: how steep the climb in beats is, when it begins, and what your pace is doing meanwhile.
Physiological drift is slow and spread out, a few beats every twenty or thirty minutes, with pace holding and breathing unchanged. You can ignore it. It becomes a signal when it arrives early, inside the first half hour, when it climbs steeply, and above all when perceived effort follows it and your pace starts to give way without any decision on your part to slow down.
Three causes come up most often. Starting too fast, which shifts the entire run onto an intensity you can’t sustain for the planned duration. Fluid debt accumulated before you left or along the way, which you can only correct once you know how much you’re losing: measuring your own sweat rate turns drinking from a habit into a quantity. And environmental conditions, which raise the cost of any speed. A fourth is less common: a short night, an infection on the way, or training load you haven’t absorbed yet will lift your heart rate from the first mile, and drift there is the most visible symptom of something already underway.
What to Watch Instead of Heart Rate
On long runs, you set the effort by pace and breathing, and heart rate serves as a ceiling rather than a target. It’s probably the worst of the three parameters to pilot a two-hour run by, precisely because it’s the only one that changes meaning while you’re looking at it.
In practice: decide your pace before you head out and hold it, checking now and then that you’re still in the range where you could hold a conversation without breaking your sentences. Assign heart rate a guardrail value, above which you genuinely slow down, and leave everything underneath it alone. Eight or ten beats picked up in the second hour won’t touch it, and dropping back into the zone by lowering your pace means finishing the long run at an intensity that no longer trains much of anything.
Factor it in before you start, too, because the second half will cost more at the same speed: the pace of your opening miles should be chosen with mile sixteen in mind, not mile two. It’s one of the reasons the weekly long run has a construction of its own, different from any other session.
How to Read the Graph After the Run
The useful moment for heart rate arrives once the run is over. Split the file into two equal halves and compare the ratio between average pace and average heart rate in each: if the heart worked considerably harder in the second half to produce the same speed, you have a measure of how far the two data streams decoupled. A five percent divergence circulates among coaches as a practical boundary, a field convention rather than a research-established threshold. Below it, the session went smoothly. Above it, it’s worth asking what made the run harder than expected.
The comparison only holds between comparable runs: same route, similar temperature, similar time of day. A July long run against an October one tells you nothing about your fitness. The same run repeated weeks apart does tell you something: if drift shrinks at equal pace and conditions, adaptation is arriving, and you’ll see it there before the stopwatch shows it.