How Often Should I Test FTP?

Most amateur cyclists should retest FTP every 6-8 weeks, ideally at the end of each training block. Testing every 4 weeks is too aggressive — fatigue masks real fitness gains. Testing once or twice a year is too rare — your zones drift out of date and your training intensity becomes noise.

How Often Should You Test FTP?

There are three honest answers to this question, depending on how you train. If you're using an adaptive platform like TrainerRoad, the algorithm is constantly inferring your FTP from your session quality — formal tests become less important. If you're self-coached on a structured periodised plan, every 6-8 weeks is the sweet spot. If you're working with a coach, they'll tell you when — typically at the end of each block.

The reason 4-week testing is too aggressive is simple: fatigue. Mid-block, you're carrying load. A 'test' at that point isn't measuring fitness — it's measuring fatigue tolerance. The number comes back lower than reality, you readjust your zones downward, and you under-train the next block. Joe Friel and the Roadman coaching network are unanimous on this: fewer high-quality tests beat more low-quality tests every time.

The reason once-a-year is too rare is also simple: zones drift. If your real FTP has moved 6% but your zones are calibrated to last year's number, every interval session is now mis-targeted. Easy rides creep into zone 3. Threshold work isn't actually at threshold. The training quality silently degrades and you don't know why your gains have stalled.

Practically, plan your testing into your periodisation up front. Most amateur build phases run 8-12 weeks. Test at the start (to set zones) and at the end (to measure the block). Take a deload week before the end-of-block test — even one easy week typically lifts the result by 3-7% versus testing under fatigue. That's not artificial — that's letting your body actually express the fitness it built.

WHERE THIS COMES FROM

Joe Friel — The Cyclist's Training Bible

Friel's periodisation framework places formal testing at block boundaries, not mid-block, for the fatigue-masking reason described above.

Roadman — Ramp Test vs 20-Minute Test

Comparison of the two most common test protocols, with prep, taper, and pacing recommendations.

Andy Coggan — Power Meter Handbook

Coggan's testing protocols include explicit taper and recovery prep — the same prep that distinguishes a real FTP from a fatigued one.

COMMON FOLLOW-UPS

Should I do a ramp test or a 20-minute test?

Either, as long as you're consistent. Ramp tests are shorter and less mentally taxing but underestimate FTP for some riders. The 20-minute test is more demanding and slightly more accurate when paced well. Pick one and stick with it so the number-to-number comparison is honest.

Do I need to test FTP if I'm using TrainerRoad?

TrainerRoad's Adaptive Training infers FTP from session quality, so you don't need to test as often. That said, most coached athletes still do a periodic formal test to sanity-check the algorithm — typically every 8-12 weeks rather than the 4-6 the platform prompts.

Can I just guess my FTP?

Estimating FTP from a hard hour or a recent race is a reasonable starting point, but it's not the same as a tested number. The estimate is usually within 5-10% of reality — fine for setting initial zones, not fine for prescribing precise threshold or VO2max sessions where 5% is the difference between adaptation and overcooked.