Sixteen weeks is the sweet spot for a marathon build. Long enough to push your peak weekly mileage to a meaningful level. Short enough that life does not derail it. Smart Runner's 16-week marathon training plan takes the structural backbone Pete Pfitzinger laid out in Advanced Marathoning and adapts the workload every week to your actual training.
Why 16 weeks works
A marathon build needs four distinct phases (base, aerobic strength, marathon-specific, taper) and each phase needs at least 3 weeks to deliver its adaptation. That puts the minimum at 12-14 weeks. Sixteen gives each phase room to breathe, a cutback week mid-phase to absorb the load, and a real taper that does not feel rushed.
Anything longer than 18 weeks risks fitness peaking too early or training getting stale. Anything under 12 weeks compresses the marathon-specific work into a window your body cannot adapt to.
The four mesocycles inside the 16-week plan
Weeks 1-4: Base
The point is consistent aerobic running. Easy days at honest easy pace, one medium-long run mid-week, one long run on the weekend. Quality work is minimal, just strides and the occasional progression long run. Peak mileage during base is roughly 70 percent of your eventual peak.
Weeks 5-9: Aerobic strength
Lactate threshold becomes the highest-priority weekly workout. Tempo intervals or continuous tempo, 25-40 minutes of work at threshold pace per session. The long run grows steadily and includes occasional pickups. Peak mileage climbs by ~10 percent per week with cutbacks every third week.
Weeks 10-13: Marathon-specific
The defining phase. Long runs include 8-15 km blocks at marathon pace. A weekly lactate-threshold session continues. VO2max work appears as accent pieces, not the focus. Peak long run (32-35 km) and peak weekly mileage land here.
Weeks 14-16: Taper
Volume drops by roughly 20 percent in week 14, 35 percent in week 15, and 50 percent in race week. Intensity stays. The TSB curve crosses into positive territory by the Wednesday before race day. By Sunday's gun, you are fresh, not flat.
Sample weeks at a glance
Week 6 - aerobic strength
52 km / 32 mi
Tue 8 km w/ 4 km tempo · Thu 12 km MLR · Sat strides · Sun 20 km long
Week 11 - marathon-specific
68 km / 42 mi
Tue 10 km w/ 5x1 km @ T · Thu 14 km MLR · Sat strides · Sun 30 km w/ 12 km @ MP
Week 14 - taper
48 km / 30 mi
Tue 8 km w/ 3x1 km @ T · Thu 10 km easy · Sat strides · Sun 22 km long
Week 16 - race
~52 km / 32 mi
Mon easy · Tue shakeout w/ strides · Wed rest · Thu 5 km easy · Sat 3 km jog · Sun race
How the plan adapts
The framework is fixed. The targets are not. Every week, Smart Runner looks at:
- What you actually ran (from Apple Health and the Apple Watch).
- Your current ATL, CTL, and TSB.
- Days until race day.
- Your VDOT, refreshed whenever you log a new race result.
From those, the next week's volume, intensity distribution, and key workouts are placed. If you missed two runs last week, this week eases off so you do not stack fatigue on top of a missed cutback. If you nailed every session and the form curve looks healthy, intensity nudges up.
What if you miss a week?
The plan rebases. Missing a single week mid-base does not move race day. Missing a week in the marathon-specific phase shifts the long-run progression back by one slot. If you miss two consecutive weeks during the marathon-specific phase, Smart Runner notifies you that a more conservative goal is appropriate and adjusts pace targets accordingly.
What you need to start
- An iPhone (iOS 17+).
- Optional but recommended: an Apple Watch for structured workout playback.
- A recent race result for VDOT calibration (5K, 10K, half, or marathon). Or skip this and start in volume-building mode.
- A race date 16 weeks out, give or take a couple weeks.
Why this plan, vs the PDFs you can download free
A free 16-week PDF from a magazine site is fixed. It assumes you nailed every previous week. It does not change when you have flu, when you skip a long run, or when you have a breakthrough race in week 8 and your paces should reset. Smart Runner is the same structural plan, with the math underneath the surface running every time the app opens.
If you want to read more about the methodology behind it, our Pfitzinger vs Daniels vs Canova guide covers the trade-offs.