Why your adaptive cycling plan keeps prescribing the same workouts

When repetition is the point: block periodization

Issurin's block-periodization framework concentrates one workout type for two to four weeks, on purpose, because adaptation requires a coherent stimulus. Inside a threshold block you should expect 4-6 threshold sessions of similar structure. The repetition is the mechanism. What separates a healthy block from a stuck plan is what happens at week three and what happens at week five.

Issurin's 2010 review of block periodization [Issurin 2010] is the cleanest articulation of why a good plan repeats workouts. The argument is that classical concurrent training spreads stimuli too thin to produce a measurable adaptation in any single capacity. Block periodization concentrates one or two compatible targets — threshold and tempo, or VO2max and high-cadence neuromuscular work — for a 2-4 week window so the residual fatigue and the residual training effect both build inside the same physiological pathway. The repetition is the load. A threshold block that runs only one threshold session per week is not a threshold block; it is a maintenance week with a label.

Inside that block, the workouts can and should look similar. Allen and Coggan's Progression Levels concept [Allen et al. 2019] formalizes this: the same workout type repeats while the difficulty climbs in small increments — interval count, time-at-target, percentage of FTP, or rest-interval ratio. A 4x8 minute sweet-spot session at 88% of FTP in week one becomes 4x10 at 90% in week two becomes 5x10 at 92% in week three. The structure looks identical because it is the same workout family. The numbers underneath are not. This is the legitimate case the rest of this spoke is contrasted against.

The block ends. That is the load-bearing word. Bosquet et al.'s 27-study taper meta-analysis [Bosquet et al. 2007] frames the end of a build block as a transition rather than a continuation — a deload week, then a new block targeting a different physiological system. Friel's Base/Build/Peak/Race/Transition macrocycle [Friel 2018] makes the same point at a longer timescale. The hallmark of healthy repetition is that the block transitions: into a deload, into a different block targeting a different system, or into a goal-event taper. If your plan never transitions, the repetition is not block periodization. It is something else.

When repetition is broken: three failure modes

A plan that repeats the same workouts indefinitely without progression is suffering from one of three causes: a thin workout catalog with nowhere to go, no progression model so the wattages never climb, or no goal-anchored periodization so the block never transitions. Each has a distinct fingerprint. All three are common in generic plans, and they often show up together.

Failure mode one: thin workout catalog. Most generic 12-week PDFs and many template-driven apps draw from a library of roughly 20-30 workouts; TrainerRoad's library famously runs into the thousands. Catalog size matters because the rider who sees the same six workouts month after month is correctly perceiving that the variety is not there. The plan is not adapting to the rider; it is rotating through a small fixed set. Filipas et al.'s 16-week pyramidal-distribution trial in recreational male cyclists [Filipas 2024] structured the protocol around shifting workout types across the 16 weeks — base aerobic, then sweet spot, then VO2max, then race-specific — precisely because the stimulus needed to evolve. A plan that cannot evolve the stimulus does not produce the trial's results.

Failure mode two: no progression model. The block runs Tuesday threshold and Thursday VO2max for four weeks, but week one and week four prescribe the same wattage, the same interval count, and the same rest. There is repetition without progression. The fingerprint is the wattage column: in a healthy build, the target percentage of FTP, the time-at-target, or the interval count climbs week-over-week inside the block. If those numbers are flat across four weeks, the plan has no Progression Levels equivalent [Allen et al. 2019] running underneath the structure. It is not building toward anything; it is holding station.

Failure mode three: no goal-anchored periodization. The block runs and runs and never transitions. There is no deload week, no shift from threshold to VO2max, no taper pointing at a date. Friel's framework [Friel 2018] is structured around a goal event because the goal is what determines when the build ends and the peak begins. A plan with no goal — or a plan whose goal does not actually drive the macro arc — has no reason to ever transition out of the current block. It just keeps prescribing what it prescribed last week. This is where Foster's training-monotony work [Foster 1998] becomes operational: across his 25-athlete cohort, illness clustered in weeks combining high load with high daily-load variance, and indefinite repetition of the same hard structure is a textbook high-monotony pattern.

How to tell which case you're in

The diagnostic is a five-minute audit. Look at four weeks of your plan and check three things: is the wattage progressing inside the block, does the block transition at week four or five, and how many distinct workout types appear across an eight-week window. If the answers are no, no, and fewer than five, the repetition is broken — and which of the three failure modes applies usually becomes obvious in the same audit.

Pull up the next four prescribed weeks and write down the Tuesday workout details for each: target percentage of FTP, interval count, interval duration, rest. If those numbers are flat — same wattage, same intervals, same rest week after week — the plan has no progression model. If they climb in small steps, the block is doing its job. Do the same for the Thursday workout. Seiler's intensity-distribution work [Seiler 2010] frames the principle here: well-trained athletes do not just repeat sessions; the distribution and the structure of those sessions evolve across a season. A plan that holds the same numbers indefinitely is not running that loop.

Now look at week five. Does the structure change — a deload week, a transition to a different block, a different intensity emphasis? If week five looks identical to weeks one through four, the plan has no goal-anchored periodization. There is nothing telling it to ever transition. This is the failure mode that is hardest to spot inside a single week and easiest to spot across two months. Bosquet et al.'s taper data [Bosquet et al. 2007] only matters if the plan ever decides to taper, and a plan with no transition signal will never get there.

Finally, count distinct workout types across eight weeks. A reasonable build cycle should touch 6-10 distinct workout structures: at least two threshold variants, at least two VO2max variants, an endurance ride, sweet spot, an over-under or microburst, and a recovery template. If your eight-week window contains four or five distinct workouts on rotation, the catalog is the problem. This is the broader question the pillar on adaptive cycling training plans returns to: a plan that survives real life has to read your data, restructure when the week breaks, and progress the stimulus across blocks. A plan that fails the four-week audit fails at the third leg before the first two are even tested. The sibling spoke on signs your training plan is not actually adapting covers the unplanned-ride and missed-week probes; this audit covers the inside-the-block question those probes do not reach.

Quick answers

Sources cited in this guide

1. 01
   Issurin 2010. New horizons for the methodology and physiology of training periodization. Sports Medicine.
2. 02
   Allen et al. 2019. Training and Racing with a Power Meter (3rd ed.). VeloPress.
3. 03
   Friel 2018. The Cyclist's Training Bible (5th ed.). VeloPress.
4. 04
   Foster 1998. Monitoring training in athletes with reference to overtraining syndrome. Medicine & Science in Sports & Exercise.
5. 05
   Bosquet et al. 2007. Effects of tapering on performance: a meta-analysis. Medicine & Science in Sports & Exercise.
6. 06
   Seiler 2010. What is best practice for training intensity and duration distribution in endurance athletes?. International Journal of Sports Physiology and Performance.
7. 07
   Filipas 2024. Effects of a 16-Week Training Program with a Pyramidal Intensity Distribution on Recreational Male Cyclists. Sports (MDPI).

More inside Adaptive cycling training plans that survive real life

Other articles in this series

1. 01

   Five signs your training plan isn't actually adapting

   Every cycling app claims to be adaptive. Three diagnostic signs separate plans that actually adjust from static plans with a glossy UI.

   →
2. 02

   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.

   →
3. 03

   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.

   →
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.

    →