You head out for a tempo run. Twenty minutes at "comfortably hard," whatever that means. Two minutes in, your watch says 168 bpm and you are breathing through your mouth. Ten minutes in it says 176 and you are negotiating with yourself about cutting it short.
Was that a tempo run, or did you accidentally do a race effort? And which zone was it supposed to be, anyway? Your watch has a zone chart, your training plan says "tempo," and the two of them don't quite agree.
The honest answer is that tempo has never had one clean heart rate definition, because tempo was never really a heart rate concept to begin with. It was a pace concept, and later a physiology concept, and the heart rate that goes with it depends on how fit you are, how you measure your zones, and what kind of tempo you're doing.
Here's how to make sense of it, and how to run the session so it does what it's supposed to do.
TL;DR: A tempo run is a sustained effort at or just below your lactate threshold, the intensity you could hold for roughly 40 to 60 minutes in a race. In heart rate terms that lands around 85 to 90% of your maximum heart rate, or roughly 80 to 88% of your heart rate reserve, which is the top of Zone 3 into Zone 4 on most five-zone charts. If your watch puts tempo in Zone 2, your zones are probably set with an underestimated max heart rate. If it puts you in Zone 5, you're running it too hard. The talk test is more reliable than the number: at true tempo you can speak about three to five words per breath, and you can hold the effort for half an hour without slowing down.
YouTube: Related video
What a tempo run actually is
Tempo is one of those words that got stretched until it stopped meaning much. In the original coaching sense, popularised through Jack Daniels' training paces, a tempo run was a sustained run at what he called threshold pace: roughly the pace you could race for an hour. Not a sprint, not a jog, but a pace that feels sustainable right up until it suddenly isn't.
The physiology underneath it is lactate threshold, specifically the second threshold. As you run harder, blood lactate rises slowly at first, then more steeply. The point where it starts climbing steeply, faster than your body can clear it, is your second lactate threshold, often called LT2 or maximal lactate steady state. Above it, you have minutes. Below it, you can keep going for a long time.
That's the whole point of tempo training. You're parked just under the line where lactate accumulation starts to outrun clearance, which is a strong stimulus for improving the clearance machinery itself: more mitochondria, more lactate transporters, better fatigue resistance at a given pace.
A 2026 meta-analysis on the moderators of metabolic threshold adaptations found that threshold-focused training does shift these markers, but the size of the effect depends heavily on how close to threshold you actually train and how much total work you accumulate. In other words, the session only works if you're in the right place. Too easy and you're just adding easy volume. Too hard and you're doing a VO2 max session with extra fatigue.
So which zone is tempo?
Let me give you the numbers, then explain why they keep disagreeing with your watch.
| Zone model | Tempo heart rate | What it feels like |
|---|---|---|
| % of max heart rate | 85–90% | Hard but controlled; breathing deep and rhythmic |
| % of heart rate reserve | 80–88% | Same effort, different arithmetic |
| RPE (1–10) | 7 | "Comfortably hard" is accurate, not a euphemism |
| Talk test | 3–5 words per breath | Short sentences, no paragraphs |
| Typical five-zone label | Top of Zone 3, mostly Zone 4 | Depends entirely on your zone setup |
The reason you see tempo described as "Zone 3" in one place and "Zone 4" in another is that five-zone models are not standardised. Some are built on percentage of max heart rate, some on percentage of heart rate reserve, some on lactate, some on ventilatory thresholds. A number that means Zone 4 in one chart is Zone 3 in the next.
Apple Watch uses a max-heart-rate-based five-zone model by default, with the zones divided around an estimated max heart rate that it derives from your age, weight, and workout history, or from a manual value you enter in Settings. That estimate is the weak link. If your real max heart rate is ten beats higher than the estimate, every zone boundary is shifted down, and a genuine tempo effort will show up as Zone 3 or even "too hard" when it's exactly where it should be.
This is the single most common reason people think their watch is broken. It usually isn't. The zones are just anchored to a number that was never measured.
If you want your zones to mean something, do a proper max heart rate test or use a field test to set a threshold heart rate directly, then customise the zones in the Watch app. It takes ten minutes and fixes months of confusing data.
How to find your tempo heart rate without a lab
You don't need a treadmill and a finger prick. You need half an hour and some discipline.
The 30-minute time trial
Warm up for ten to fifteen minutes, then run thirty minutes as hard as you can sustain evenly, without blowing up. The average heart rate over the final twenty minutes is a good approximation of your threshold heart rate. This is an old coaching method, not a lab measurement, but it is close enough for pacing decisions.
Two caveats. Don't start too fast; if your first five minutes are the hardest, you'll finish the test at a lower heart rate than your true threshold and set your zones too low. And do it rested, not the day after a hard session, or you'll be measuring fatigue rather than fitness.
The talk test
This is the one I'd trust most if you're new to this, because it needs no equipment and no arithmetic.
Run progressively harder. At easy pace you can hold a conversation. At tempo, you can speak in short phrases of three to five words before you need another breath, and you can keep doing that for twenty or thirty minutes. If you can only get one or two words out, you've gone past threshold into VO2 max territory. If you can speak in full sentences, you're below it.
The talk test tracks the ventilatory threshold reasonably well in practice, and it has a useful property your watch doesn't: it responds to the actual physiological state you're in today, not to a number derived from last month's data. On a hot day or after a bad night, the same heart rate corresponds to a harder effort. Your breathing tells you that. Your zone chart doesn't.
Watch for cardiac drift
Heart rate rises during a sustained run even when pace and effort stay constant. This is cardiac drift, driven by rising core temperature, fluid loss, and a slow decrease in stroke volume that gets compensated for by a higher rate.
Over a thirty-minute tempo in cool conditions, drift might be three to five beats. In the heat, or late in a long session, it can be considerably more. This matters because chasing a fixed heart rate ceiling during a tempo run pushes you to slow down as the run goes on, which defeats the purpose. You end up running the last ten minutes of a tempo at a pace that isn't tempo anymore.
The fix is straightforward: set the pace or effort at the start based on the talk test, let the heart rate drift upward within a band of about five beats, and don't fight it. If the drift is much bigger than that, heat or dehydration is the story, and you should adjust the session rather than the zones.
Three ways to run tempo (and which heart rate each one uses)
Tempo isn't one workout. It's a family of them, and the heart rates differ slightly between members.
Continuous tempo. Twenty to forty minutes in one block at threshold. The classic. Heart rate settles into the 85–90% band after a few minutes of lag and drifts up slowly. Best for runners with a solid base.
Cruise intervals. Three to five repeats of six to ten minutes at threshold with one to two minutes of easy jogging between. Total time at threshold is similar, but the recovery keeps heart rate and form from degrading. This is the version I'd recommend for most people, because it lets you accumulate quality without the late-session breakdown that turns tempo into a race.
Progressive tempo. Start ten to fifteen beats below threshold and build to it over the final third. Useful when you're tired, in heat, or coming back from a break, because it gives you a ramp instead of a cliff.
Notice that none of these is defined by a heart rate. The heart rate is a consequence of the pace and the day. That's why the session should be paced by feel and confirmed by data, not driven by a number on your wrist.
The mistakes that make tempo stop working
Running it too fast. The most common one. If you finish a tempo run wrecked, unable to do an easy jog the next day, or with your heart rate pinned at 92% of max for the last ten minutes, you turned it into a threshold-plus session. You'll get some fitness from it, and you'll also accumulate fatigue that compromises the rest of your week. Tempo should leave you tired but functional.
Running it too slow. The opposite error, and increasingly common now that everyone has been told to do Zone 2. Tempo is not Zone 2. If you can hold a full conversation for the entire block, you're doing an easy run with a fancy name. That's fine as training, but it isn't the threshold stimulus you were aiming for.
Doing it too often. Most runners get the majority of the benefit from one threshold session a week, occasionally two in a high-volume block. The 2025 analysis of training intensity distribution in marathon runners across performance levels is a useful reality check here: faster runners tend to concentrate their hard work into a smaller number of clearly hard sessions and keep everything else genuinely easy. The middle ground, where every run is moderately hard, is where progress stalls.
Doing it on a bad recovery day. If your HRV is well below your baseline, your resting heart rate is up, and you slept badly, a threshold session is the worst choice available. It's hard enough to add fatigue and not hard enough to be worth digging for. Move it, or swap it for an easy run. Your morning recovery check exists exactly for this decision.
What your watch can tell you after the fact
Once the run is done, the data becomes genuinely useful, because you're no longer trying to pace off a lagging signal.
Time in zones. Look at how much time you spent above 90% of max. A well-executed thirty-minute tempo should be mostly in the 85–90% band with a short ramp at the start. A big block above 92% means you overcooked it.
Heart rate at a given pace, over months. This is the real progress marker. If the same pace now costs you fewer beats than it did eight weeks ago, your threshold is moving. This is also why heart rate drift during steady runs is worth tracking; it's the same signal in a different format.
Heart rate recovery after the session. How fast your rate drops in the first minute after you stop is a decent proxy for fitness and a useful check on how much the session cost you.
Your next-morning numbers. A tempo run should produce a small, temporary bump in resting heart rate and a modest dip in HRV that resolves within a day or two. If it takes four days to come back, the session was too hard or your base isn't there yet.
That last point is where a tool like Century AI fits in without much effort on your part. It reads the recovery data your watch already collects, puts it next to your training, and gives you a daily score so you can see whether the tempo session landed the way you intended. Not a replacement for judgment, just a second opinion that doesn't forget what last Tuesday looked like.
Where tempo fits in a week
A simple, sustainable structure for most recreational runners doing three to five runs a week:
- One tempo or threshold session, twenty-five to forty minutes of quality total
- One longer easy run
- Two to three genuinely easy runs, conversational pace
- Optional: strides or short hill reps at the end of an easy run, which build speed without adding much fatigue
That gives you roughly 80% easy, 20% hard, which is the distribution most of the evidence supports. The tempo session is the one place in the week where "comfortably hard" is the target, and everything else should feel almost embarrassingly slow by comparison.
If you're training for a specific race, tempo becomes more specific as you get closer to it. Early in a block, cruise intervals at threshold. Later, continuous tempo at goal race pace or slightly faster. In the final couple of weeks, less of it, because you're sharpening rather than building.
The short version
Tempo heart rate is not a fixed number, and anyone who gives you one without asking about your max heart rate, your zone model, and the weather is guessing.
Aim for the effort you could hold for about an hour in a race. Confirm it with the talk test: three to five words per breath, sustainable for twenty to forty minutes. Expect it to land around 85 to 90% of your max heart rate, which is the top of Zone 3 into Zone 4 on a properly calibrated watch. If your zones disagree with your breathing, trust your breathing and fix your zones.
And if you finish a tempo run and can't remember what "comfortably" was supposed to mean, you already know what to change next week.
Century AI helps you understand your body with a daily health score, recovery score, and sleep insights — using the watch you already wear.
