Start at the mileage you already run, not the peak

High confidence

Start a plan at the mileage you already run, not the bigger number it builds to later. The plan's whole job is to carry you up to that peak, so week 1 should feel like a normal week, not a reach.

Why it works

The body adjusts slowly. Muscles, tendons, and the heart take weeks to catch up to harder training, and that steady week-by-week climb is what actually builds fitness. So week 1 only needs to match what you already handle. Anchor it to the peak instead and the first week becomes a big spike (a high acute-to-chronic load ratio, where one week towers over your recent average). That spike also skips the very adjusting the build is meant to create.

What it means in practice

Set recommendedStartingVolume to the plan's week-1 volume, and write the entry bar to match ('you should already be running about X'), not the peak. In plan reviews, flag two things: prose that tells a runner they only need a base well below week 1 (a hidden week-1 spike), and starting volumes set near the peak. Check that the ramp works from the anchor. Don't raise the anchor to pre-cover later weeks.

The evidence

Why we call confidence high

The finding lines up across several kinds of study. Plans built off a measured baseline support it (Nuuttila 2022, Roberson 2018). So do staged plans that ease runners in before the hard block (Ramskov 2018, Auersperger 2013) and clinical and marathon guidance (Vora 2018). The direction is well supported. But most of this evidence comes from how the studies were designed and observed, not from trials built to test baseline-setting on its own, so it rates high rather than very-high.

Where it applies

Adult recreational and trained runners starting a multi-week structured plan, at any race distance.

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 Jun 11, 2026. See how we score.