Is my training plan actually adapting? The diagnostic test for self-coached cyclists

Sign one: it gives the same plan to a 6h/wk rider and a 12h/wk rider

If two riders with similar FTPs but different weekly time budgets receive structurally identical plans — same workout types, same progression, same intensity distribution — the plan is not adapting to either of them. It is fitting both to a population template. Individualization at the level of weekly load is the lowest bar an adaptive plan must clear, and a surprising number of products fail it.

Kiely's 2018 review of periodization theory [Kiely 2018] is one of the most direct critiques of how training plans are actually built. Prescriptions are typically derived from group means rather than individual response curves, and the inter-individual variation in adaptive response to identical training is large enough that a plan calibrated to the population mean can be net-negative for a meaningful share of athletes. A plan that does not take weekly hours and recovery capacity as primary inputs is, by construction, optimizing for a population the rider may not belong to.

The mechanism this hides is Foster's training-monotony curve [Foster 1998]. The 6h/wk rider on a plan calibrated for 10h/wk lands in a high-monotony zone — too much of the time gets swallowed by intensity because the plan assumes endurance volume is being added on top. The 12h/wk rider on the same plan is under-stimulated and adds unstructured volume to compensate, which then collides with the next prescribed hard day. Both failures look like the rider's problem and are actually the plan's. A genuinely adaptive plan reshapes the entire weekly intensity distribution around hours-per-week before a single workout is selected.

Sign two: a 90-minute hard group ride does not shift the rest of the week

An unscheduled hard ride banks intensity stimulus the plan was going to prescribe later. If the plan reads the ride and changes nothing — Tuesday's threshold session still on the calendar, weekly TSS target unchanged — it is not adapting. The week is a budget, not a sequence, and a plan that cannot rebalance after an unplanned effort is treating it as a sequence.

The mechanism here is the weekly intensity distribution, not the daily TSS total. Stoggl & Sperlich's 2014 controlled trial [Stoggl & Sperlich 2014] randomized 48 well-trained endurance athletes across four distribution models for nine weeks; the polarized group — roughly 80% low intensity, 20% high intensity, very little tempo — produced the largest VO2peak gain (+11.7%) and the largest time-to-exhaustion gain. The follow-up across well-trained and elite athletes [Stoggl & Sperlich 2015] confirmed the distribution is what matters, not any single workout. A plan that lets a hard unplanned ride land on top of a normal week of intensity has pushed the ratio outside the band where adaptation happens.

Foster's monotony work [Foster 1998] amplifies the same point from the illness side. Across his 25-athlete cohort, illness clustered in weeks where load and daily-load variance were both high — exactly the pattern produced when an unplanned hard ride lands on an unchanged plan. The right reaction is to redistribute. Tomorrow's threshold work becomes recovery; the weekend's prescribed hard ride drops one tier or pushes 24 hours; the weekly TSS target may not change at all. A plan that does this is reading the ride. A plan that reprints the same Tuesday workout is reading the calendar.

TrainerRoad's Adaptive Training adjusts the difficulty of the next indoor workout, but the structure of the week stays fixed by the Plan Builder block. Xert's Training Load model continuously updates against every effort, including outdoor rides, and is genuinely strong here. JOIN handles a moderate version of this case well; many TrainingPeaks plans and most generic 12-week PDFs fail it outright. The probe is simple: do an unscheduled 90-minute hard ride on Sunday, then check Monday whether anything in the plan moved.

Sign three: a sick week makes the plan shrink, not restructure

When illness or travel removes a week, a static plan compresses what got missed into the following weeks at lower volume — the plan shrinks. An adaptive plan restructures: skip the missed work, reset the chronic-load ramp, and re-anchor the macro arc to the new dates. Compression is the most common amateur-coaching error and one of the strongest signals that the plan is not adapting at all.

Mujika & Padilla's detraining series [Mujika & Padilla 2000] documented that even short interruptions of 7-14 days produce measurable cardiovascular drift — VO2max drops driven mostly by reduced blood volume and stroke volume, with peripheral adaptations largely intact. Resuming the original plan at the original wattages puts the rider back at full chronic load on a decompressed acute base. The acute:chronic workload framework [Hulin et al. 2016] places elevated injury and illness risk at ratios above roughly 1.5, and a normal full-volume week after seven days off lands well outside that band.

The diagnostic version of this sign is simpler. Look at what the plan does on the day you log a sick week. If the next week starts at 100% of pre-break target and the prescribed intervals look identical, the plan has not adapted — it has just slid forward by seven days. If the plan compresses the missed peak block into fewer weeks at the same intensity, it has done the worst thing on the menu: increased acute load on a decayed chronic load while shortening the recovery between hard days. A plan that adapts will skip the missed work, set the resumption week at 60-70% of pre-break volume, and either move the goal event back or downgrade it from A to B priority.

How to probe your plan in 14 days

If reading the signs is ambiguous, run the probe. Two weeks, three deliberate perturbations, three things to check. The probe is designed so a genuinely adaptive plan will visibly respond and a static plan will visibly not. It costs nothing in fitness — every perturbation is a normal cycling event that real life produces anyway.

Day 1: skip a prescribed key workout — the hardest one of the week. Mark it as missed in whatever app you are using. Check the next prescribed week. A genuinely adaptive plan will have shifted the intensity distribution, dropped the next hard day one tier, or rebuilt the week to absorb the missed stimulus across two or three sessions. A static plan will look identical, with the missed workout either deleted or copy-pasted into the next available slot. Halson's training-load monitoring review [Halson 2014] is direct: load monitoring exists to confirm whether an athlete is adapting to the program, and a plan that does not respond to a missed key session is not running that loop.

Day 5: do an unscheduled 90-minute hard group ride at zone 3 to threshold. Check the next 48 hours. Did Tuesday's threshold work shift to recovery? Did the weekly TSS target adjust to keep the intensity ratio inside the polarized or pyramidal band [Stoggl & Sperlich 2015]? Day 12: log a 7-day forced break — most apps support this through a sickness flag or travel block. Check the resumption week. If it starts at 100% of pre-break volume, the plan is not handling the detraining curve [Mujika & Padilla 2000]. If it starts at 60-70% with intensity backed off, the plan is doing the right thing.

Two or more failures and the plan is operating as a static schedule with adaptive marketing — at which point the choice is to keep the plan and become your own restructure engine, or to move to a tool that does it natively.

Quick answers

Sources cited in this guide

1. 01
   Kiely 2018. Periodization Theory: Confronting an Inconvenient Truth. Sports Medicine.
2. 02
   Foster 1998. Monitoring training in athletes with reference to overtraining syndrome. Medicine & Science in Sports & Exercise.
3. 03
   Stoggl & Sperlich 2014. Polarized training has greater impact on key endurance variables than threshold high intensity or high volume training. Frontiers in Physiology.
4. 04
   Stoggl & Sperlich 2015. The training intensity distribution among well-trained and elite endurance athletes. Frontiers in Physiology.
5. 05
   Mujika & Padilla 2000. Detraining: loss of training-induced physiological and performance adaptations. Part I: short term insufficient training stimulus. Sports Medicine.
6. 06
   Hulin et al. 2016. The acute:chronic workload ratio predicts injury: high chronic workload may decrease injury risk in elite rugby league players. British Journal of Sports Medicine.
7. 07
   Halson 2014. Monitoring training load to understand fatigue in athletes. Sports Medicine.

More inside Adaptive cycling training plans that survive real life

Other articles in this series

1. 01

   Missed key workout vs missed recovery ride: why it matters

   Missing a threshold session and missing a recovery ride are different signals. Why an adaptive plan should respond to each differently.

   →
2. 02

   Can an adaptive cycling plan work without a goal race?

   What an adaptive training plan looks like when there's no event date — the rolling structure, the goal proxies, what doesn't change.

   →
3. 03

   Why your adaptive plan keeps prescribing the same workouts

   Block periodization explains some workout repetition. Three failure modes explain the rest — and how to tell which one your plan is doing.

   →
4. 04

   Adaptive cycling plan vs static plan: 5 structural tells

   Most plans marketed as adaptive are static plans with a reactive UI. Five structural differences that separate genuine adaptation from rebranding.

   →
5. 05

   What your training plan should do after an unplanned group ride

   An unscheduled hard group ride banks intensity the plan was going to prescribe later. What an adaptive plan should do tomorrow — and why most don't.

   →
6. 06

   What an adaptive cycling plan does after a sick week

   Not the return-to-riding question — the plan-mechanism question. What the plan should do to itself after illness: skip, ramp, and macro-arc rules.

   →
7. 07

   Goal race rescheduled mid-block: how an adaptive plan adjusts

   When the A-priority date moves earlier or later mid-build, the plan has to restructure — not just relabel the calendar. The math behind each scenario.

   →
8. 08

   Adding a gravel event mid-block: what an adaptive plan changes

   A gravel event added mid-build is a durability problem first. What an adaptive plan should change in the next 4 weeks — and what it shouldn't.

   →
9. 09

   What 'restructuring the week' actually does in an adaptive plan

   Restructure is the marketing word. Operationally it is a four-constraint solver on the remaining week — what it reads, decides, and cannot do.

   →
10. 10

    AI cycling coach vs human coach: when each one wins

    Where the AI-vs-human-coach line actually sits in 2026 on adaptation — what each does well and when to pay the premium for a person.

    →
11. 11

    TrainerRoad vs JOIN vs AdaptCycling on adaptation

    Three apps, three definitions of adaptation. How TrainerRoad, JOIN, and AdaptCycling actually differ on plan restructure — and how to pick.

    →