CoachingAnswer

HOW OFTEN SHOULD I TEST MY FTP?

By Anthony WalshRoadman CyclingUpdated 26 May 2026

WHO THIS IS FOR

IS THIS YOU?

The rider testing every 4 weeks

You're testing too often, accumulating meaningless data on fatigued days, and potentially sandbagging your zones.

The rider who hasn't tested in months

Your training zones are based on an old number and your hard sessions are increasingly mis-targeted.

THE ROADMAN VIEW

FTP testing is expensive. It costs a meaningful hard effort, a day of fatigue, and at least two easy days of prep. That's a lot to spend on a number you'll then use for the next 6–8 weeks — so the obvious question is whether you need to spend it more often. You don't. The common mistake is testing every three to four weeks, usually on a Thursday or Friday after a big training week, and then wondering why the number looks flat or even dropped.

The honest insight from coaches like Joe Friel is that FTP is best understood as a snapshot of peak fitness on a rested day, not a rolling live reading. Training blocks are typically 4–6 weeks of build followed by a recovery week. Test at the end of that recovery week, when your body has absorbed the training. That's when the number actually expresses what you've built — not a week into the block.

And when you test, use the same protocol every time. Comparing a ramp test to a 20-minute test gives you a different number for the same fitness — that's not progress tracking, it's noise. Pick one and stick with it. The number that matters is the trend across tests, not the absolute value of any single one.

EXPERT EVIDENCE

WHAT THE EXPERTS SAY

Joe FrielAuthor of The Cyclist's Training Bible; co-founder of TrainingPeaks
Periodised testing — at block boundaries with proper recovery — gives you data you can act on. Testing mid-block or on accumulated fatigue gives you a false baseline that mis-targets your zones for the following weeks.
Hear it: Joe Friel's Cycling Training Plan Structure | Roadman Cycling
Dan LorangHead of Performance, Red Bull–Bora–Hansgrohe
At World Tour level, performance testing is done periodically with full tapering, not as a regular training task. The amateur equivalent is testing at the end of a block after a recovery week — not when you're deep in a training load.
Hear it: 13 Years Of Coaching Pros: What Amateurs Don't Know

PRACTICAL APPLICATION

DO THIS WEEK

Schedule tests in your calendar at block boundaries
Map out your training blocks for the next 16 weeks. Mark the test days at the end of recovery weeks — not as optional additions but as part of the plan. Having the date set stops the temptation to test mid-block when you feel good.
Arrive rested: make the 2–3 days before genuinely easy
Two short zone 2 rides before the test day. No long rides, no intensity. The prep is not tapering — it is the minimum to let the fatigue of the previous block dissipate enough to get an honest number.
Use interval feel as a leading indicator
If your 95% FTP intervals feel consistently easier than they did 4 weeks ago, that's your early signal that FTP has moved up. You don't need to test early — the feel tells you the test will confirm it.

COMMON MISTAKES

WHAT CYCLISTS GET WRONG

MISTAKETesting mid-block on a training-fatigued day.
FIXAlways test at block-end, after easy days. Mid-block fatigue routinely understates FTP by 5–10% and sets your zones too low for the next block.
MISTAKESwitching between ramp test and 20-minute test for different blocks.
FIXPick one protocol and use it every time. The two can produce different absolute numbers. Mixing them means you're comparing different things and cannot track real progress.
MISTAKETreating a lower-than-expected test result as a training failure.
FIXCheck the conditions: were you rested, properly warmed up, and not fighting heat or illness? Often a disappointing test is a prep failure, not a fitness failure.

FAQ

FREQUENTLY ASKED QUESTIONS

Is it possible to test FTP too often?

Yes. Testing every 2–3 weeks burns hard efforts on data collection rather than adaptation, and the results are unreliable due to accumulated fatigue. It also cultivates anxiety about short-term fluctuations that are normal and meaningless.

What if my FTP drops at a retest?

A lower result usually means you were not rested enough, the test conditions differed, or you are in an overreaching phase. One drop is noise. Two consecutive drops after proper rest is a signal to examine training load, fuelling, and recovery.

Do I need to test FTP if I use an adaptive training platform?

Less frequently. Adaptive platforms like TrainerRoad or Xert infer FTP from session quality continuously. A formal test every 8–12 weeks still serves as a sanity check, but you can go longer between tests if the platform is tracking well.

Should I test FTP indoors or outdoors?

Test in the environment you mostly train in. Indoor FTP can run 3–7% lower due to heat and reduced cooling. The key is consistency — always test in the same place so your results are comparable.

How long before a key race should I test FTP?

At least 3–4 weeks before a target event. You need the result to set final build-block zones, and testing any closer to the event eats into your taper. Use feel and interval data in the final weeks rather than formal tests.

Does a higher test cadence make sense in base phase?

No. Base phase is typically low intensity where FTP barely moves for weeks at a time. Testing every 8 weeks in base is fine. Increase to every 6 weeks in a dedicated build block when you expect faster gains.

RELATED EPISODES

HEAR THE CONVERSATIONS

Joe Friel's Cycling Training Plan Structure | Roadman Cycling

80/20 Training to Ride Faster | Dr Stephen Seiler

Heat Training for Cyclists: +30 Watts FTP | Roadman Cycling