The marathon is the distance least forgiving of a plan you cannot actually follow. Sixteen weeks is long enough that something will go wrong: a cold, a work trip, a week you simply cannot train. What separates finishers who run well from finishers who suffer is rarely the plan they downloaded. It is what happened when the plan met reality.
This guide covers the structure that works, how to set a goal you can actually hit, and where marathon blocks usually break down. Here is the shape of the whole thing first.
What a 16-week marathon block looks like
Not the same week repeated. Volume climbs in waves, with a lighter week roughly every fourth to absorb the load, then drops sharply so you arrive fresh.
- Peak week
- 52 milesweek 11
- Race week
- 14 milesabout 27% of peak
- Base Volume grows, nearly all of it easy
- Build Volume holds, quality increases
- Peak Longest runs, most race-specific work
- Taper Volume drops, freshness returns
Illustrative for a runner peaking near 50 miles a week. The shape is what matters, not the numbers: your own peak depends on your base, your history, and the hours you actually have.
Before you start
Two honest prerequisites.
A base. You want to be running comfortably several times a week before a marathon block begins, with a longest run already in the region of an hour or more. If you are starting from scratch, spend a few months building that base first. Marathon training builds on aerobic fitness; it is a poor way to acquire it.
The time. A marathon block is not just the long run. It is four to six sessions a week for months, and the long runs alone stretch to two and a half or three hours plus recovery. Be honest about the hours before you pick a goal that requires more of them than you have.
How long you need
For most runners with a reasonable base, twelve to twenty weeks. Twelve is workable if you are already fit and running regular long runs. Sixteen is the common default and suits most people. Twenty gives room to build gradually and absorb interruptions, which matters more than it sounds.
If you have never run the distance, plan toward the longer end. The extra weeks are not extra fitness so much as extra tolerance for the weeks that go wrong.
The shape of a block
A marathon plan is not the same week repeated. It moves through phases, each building on the last.
Base. Volume grows gradually, nearly all of it easy. Long runs extend. Intensity is limited, mostly some light strides or short threshold work to keep turnover.
Build. Volume plateaus near its peak while quality increases: threshold sessions get longer, and marathon-pace work starts appearing inside long runs. This is the phase that makes goal pace feel manageable.
Peak. The highest-demand weeks, with the longest runs and the most race-specific sessions. Also where injury risk is highest, which is why what comes next is not optional.
Taper. Two to three weeks of reduced volume with some intensity retained. You do not lose fitness in a taper; you shed accumulated fatigue and arrive fresh. Runners who skip it race tired and cannot understand why the goal pace felt so much harder than in training.
Down weeks are part of the plan
Adaptation happens during recovery, not during the hard session. A block that climbs every single week accumulates fatigue faster than fitness. Most well-built plans pull volume back roughly every third or fourth week so the next block starts from a recovered base.
The long run
The cornerstone, and the session most often done wrong.
Distance. Most plans build toward a longest run somewhere between 18 and 22 miles, or roughly three hours, whichever comes first. Time on feet matters more than the number, and for slower runners a full 22 miles in training costs far more in recovery than it returns.
Pace. Predominantly easy. The long run's job is aerobic development and time on feet, not proving you can run fast when tired. As the block progresses, adding a segment at marathon pace inside a longer easy run is where the real race-specific gains come from.
Fuelling. Practise it. Take on carbohydrate and fluid during long runs at the same rate you intend to use on race day, and use the products the race actually serves if you can. A gut that has never been asked to absorb fuel at pace will refuse on race day, and no amount of fitness compensates.
Setting a goal time you can actually hit
Start from evidence rather than hope. Run a 10K or half marathon in the block and convert it with the race time predictor, then treat the marathon number with suspicion.
The formula assumes you are equally well trained for both distances, and that assumption fails hardest at the marathon. Predicting a marathon from a 10K flatters anyone who has not done the long runs, often by several minutes. The tool has a fatigue factor for exactly this: raise it toward 1.10 if your weekly mileage is modest, and treat the prediction as a ceiling rather than a target.
Once you have a realistic goal, turn it into per-mile numbers and splits with the running pace calculator, and note them somewhere you will see them on race morning.
Race day pacing
The most common way to ruin a marathon is to run the first 10K faster than goal pace because it feels easy. It feels easy because it is early, and the debt comes due after 20 miles.
Aim for even or very slightly negative splits. If anything, run the first few miles a touch slower than goal pace and let the pace settle. The time you save going out fast is small; the time you lose to a blown second half is enormous.
For managing effort rather than pace, especially in heat or on hills, having your heart rate zones set correctly gives you a second reference when pace alone is misleading.
Where marathon blocks actually break down
- Easy days run too hard. The most common error, and it quietly wrecks the hard sessions that matter. See understanding your training paces.
- Chasing missed sessions. A missed week is not recovered by cramming it into the next one. Absorb the loss and continue from where you actually are.
- Building volume too fast. Most running injuries trace back to a jump in load the body was not ready for.
- Skipping or shortening the taper. Fitness gained in the last two weeks is negligible. Freshness lost is not.
- Testing something new on race day. Shoes, fuel, a jacket, a pacing strategy. Race day is for rehearsed decisions only.
Why plans fail, and what to do about it
Nearly every marathon plan is written for someone whose next sixteen weeks go exactly as scheduled. Nobody's do. You get sick in week seven, travel in week eleven, and tweak a calf in week fourteen, and the neatly printed PDF has no answer for any of it.
The skill is knowing what to drop, what to keep, and how to rebuild the weeks ahead around where you actually are. Vaast does that continuously: it holds your goal and race date, reads the training you have genuinely completed, and reshapes the remaining weeks whenever life gets in the way, so the plan still lands you on the start line ready.