
Keep unusual race results visible, tag their context, and compare similar events in N+One without letting one race distort your training trend.
On this page

Tag unusual race results, keep the original data, and compare the wider trend before changing training. One race is a data point, not your whole story.
Course, conditions, pacing, equipment, and race role are useful details to record when results seem hard to compare. Treat them as context, not proof that any factor caused the result or that your fitness changed. This guide helps you organize and interpret records; it does not diagnose health or measure fitness from one event.
An outlier is a result that differs noticeably from the other results you have chosen for comparison. It can be unusually strong or weak, and the difference alone does not tell you why it happened.
Choose your review rule before deciding whether you like the result, then apply it to strong and weak performances. A useful rule is to flag a marked difference for review, while keeping any known event context separate.
Keep the original record intact and write down what you know, rather than filling gaps with a likely explanation. For example, “stopped for a wheel change” records an event; “lost fitness” makes a claim the note cannot establish.
Use a short label such as “outlier review” in your notes, rather than treating the label as a confirmed cause. If your current N+One view lacks a suitable tag or note field, keep a separate race log alongside it.
When an unusual race follows a quieter training spell, use a careful reading after easier training to frame your review. Keep that broader context separate from the question of whether the race belongs in a particular comparison.
Avoid setting a statistical cutoff simply because it makes the chart look cleaner or removes a disappointing race. This guide supplies no validated cutoff, and a tag does not automatically justify excluding the result from analysis.
Keep the original race result and activity file.
Use the same review rule for unusually strong and weak results.
Record known course, conditions, equipment, and race-role details.
Separate observed facts from possible explanations.
Leave uncertain results visible with a brief review note.
In N+One terms: preserve the data point and make its context visible.

Photo by Mathias Reding on Unsplash.
Start with the question you want answered, then choose a metric and comparison group that fit that question. Finishing place, elapsed time, and recorded power describe different things; do not treat them as interchangeable measures of progress.
For a time-based comparison, first check whether the route, distance, and timing method make the results useful together. For placing, record the event format and field context rather than assuming the same position means the same performance.
Keep your comparison rule stable across the review, including when a different choice would produce a more pleasing story. The same habit matters when reviewing month-to-month changes fairly, especially when your calendar contains different kinds of riding.
Review the full set first, then consider a second view without the tagged result if the comparison warrants it. Label both views clearly and state why you left the result out; neither view becomes correct just by looking smoother.
If your conclusion changes when the tagged race is removed, describe that conclusion as sensitive to the comparison choice. Do not silently choose the version that supports the training change you already wanted to make.
Use a broader view of recorded progress to keep individual races within your wider history. When comparable records are sparse or mixed, write “tentative” rather than turning a weak comparison into a firm claim.
During the autumn shift from racing toward base work, keep race results separate from routine training comparisons where needed. Record the change in purpose instead of treating every ride as another attempt at the same performance.
Choose the question before choosing the metric.
Group results by relevant event format and recording method.
Review the full record before any tag-excluded comparison.
Label exclusions and explain their reasons.
State uncertainty when comparable results are limited.
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.
Keep the race result in your record; add a clear outlier tag and a short note about the context.
Keep reading
- Mid-Season FTP Check‑In in N+One: How the App Detects a New Threshold Without a Test — How N+One flags a mid-season FTP shift from recent ride power, heart-rate, and recovery context, plus a short micro-check for mixed signals.
- Mid-Season FTP Check-In in N+One: Reviewing a Threshold Estimate Without a Test — Review a possible FTP update in N+One without confusing an estimate with a test. Check your records, understand the limits, and choose one next step.
- N+One Power Curve vs Strava Power Curve: Why the Numbers Differ — Why N+One and Strava power curves differ, how smoothing and ride selection change the numbers, and the 7-day protocol to compare matched raw files.
Open the race activity and check the recorded date, event details, and metric you intend to compare with other results. If you find a recording issue, document the correction while preserving the source file wherever possible for later review.
Add your context note, then use a side-by-side review of similar rides to inspect a relevant comparison. Keep unlike events apart rather than forcing a race and a routine ride into the same performance judgment.
A useful note might read: “Unusual elapsed time; stopped for a wheel change; original file retained; compare moving efforts separately.” That note records the known issue without claiming how the rider would have finished under different circumstances.
Treat an exceptional result with the same care, using a closer look at recorded peak efforts when relevant. Keep the achievement in your record, but do not turn one peak into a claim about every aspect of performance.
A review tag is an aid to interpretation, not an instruction to remove the activity from every calculation. This guide does not establish that N+One supports automatic tag-based exclusions, so do not assume a note changes dashboard calculations.
Before changing training, write down the broader pattern that supports the change and the evidence that would challenge it. If the race is your only reason, keep the decision provisional and seek another relevant comparison before rewriting the plan.
Revisit the tag when another comparable result becomes available, checking whether your original note still describes the situation fairly. Repeated unusual results are a reason to review the comparison rule, not to keep excluding more of your history.
Verify the race record before interpreting it.
Add a factual context note or keep one in a separate log.
Compare similar results alongside the wider training history.
Do not assume a tag changes N+One calculations.
Make a training change only when the broader pattern supports it.
In N+One terms: the tag preserves context while the wider record guides your next decision.
Verify: Check the race result, event details, and recorded metric before drawing conclusions from the activity.
Tag: Flag an unusual result for review and add a factual context note, keeping the original data intact.
Compare: Review similar results first, then label any comparison that leaves the tagged result out and explain why.
Decide: Avoid changing training on the race alone; make one adjustment only when the wider pattern supports it.
Reassess: Review the next comparable result and update your interpretation, including the tag, when the record warrants it.
Keep the result, add context, and let the wider trend earn your attention before changing your training. Your next move is to tag the race for review and compare it with the most relevant events, without hiding either strong or weak performances.
Race result analysis — Reviewing a race record alongside its context and sufficiently similar results to answer a clear question. Outlier tagging — Labeling a result that differs noticeably from its comparison set, without deleting it or assuming a cause. Training trends — The overall direction across multiple training observations, interpreted with attention to how those observations were chosen.