Heart-Rate Zones vs Power Zones: Why They Differ and How to Use Both

Most structured training is organised into zones — bands of intensity from easy to maximal — and triathletes end up with two zone systems: heart-rate zones, and power zones (on the bike) or pace zones (on the run). The trap is assuming they're interchangeable. They're not.

The reason is simple but fundamental: heart rate measures your body's response to effort, while power and pace measure the effort you're producing right now. Those are different quantities, so a session that sits squarely in your power "zone 2" can drift into heart-rate "zone 3" by the end — same effort, different zone. A heart-rate zone 2 and a power zone 2 are simply not the same thing.

This page is about that relationship — how the two zone systems differ, how to set each up, and how to reconcile them when they disagree. It's a companion to the broader question of which metric to train with in the first place; here we assume you'll meet both and want to use their zones intelligently.

Heart-rate zones reflect your true physiological cost, which is exactly why they're valuable — and why they behave the way they do. Because HR is a response, it's affected by sleep, heat, hydration, caffeine, stress and accumulated fatigue, and it has two built-in quirks:

• Lag. Your heart rate takes a minute or two to catch up to a change in effort. Start a hard rep and your HR is still climbing when the rep is half over.
• Drift. Over a long session, heart rate creeps upward at the same effort (cardiac drift), especially in heat — so a steady ride that started in one HR zone ends in a higher one.

That makes heart-rate zones excellent for long endurance work, for long-course racing where heat and fatigue matter, for tracking aerobic fitness over months, and for spotting overtraining (a rising resting HR is a red flag). They're poor for anything short — reps under a few minutes end before HR settles — and unreliable in cold open-water swims.

Power (cycling watts) and pace (running min/km) zones measure output directly, so they have the opposite properties: instant and drift-free. The number tells you exactly what you're doing this second, regardless of heat, fatigue or how you feel.

That makes power/pace zones ideal for:

• Short intervals where HR lag would make you overshoot.
• VO2 and threshold work, where hitting a precise band matters.
• Hills, where HR is still rising as the climb ends but watts show the real effort instantly.
• Race-day pacing on the bike, where holding a steady sub-threshold power protects your run.

The honest limitation is the mirror image of HR's: power and pace tell you the effort but not the cost. A power zone 2 on a hot, tired day is harder on your body than the same watts fresh — which is exactly the gap the two systems together reveal. For the underlying number on the bike, see FTP explained and cycling watts explained.

Zones are only as good as the anchor you build them from, and each system needs its own:

• Heart-rate zones are built from your threshold heart rate, estimated from a field test (for example, your average HR over a sustained hard effort) — not the "220 − age" formula, which research on maximal heart rate shows is wrong for many individuals by 10–20 bpm. Some athletes use maximum HR or heart-rate reserve instead; the key is to base it on your numbers. See heart-rate zones explained.
• Power zones are built from your FTP (commonly a 20-minute test times about 0.95) — the method and caveats are in FTP explained.
• Pace zones are built from a recent threshold pace or race result; the pace calculator turns that into bands.

Two honest points: zone boundaries are organisational ranges, not sharp biological walls, and different systems (3-zone, 5-zone, 7-zone) draw them in different places — so always label which model you're using. And re-anchor every season: last year's zones aren't this year's.

Here's where using both pays off. On a normal day, your power/pace zone and your heart-rate zone roughly agree. On an abnormal day they don't — and the disagreement is the information.

The classic example: you're riding your prescribed power zone 2, the watts feel fine, but your heart rate is 10–15 bpm higher than usual and creeping toward zone 3. That gap is your body telling you something — heat, dehydration, poor sleep, the start of an illness, or accumulated fatigue. The watts alone would have missed it; the heart rate alone might have made you back off a genuinely appropriate effort. Together, they let you make a smart call: ease off, because today the same output is costing you more.

It works the other way too — if your HR won't climb into its usual zone despite solid watts, you may be over-tired or under-fuelled. Treat a persistent HR-vs-power mismatch as a prompt to check your recovery, not as a number to override. The sleep and recovery guide covers what those signals mean.

The practical resolution isn't to pick one system — it's to let each do what it's best at within a single session:

1. Set the workout target by power or pace. For intervals and threshold work, the instant, drift-free metric keeps you honest — hit the band from the first second.
2. Add a heart-rate ceiling as a safety check. Decide in advance that you won't push past a certain HR even if the watts say you can, so a bad day doesn't turn a session into a hole.
3. Lead with heart rate for the easy stuff — warm-ups, cool-downs and long aerobic segments, where capturing the true cost (and keeping easy genuinely easy) matters more than precision.

Across a brick, heart rate also gives you one continuous metric that spans bike and run, where your power and pace zones are on different scales. This hybrid is why most experienced age-groupers wear both — not out of gadget love, but because the two zone systems answer different questions.

The two-system picture looks a little different in each sport, which is worth planning for:

• Swim: you'll usually work to pace and perceived effort (and stroke rate), since heart rate is hard to read reliably in the water and power meters are niche. Zones here are looser by necessity.
• Bike: the richest case — power for precision plus heart rate for cost. If you only have one, heart rate still paces you well.
• Run: pace for precision plus heart rate for cost, with the same trade-offs as the bike; on hilly runs, effort and HR can be more useful than raw pace.

Because the metrics and scales differ by discipline, don't expect a single "zone" to mean the same thing across all three. What carries over is the principle: lead with the output metric for precision, and use heart rate to check the cost — and keep most of your training genuinely easy, since the research on intensity distribution consistently favours a large base of low-intensity work whichever metric you watch.

You don't need everything at once — build up as your training gets more structured:

• Heart-rate zones need a heart-rate monitor. A wrist optical sensor is fine for easy endurance zones, but for intervals and precise zone work a chest strap is far more reliable — the heart-rate monitors and chest strap guides cover the difference.
• Power zones need a power meter on the bike, or a smart trainer that reports power indoors — see power meters for triathlon.
• Pace zones need nothing beyond a GPS watch you likely already own.

A sensible order for most triathletes is heart rate first (you can start today with almost any watch), pace next (also essentially free), and power on the bike later, once you're doing enough structured cycling to use it. The point isn't to own every sensor — it's to have a trustworthy anchor for whichever zones you're actually training to.

A few errors undermine zone training with either system:

• Treating a HR zone and a power zone as equivalent. They measure different things and won't match rep-for-rep — that's expected, not a fault.
• Building HR zones from 220 − age. It's inaccurate for many people; anchor from your own testing.
• Judging short reps by heart rate. HR lag means you'll overshoot — use power or pace for anything short.
• Chasing power/pace on a bad day while ignoring a sky-high heart rate that's begging you to ease off.
• Never re-testing, so you're training to zones that no longer fit your fitness.
• Over-precise boundaries. Zones are ranges; a single watt or beat either side of a line changes nothing.

Heart-rate zones and power/pace zones aren't rivals — they're two lenses on the same effort. Heart rate shows the cost (with lag and drift), power and pace show the output (instant and steady), and the same session lands in different zones on each. Anchor both from your own testing, lead with power or pace for precision and heart rate for the easy work and the fatigue check, and treat any disagreement between them as useful information.

Get that right and you stop arguing with your watch and start reading it — using each zone system where it actually shines.

From here: which metric to train with for the bigger decision, heart-rate zones explained and FTP explained for setting each anchor, threshold vs sweet-spot training for what to do in your zones, and data-driven training for turning it into faster racing.