What matters is that zone 3 cycling sits in the steady, demanding middle of the intensity spectrum: harder than endurance riding, but still controlled enough to repeat and build on week after week. In practice, it is the pace that helps you hold a useful effort on long climbs, rolling roads, and steady group rides without turning every session into a threshold test. This article breaks down what that zone means, how to set it correctly with heart rate or power, and when to use it so it improves fitness instead of just adding fatigue.
The key things to know before you ride tempo
- Zone 3 is usually called tempo or upper aerobic work, and it sits above easy endurance but below threshold.
- Garmin places heart-rate zone 3 at 70-80% of maximum heart rate; Coggan-style power zones put tempo at 76-90% of FTP.
- It feels steady and purposeful: you can speak in short phrases, but a full conversation starts to break apart.
- Tempo is useful for long climbs, time trials, gravel events, fondos, and races that reward steady pressure.
- The main risk is doing too much of it, too often, and ending up tired without getting the full benefit of either easy riding or hard intervals.
- The best results come when zones are tested, the workout has a clear purpose, and the rest of the week is not dragged into the same middle gear.
What zone 3 means on the bike
On the road, this is the effort that feels stable but clearly workmanlike. Your breathing deepens, your legs start to notice the load, and the ride no longer feels casual. Garmin’s zone guide places heart-rate zone 3 at 70-80% of maximum heart rate, while TrainingPeaks’ Coggan model puts tempo at 76-90% of FTP. Those numbers are not identical because different systems use different anchors, which is exactly why riders sometimes talk past each other when they say “zone 3.”
In practical terms, I think of it this way: if zone 2 is the pace you can hold while thinking about dinner, zone 3 is the pace where you stay focused on the bike. You can still speak in short phrases, but you would not want to give a long answer. If your FTP is 250 watts, a tempo interval will usually land somewhere around 190-225 watts, depending on the exact zone model you use and how fresh you are that day.
| Measure | Typical zone 3 range | How it feels in real life |
|---|---|---|
| Heart rate | 70-80% of max HR | Moderate, controlled, conversation becomes broken up |
| Power | 76-90% of FTP | Steady tempo pressure that is sustainable but not easy |
| Effort | About 3-4 out of 10 | You know you are working, but you are not on the edge |
That spread is the reason the same ride can feel perfect for one cyclist and a little too soft or too hard for another. Once the numbers are clear, the next question is whether this intensity is actually worth using, and for many riders it absolutely is.
Why cyclists use it instead of staying easy all the time
Tempo work has a specific job: it teaches you to produce useful power for longer without drifting into the tax of threshold sessions. That matters on long climbs, steady solo efforts, and races where the pace stays honest for hours. It is also one of the most practical intensities for recreational riders in the United States, where weekday trainer rides are often short and weekend outdoor sessions need to do a lot of work in one go.
The main benefits are straightforward:
- Muscular endurance - your legs learn to keep turning over pressure for longer.
- Pacing control - you get better at sitting on an effort instead of spiking above it.
- Race specificity - it matches the demands of long climbs, breakaways, gravel events, time trials, and fondos.
- Aerobic durability - you build the ability to stay productive when fatigue starts to creep in.
- Mental tolerance - the zone is demanding without being chaotic, which makes it useful for race preparation.
The catch is that it is easy to overdo. Too little tempo and you never really touch its benefits; too much and you accumulate fatigue that can flatten the rest of the week. That is why I use it as a tool, not as a default mood. The smartest riders are the ones who know when this zone solves a problem and when it just adds noise.
How to set the right numbers before you train
If the zones are wrong, the workout is already compromised. TrainingPeaks recommends setting zones from threshold-based data rather than guesswork, which is the right mindset whether you train by power, heart rate, or both. In other words, do not build your plan around a number you have not tested recently.
The most useful setup is usually this:
- Power - use FTP from a consistent ramp test, 20-minute test, or another repeatable threshold protocol.
- Heart rate - use maximum heart rate or lactate threshold heart rate, depending on the zone system your device uses.
- Perceived effort - use it as a reality check when heat, stress, or terrain make the data noisy.
Heart rate is useful, but it is slower to respond than power and more sensitive to heat, dehydration, caffeine, and accumulated fatigue. That makes it a better cross-check than an exact steering wheel. Power is cleaner for tempo work because it tells you what the bike is doing right now, not what your body has decided to reveal after a delay.
When I set zones for a cyclist, I prefer to test after a recovery day, then re-check the numbers every 6-8 weeks during a structured block or whenever the current targets stop matching the rider’s effort. A stale FTP or threshold HR can make a supposedly productive tempo ride turn into either an endurance spin or an accidental threshold workout. Once the numbers are right, the workouts become much easier to design.

Workouts that fit tempo riding
Tempo is not one workout. It is a family of sessions that all live in the same middle intensity range. The best version depends on the terrain, the time you have, and the event you are trying to support. For riders with limited time, I usually prefer a structured block over a vague “ride hard for a while” approach, because structure keeps the effort honest.
| Session | Example | Why it works | What to watch |
|---|---|---|---|
| Continuous tempo | 45-75 minutes steady in zone 3 | Builds durability and teaches you to sit on pressure | Do not let it drift into a race effort if the route gets hilly |
| Broken tempo | 3 x 15 minutes with 5 minutes easy between | Gives you quality without forcing one long uninterrupted block | Keep the recoveries truly easy, not sneaky threshold |
| Climbing tempo | 4-6 repeats of 6-10 minutes on a steady climb | Matches long uphill demands and improves pacing discipline | Do not surge over the top of each rep just because the grade changes |
| Progression ride | 90 minutes total, with the final 25-35 minutes in tempo | Teaches late-ride resilience and fatigue resistance | Fuel early so the last block is controlled, not desperate |
A good tempo workout should feel like pressure you can sustain, not like a series of small emergencies. If you are on the trainer, steady output is easier to control; if you are outside, wind, corners, and traffic can hide too much variation. In that case, I pay closer attention to average effort over each block than to moment-to-moment spikes. The final piece is dosage, because the same workout can help or hurt depending on how often you use it.
How much tempo work your week should carry
There is no universal quota, but there is a practical pattern. For most riders, one focused tempo workout per week is enough to start. If recovery is good and the rest of the week is not overloaded, a second session can make sense. Beyond that, I become careful, because the middle intensity starts eating into the freshness you need for either endurance volume or genuinely hard intervals.
My rule of thumb is simple:
- Newer cyclists - start with 15-30 minutes of actual tempo work in a session.
- Consistent recreational riders - build toward 30-60 minutes of tempo work in one ride.
- Time-crunched athletes - use tempo as the anchor of one midweek ride and one longer weekend ride, not every ride.
That does not mean tempo is bad. It means it should have a purpose. If your goal is to improve long climbs, gravel speed, or steady road events, tempo belongs in the plan. If your goal is to sharpen high-end race power, too much of it can crowd out threshold and VO2 work. I would rather see one well-executed tempo session than three half-hard rides that leave the week feeling heavy and vague.
A useful test is this: if a tempo day leaves your next easy ride feeling strangely labored, the dose was probably too big. If you are still able to complete quality work two or three days later, the amount was probably about right. That leads directly to the mistakes that most often waste the effort.
Common mistakes that turn tempo into junk fatigue
The biggest mistake is also the most common: riding in the middle without knowing why. Cyclists do this on rolling group rides, on hilly commutes, and on trainer sessions where they keep nudging the power up and down instead of holding a clean target. The result is a ride that feels hard enough to matter but not focused enough to drive a specific adaptation.
- Using stale zones - FTP and threshold HR change, and old numbers quietly distort every session.
- Confusing tempo with threshold - zone 3 should be controlled; if you are hanging on, you have moved too high.
- Letting terrain fake the workout - average speed and average power can hide a ride full of spikes and coasting.
- Skipping fuel - tempo burns through carbohydrate faster than easy endurance, especially on longer rides.
- Training every group ride in the same middle gear - that is how riders end up tired but not especially fit.
- Ignoring heat and indoor drift - the same power can produce a much higher heart rate on a hot road or a poorly cooled trainer session.
TrainingPeaks notes that average power alone can misrepresent the stress of a hilly ride or a stop-and-go group session, and that is exactly the trap I see most often. The workout may look tidy on paper while the body experienced a mess. The fix is not to avoid tempo; it is to use it deliberately. A simple weekly template keeps those mistakes from becoming habits.
A simple week that keeps tempo useful
If I were building a practical week for a rider who wants better endurance without living at threshold, I would keep it clean: one easy endurance ride, one tempo session, and one longer ride that may include a tempo block late in the workout. Everything else stays genuinely easy or genuinely hard, not stuck in the middle.
For a rider with three rides per week, that can look like this: one 60-minute endurance spin, one 2 x 20 minute tempo workout, and one longer weekend ride with the final 20-30 minutes at tempo. For a rider with five or six rides per week, I would usually keep tempo to one main workout and let the other days support recovery, skills, or true endurance. That pattern gives you the benefit of middle-intensity work without letting it take over the calendar.Used this way, tempo is a sharp tool. It builds the ability to ride strongly for long stretches, but it does not replace endurance, threshold, or VO2 work. When the effort is calibrated, the dose is sensible, and the rest of the week stays disciplined, it becomes one of the most reliable ways to ride stronger without burning yourself out.