FTP Testing for Triathletes: What It Is and Why It Matters When You Don't Have Hours to Train
If you're training for a triathlon with limited hours in the week, the bike is usually where those hours matter most. It's the longest leg by time in almost every race distance, and it's the discipline where structured, targeted training tends to produce the biggest gains for the time invested. FTP, functional threshold power, is the number that lets you train the bike properly instead of guessing.
What FTP actually is
FTP is an estimate of the highest power output you could sustain, in watts, for around an hour. It's not a maximum effort in the way a sprint is, it's closer to your sustainable hard limit, the pace you could hold in a serious 40km time trial or a hard bike leg without blowing up.
Once you know it, you can set training zones as a percentage of that number, meaning easy and hard stop being feelings and become numbers you can actually hit consistently, session after session, rather than pacing by how you happen to feel that day.
How it's usually tested, and why the standard test isn't perfect
The most common FTP test asks you to ride as hard as you can sustain for 20 minutes, then takes 95% of that average power as your estimated FTP. It's popular because it's short enough to fit into a normal session, unlike genuinely testing a full hour effort.
What the evidence says: research by Karsten and colleagues, published in Frontiers in Physiology in 2021, compared this 20-minute test against a more rigorous measure called critical power in 17 trained cyclists. The two measures correlated strongly, but the actual agreement between them was wide, varying from 19 watts lower to 33 watts higher than the more rigorous measure. The researchers were blunt about it: the two numbers generally should not be used interchangeably. They also noted that a 20-minute maximal effort involves a different, more central kind of fatigue than a longer sustained effort, which is part of why the 95% shortcut doesn't hold perfectly across different athletes.
How to use this: treat your FTP test result as a genuinely useful working number, not a scientifically precise one. It's accurate enough to set training zones and track whether you're improving over time, which is what actually matters for training. It's not accurate enough to be worth agonising over a few watts either way, and it's worth retesting every 6 to 8 weeks rather than treating one number as fixed for a whole season.
Making the test worth the effort if you're short on time
If you've only got one session to spend on testing, the 20-minute protocol is a reasonable trade-off between accuracy and time. A few things make it more reliable when you do it:
Warm up properly. A rushed warm-up produces a number that undersells your real fitness.
Pace it. Going out too hard in the first five minutes and fading is the single most common way to get a falsely low number.
Test on a day you're actually fresh, not squeezed in after a heavy training week when the number will reflect fatigue as much as fitness.
Repeat it under similar conditions each time, same rough time of day, similar fatigue state, so the number you're comparing against yourself means something.
Why this matters more when your hours are limited
If you can train 12 hours a week, imprecise pacing is a nuisance. If you can train 6, it's a genuine cost, because every session that's accidentally too easy or too hard is training time that isn't producing what it could have. Knowing your FTP is one of the cheapest ways to make a small number of weekly hours count for more, because it turns ride hard into a specific, repeatable target you can actually train against week after week.
Where this fits into a bigger plan
FTP is a useful number, but it's only useful in the context of a training plan that actually uses it, adjusting your zones as you improve and building sessions that target the right physiological system at the right time. A number on its own doesn't get you fitter. What you do with it does.
If you want your bike training built around real data rather than guesswork, that's part of how LimitX's coaching works.

Comments