Start with recent representative data
Use recent workouts or tests from the current training phase to avoid stale threshold references.
How to use threshold estimates
Treat CP, FTP, and LTHR as starting points, then validate them against workout execution and fatigue response.
Compare multiple estimate paths
File-based and model-based estimates should be directionally aligned before making a big zone update.
Apply small calibration steps
Adjust thresholds conservatively first, then validate with key-session quality and perceived effort.
Re-estimate on block transitions
Thresholds can drift across blocks. Recheck before entering build or race-specific phases.
Should CP and FTP always match closely?
Not exactly. They often track similarly, but method and data quality can create a meaningful gap.
Can LTHR be estimated without lab testing?
Yes. Field-test and workout-derived methods can provide practical estimates for training decisions.
Do I need to update thresholds every week?
Usually no. Update when trend evidence supports change, not on isolated good or bad sessions.