How to Use Heart Rate Drift to Catch Dehydration Before It Wrecks Your Race

In Summary

Cardiac drift — heart rate rising at the same pace — is your watch telling you you're dehydrating.
A drift of 10–15% from your first-half average signals you're falling behind on fluid.
Drinking earlier and adding sodium slows drift more than speeding up intake later.
Sweatr detects drift automatically from your Garmin or Apple Watch data and adjusts your plan.

You're 90 minutes into a long run. Your pace hasn't changed, your legs feel fine, but your heart rate is 12 beats higher than it was at the same effort 45 minutes ago. You slow down. It barely drops. Something is off.

What you're seeing is cardiac drift, and it's one of the most useful dehydration signals your running watch already tracks — if you know how to read it.

Most runners glance at heart rate to gauge effort. But cardiac drift tells you something different: how much fluid you've lost. And if you catch it early enough, you can adjust your hydration mid-run before it costs you minutes — or your entire race.

What cardiac drift actually is

When you run at a steady pace, your heart pumps blood to deliver oxygen to your working muscles. Early in the run, your blood volume is high, so each heartbeat delivers a large amount of oxygen. Your heart rate stays stable.

As you sweat, you lose plasma volume. Your blood gets thicker. Each heartbeat delivers less oxygen. To compensate, your heart pumps faster — even though your pace hasn't changed.

That upward creep in heart rate at a constant effort is cardiac drift.

It's not fatigue (though fatigue makes it worse). It's not poor fitness. It's your cardiovascular system compensating for fluid loss. And your watch records every beat of it.

How much drift means you're in trouble

Some drift is normal. Your heart rate will naturally rise slightly over a long run due to increased core temperature and the gradual depletion of glycogen. But the magnitude tells you whether dehydration is the primary driver.

The rough thresholds:

Less than 5% increase from your first-half average heart rate: Normal. Hydration is likely fine.
5–10% increase: Mild dehydration developing. You should increase fluid intake now.
10–15% increase: Significant dehydration. Performance is already being affected. You're losing pace whether you feel it or not.
Above 15%: You're in a hole. Catching up is difficult mid-run. This is where bonking, cramping, and GI distress live.

For example, if your average heart rate for the first 45 minutes of a long run at 5:30/km pace is 148 bpm, and it's sitting at 165 bpm at the same pace 90 minutes in, that's an 11.5% increase. You're dehydrating faster than you're replacing fluid.

How to track drift during a run

You don't need any special equipment — just your Garmin or Apple Watch and a basic understanding of your zones.

Method 1: Compare halves in your watch app

After your run, open Garmin Connect or the Apple Fitness app and look at the heart rate graph. Split the run mentally into the first half and the second half. Compare average heart rate for each half at similar paces.

If the second half is 10+ beats higher at the same pace, drift is significant.

Method 2: Use lap data

Set your watch to auto-lap every kilometre or mile. After the run, compare heart rate per lap against pace per lap. Look for laps where pace is steady but HR has climbed. That's where drift kicked in.

Method 3: Real-time HR alerts

Set a heart rate alert on your watch for 10 beats above your expected steady-state HR. When it goes off, that's your cue to drink — not to slow down. Slowing down treats the symptom, not the cause.

Why drift is a better signal than thirst

The standard advice is "drink to thirst." And for short runs under 60 minutes, that works fine. But for long runs, races, and hot conditions, thirst is a lagging indicator.

By the time you feel thirsty, you've typically lost 1–2% of your body weight in fluid. At 2% loss, your pace is already degrading by 4–6%. Your heart rate has been climbing for 20+ minutes. You're playing catch-up.

Cardiac drift gives you a 15–20 minute head start on thirst. It's an early warning system that's already strapped to your wrist.

This is especially true in heat. Research shows that sweat rates can double in temperatures above 25°C compared to 15°C. Your thirst mechanism doesn't scale proportionally, but your heart rate response does.

What to do when you spot drift

Catching drift early changes what you can do about it.

If drift is 5–10% (early warning)

Take 150–200ml of fluid immediately
Add sodium if you're drinking plain water — 300–500mg per 500ml
Shorten your drinking intervals from every 20 minutes to every 10–15 minutes
Continue at pace — you're ahead of the problem

If drift is 10–15% (active dehydration)

Take 200–300ml of fluid with electrolytes
Reduce pace by 10–15 seconds per kilometre to reduce sweat output
Switch from water to an electrolyte drink if available
Accept that the back half of this run will be slower — the priority is limiting damage

If drift is above 15% (damage control)

Stop and drink 300–500ml over 5 minutes
Walk if necessary — pushing through significant dehydration increases your risk of heat illness
Reassess whether you should continue at race effort or convert to a training run
After the run, calculate your sweat rate so you can prevent this next time

The sodium factor most runners miss

Drift isn't just about fluid volume. It's about what's in the fluid.

When you sweat, you lose sodium. Sodium helps your body retain water in your bloodstream. If you replace fluid without sodium, much of it passes straight through — you urinate it out or it sits in your stomach without being absorbed.

This is why runners who drink plenty of water can still experience cardiac drift. They're hydrating, but they're not replacing the sodium that keeps fluid in their blood plasma.

The fix is straightforward: add 300–800mg of sodium per litre of fluid during runs over 60 minutes. Electrolyte tablets, salt capsules, or a properly formulated drink mix all work. The key is that some sodium is present — the exact amount depends on your personal sweat sodium concentration.

Most runners lose between 400 and 1,800mg of sodium per litre of sweat. That's an enormous range, and it's why generic "add a pinch of salt" advice falls short. Your number is specific to your physiology.

How heat changes everything

Cardiac drift is present in all conditions, but heat amplifies it dramatically.

In cool weather (10–15°C), you might see 3–5% drift over a 90-minute run. In summer heat (28–35°C), the same run at the same pace can produce 12–18% drift. Your sweat rate is higher, your core temperature rises faster, and your cardiovascular system is under dual stress — cooling you AND fuelling your muscles.

If you're training through summer for a fall marathon, this matters. Your long runs in July and August will show more drift than the same runs in October. That doesn't mean you're less fit — it means heat is taxing your hydration harder.

The practical takeaway: your hydration plan for summer training and your hydration plan for a fall race should not be the same. Conditions change, and your fluid needs change with them.

Using drift data to build a better hydration plan

Here's where cardiac drift becomes genuinely powerful — not just as a warning signal, but as a planning tool.

Step 1: Establish your baseline

Run 60–90 minutes at an easy, steady pace in moderate conditions. Note your average heart rate for the first 30 minutes. This is your baseline.

Step 2: Track drift across conditions

Over 3–4 long runs, record your drift at different temperatures, paces, and hydration strategies. You'll start to see patterns: more drift in heat, more drift when you skip electrolytes, less drift when you drink earlier.

Step 3: Calibrate your fluid intake

Adjust your drinking volume and timing until you can keep drift below 8–10% on a 90-minute run. That's your personalised hydration rate — and it's far more accurate than any generic "drink X ml per hour" recommendation.

Step 4: Test it at race pace

Your race pace produces more heat and more sweat than your easy pace. Run a portion of a long run at race pace and check drift. If it spikes, your hydration plan needs to account for the higher intensity.

Your watch gives you the data — Sweatr tells you what to do with it

Cardiac drift is one of dozens of signals your Garmin or Apple Watch captures every run. But unless you sit down after every session with a spreadsheet, most of that data goes unused.

Sweatr pulls your heart rate, pace, and environmental data automatically and flags when drift suggests you're dehydrating. It calculates your personalised fluid and sodium targets based on your actual sweat data — not generic ranges — and adjusts your hydration plan as conditions change.

If your watch is the sensor, Sweatr is the intelligence layer that turns the reading into action.

Key takeaways for your next long run

Cardiac drift isn't a problem to fix — it's a signal to use. Your watch is already tracking it. The difference between runners who bonk at mile 20 and runners who finish strong often comes down to whether they caught the early warning signs and adjusted.

Before your next long run:

Note your heart rate at 15 and 30 minutes as your baseline
Check it again at 60 and 90 minutes at the same pace
If drift exceeds 10%, drink more and add sodium
After the run, calculate your sweat rate (pre-run weight minus post-run weight plus fluid consumed)
Adjust your plan for the next long run based on what you learned

Every long run is a data point. Stack enough of them, and you'll have a hydration plan built on your body — not someone else's averages.