
Why your FTP estimate can move without a formal test, what to check in your ride data, and why one update should not drive a training overhaul.
On this page

Photo by Bundok Biker on Unsplash.
Your FTP estimate can change without a formal test, but that alone does not prove your fitness changed. Check the data before changing your plan.
A moving number invites a quick response, especially when you use it to guide your next training session. The first task is simpler: separate what the screen shows from what the available evidence can actually establish. This guide explains what to check without assuming how N+One calculates its estimate or claiming a verified accuracy level.
An estimate is a value inferred from available data, rather than a result recorded through a formal test. Those labels describe different kinds of information, so keep them separate when you compare your latest numbers.
Start by checking the value’s label, its update date, and any explanation shown beside it in the app. An updated display establishes that the displayed value changed; it does not establish why that change took place.
For related reading, see how breakthrough rides relate to estimate updates, while keeping product-specific explanations separate from assumptions. If you need a test-based comparison, review how to set up a threshold test before choosing your benchmark.
Keep the earlier value and its date in your notes rather than replacing the record with the latest number. That gives you a clear comparison without treating either entry as a complete account of your current riding.
Check whether the value is labeled as estimated or tested.
Note the update date and any explanation shown beside it.
Keep the previous value available for comparison.
Do not treat one update as a confirmed performance change.
In N+One terms: read the number with its training context, not in isolation.

Photo by Ben Guernsey on Unsplash.
Treat possible explanations as questions to investigate, not as a confirmed account of how N+One calculates your estimate. The supplied source does not identify its inputs, training window, update rules, or handling of missing ride records.
Compare the update date with your activity list, looking for missing rides, duplicate entries, or records that arrived later. Check whether the efforts you expected to see are present, without assuming the estimate uses those specific efforts.
Next, note any change in your recording device, power source, or account connection around the same update date. For a device-focused review, use checks for consistent power readings alongside the instructions supplied by your device maker.
During the autumn move indoors, record which rides came from your outdoor meter and which came from your trainer. Keep those settings visible when reviewing comparisons between indoor and outdoor numbers, rather than treating every ride as interchangeable.
Finding a changed record gives you something concrete to investigate, but timing alone does not prove a causal link. If the records look unchanged, leave the cause unresolved rather than filling the gap with a confident explanation.
Compare the estimate’s date with the activities recorded around it.
Look for missing, duplicated, or newly synced rides.
Note changes in devices, power sources, or account connections.
If no clear explanation appears, wait for further information before drawing a conclusion.
Data analysis is free, forever. The Dynamic Coach is Pro. Connected to Garmin, Strava, Whoop, and intervals.icu.
One tactical email with training ideas and product updates. No spam — unsubscribe anytime.
An estimate is not the same as a formal test result.
Your next move is to verify the record before using the estimate as a reason to change training. Do not change intensity, volume, and equipment together just to respond to a number whose meaning remains unclear.
Keep your current plan as the starting point while you check the inputs, unless another reason warrants changing it. This is a rule for interpreting an estimate, not advice to ignore illness, pain, or concerns about training.
Write a short note stating what changed, what you checked, and what remains unknown about the latest update. That note gives your next review a clear starting point instead of another round of guessing from memory.
If you need a test-based benchmark, choose a formal protocol and keep the comparison method and conditions as consistent as practical. Compare results from the same protocol rather than treating unlike tests and app estimates as the same measurement.
You do not need to settle every question before your next ride; you need to avoid an unsupported decision. A moving estimate can prompt a useful review without becoming the sole reason to rewrite your training targets.
Review the activities recorded around the update.
Confirm that ride records and power data appear complete.
Keep training steady while checking the estimate, unless other circumstances warrant a change.
Use a consistent formal test when you need a test-based comparison.
Let one estimate inform the decision, not make it for you.
Keep reading
- FTP Tests Compared: 20-Minute vs Ramp Test — Compare the 20-minute FTP test and ramp test, learn what each measures, and choose the right protocol for consistent cycling training zones.
- The FTP Ceiling: Why Your Progress Has Stalled — The FTP Ceiling: Why Your Progress Has Stalled
- Normalized Power Inflation on Lumpy Routes: Correcting Mental Math for Climbers — Learn why Normalized Power can read high on lumpy climbs, how to spot route-driven inflation, and how to set better climb pacing targets from sustain...
The source supplied for this article is a PubMed search page, not a verified study of N+One’s estimate. It does not establish the product’s formula, the data it uses, or how closely its estimates match test results.
That means this article cannot assign a reliable cutoff separating harmless drift from a meaningful change in performance. Nor can it say that a particular update proves a change in your threshold, recovery, or training readiness.
An increase deserves the same careful review as a decrease, rather than an automatic rise in your training targets. Check what the update actually tells you before assigning it a broader meaning about your fitness or progress.
For a wider discussion, read why a threshold number is only a snapshot, without treating it as validation of this estimate. Product documentation and verified research would be needed before making stronger claims about calculation rules or measurement accuracy.
Check the update. Record the estimate, its date, and its label without treating the change as a confirmed fitness shift.
Review the data. Look for missing, duplicated, newly synced, or differently connected ride records around the update, and note device changes.
Decide calmly. Keep training steady while verifying the inputs, unless other circumstances warrant a change; use a consistent formal test when you need a test-based benchmark.
Check the data before changing the plan: identify the update, inspect the ride records, and note any connection changes. One estimate is not enough to confirm a precise change in fitness or justify a training overhaul. If you want day-to-day guidance without second-guessing, let N+One translate your latest training and recovery context into one clear next decision.