Anchor baseline to current load, not peak

A training plan's starting volume should be anchored to the load the runner already tolerates - the plan's first-phase / week-1 volume - not to the peak or later weeks.

In plain English

Start a plan at the mileage you're already running, not the big number it builds to later. The plan's job is to grow you toward the peak, so week 1 should feel like a normal week, not a stretch.

Why it works

Tissue and aerobic adaptations accrue over weeks, and the planned progression is the intended driver of fitness, so the entry load only needs to match current capacity. Anchoring to peak would front-load a large jump (high acute:chronic ratio) and skip the adaptation the build is meant to deliver.

What it means in practice

Set recommendedStartingVolume to the plan's week-1 volume, and calibrate entry-bar prose ('you should already be running about X') to that same number, not to peak. In plan reviews, flag prose that tells a runner they only need a base well below week 1 (a hidden week-1 spike) and flag starting volumes set near the peak. Verify the ramp is feasible from the anchor, but do not raise the anchor to pre-cover later weeks.

The evidence

Why we call confidence high

Convergent across individualized endurance-training designs that scale the program off a measured baseline (Nuuttila 2022, Roberson 2018), staged designs that precondition before the specialized block (Ramskov 2018, Auersperger 2013), and clinical/marathon guidance (Vora 2018). Direction is robust; evidence is largely design-level and observational rather than RCTs isolating baseline-setting, so high not very-high.

Where it applies

Adult recreational and trained runners beginning a multi-week structured plan, across event distances.

Does not apply to: true beginners starting from walk-run, where week 1 may be near-zero and 'current tolerated load' is the relevant anchor rather than a mileage number; elite athletes with bespoke coaching.

Last reviewed 2026-06-12. See how we score.