What Your FTP Number Is Actually Telling You (And What It Isn't)

Every indoor cyclist eventually gets obsessed with one number. FTP. You test it, you post it, you compare it to your teammates', and you build your whole season around it. That's not wrong — but it's incomplete. FTP is a snapshot, not a story. The real signal is in how your zones shift over weeks and months, not in the single number you see after one hard test.

FTP is a threshold, not a grade

Functional Threshold Power is the highest average power you can sustain for about an hour before fatigue forces you to back off. It's an estimate of your lactate threshold — the point where your body can no longer clear lactate as fast as you're producing it. Most riders test it with a 20-minute max effort and take 95% of that average as their FTP, since a true 60-minute test is brutal and rarely necessary.

Here's what trips people up: FTP is not a fitness score you're trying to maximize in isolation. It's a calibration tool. Every training zone you ride in — recovery, endurance, tempo, threshold, VO2max — gets set as a percentage of that number. If your FTP is wrong, every zone underneath it is wrong too, and your "easy" rides might actually be too hard, or your "hard" intervals not hard enough to produce adaptation.

Read your zones, not just your watts

A common mistake is treating all training zones as directly proportional to FTP in a fixed, linear way and never questioning it. In practice, your zones should reflect how your body actually responds:

Zone 2 (endurance) is where you build the aerobic base that everything else sits on top of. If you find yourself drifting into Zone 3 during what should be an easy ride, that's not toughness — it's a sign your FTP estimate might be stale, or that fatigue is masking your real threshold that day.

Zone 4 (threshold) is where FTP gets its name. Intervals here — 2x20 minutes, 3x15 minutes — are the classic way to nudge threshold upward over a training block.

Zone 5 (VO2max) intervals are shorter, harder, and improve your ceiling rather than your threshold directly. A rising VO2max without a corresponding FTP bump usually means the top end is improving faster than your sustainable power — which is common early in a build phase.

Retest on a schedule, not a feeling

Retesting FTP every 4-6 weeks during a structured block gives you a trend line instead of a single data point. A single ramp test on a bad sleep night can tank your number and send your zones sideways for a week. What actually matters is the direction of travel over two or three tests, not any individual result.

If you're using VeloWorkout for structured indoor sessions, this is exactly what the built-in FTP test and zone tracking are for — they're there so you're not guessing at intervals off a number from three months ago. Log the test, let the app recalculate your zones, and trust the recalculation rather than manually eyeballing what "feels right."

The metric that matters more than FTP: durability

A rider with a 280-watt FTP who can hold 250 watts for three hours is often stronger, race-day, than a rider with a 300-watt FTP who fades to 220 watts after ninety minutes. This is durability — your ability to hold power output as fatigue accumulates — and it doesn't show up in a 20-minute test at all.

Track it by comparing your power in the first 20 minutes of a long session against your power in the final 20 minutes. If that gap is shrinking over a training block, you're getting fitter in a way FTP alone will never show you. If it's growing, you may be overreaching without enough recovery between hard days.

Progress hides in the boring metrics

The exciting number is FTP. The useful numbers are quieter: your average heart rate at a fixed power output dropping over eight weeks (a sign of improving aerobic efficiency), your ability to repeat the same interval set at the same power with less perceived effort, your recovery heart rate after intervals coming down faster.

None of these show up on a single test day. They show up when you actually look back at a training log instead of just the most recent ride.

What to actually do with this

Don't retest FTP more than once every 4-6 weeks — daily fluctuation will just create noise. Do track your zones as ranges, not fixed numbers, and expect them to feel different depending on how recovered you are. Watch durability, not just peak power. And keep a log you actually review, because the trend across a month tells you far more than any single ride ever will.

Your FTP number gets you started. What you do with the weeks of data around it is what actually makes you faster.