
N+One adds non-cycling Apple Health workouts to your training load so the coach sees the fatigue, but they never tick off a planned ride.
On this page

Photo by paolo candelo on Unsplash.
N+One adds non-cycling Apple Health workouts to your training load so the coach sees the fatigue, but they never stand in for a planned ride.
This guide is practical coaching and data hygiene, not new physiology research. A PubMed search did not return direct evidence for this exact product workflow, so the guidance below stays narrow: clean the source data, label what matters, and avoid giving incidental workouts the same weight as planned rides.

Photo by Ricardo IV Tamayo on Unsplash.
Apple Health can show workouts that were never meant to steer your cycling plan. N+One adds non-cycling Apple Health workouts to your training load, without letting them tick off a planned ride.
The aim is not to prove a new training model from one app export. The aim is to keep your ride signal clean before your next workout is set.
If you are still setting up Apple Health access, start with linking iPhone Health to N+One before you judge any workout labels.
Treat this as coaching plus data hygiene, not new physiology research.
Do not infer fitness gains from random Apple Health rows.
Keep planned cycling files as your first signal.
Count non-cycling workouts in training load; they never tick off a planned ride.
In N+One terms: clean inputs protect the next decision.
Clarify the signal, reduce the noise.
Apple Health gathers entries from a watch, phone, third-party apps, and manual logs. That wide net is useful, but it can also blur what counts as training.
A strength session, short walk, treadmill run, or auto-detected workout may land beside your rides. Some rows belong there; some only add noise.
The same issue shows up across devices and recovery tools, which is why comparing recovery sources calmly matters more than chasing one number.
Duplicate rides: one session logged twice from two sources.
Cross-training: strength, run, yoga, or swim sessions that were planned.
Noise: short, incidental, or auto-detected sessions with little coaching value.
Device drift: one source names the workout better than another.
Label first, then weigh.
N+One scores every completed Apple Health workout into the same daily training load as rides, from power, heart rate or RPE, with a lower fallback when those are missing. Non-rides never tick off a planned bike session…
Data analysis is free, forever. The Dynamic Coach is Pro. Connected to Garmin, Strava, Whoop, and intervals.icu.
Use three labels: ride, cross-train, and ignore. The label should reflect coaching value, not just the app category.
Keep rides that came from a trusted cycling source, especially when they include power, heart rate, or full duration. If power is missing, heart-rate-only setup limits help set safer expectations.
Reclassify planned strength, run, yoga, or swim work as cross-train when it was part of your week. Ignore short, incidental rows unless you know they mark a real planned session.
Keep if the activity is cycling or clearly named bike, ride, indoor bike, or trainer.
Reclassify if it was planned non-cycling work that supports the week.
Ignore short auto-detected sessions with no clear training purpose.
Protect races, tests, and key rides before any broad filter runs.
In N+One terms: the label decides how much the workout can steer you.
Conserve your cycling signal; deprioritize incidental volume.
Start with the source that records the ride best, not the source that syncs first. For many cyclists, that means a head unit, smart trainer, or power meter file.
Then set your app chain so the clean ride file wins over a generic watch workout. If you use a head unit, Karoo and Hammerhead workout sync can keep the main ride path clear.
For exports, add one field named N+One_label and use ride, cross-train, or ignore. This small step makes the training system easier to audit later.
Pick one primary cycling source for ride files.
Turn off incidental auto-adds if they keep polluting the log.
Add N+One_label to exports before importing them elsewhere.
Check the last week after each rule change.
Prefer the high-fidelity source and label the rest.
One tactical email with training ideas and product updates. No spam — unsubscribe anytime.
Keep reading
- Connecting intervals.icu to N+One: What Syncs and What Stays Local — Learn what may sync between intervals.icu and N+One, what likely stays local, and the safest way to test a structured workout import.
- Stages, 4iiii, Favero, and Quarq Power Meters With N+One: Calibration and Zero-Offset Tips — Use a simple pre-ride zero-offset workflow for Stages, 4iiii, Favero, and Quarq power meters before your next key workout with N+One.
- Connect Strava to N+One: Step by step — Connect Strava to N+One with a clear setup flow: open settings, choose Strava, authorize access, verify your first ride, and fix common sync issues.
N+One does not treat every Apple Health workout as an equal cycling input. It first looks for useful signals, then weighs the session by its role.
A ride with power is closer to the core cycling model than a generic strength entry. When power is absent, heart rate and duration can give context, but they should not be stretched into false certainty.
This same logic applies when structured work comes from other tools, such as Zwift sessions into an adaptive plan or smart trainer files in N+One.
Use power first when a real cycling file has it.
Use heart rate and duration as supporting context.
Downweight vague cross-training instead of overstating it.
Exclude incidental rows from weekly ride volume.
In N+One terms: non-ride load shapes fatigue and recovery without rewriting the ride plan.
Supportive work still adds load so the coach sees the fatigue, but it does not replace the main cycling stimulus.
Do not let a broad filter delete your best evidence. Races, time trials, long endurance rides, and planned bricks deserve review before they are dropped.
If a watch merges a ride and run, split the file if your tools allow it. If a head unit loses GPS but the workout still matches the plan, keep it and note the gap.
When a session looks odd, flag it as protected until you check it. The same audit habit helps when pairing a power meter or fixing Garmin auto-sync.
Keep races and time trials even when the activity type looks wrong.
Split merged brick sessions into clear ride and run labels.
Keep planned rides with device gaps, then annotate what failed.
Review protected sessions before any bulk clean-up.
Protect high-value sessions first.
Day 0 — Snapshot: Export the last month from Apple Health, or open your sync app, and count cycling entries, non-cycling sessions, and short incidental rows.
Day 1 — Apply the decisive filter: Flag short auto-detected workouts as ignore, then tag planned strength, run, yoga, or swim sessions as cross-train.
Day 2 — Prioritize sources: Prefer dedicated cycling files from a head unit, trainer, or power meter over phone or generic watch sources.
Day 3 — Protect key work: Mark races, long endurance rides, tests, and planned bricks as protected before broader filters run.
Day 4 — Feed the cleaned log: Send the labeled data into your coach or training log, with cross-train as context and ignored rows outside weekly ride volume.
Day 7 — Reassess and lock: Check whether valuable sessions were missed, adjust the rules once, then hold them steady for the next training block.
N+One adds non-cycling Apple Health workouts to your training load, without letting them tick off a planned ride. Your clear next move is to label the last week as ride, cross-train, or ignore, then let the next workout decision come from the cleanest signal.
No. The coaching logic is to classify the workout first, then decide how much it should shape cycling guidance. Planned cross-training can still matter, while incidental rows should not drive your ride plan.
Keep the higher-fidelity cycling file as the main ride record. In most cases, that means the file with the better cycling data, such as power, full duration, and a clear activity type.
Treat strength work as real training load, not as a completed cycling session. It may affect readiness and how the next workout feels, but it should not be logged as a ride.
Use heart rate and duration as useful but limited signals. N+One should stay conservative when power is missing, because the session carries less cycling-specific detail.