Why Your FTP Test Disagrees With Your Lab Threshold — and Which One to Trust
5 min read
FTP and lab thresholds can disagree because they measure different things. Learn which number to trust for workouts, zones, and retesting.
On this page
Photo by Alexander Fastovets on Unsplash.
FTP is a field-derived proxy; lab thresholds measure physiology more directly. Trust the number that best matches the decision you need to make.
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.
FTP is a practical field estimate drawn from hard riding, often a timed test or software model. It blends aerobic fitness, pacing skill, motivation, heat, terrain, and how well you handled the day.
Lab thresholds, such as lactate or ventilatory threshold, come from a controlled test setting. They use blood or breathing data to find shifts in how your body meets the work demand.
That means the numbers can disagree without either one being useless. Your threshold did not disappear; the test measured a different part of the system.
Use FTP for normal power targets.
Use lab data for zone checks.
Keep one main testing method stable.
Compare trends, not one-off scores.
Match the number to the decision so your training stays clear.
FTP is a useful indicator for the training system; a lab threshold is a diagnostic measurement.
Photo by Bayu Putra Pamungkas on Unsplash.
An FTP test asks what power you can hold in a field setting. Your result depends on pacing, warm-up, recent load, road feel, and your comfort riding hard alone.
A lab threshold test asks a narrower question under tighter control. Blood lactate or breathing data can show when the internal cost of work begins to shift.
Critical power testing is different again, because it models the power-duration curve from repeated hard efforts. If you use a power meter, make sure the device is sound before comparing tests; start with keeping power readings stable and checking meter setup before FTP.
These tools are not rivals. They are lenses, and each lens shows the rider from a different angle.
FTP: field power under real riding strain.
Lactate threshold: blood response to rising work.
Ventilatory threshold: breathing response to rising work.
Critical power: modeled power-duration behavior.
FTP is the practical system gauge; lab measures are snapshots of underlying physiology.
FTP is an estimate of sustainable power from a timed effort; a lab threshold uses physiological measurements (lactate or gas exchange).
Photo by jymy duhomme on Unsplash.
Most mismatches start with the protocol, not with your fitness. A short maximal test, a long steady test, and a ramp test place different demands on the same rider.
Pacing also matters. If you start too hard, fade early, or test after a poor warm-up, your field FTP can look lower than your true repeatable training power.
Fatigue shifts the picture too. A hard training block, poor sleep, heat, or travel can blunt a field test more than a lab visit where steps are fixed and staff guide the process.
If your zones often feel wrong, compare the threshold source with how you train most often. You may also need a clearer power zone setup or a check on misleading training zones.
Do not compare unlike protocols blindly.
Retest under similar rest and warm-up.
Note heat, sleep, and recent load.
Watch pacing before blaming fitness.
One tactical email with training ideas and product updates. No spam — unsubscribe anytime.
Keep reading
- Heart Rate Variability for Cyclists: How to Measure, Interpret, and Use HRV to Guide Training — A practical, science-based guide for cyclists: how HRV works, how to measure it reliably, how to interpret individual patterns, and how to use HRV wi...
- Polarized vs. Pyramidal Training: Finding Your Optimal Intensity Distribution — Compare polarized and pyramidal intensity distributions for cyclists. Evidence-based guidance, practical session examples, and periodization advice t...
- Nutrition While Riding: Practical Fueling for Intensive and Recovery Rides — Nutrition while riding shapes power, fatigue, and recovery. Evidence-informed, practical guidance for fueling intensive sessions and recovery spins —...
Trust FTP when you need a repeatable field target for workouts, pacing, and day-to-day load. It is useful because it lives where you train, not because it is perfect.
Trust a lab threshold when the question is more diagnostic. If zones feel wrong for weeks, lab data can help show whether the issue is pacing, fatigue, or the threshold model itself.
When they disagree, choose the metric that best matches the next decision. Field intervals should be anchored to a field-tested number, while precise zone work may lean on lab findings.
Then keep the system consistent long enough to learn from it. Pair threshold work with heart rate zone context, and use lactate and reserve concepts when you need a deeper threshold check.
Use FTP for normal workout pacing.
Use lab data for precise zone checks.
Choose the test closest to your event.
Hold zones steady before retesting.
A clear threshold choice keeps the next workout from becoming guesswork.
Keep the training intensity system consistent—match the test to your use case.
Small differences are normal because no threshold test captures the whole rider. Power, breathing, blood markers, and perceived effort each tell part of the same story.
Do not rebuild your plan after one odd test. First ask whether the test setup, recovery state, and device data were close enough to compare.
If both tests point in the same broad direction, keep training. If one number makes key sessions feel far too easy or too hard, adjust the source rather than forcing the rider.
Look for trend agreement first.
Treat one bad test as noise.
Keep notes on test conditions.
Adjust only when sessions confirm it.
Day one: Ride easy and include a controlled warm-up with short tempo blocks. The goal is to reduce warm-up bias before any harder test.
Day two: Perform your usual FTP field test under repeatable conditions. Record power, perceived effort, pacing, device setup, and how the effort felt.
Day four: Ride easy and keep the session low strain. Protect sleep and fueling so the next test is not shaped by leftover fatigue.
Day six: Use a lab threshold test if you have access. If not, repeat a formal field protocol that your coach or testing platform already uses.
Day seven: Choose the number that matches your next training task. Use field FTP for field sessions, and use lab data when precise zone setting is the main goal.
FTP is a field-derived proxy, while lab thresholds measure physiology more directly. Neither number wins every time. Trust the one that best fits your next training decision, then keep the system stable enough to learn from it.
Not always. It may mean the field test was shaped by pacing, fatigue, heat, or motivation. Check the setup before you judge the fitness signal.
Only if the lab result matches how you plan to train. If most sessions use field power, blend the lab finding into your zones rather than making a sudden full reset.
Yes, heart rate can add context, especially during steady endurance work. It should not replace power or lab data, but it can show whether the load feels matched internally.
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.