Why Your FTP Test Disagrees With Your Lab Threshold — and Which One to Trust
5 min read
FTP and lab thresholds can disagree without either being wrong. Learn which number to trust for pacing, metabolic zones, and your next training decision.
On this page
This mismatch matters because your threshold number sets workout load, pacing, and fatigue expectations. If the number is wrong for the job, the whole training system shifts around a weak signal.
A lab threshold uses controlled testing to find a physiological breakpoint, often from breathing or blood markers. FTP is a field estimate of hard steady power, shaped by pacing, motivation, fatigue, warm-up, and conditions.
Neither number has to be wrong when they disagree. The lab value is better for physiology-led zone checks, while FTP is better for repeatable field pacing.
If you need one clear move today, use the lower value for planned intervals. Then keep the test method stable enough to learn from the next two weeks.
Lab threshold means a controlled physiological breakpoint.
FTP means practical hard-steady power in the field.
Use the lab value for metabolic zone checks.
Use FTP for pacing workouts and race-like efforts.
When unsure, train from the lower number first.
This keeps the next workout clear while you sort the test signal from test-day noise.
In N+One terms: the lab gives you the system’s setpoint, while FTP shows current output under real-world strain.
Photo by Uran Wang on Unsplash.
The first split is language. A lab may report lactate threshold, ventilatory threshold, or another marker, while FTP is a field-based estimate of sustained output.
The second split is protocol. A ramp test, a stepped lab test, and a long field effort each stress the rider in a different way, so compare ramp and 20-minute test choices before you rewrite zones.
The third split is the day itself. Sleep, recent load, heat, fueling, illness, and warm-up can all change what you can show on the bike.
Measurement also matters. If the power meter drifts, or if two devices disagree, the field number may move even when the rider did not, so start with stable power readings on long rides.
Confirm the exact lab marker reported.
Match ramp, step, or field test types before comparing.
Note sleep, heat, fueling, travel, and illness.
Check power meter setup before blaming fitness.
Keep the same warm-up for repeat tests.
FTP is an estimate of sustainable power derived from field tests and is sensitive to protocol, pacing, nutrition, and motivation.
Data analysis is free, forever. The Dynamic Coach is Pro. Connected to Garmin, Strava, Whoop, and intervals.icu.
Trust the lab threshold when the question is physiological. That is the better anchor when you want to refine metabolic zones, review breathing or lactate markers, or sense-check a long-standing training model.
Trust FTP when the question is execution. Field sessions, group rides, time trials, and race-like pacing need a number that came from the same world where you ride.
When the numbers conflict, choose the lower value for interval targets and hold the session shape. If zones suddenly feel mismatched after a large change, use zone adjustments after a jump rather than chasing every new score.
Do not cut intensity first if the workout purpose is still right. Keep the target type, trim volume briefly, and watch whether recovery and repeatability improve.
Use lab data for physiology-led zone checks.
Use FTP for field pacing and workout control.
When they conflict, start from the lower value.
Keep the workout aim, but reduce total load briefly.
Reassess after consistent sessions, not one ride.
That single rule protects training quality while the data catches up.
In N+One terms: train to the safer setpoint, then use field output to judge real-world execution.
If lab threshold is higher than FTP, the field test may have been capped by pacing, fatigue, warm-up, or fuel. Treat that result as a recovery and execution question before you lower every zone.
If lab threshold is lower than FTP, first check what the lab actually reported. Ventilatory and lactate markers do not always map cleanly onto a field FTP estimate.
A small gap is not a crisis. Threshold tests use different signals, and each signal can move with context, so look for agreement across workouts, not one tidy match.
If the gap is large enough to change key sessions, repeat the field test with the same protocol and better controls. For wider zone context, compare power zones for smarter riding with heart-rate zone context.
Lab higher than FTP: check fatigue and pacing first.
Lab lower than FTP: verify the lab marker and protocol.
Small gaps are expected across different test types.
Repeat the field test before a full zone reset.
Use session feel to flag obvious mismatch.
One tactical email with training ideas and product updates. No spam — unsubscribe anytime.
Keep reading
- Running Heart Rate Zones vs Cycling Heart Rate Zones: Why They Are Different — Running and cycling heart-rate zones differ because posture, muscle use, and load change the response. Learn how to set bike-specific HR zones.
- Setting Heart Rate Zones for Cyclists Who Train in Heat — Training in heat raises heart rate for a given power. Learn how to set heat-specific cycling HR zones with testing, power, RPE, and reassessment.
- Heart Rate Zones for Mitochondrial Adaptation in Cycling — How to use heart rate zones for mitochondrial adaptation in cycling: practical Zone 2 rules, session templates, and adaptive coaching tips.
Before changing zones, write down the exact test names, protocol steps, device used, warm-up, and last hard ride. Most bad decisions start with missing context, not missing effort.
Then ask whether your current zones fail in training. If only one test looks odd, but workouts still match effort and heart rate, the system may not need a full reset.
If endurance rides drift upward too often, the issue may not be threshold at all. Review why training zones can mislead and watch for unplanned tempo creep.
For late-season riders moving toward base, be conservative. Shorter daylight and accumulated race load make it easy to overread one hard test.
Name the lab marker and the field test used.
Log sleep, travel, heat, illness, and recent load.
Check whether normal workouts still feel right.
Use the lower target until uncertainty clears.
Retest only after a stable preparation window.
A clean checklist turns disagreement into one clear next decision.
This article keeps physiology claims narrow because threshold terms vary across studies and protocols. PubMed-indexed literature includes work on functional threshold power, lactate threshold, ventilatory threshold, and cycling performance testing.
The useful training lesson is not that one label always wins. It is that each test must be read with its protocol, signal, and day-to-day context intact.
When you need study-level detail, start with the linked PubMed search and review the actual methods. Look for the riders tested, the threshold definition, and the protocol used before applying findings to your own zones.
Once you choose the number, keep the next training block simple. Two sub-threshold rides and one easy aerobic ride will teach you more than stacking new tests back-to-back.
If the conservative number makes sessions too easy across several rides, move with care. A threshold that is slightly low is usually less costly than one that pulls every steady ride too high.
Base work after a late race season does not need constant threshold drama. Keep easy riding honest with zone 2 guardrails for cyclists, then bring threshold work back when the signal is cleaner.
Keep intensity targets clear for one week.
Use two controlled sub-threshold rides.
Add one easy aerobic ride.
Avoid another maximal test while tired.
Raise zones only after repeatable evidence.
Day 0 — Immediate decision: If lab and FTP differ, use the lower value for interval intensity today. Keep the planned interval type, but reduce weekly training volume by 20% for the next 7 days.
Days 1–7 — Recovery check: Track sleep, resting heart rate, and perceived recovery. Avoid new maximal tests, then ride two controlled sub-threshold sessions at or below the conservative number and one easy aerobic ride.
Days 8–14 — Repeat field test if needed: If the mismatch still changes training decisions, repeat the same FTP protocol after rested, well-fueled preparation. Test at a similar time of day and use the same pacing plan.
Days 15–21 — Reconcile and adjust zones: Compare the repeat field result with the lab threshold. Use the lab threshold for physiology-led targets and the field value for pacing. If the gap remains large, consider repeat lab testing or a sport physiology review.
FTP and lab thresholds measure related but different things. Use the lab threshold as your physiology baseline, FTP as your field pacing tool, and the lower value when you need one safe target today.
Not always. It may mean the field test was shaped by pacing, fatigue, warm-up, heat, or fueling. Check the setup before you judge the fitness signal.
Only if the lab result fits how you plan to train. If most sessions use field power, blend the lab finding into your zones instead of making a sudden full reset.
Yes, heart rate can add useful context during steady work. It should not replace power or lab data, but it can show whether external load matches internal strain.
Retest when the current number no longer guides workouts well, or after a stable training block. Testing too often can add noise instead of clarity.
