16-Week Marathon Training Plan: Science-Backed Structure with VDOT Paces

Most 16-week marathon plans give you a schedule. This one gives you a framework — and the science behind every decision so you can adapt it intelligently when life intervenes.

The structure comes from Jack Daniels' periodization principles and the VDOT system. The paces come from your race history, not a generic target time. The load management comes from understanding CTL, ATL, and TSB — the three numbers that tell you whether you're building fitness or digging a hole.

I used a version of this structure for my first sub-3:30 marathon. The plan on paper looked conservative — more easy running than I'd ever done, threshold sessions shorter than I expected. Weeks 10–13 were the hardest training I'd ever done. Week 15 I felt flat and worried I'd lost everything. Race day I ran 3:27. The structure was right; my doubts were wrong.

Who this plan is for

This plan is designed for intermediate runners who:

• Have a recent race result (5K, 10K, or half marathon) to calculate VDOT
• Are currently running 40–55 km/week consistently
• Have at least one previous marathon or half marathon finish
• Are targeting a meaningful time goal, not just a finish

If you're running under 30 km/week, spend 6–8 weeks building your base before starting week 1.

How to find your training paces

Before following any session in this plan, calculate your VDOT from a recent race result.

Once you have your VDOT, every pace in this plan — E, M, T, I, R — has a specific target. Do not use your goal marathon time to set paces. Train to where you are, not where you want to be. The fitness you build in 16 weeks will move your VDOT upward; your paces will adjust naturally.

The four phases

Phase 1 — Base (weeks 1–5)

Goal: Aerobic foundation and connective tissue adaptation
Volume: Build from your current base to ~65–70% of peak
Intensity: Primarily E pace, strides twice per week, one M-pace segment in the long run by week 4

The first five weeks are less exciting than they feel necessary. Resist adding intensity early. The aerobic adaptations from this phase — mitochondrial density, fat oxidation, capillary development — take 4–6 weeks to materialise and underpin everything that follows.

CTL target: Build at +3–4 points/week. TSB should stay above −10.

Sample week (week 3):

Phase 2 — Build (weeks 6–11)

Goal: Raise lactate threshold and introduce race-specific stress
Volume: Peak volume — 70–80 km/week for most intermediate runners
Intensity: E + T + M pace. One threshold session and one long run with M-pace miles per week

This is the phase where training starts to feel like marathon preparation. Threshold sessions appear: cruise intervals at T pace, marathon-pace long runs. The hard days get harder; the easy days must stay genuinely easy.

The most common mistake in this phase: running easy days too fast because fitness is improving and slow feels wrong. Easy days at E pace are not recovery — they're aerobic stimulus at the correct intensity. Running them 20–30 seconds/km too fast increases ATL without proportional CTL gain.

CTL target: Continue building at +3–5 points/week. TSB will oscillate between −5 and −20. Weeks after hard blocks should show TSB recovering toward −5.

Sample week (week 9):

Phase 3 — Peak (weeks 12–13)

Goal: Maximum training stress — highest CTL of the cycle
Volume: Equal to or slightly above build phase peak
Intensity: All zones active — E, M, T, and I pace sessions in the same week

These are the hardest two weeks of the cycle. Easy runs feel hard. Your VDOT paces feel out of reach. Your legs are heavy going into quality sessions. This is expected — ATL is high, TSB is deeply negative (−20 to −30), and the fatigue is real.

Do not cut peak phase short. The fitness gains from these weeks only express themselves after the taper. Runners who enter peak phase and reduce volume because they feel terrible arrive at race day under-prepared. The data matters more than the feeling here.

CTL target: Highest of the cycle — typically 65–85 for runners at 70–85 km/week.

Sample week (week 12):

Phase 4 — Taper (weeks 14–16)

Goal: Drop ATL while preserving CTL → reach TSB +10 to +20 on race day
Volume: Reduce 30% in week 14, 40–50% in week 15, 25% of peak in race week
Intensity: Maintained but brief — short quality sessions in weeks 14 and 15 only

Taper is where fitness becomes race performance. Volume drops sharply; intensity is maintained in short doses to keep neuromuscular sharpness.

Week 16 (race week): easy running only, 30–45 minutes per session, with 4–6 strides on Wednesday. No quality sessions after Sunday of week 15. Rest Thursday or Friday before Saturday/Sunday race.

Race day TSB target: +10 to +20. If your TSB is below +5 the day before race, your taper was insufficient — note this for next cycle. If it's above +25, you over-tapered — shorten taper by 3–4 days next time.

Sample week (week 15):

Weekly volume across the 16 weeks

The key principles behind every session

Easy runs must be easy. Your E pace from VDOT will feel almost embarrassingly slow, especially in the first few weeks. That is correct. Easy runs at the right intensity build aerobic capacity without accumulating excessive fatigue. Easy runs at the wrong intensity increase ATL without proportional CTL gain.

Threshold sessions are the primary driver of marathon fitness. The T-pace cruise intervals in the build phase directly raise your lactate threshold — the physiological ceiling of your marathon pace. More than 10% of weekly volume at T pace produces diminishing returns and elevated injury risk.

The long run is the cornerstone, not the entire plan. Runners who focus only on long runs while neglecting threshold work and easy volume end up aerobically capable but metabolically undertrained for marathon pace. The long run builds endurance; the other sessions build the speed to use it.

Every missed week matters less than you think. If illness or life forces you to miss 5–7 days, don't try to make up the missed sessions. Resume at 70% of where you left off and rebuild. Trying to compress two weeks of training into one produces ATL spikes that take longer to recover from than the missed training itself.

When to update your VDOT

Recalculate your VDOT after any tune-up race or flat time trial during the plan. A common approach:

• Week 4–5: 5K or 10K tune-up race → update paces for the build phase
• Week 9–10: Half marathon or fast 10K → update paces before peak phase

Updating paces mid-plan is not a sign the plan is broken — it's the plan working. If your VDOT rises by 2 points after a tune-up race, every subsequent session should be run at the updated, faster paces.

Why this works better than a generic plan

Generic marathon plans prescribe paces based on your goal time. If you're targeting sub-4:00, your threshold pace is X, regardless of whether you're currently capable of running threshold sessions at that pace.

This plan prescribes paces based on your current fitness via VDOT. The difference is not cosmetic — it determines whether your training stress lands in the right physiological zone or misses it entirely.

A runner targeting sub-4:00 who is currently at VDOT 42 has a T pace of approximately 5:55/km. A generic sub-4:00 plan might prescribe threshold work at 5:30/km — 25 seconds/km too fast. Those sessions accumulate excess fatigue, raise injury risk, and produce less lactate threshold adaptation than correctly-paced sessions would.

Adaptive plans take this further — recalibrating not just paces but session lengths, recovery windows, and taper duration based on your actual CTL, ATL, and TSB each week. This plan is a strong framework. An adaptive plan is that framework responding to what you actually do, not what you were supposed to do.

Sixteen weeks is enough time to build meaningful fitness, peak correctly, and arrive at race day with a TSB that reflects months of accumulated work. The plan works when the paces are honest, the easy days are genuinely easy, and the taper is trusted rather than abandoned.

Frequently Asked Questions

Is 16 weeks enough to train for a marathon?

16 weeks is the standard and sufficient preparation window for intermediate runners who have a base of 40–50 km/week before starting the plan. It allows 6–8 weeks of base and build work, 2–3 weeks of peak training, and a 2–3 week taper. Runners with less base should consider an 18–20 week plan to build aerobic foundation before the quality work begins.

How do I find my training paces for a marathon plan?

Use your most recent race result to calculate your VDOT score, then use that score to find your E, M, T, I, and R training paces. A 10K in 55:00 gives VDOT ~43; a half marathon in 2:05 gives VDOT ~44. Every training pace in this plan is derived from VDOT — not from your goal time. Training to your current fitness, not your goal, is what actually gets you to the goal.

How many days per week should I run for a marathon?

Most intermediate marathon plans work best on 4–5 running days per week. This allows sufficient volume (50–70 km/week at peak) while preserving recovery between hard sessions. Running 6–7 days per week is viable for experienced runners who have adapted to high volume, but for most intermediate runners it increases injury risk without proportional fitness gain.