FTP Testing: Protocols and Best Practices

Functional Threshold Power (FTP) is the single most important number in modern cycling training. It represents the highest power you can sustain in a quasi-steady state for approximately one hour, and every training zone in your plan is calculated from it. Getting FTP right matters: if the number is wrong, every interval is mistargeted, and weeks of training are compromised. We analyze the validated FTP testing protocols, how to pace them, common errors, and how to interpret your results.

Why FTP Is the Cornerstone of Training

FTP anchors the entire power-based training zone model. Each zone is defined as a percentage of FTP:

Zone	Name	% FTP	Purpose
1	Active Recovery	$< 55\%$	Blood flow, recovery
2	Endurance	$56\%-75\%$	Aerobic base building
3	Tempo	$76\%-90\%$	Sustained aerobic power
4	Sweet Spot / Threshold	$91\%-105\%$	FTP improvement
5	VO2max	$106\%-120\%$	Aerobic capacity
6	Anaerobic	$121\%-150\%$	Lactate tolerance
7	Neuromuscular	$> 150\%$	Sprint power

Because zones are derived as fractions of FTP, a 5% error in your FTP test shifts every zone boundary by 5%. Training at the wrong intensity wastes time or causes excessive fatigue. This is why FTP testing cycling protocols demand precision.

The Three Validated FTP Test Protocols

1. The 20-Minute Field Test

The most widely used and research-supported field protocol (originally popularized by Allen and Coggan) involves a maximal 20-minute effort. The procedure:

1. Warm-up: 15-20 minutes progressive riding, including 2 x 1-minute fast pedaling efforts at 100+ rpm, and one 5-minute all-out effort to activate the anaerobic system.
2. Recovery: 10 minutes easy spinning.
3. The effort: Ride as hard as you can sustain for 20 minutes. Pacing is critical — see below.
4. Calculation: FTP = 20-minute average power × 0.95.

The 0.95 multiplier accounts for the fact that 20 minutes is above true 60-minute power for most riders. The 5-minute all-out effort before the test depletes anaerobic reserves, making the 20-minute result more closely reflect aerobic capacity.

2. The Ramp Test

The ramp test is a progressive incremental test to exhaustion:

• Start at 100 W, increase by 20 W per minute (15 W/min for women is commonly used).
• Ride until you cannot maintain cadence above 70 rpm.
• Record the highest 1-minute average power (the final completed minute is often used).
• Calculation: FTP = ramp final minute power × 0.75.

The ramp test is easier to pace because you simply follow the steps until failure. However, it systematically underestimates FTP for riders with strong anaerobic capacity — the test ends quickly due to muscle recruitment limits rather than aerobic threshold. For well-trained riders, the 20-minute test is preferred.

3. The 8-Minute Dual-Effort Test

Some coaches use two maximal 8-minute efforts separated by 10 minutes of recovery:

• FTP = average power of both 8-min efforts × 0.90.

This protocol suits riders who find 20 minutes mentally taxing. It is less validated than the 20-minute test but provides a reasonable approximation and is useful for tracking changes.

Pacing the 20-Minute Test

The most common FTP testing error is poor pacing. Starting too hard creates early lactate accumulation that forces a power collapse. Starting too conservatively underestimates FTP.

An ideal 20-minute pacing curve looks like:

• Minutes 0-3: Settle into a power about 5% above target FTP. This is the "start slightly high" phase to account for freshness.
• Minutes 3-17: Steady-state at target FTP ± 2%. This is where the test is won or lost.
• Minutes 17-20: Gradually increase power, finishing with everything left. The last 3 minutes should hurt.

A flat power file with a steady heart rate that drifts upward by 8-12 bpm over the effort indicates correct pacing. A power spike followed by a collapse indicates going out too hard.

The Training Stress Score (TSS) of a well-paced 20-minute test is approximately:

$$TSS = \frac{t \times NP \times IF}{FTP \times 3600} \times 100$$

where $t$ is duration in seconds, $NP$ is normalized power, and $IF$ (intensity factor) for a maximal 20-minute effort typically falls around 1.05-1.10, yielding a TSS of roughly 50-55 for the test effort alone.

Common FTP Testing Mistakes

Testing While Fatigued

If you are in a high-load training week or have not recovered, FTP will appear artificially low. Test during a recovery week or after 2-3 light days.

Poor Warm-Up

Skipping the activation efforts produces a sluggish first 5 minutes and a low result. The neuromuscular system needs priming.

Insufficient Motivation

A field test is a maximal effort. Testing alone at home with low motivation underestimates FTP by 5-10% compared to a group or race-day environment.

Changing Conditions

Test on the same trainer, with the same tire pressure (for wheel-on trainers), same gearing, and same cooling (fan) setup. Environmental drift corrupts comparisons across tests.

Interpreting Your FTP Test Results

After each test, record:

• Absolute FTP (W): The raw number.
• FTP per kg (W/kg): FTP divided by body weight. This determines climbing ability.
• Heart rate drift: bpm increase over the effort. Excessive drift (>15 bpm) suggests poor heat acclimation or inadequate fitness.
• Cadence distribution: Tight cadence range (80-90 rpm) indicates efficient pacing.

Track FTP every 4-8 weeks. A well-structured training block typically yields a 2-5% FTP improvement over 8-12 weeks for trained riders, and 5-15% for riders new to structured training.

Using Technology During Testing

A power meter is mandatory for FTP testing — heart rate alone cannot establish FTP. Ensure your power meter is calibrated (zero-offset) immediately before the test. Dual-sided power meters provide additional data on left/right balance.

The DIDI.BIKE sensor integrates with your power data, streaming real-time telemetry — power, heart rate, cadence, and body posture — to Garmin, Wahoo, Strava, and TrainingPeaks for $299. During testing, the posture and telemetry data helps you verify that your position remained stable throughout the effort, ensuring the FTP number reflects true sustainable power rather than a position breakdown in the final minutes.

When to Retest

Retest FTP:

• After completing a training block (every 4-8 weeks).
• After a significant weight change.
• After heat or altitude adaptation.
• At the start of a new season or training cycle.

Avoid retesting within a week of a previous test unless you suspect a pacing error — the learning effect from the first test inflates the second.

Putting FTP Into Practice

Once you have a validated FTP, your entire training plan becomes data-driven. Interval targets, sweet spot sessions, and recovery rides all anchor to the number. For a complete framework on designing intervals around FTP, see our guide on cycling interval design. To understand how environmental factors like heat and altitude affect your FTP reading, read heat and altitude cycling. For the broader context of all training and racing data, start with the cycling data guide.

FAQ

What is the most accurate FTP test protocol? The full 20-minute effort at the highest sustainable power, with the result multiplied by 0.95, remains the most validated field test for FTP. Ramp tests offer convenience but often underestimate FTP for riders with strong anaerobic capacity.

How often should I test my FTP? Most coaches recommend retesting every 4 to 8 weeks, or after a major training block. Avoid testing during a taper or when fatigued, as the number will not reflect true fitness.

Is a ramp test or 20-minute test better for FTP? A 20-minute test better reflects true sustainable power for experienced riders, while a ramp test is easier to pace and ideal for beginners who struggle with steady-state efforts.

Should I warm up differently for each FTP test? Yes. The 20-minute test requires a thorough warm-up including high-cadence spin-ups and a short anaerobic effort to open the system. A ramp test needs only 10 to 15 minutes of progressive spinning.

Can the DIDI.BIKE sensor help during FTP testing? Yes. The DIDI.BIKE sensor streams real-time power, heart rate, and posture data to Garmin, Wahoo, Strava, and TrainingPeaks, allowing you to monitor pacing and verify test conditions live.

References

1. Medicine & Science in Sports & Exercise: Modeling anaerobic work capacity (W') and fatigue dynamics.
2. International Journal of Sports Physiology and Performance: Altitude training block dynamics and VO2max recovery.
3. DIDI.BIKE Technical Reprints: Realtime physiological telemetry and training stress balance tracking.