FTP is a moving target. Train consistently and it climbs. Back off, get sick, or pile up fatigue and it falls. The problem most riders have isn't understanding that FTP changes — it's knowing when a retest will give them an accurate picture rather than a number distorted by timing.
This chapter covers the typical rate of FTP change, the factors that accelerate or slow it, and a practical framework for deciding when to retest.
How Quickly FTP Actually Changes
FTP responds to training load over weeks, not days. A single hard session doesn't move it. A single rest week won't crater it either. Change accumulates across a training block.
Upward movement
For most trained riders, meaningful FTP gains require several weeks of consistent, progressive overload. Beginners and returning riders tend to see faster early gains because they have more low-hanging physiological adaptation available. Well-trained riders may grind for months to add a few watts.
The general pattern:
- Newer or detrained riders — noticeable gains can appear within four to six weeks of structured training
- Intermediate riders — a focused block of eight to twelve weeks typically produces a measurable improvement
- Advanced riders — gains accumulate more slowly; a season-long view is often more informative than block-to-block comparison
Downward movement
FTP declines faster than it rises. Extended rest, illness, or a sudden drop in training load can reduce functional threshold within two to three weeks. The drop accelerates with complete inactivity and slows when some volume is maintained — even low-intensity riding preserves a meaningful portion of fitness.
This asymmetry matters for test timing: if you've had an unplanned break, a test immediately after returning will understate your actual ceiling once adaptation catches back up.
What Drives FTP Change
Understanding what moves FTP helps you predict when a retest makes sense.
Training factors that raise FTP
- Sustained increases in weekly training load (volume and/or intensity)
- Threshold and sub-threshold work targeting the systems that set FTP
- Improved aerobic base that allows you to sustain higher intensities longer
- Race-specific preparation and peak fitness phases
Factors that lower or obscure FTP
- Accumulated fatigue — the most common reason a test produces a number that doesn't reflect true fitness
- Illness, especially respiratory infections that affect aerobic capacity
- Life stress, poor sleep, and caloric deficit sustained over weeks
- Detraining from injury or planned off-season rest
Fatigue deserves particular attention. A tired rider will underperform in a test. The number they produce is real — it reflects what they can do right now — but it isn't a reliable proxy for their actual physiological ceiling. Testing in a fatigued state can lead to training zones that are too low, which then means undertraining through the next block.
Standard Retesting Intervals
A common default is retesting every six to eight weeks — roughly at the end of a training block. This interval makes sense because:
- It's long enough for genuine adaptation to occur
- It aligns with natural periodization structures (base, build, peak)
- It's frequent enough to catch meaningful changes before you've been training in misaligned zones for too long
That said, the calendar shouldn't be the only trigger. A fixed interval can push you toward testing when you're too fatigued to get a useful result, or hold you back from testing when conditions are ideal.
When to Retest: Practical Signals
Use these signals alongside your planned schedule to decide whether to test, delay, or skip.
Strong reasons to retest
- You've completed a structured build block and had three to five days of easy riding or rest going into the test
- Your current zones feel too easy — you're consistently riding at the top of a zone without it feeling like the intended effort
- You've returned from a race peak and want to reset your training zones for the next block
- It's been more than ten to twelve weeks since your last test and your training has been consistent
Reasons to delay
- You're in the middle of a high-load training week or just finished one
- You've been ill in the last two weeks
- Sleep has been consistently poor for more than a few days
- You feel flat or heavy-legged — trust that signal
Reasons to skip and estimate instead
If you've had an extended unplanned break and you're returning to training, testing immediately is usually counterproductive. Your FTP has declined but will recover relatively quickly. A better approach is to return to training using your previous zones at conservative intensities, then test after four to six weeks of rebuilding. The FTP estimator can give you a working number to start from without burning a test effort.
Tapering Before a Test
The quality of a test result depends heavily on how you arrive at it. A proper short taper before an FTP test isn't pampering — it's methodology.
A minimal effective approach:
- Two to three days of reduced volume and no intensity before the test
- Keep some activation work in the day before (short, easy ride with a few short efforts to prime the legs)
- Test on a day when motivation and sleep have been normal
- Test at the same time of day, on the same course or trainer setup if possible, to reduce variables between tests
Consistency in test conditions matters as much as consistency in test timing. If you test rested on a trainer in winter and fatigued outdoors in summer, you're not comparing the same thing.
Reading the Result: Did the Test Go Well?
Not every test produces a usable number. Learn to evaluate the effort itself.
Signs the test was valid:
- You paced it evenly or with a slight negative split (went slightly harder in the second half)
- The effort felt genuinely maximal by the final few minutes
- Your power output was consistent, not wildly variable
Signs to treat the result with skepticism:
- You went out too hard and collapsed in the second half
- You felt flat throughout and couldn't push into real discomfort
- External conditions (extreme heat, poor sleep the night before) clearly affected output
If a test goes badly, don't immediately update your zones based on a number you don't trust. Wait a week and retest, or use a recent hard ride to estimate via the FTP estimator.
Tracking Change Over Time
Single FTP numbers are less useful than a trend. Keep a simple log: date, test format, result, and a brief note on conditions and how the effort felt. Over a season, this log tells you far more than any individual test.
Look for:
- Whether gains are accumulating across blocks
- Whether certain training phases consistently produce improvement
- Whether your FTP and your perceived effort in races or hard group rides are aligned — if they diverge, trust the rides
For more on what FTP represents and how it's measured, see the complete guide to FTP.