What it takes
Marathon training is about building the deepest aerobic engine you can in 16–20 weeks without getting injured. The long run is the cornerstone, but marathon-pace work, threshold sessions, and strategic recovery are what separate a good race from a painful one. Plans that skip the taper or rush the build phase produce DNFs.
Training phases
| Weeks | Phase | Focus |
|---|---|---|
| 1–4 | Base | Aerobic volume, build long run to 12–14 miles, establish routine |
| 5–8 | Build I | Introduce marathon pace work, tempo runs, long run to 16 miles |
| 9–13 | Build II | Peak mileage weeks, MP long runs, threshold intervals, long run to 18–20 miles |
| 14–16 | Peak | Highest volume and intensity, race-simulation long run at 20–22 miles |
| 17–18 | Taper | Volume reduced 40–60% over 2–3 weeks, short MP touches, full glycogen loading |
Key workouts
- Long runs building to 18–22 miles with the final miles at marathon pace
- Marathon pace runs: 8–14 miles at goal pace to lock in rhythm and fueling
- Threshold intervals to raise lactate clearance
- Cutback weeks every 3–4 weeks to absorb training load
Am I ready?
You should be running 5–6 days per week with a long run of 10+ miles and 25–30 miles per week as a baseline. A recent half marathon is the best predictor of marathon readiness. If you haven't run a half, build to that distance first — jumping straight to marathon training from low mileage is the most common path to injury.
What to expect on race day
The marathon is two races: miles 1–20 and miles 20–26.2. The first half should feel almost too easy. The wall — a sudden, dramatic fatigue around miles 18–22 — happens when glycogen stores deplete. It's not optional for most runners; it's physiology. Fueling early and often (30–60g carbs per hour starting at mile 3–4) delays it. Expect to run the last 10K slower than the first, and plan for it. Race-day weather matters enormously — every 10°F above 55°F costs roughly 1–2% in performance.
Common mistakes
- Starting too fast — even 10–15 seconds per mile too fast in the first half can blow up the second half
- Inadequate fueling practice — your gut needs training to absorb carbs at race effort; practice in every long run
- Skipping cutback weeks — the body adapts during recovery, not during hard training; 3-up-1-down is the standard pattern
- Running the long run too fast — Pfitzinger recommends 20–25% slower than marathon pace for most long runs
- Training in the 'moderate zone' too often — threshold and tempo work matter, but the majority of your miles should be truly easy to protect recovery and let hard sessions land
Sample week
| Day | Session |
|---|---|
| Mon | RunEasy Run |
| Tue | RunThreshold Intervals — 4×1.5mi |
| Wed | RunEasy Run |
| Thu | RunMarathon Pace Run |
| Fri | RestRest |
| Sat | RunLong Run |
| Sun | RunEasy Recovery |
How it works
The coach researches your race
Name your event and the coach searches the web for course profile, elevation, and conditions — then factors them into your marathon plan.
Your plan starts where your fitness is
The coach checks your recent Strava activity and your local weather before recommending anything. A 16–20 weeks plan structured by phase — base, build, peak, taper — around what you can actually do.
Train, sync, adapt
Activities auto-match to planned sessions. The coach sees your paces, HR, and effort patterns — and adjusts as your fitness changes. Flag a bad week at work, a nagging knee, or a schedule change, and the plan adapts through conversation.
See it in action
Why AI coaching
- Manages the fine line between peak mileage and injury risk
- Reschedules your longest runs around weather and schedule conflicts
- Taper is science-based — not just guessing when to back off
- Progression rate stays within evidence-based limits across the full training cycle
- Tell the coach about a bad night of sleep, a schedule change, or a nagging injury — and the plan adjusts through conversation, not a settings page
- Searches the web for your specific race — course details, elevation, and conditions inform the plan
Grounded in training science
Plan structure follows periodization principles from Daniels’ Running Formula and Pfitzinger’s Advanced Marathoning — base building, threshold development, race-specific sharpening, and taper. Intensity distribution follows the polarized model (Seiler 2010; Stöggl & Sperlich 2014) — roughly 80% of training at low intensity with targeted hard sessions, rather than moderate effort every day. Volume progression stays within evidence-based limits to manage injury risk (Nielsen et al. 2012). Taper protocols reflect findings from Wang et al. (2023), a meta-analysis of 14 studies on optimal taper duration and training load reduction for endurance events.
Seiler, S. (2010). “What is best practice for training intensity and duration distribution in endurance athletes?” Int J Sports Physiol Perform, 5(3). · Stöggl, T. & Sperlich, B. (2014). “Polarized training has greater impact on key endurance variables.” Front Physiol, 5. · Nielsen, R. et al. (2012). “A prospective study of overuse running injuries.” Br J Sports Med, 46(6). · Daniels, J. Daniels' Running Formula, 3rd ed. · Pfitzinger, P. & Douglas, S. Advanced Marathoning, 2nd ed. · Wang, Z. et al. (2023). “Effects of tapering on performance in endurance athletes: a systematic review and meta-analysis.” PLOS ONE, 18(5).
Frequently asked questions
- How long is a typical Marathon training plan?
- A well-structured Marathon plan typically runs 16–20 weeks, depending on your starting fitness level.
- How many hours per week for Marathon training?
- Most Marathon plans require 6–10 hours per week, scaling up through the build phase and tapering before race day.
- Can AI build a personalized training plan?
- Yes. An AI coach checks your recent training data, researches your specific race, and builds a periodized plan grounded in your actual fitness. Ask it why a workout is prescribed and it explains the reasoning. Flag an injury or schedule change and the plan adjusts through conversation — not a form field.