The N+One Race Plan Module: How the App Builds a Pacing Strategy for Your A‑Race
5 min read
See how the N+One Race Plan Module turns your A‑race goal, course profile, and recent training context into one adaptive pacing strategy.
On this page
Photo by Krzysztof Kowalik on Unsplash.
The Race Plan Module turns your race goal, course data, and recent training context into one adaptive pacing plan for your A‑race.
This refresh keeps the original promise: one pacing strategy you can trust when race week gets noisy. It adds a tighter how-to, clearer evidence boundaries, and a simple week-of-race protocol for late-season A‑races.
Photo by Rokas Niparas on Unsplash.
This article refreshes the Race Plan Module without changing its core job. It still helps you turn a goal, a course, and recent training context into one pacing choice.
The update sharpens how you should use the module in race week. It also keeps physiology claims narrow, because the grounding source points to PubMed-indexed literature rather than one named trial.
Use this piece as a working guide, not as a lab review. For the wider system behind the feature, see how N+One plans weekly rides and how the coach engine works.
Refresh the Race Plan article with evidence-aligned updates.
Use it if you are preparing an A‑race and want one pacing call.
Keep physiology claims tied to PubMed-indexed evidence boundaries.
Make one clear next decision before race week gets noisy.
In N+One terms: keep your pacing logic, refresh the inputs.
Keep your pacing logic, refresh the inputs.
The Race Plan Module starts with the race you name as important. Your time goal, rank goal, course profile, and training context give the app its working frame.
It then reads recent rides from your connected sources and checks the course demands against what you have shown in training. The aim is not a perfect forecast, but a raceable pacing profile you can hold under pressure.
The output is a segment-by-segment plan with target pace or power bands and simple checkpoints. If you want the build-up logic, pair this with building backward from your A‑race.
The plan also updates when the inputs change. A new hard ride, a course change, or a shift in recent training context can move the recommendation toward a safer or more assertive band.
That closed loop is the point. Your strategy should reflect your current training state, not the rider you hoped you would be when you first added the race.
Add the race goal, distance, route, and key segments.
Confirm recent training files from power, heart rate, or wearable sources.
Review the first, middle, and finish checkpoints before you lock the plan.
Use the target band, not one brittle number, as your race guide.
The module creates one clear pacing strategy for your A‑race by combining your stated goal, course profile, and recent training data.
Data analysis is free, forever. The Dynamic Coach is Pro. Connected to Garmin, Strava, Whoop, and intervals.icu.
The module uses broad training ideas that should sound familiar to cyclists: sustainable effort, repeatability, recent load, and recovery context. Those ideas must be handled with care when no single study is named.
Power-duration relationships help frame how long a rider can hold a given effort. Fatigue and recovery context help explain why the same target can feel different across two weeks.
For this refresh, we describe the product logic plainly and keep the evidence line clear. The only provided source is a PubMed search pointer, so detailed physiology claims should be checked against indexed research.
The practical update is simple: very recent hard work and explicit recovery inputs get more attention when the plan reads short-term readiness. Your threshold did not disappear; your recovery inputs shifted, so the usable output may drop.
If you want to see how long-term memory supports this reading, use coach memory across months. For race execution, keep power-based race pacing close.
Check whether recent high-intensity work still matches your target race demand.
Treat recovery context as an input, not as a moral score.
Re-run the plan after a hard session close to race day.
Do not over-read physiology claims without indexed sources.
In N+One terms: your threshold didn’t vanish — recent stress and recovery shifted the usable output.
Your threshold didn’t vanish — recent stress and recovery shifted the usable output.
Your next move is decisive: load the current race file and recent training context, then follow the pacing profile unless a key input changes. Do not build three backup plans that fight each other.
In the final week, keep the race-specific feel and cut the clutter. If recent recovery markers are low or hard repeats have dropped off, trim total ride time and keep the key intensity cues.
If those markers look normal, hold the planned segment intensities and avoid adding new work. Freshness matters more than squeezing in one more proof session.
This is where the Race Plan Module pairs well with adaptive periodization for an A‑race. The peak is built over weeks, then protected in the final stretch.
Late-season racing often brings cooler mornings, wind, and shorter daylight. Add those conditions to the course notes if they change your warm-up, clothing, or timing.
Load your recent training context before changing the plan.
If recovery inputs are low, cut race-week volume and keep key intensity.
If recovery inputs are normal, hold the planned segment targets.
Update the plan if illness, weather, or course details change.
One tactical email with training ideas and product updates. No spam — unsubscribe anytime.
Keep reading
- The N+One Weekly Review: What the Algorithm Looks At and What You Should — No PubMed-indexed article describes the N+One Weekly Review algorithm. Learn how to audit data, compare training and recovery, and choose one next mo...
- What’s New Feed for Athletes: How Product Updates Surface in the App — Learn how the What’s New feed surfaces product updates, alerts, and experiments, and how athletes can turn each update into one clear training action.
- Feature Flags You Actually Notice: What Changes When New Coaching Tools Roll Out — Feature flags let new coaching tools roll out gradually. Learn what you may notice, how it can affect training choices, and how to test a new feature...
Race day is not the time to redesign the strategy. Start inside the first target band and let the opening checkpoint tell you whether the model matches your legs.
If power or pace and perceived effort agree, keep riding the plan. If effort feels too costly early, move to the safer side of the same plan rather than chasing the group.
The checkpoints are there to slow down bad decisions. They give you a place to ask whether the day still matches the forecast.
Use the plan as one canonical decision. For a broader product view, see what an AI coach adds beyond workouts and asking for race-specific strategy.
Start on the calmer side of the first target band.
Check power, pace, and feel before reacting to surges.
Use the mid-race checkpoint before making a bigger move.
Shift safer if effort feels too costly early.
A pacing plan narrows uncertainty, but it cannot remove uncertainty. Wind, traffic, pack flow, crashes, and mechanical problems can change the cost of the same target.
The app can respond when you update the inputs. It cannot know every live race event before it happens.
That is why the best use is a single reviewed plan with clear checkpoints. You are not outsourcing judgment; you are reducing noise so judgment has a better frame.
The science boundary matters too. Because the provided grounding source is a PubMed search pointer, physiology claims in this article stay broad and conservative.
Treat the plan as guidance, not a guarantee.
Update it when key race or training inputs change.
Use checkpoints when the course stops matching the forecast.
Keep claims about physiology tied to indexed evidence.
In N+One terms: the plan narrows uncertainty, then gives you a cleaner way to act.
The plan narrows uncertainty, then gives you a cleaner way to act.
Day 0 — Decision: choose one adjustment. If recent recovery inputs look normal, keep the planned segment intensities. If they look low, reduce race-week volume and keep the key intensity targets.
Days 1–3 — Maintain intensity, reduce volume: ride two short sub-threshold sessions with brief race-rhythm efforts. Keep the work controlled, and avoid adding new maximal tests.
Day 4 — Race simulation: if useful, ride a course-specific session at planned segment targets. Compare the planned effort with power, pace, breathing, and control.
Days 5–6 — Taper and confirm: keep rides short and easy, with a few brief efforts to stay sharp. Re-run the Race Plan Module with the latest data.
Race day — Checkpoints: start conservative, assess at mid-race, then decide whether to hold or lift the effort toward the finish based on the plan and your remaining energy.
The Race Plan Module turns your race goal, course profile, and recent training context into one adaptive pacing plan. Load the latest inputs, trust the target profile, and change it only when the facts change.
Use it as your main pacing guide, but not as a guarantee. If effort feels clearly wrong early, move to the safer side of the target band.
Update the source before you lock the plan, or use the app’s modeled value if it matches recent training. A stale input can make the band less useful.
Re-run it after a hard session, course change, weather shift, or notable illness close to race day. Small changes matter most when they alter the race demand.
It can guide pacing and contingencies, but it cannot predict every live event. Use the checkpoints with perceived effort when the race changes.