Training
Heart rate, pace, or power: what should actually govern your training?
The three signals are not competing versions of the same measurement. Here is what each one physically is, which session each should run, and what it means when they stop agreeing.
Govern each session with the most direct measure of what you are producing — power on the bike, pace on the run when the ground is flat — and read heart rate as the second opinion on what that output is costing you. That is the short answer, and it works because the three numbers are not rival versions of the same measurement. Power and pace are outputs: what you put into the pedals or the ground. Heart rate is a cost: what your body is spending to produce that output. Asking which is best is like asking whether the speedometer or the fuel gauge is the better instrument. You steer with one and watch the other, and if you only ever look at one you will eventually be surprised.
The argument is about two different measurements
Almost every "heart rate vs power vs pace" argument online is two people describing different halves of the same session and assuming the other one is wrong.
External signals — power and pace — measure work leaving your body. Watts at the crank, minutes per kilometer over the ground. Immediate, drift-free, and indifferent to how you feel: 250 watts is 250 watts whether you are fresh or wrecked.
Internal signals — heart rate, and to a degree perceived effort — measure what that work costs. Heart rate is your cardiovascular system's response to the demand you placed on it, filtered through heat, hydration, sleep, stress, illness, caffeine, and accumulated fatigue.
That difference explains every strength and every failure of both. You want the exact, indifferent number as your target, and the sensitive one as your report on how the day is actually going.
Power: the most direct number you can get
A power meter measures mechanical output — force on the pedals, times how fast they are turning. Nothing is inferred. Four properties make it the best training signal in endurance sport, on the bike:
It is instant. Power responds the second you push. There is no delay to work around, which is the entire reason short intervals should be steered by power.
It does not drift. Two hundred and fifty watts in the third hour is the same mechanical output as in the first. The cost of producing it climbs; the number does not move.
It is terrain-proof. On a rolling course, pace tells you about the gradient and heart rate is still catching up from the last climb. Power is the only signal that stays honest through a ninety-second rise.
Two honest limitations. First, for most people it is bike-only. Running power meters and footpods exist, but different devices disagree with each other and there is no shared definition of what running power means the way there is for watts at a crank. A running power number is useful against itself, on one device. Treat it as a private currency.
Second, and more important: power is blind to cost. Two hundred and fifty watts on a cool morning after eight hours of sleep and 250 watts on day three of a heat wave after a red-eye flight are the same number and completely different events. Power will let you hold a target that is quietly taking you apart, and it will never once mention it. That is the job heart rate does.
Pace: honest on flat ground, a liar on hills
Pace is running's external signal, and it is free — every GPS watch has it. On a track, or on flat road in still air, pace is genuinely excellent: direct, immediate, comparable across seasons, and it maps straight onto the thing you are actually trying to do in a race.
Off flat ground it degrades fast, and it does not warn you.
- Hills. The same effort uphill produces a much slower pace and downhill a much faster one, with more muscle damage attached. A pace target on rolling terrain means running too hard up and too easy down.
- Wind. A headwind is a hill you cannot see.
- Surface. Trails, sand, snow, and grass all cost more per kilometer than tarmac at the same effort.
- Heat and altitude. Both raise the cost of a given pace without changing the pace.
- GPS noise. Instant pace bounces under tree cover and between buildings. Lap pace over a kilometer is far more trustworthy than the number flickering on your wrist, and a track beats both. Treadmill speed is a factory setting, not a measurement.
Grade-adjusted pace helps and is worth using: it estimates what your effort would have produced on the flat, which makes hilly runs comparable week to week. But it is a model, not a measurement — directionally right on moderate gradients, and progressively less reliable as the grade steepens, especially on descents, where the metabolic saving is much smaller than the time saving.
The practical rule: pace governs on flat, measured ground. On hills and trails, stop reading it. Run by effort or heart rate, and measure the session in minutes rather than kilometers.
Heart rate: the only signal that sees the cost
Heart rate is the only one of the three that responds to heat, dehydration, poor sleep, an oncoming cold, or four weeks of training you have not absorbed. That sensitivity is the entire value, and the source of every complaint people have about it. Four limitations, all real, none disqualifying:
It lags. After a change in effort, heart rate takes roughly thirty seconds to a couple of minutes to settle, longer when you are cold. A three-minute interval is essentially over by the time it has arrived, so steering short work by heart rate means going too hard through the first half of every rep, chasing a number that has not caught up.
It drifts. Hold a fixed output for a long time and heart rate climbs anyway — the classic cardiac drift, driven by rising core temperature, plasma volume loss from sweating, and simple duration. A heart rate that is correct for an easy ride at minute 20 is describing a harder effort at minute 150.
It gets suppressed. Under heavy accumulated load, athletes commonly find they cannot get heart rate up at all: legs heavy, output down, heart rate lower than usual for the effort. A low heart rate is not automatically good news. Read it alongside what you were able to produce.
It is noisy day to day. Swings of several beats at the same output are normal from sleep, caffeine, dehydration, room temperature, race nerves, or a hard conversation an hour earlier.
Two notes on measurement, both properties of the method rather than of any brand. Optical wrist sensors are good at steady efforts and least reliable exactly where you want precision — the first minute of hard intervals, and in the cold, where they sometimes settle onto your cadence instead of your pulse. A chest strap is meaningfully more trustworthy for interval work. And zones built from an age formula such as 220 minus age carry enormous individual spread: two athletes the same age can have maximum heart rates twenty or more beats apart. Zones cut from your own measured threshold effort beat a formula every time.
Which signal should govern which session
The mature answer is not to pick a team. It is to let the most direct available signal run each session, and read the other one as the cost report.
| Session | Governed by | Sanity-check with | Why |
|---|---|---|---|
| Bike intervals | Power | HR at the end of each rep | HR arrives too late to steer a short rep |
| Run intervals, track or flat road | Pace | HR at the end of each rep | Same lag; pace is honest on measured flat ground |
| Long steady ride | Power, with an HR ceiling | HR drift across the ride | Cost climbs through a long session even when watts do not |
| Long steady run, flat | Pace, with an HR ceiling | HR drift across the run | Same, and fueling problems show up in HR first |
| Hilly or trail run | Effort or HR | Time, not pace | Pace on a 10% grade describes the hill, not the athlete |
| Recovery session | HR ceiling and honest feel | Nothing | The point is low cost; the output number is irrelevant |
| Long-course bike leg | Power | HR | Power stops you overcooking hour one; HR says what today can afford |
| Racing in heat | HR ceiling over the pace or power target | Pace and power | The same output costs more when you cannot shed heat |
| Sprint race or 5 km | Pace, power, or feel | Nothing | Too short for drift, too fast for HR to keep up |
| Swim | Pace off CSS | Stroke count and feel | Neither power nor HR reads usefully in water |
The pattern: short and hard is governed by output. Long and steady is capped by cost. When the terrain corrupts the output signal, fall back to cost.
Aerobic decoupling: the read that needs both
One genuinely useful number exists only because you have both kinds of signal, and most athletes never look at it.
Take a long, steady, single-intensity session and split it in half. Work out the ratio of output to heart rate — watts per beat, or pace per beat — for each half, and compare. If the second half needed noticeably more heartbeats to produce the same output, you decoupled. The widely used cutoff is around 5%, a convention people settled on rather than a constant anyone measured.
Low decoupling means your aerobic system held its shape for the whole duration. That is close to what people mean by base fitness, and it improves over months of consistent endurance work rather than weeks.
The caveats matter as much as the number. Heat, dehydration, under-fueling, and starting too hard all produce decoupling that says nothing about your fitness. Compare like with like: similar duration, intensity, temperature, and food. The same route year over year is a decent read; a hot July long ride against a cool October one measures the weather.
Five rules that survive real training
1. Never chase heart rate in the first ten minutes. It has not arrived yet. Riding harder to drag it into the zone at minute four means spending the next hour doing a tempo effort with an endurance heart rate, and wondering later why an easy ride left you flat.
2. Set intervals by output, read heart rate afterward. Hit the watts or the pace, let heart rate do whatever it does, then check where it ended each rep. Rising end-of-rep heart rate across a set is normal. Falling end-of-rep heart rate with falling output is a reason to stop.
3. Cap long steady work by heart rate, and treat the drift as information. Shedding a few watts in hour three to hold the same heart rate is ordinary. Shedding a lot in hour one is a message about heat, fueling, or how much you have absorbed this week.
4. In heat, heart rate wins the argument. The same output costs more when your body is also trying to dump heat. Racing to a pace number on a hot day is the most reliable way to end up walking the last 10 km.
5. Choose the governing signal before you start. Switching mid-session to whichever number currently looks better is not training by data. It is negotiating.
Underneath all five sits one requirement: the zones have to be cut from a threshold that is still true. A fraction of a stale number is a stale number. PaceBeats seeds your zones and critical swim speed from your imported training history and proposes threshold updates as your real efforts move, so the zones stay attached to your current fitness rather than to a test you did last winter.
When the signals disagree for days, the disagreement is the message
One session where heart rate sits several beats high at your usual pace is noise. It was hot, or you slept badly, or you had coffee, or you are nervous about the session. Ignore it.
The same gap, day after day, with no weather to blame, is not noise. That pattern is the most useful thing your data does, and it only exists because you were tracking cost and output separately. It shows up in two shapes:
High cost for normal output. Usual pace, usual watts, heart rate consistently elevated and perceived effort climbing. Typically accumulating fatigue, an infection incubating, dehydration, or life stress that your training plan does not know about.
Suppressed cost with falling output. You cannot get heart rate up, the legs are heavy, and the numbers you used to hit are simply not there. This is the deeper version and the one worth taking seriously.
Both are reasons to take days off, not to push through and find out. This is also where a training load chart will mislead you: TSS, CTL, and ATL only see the training you did, not what it cost you, so two identical charts can belong to athletes in completely different states. If the disagreement has been running for a week or more, read the signs of overtraining before you read your next training plan.
Swimming, where neither signal works
Swimming is the exception that explains the rule. There is no practical power meter for the water, and heart rate is awkward to read mid-swim — optical sensors are unreliable submerged, and a reading taken at the wall describes what happened a few seconds ago.
So swimming governs by pace, expressed against your critical swim speed. It works precisely because water is a stable medium: no hills, no wind, no descents, so pace stays honest in a way it never does on land. The details are in critical swim speed, explained.
If all you own is a watch
You are not missing much on the run. Pace on flat ground plus heart rate on hills covers almost everything a runner needs.
The bike is where the gap is real. Riding endurance by heart rate and perceived effort works fine. Riding short intervals by heart rate does not, because of the lag — you overshoot the start of every rep and never quite know what you produced. If you buy one thing for triathlon, a power meter or a smart trainer is the highest-value purchase, well ahead of another watch.
Whatever you own, the number that matters most is the threshold your zones are cut from. Watch-estimated thresholds are a reasonable starting point with knowable limits, worth understanding before you build a season on one — see what your watch's FTP estimate really means.
The signals were never in competition. Output tells you what you did. Heart rate tells you what it cost. Train to the first, listen to the second, and pay real attention on the days they stop agreeing.
Questions athletes ask
Should I run by pace or heart rate?
Both, for different sessions. Run intervals and race-pace work by pace, on a track or flat road, because heart rate takes thirty seconds to a couple of minutes to catch up with a change in effort and short reps are over before it arrives. Cap long steady runs with heart rate as well as pace, because the cost of a fixed pace climbs through a long session as you heat up and dehydrate. On hills and trails, ignore pace entirely — it describes the terrain more than the athlete — and run by heart rate or effort, measuring the session in minutes rather than kilometers.
Do I need a power meter for triathlon?
No, but it is the highest-value piece of equipment for the bike after the bike itself. Power is instant, does not drift over a long ride, and stays accurate on hills and in wind, which makes it the only signal that can properly steer short bike intervals — heart rate lags too much to do that job. You can train endurance perfectly well on heart rate and perceived effort. Where you genuinely lose out without power is interval precision and pacing the bike leg of a long-course race, where holding a set output for the first hour is what protects the run.
Why is my heart rate high at my usual pace?
For a single session, the usual causes are heat, dehydration, poor sleep, caffeine, a stressful day, or the start of an illness, and it is not worth worrying about. Elevated heart rate at your normal pace for several days in a row, with no weather to explain it and rising perceived effort, is a different thing: it usually means accumulated fatigue you have not absorbed, an infection, or life stress your plan does not know about. The response is easier days or days off, not pushing through. The opposite pattern — heart rate that will not rise, with output falling and legs feeling heavy — is a more serious sign of being deep in a hole.
What is cardiac drift?
Cardiac drift is the slow upward climb of heart rate during a long session at constant output. Your core temperature rises, sweating reduces plasma volume, so each beat moves slightly less blood and the heart compensates by beating more often. It means a heart rate that is correct for easy riding at minute 20 is describing a harder effort at minute 150, so a single fixed heart rate cap gradually turns a long ride into an easier one. A little drift on a long session is normal. A lot of drift early is usually heat, under-fueling, dehydration, or starting too hard.
What is aerobic decoupling and how do I measure it?
Aerobic decoupling is how much more your heart has to work to hold the same output late in a session compared with early. Take a long, steady, single-intensity ride or run, split it in half, and compare the ratio of output to heart rate — watts per beat, or pace per beat — between the halves. The commonly used cutoff is around 5%, which is a convention rather than a measured constant. Low decoupling means your aerobic system held its shape for the whole duration. Only compare sessions with similar duration, intensity, temperature, and fueling, because heat and under-fueling produce decoupling that says nothing about your fitness.
Next step