Set block goal
Define the current phase goal and weekly structure before changing sessions.
Build the block, execute the week, review drift, and adjust only what is necessary.
Define the current phase goal and weekly structure before changing sessions.
Bring completed workouts back into the plan and mark execution quality.
Check ATL/TSB pressure and effective VO2max response before editing volume or intensity.
Apply draft changes only after the rationale is clear and tradeoffs are explicit.
Good AI planning is conservative, explicit, and easy to audit.
Adjust either volume or intensity first, then validate response on the next key workout.
When stress rises quickly, preserve frequency and reduce intensity before adding more load.
Long runs and marathon-pace sessions stay high quality by trimming surrounding fatigue.
Each adjustment should include before/after context and why the change was made.
Common marathon planning questions: weekly structure, load control, and when to adjust.
Adjust only when execution or recovery signals materially diverge from plan assumptions, not after every minor fluctuation.
Usually maintain the key session and reduce supporting intensity first to protect adaptation while controlling fatigue.
Yes. AI can summarize load trend and readiness signals, but final taper tradeoffs should still be confirmed by athlete or coach.
It helps verify whether training stress is translating into usable performance, especially when volume is high.
The free marathon page owns the week-by-week schedule. This page owns the AI marathon training plan: how completed runs and training load become confirmable adjustments after you start that block.
Last updated: