What 'restructuring the week' actually does inside an adaptive training plan

What 'restructure' means operationally: swap, shift, restructure are three different operations

A swap is one-for-one substitution: Tuesday's threshold becomes Tuesday's endurance. A shift slides days: Tuesday's threshold becomes Wednesday's threshold. A restructure rebuilds the entire remaining week against a new constraint set — load, intensity ratio, recovery placement, and goal arc all recomputed together. Most apps that claim to restructure are actually doing one of the first two.

The distinction matters because the three operations solve for different things. A swap defends the day; a shift defends the calendar; only a restructure defends the week. When an athlete logs a missed VO2 on Monday with five days left and eight weeks to a goal event, swap-only logic asks what Monday should have been; shift-only logic asks where the session goes next. A restructure asks what the remaining five days should look like given the missed stimulus, current chronic load, the polarized-distribution target [Seiler 2010], and goal proximity — then rebuilds Tuesday through Sunday as a single decision.

Concretely: weekly target was 600 TSS with one VO2 session, one threshold session, and a long endurance ride. The athlete misses the VO2. A restructure skips it rather than rescheduling, demotes Tuesday's threshold to tempo to keep the high-band budget defensible, holds Friday's recovery, and defends Saturday's long ride because endurance volume protects the chronic-load ramp [Allen et al. 2019]. New weekly target is 470 TSS. IF lands inside the polarized band. No compression. The missed VO2 is gone — most lost stimuli should be skipped, not chased.

TrainerRoad's Adaptive Training swaps well within an indoor block. JOIN handles partial shifts cleanly. Xert updates load continuously but defers the week-shape decision to the athlete. Wahoo SYSTM and Garmin DSW are template-rotation systems with intensity-tier swaps bolted on. None of those products are bad at what they do — they are doing the swap or the shift, not the restructure, and the marketing word does not distinguish.

The four constraints the solver must honor

Any honest restructure has to satisfy four periodization invariants simultaneously: the chronic-load ramp from the Coggan and Allen framework, the weekly intensity distribution from Seiler's polarized-pyramidal evidence, the daily-load monotony bound from Foster's overtraining work, and the macro-arc anchor from Friel's goal-event periodization. Violate any one and the restructure has solved the wrong problem.

Constraint one is the chronic-load ramp. The standard guidance from Allen and Coggan [Allen et al. 2019] keeps weekly TSS increases inside roughly 4 to 7 TSS-per-day per week during a build phase. A restructure that proposes a 600-to-720 TSS jump to make up for a missed week violates this directly; a restructure that proposes 470 TSS after a partial-week disruption sits comfortably inside the band. Constraint two is the intensity distribution. Seiler's polarized-training synthesis [Seiler 2010] is the most replicated finding in endurance research: the ratio of low to high intensity across the week is what produces the adaptation, not the gross load. The restructured week has to keep roughly 75 to 85 percent of the time below the first lactate threshold.

Constraint three is daily-load monotony. Foster's 25-athlete cohort study [Foster 1998] showed illness clustered in weeks where load was high and daily-load variance was low — when every day looked similar in stress. A restructure that fills the gap from a missed key session with three medium days hits the monotony trap directly. The solver has to preserve at least one genuine recovery day and one clear high-intensity day inside the rebuilt week. Constraint four is the macro arc. Friel's Base-Build-Peak-Race-Transition framework [Friel 2018] and Bosquet et al.'s 27-study taper meta-analysis [Bosquet et al. 2007] anchor the restructure to the goal date: the rebuilt week has to leave the macro phase intact, or the engine has to explicitly move the goal.

Issurin's block-periodization work [Issurin 2010] sits across all four. A restructure inside a threshold block has to keep the block's concentrated stimulus coherent — skipping the week's only threshold session because Tuesday got blown by life turns the block into a maintenance week with a label. When no remaining-week shape satisfies the four invariants and delivers the block's intended adaptation, the right answer is to extend the block by a week and re-anchor the macro arc, not to compress missed work into the days that are left.

What inputs the engine reads

A restructure that gets the math right reads five inputs every time: the Strava-derived ride data for the week so far, the completion state of remaining sessions, the athlete's profile and weekly-hours budget, the calendar window with constraint days marked, and the goal-event distance. Plans that read fewer inputs end up doing swaps and shifts dressed as restructures.

Strava ride data is the first input and the one most apps use well: normalized power, intensity factor, time-in-zone, and TSS from the Allen and Coggan framework [Allen et al. 2019]. A 90-minute unscheduled ride at NP 230 on a 250-watt FTP returns IF 0.92 and roughly 127 TSS — enough to know the week's high-band budget is partially spent before the solver looks at tomorrow. Completion state is the second input. A restructure on Tuesday with three sessions still on the calendar has more degrees of freedom than one on Friday with one session left. Most static plans do not read this and propose the same compression regardless of when the disruption occurred.

The athlete profile is the third input — weekly hours available, FTP, experience, recovery capacity. A 6-hour-per-week rider's restructure cannot copy a 12-hour-per-week rider's even when the disruption is identical, because the constraint surface is different. The calendar window with constraint days marked — soccer tournament, work travel, wedding — is the fourth input. The fifth is goal-event distance. Eight weeks out from an A-priority event, the restructure can absorb a missed VO2 without moving the goal. Three weeks out, the same disruption forces a goal-priority decision because the taper window [Bosquet et al. 2007] cannot share days with a rebuild.

This is the architecture the broader question — what adaptive cycling training plans should do when life gets in the way — depends on. The parent guide on adaptive cycling training plans makes the case that reading these five inputs and reshaping the week against the four constraints is what separates plans that survive real life from plans that just generate. A restructure that does not read what actually happened is running the loop open.

What restructure cannot do

A restructure is a solver over the days the athlete has left. It cannot violate the four periodization invariants, cannot manufacture lost adaptation, and cannot rebuild fitness faster than the underlying physiology curves allow. Athletes who expect a restructure to recover a missed peak block in two weeks are asking for an operation the engine has no legal move for.

The hard physiology constraint is the detraining curve. Mujika and Padilla's short-term detraining review [Mujika & Padilla 2000] documents that VO2max decline inside the first month off is driven largely by reduced blood volume and stroke volume, with rebuild times in the 2 to 3 week range under structured training. A restructure proposing full pre-break wattages in week one of a post-illness rebuild is asking the cardiovascular system to be where it physiologically is not. The correct move is to cap intensity time at 60 to 70 percent of pre-break load and let the chronic-load ramp [Allen et al. 2019] do the rebuild work over two to three weeks, not one.

The hard periodization constraint is the macro arc. A restructure cannot decide on its own that the goal event moves — that is an athlete decision the engine surfaces. What it can do is compute the math: a missed week six-plus weeks from the event usually absorbs cleanly; a missed week inside three weeks collapses the taper window and forces the goal to move, downgrade in priority, or shift to participation. The restructure surfaces the choice with numbers attached. It does not make it.

The hard accounting constraint is that lost stimulus is lost. The right move when a key session is missed is almost always to skip it, accept the block ran one stimulus light, and let the next block proceed on schedule [Issurin 2010]. The wrong move — and the one static plans default to — is to compress missed work into the following weeks, which violates the chronic-load ramp and the monotony bound simultaneously and produces the overtraining signature Foster's work [Foster 1998] is built on. A restructure's most important property is that it knows when to skip.

Quick answers

Sources cited in this guide

1. 01
   Allen et al. 2019. Training and Racing with a Power Meter (3rd ed.). VeloPress.
2. 02
   Seiler 2010. What is best practice for training intensity and duration distribution in endurance athletes?. International Journal of Sports Physiology and Performance.
3. 03
   Foster 1998. Monitoring training in athletes with reference to overtraining syndrome. Medicine & Science in Sports & Exercise.
4. 04
   Friel 2018. The Cyclist's Training Bible (5th ed.). VeloPress.
5. 05
   Bosquet et al. 2007. Effects of tapering on performance: a meta-analysis. Medicine & Science in Sports & Exercise.
6. 06
   Mujika & Padilla 2000. Detraining: loss of training-induced physiological and performance adaptations. Part I: short term insufficient training stimulus. Sports Medicine.
7. 07
   Issurin 2010. New horizons for the methodology and physiology of training periodization. Sports Medicine.

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

   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.

   →
5. 05

   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.

   →
6. 06

   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.

   →
7. 07

   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.

   →
8. 08

   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.

   →
9. 09

   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.

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

    →