Training · guide
Hansons Marathon Method: How the Training Works
What the Hansons Marathon Method actually prescribes, why its longest run stops at 16 miles, and which runners the system suits.
The Hansons Marathon Method is usually introduced with one detail: its longest run is 16 miles. That detail is accurate, and it is also the least useful part of the system to adopt on its own.
The method was developed by brothers Keith and Kevin Hanson, who coach the Hansons-Brooks Distance Project, and written up with coach Luke Humphrey. Its defining feature is not a distance. It is a complete weekly structure built around cumulative fatigue. Keep the 16-mile cap while discarding the structure, and you have not simplified the plan—you have removed the reason the cap works.
Cumulative fatigue is the organizing idea
Humphrey’s own definition is the clearest place to start. Cumulative fatigue, he writes, is present “when fatigue is coming from the culmination of training and not from one specific aspect.” The runner is tired but still able to run well, and has not gone past the point of recovery.
That is a narrower target than it first appears. The aim is not to be wrecked by any single session, but to arrive at each key workout still carrying residue from the days before, so the work happens under conditions that resemble the later stages of a marathon.
The margin between this state and overtraining is thin, and Humphrey is direct about it. The dividing line he describes is performance: while workouts still go as planned, the fatigue is doing its job; when a runner starts to feel terrible and times decline, the process has crossed from productive overload into overreaching. This is why the easy days in the plan have to be genuinely easy—they exist to keep the fatigue controlled rather than to add fitness directly.
Why the long run stops at 16 miles
The cap follows from one observation about proportion. If you run 40 miles a week and your long run is 20 miles, half of your week sits in a single outing. Kevin Hanson’s argument, made in a Runner’s World interview, is that this ratio is unlike anything a competitive runner does: someone logging 100 to 140 miles a week covers 20 miles in barely a fifth of that. A 16-mile long run inside a 60-mile week is about 27 percent. The distance is not the principle; the share of the week is.
Humphrey puts the coaching guideline in similar terms. He keeps long runs “at less than 30% of total weekly volume and really under three and a half hours” so that the rest of the week can still be trained.
Two consequences follow. First, the long run is intentionally scheduled on slightly tired legs. After a Thursday marathon-pace tempo and a shorter run on Saturday, the Sunday long run is covered with glycogen not fully restored—so the last miles feel closer to the closing stretch of a race than to a fresh weekend effort. Hanson’s framing is that you are rehearsing the last 16 miles of the marathon rather than the first 16.
Second, the cap is not a law. Humphrey states plainly that neither 16 nor 20 is a magic number. In his own programming, a long run can move to about 18 miles at a 60-mile peak and up to 20 at 65 miles. The number scales with weekly volume; it is not a fixed ceiling to defend.
What the method does not claim is that 16 miles is optimal for every runner. This is a coaching framework with reasoning behind it, not a controlled trial showing that a capped long run outperforms a longer one. The comparison that matters is between whole systems, not between two Saturday routes.
The week, not the run, is the unit
Published versions of the plan differ in their details, but the shape is consistent: six running days with one full rest day, and three quality sessions that Humphrey’s method labels SOS—“something of substance.” Peak weeks reach roughly the 50s for newer marathoners and into the 60s or about 70 for more advanced runners, depending on the edition.
Everything else is easy running, and its job is volume rather than intensity. That is what makes the proportions work, and it is also the part most often lost. Humphrey’s warning about partial adoption is blunt: a 16-mile long run, taken alone, “won’t get the job done.” In the same discussion he compares the components to a Jenga tower—pull one piece out and the rest does not stay upright.
What the SOS sessions actually are
The three quality sessions are not interchangeable, and they change across the plan.
Speed work comes early, usually on a Tuesday, and consists of short repetitions from about 400 meters up to a mile at roughly 5K effort. The purpose is running economy and maximal aerobic power—qualities that support faster running later but are not themselves marathon-specific.
Strength work replaces speed work in the later weeks. It is long-interval work, such as repetitions of one to three miles run slightly faster than goal marathon pace with short recoveries. The idea is a large volume of running close to, but not over, threshold, rather than a short all-out session. Doing this too fast is a common error and defeats the purpose.
Tempo runs, usually Thursday, are run at goal marathon pace and grow from roughly five miles toward ten. This is the most race-specific session in the plan. Its function is to make marathon pace familiar and to test whether the goal is realistic.
The long run is run somewhat slower than marathon pace, often described as roughly 30 to 90 seconds per mile above it, and capped as above.
Every pace in the plan is anchored to one number: your goal marathon pace. Third-party pace calculators and successive editions differ by a few seconds per mile on the strength and tempo sessions, and it is not worth arguing over that gap. What matters is that easy running stays easy, quality work stays controlled, and the anchor is a goal you have reason to believe. If that anchor is wrong, the whole structure amplifies the error—our guide to a controlled test effort explains how to check it.
How the 18 weeks are structured
The published plans run 18 weeks and divide into four phases. The beginner and advanced versions differ mainly in how long the first two phases last.
| Phase | Beginner plan | Advanced plan | What the week contains |
|---|---|---|---|
| Base | about 5 weeks | about 1 week | Easy mileage only, no SOS sessions |
| Speed | about 5 weeks | about 9 weeks | Tuesday intervals, 400 m to a mile, near 5K effort |
| Strength | about 7 weeks | about 7 weeks | Tuesday intervals of one to three miles just under threshold; Thursday tempo grows toward ten miles |
| Taper | final 10 days | final 10 days | Volume and intensity fall, running frequency stays |
The advanced plan assumes a marathon background, so it begins from a higher weekly volume and spends far longer in the speed phase—nine weeks against five. That difference, not the long run, is what actually separates the two plans. Phase boundaries also vary a little between published editions and third-party reproductions, so treat the week counts as approximate.
Long runs are absent from the earliest weeks, then step up through roughly 10, 12 and 14 miles with a lighter week between each step before settling at 16. The 16-mile distance typically appears about three times in the closing weeks rather than once.
The taper is unusually short—roughly the last ten days rather than the two to three weeks common in other marathon plans. The reasoning is continuity: the body has adapted to running six days a week, and a long shutdown is said to leave runners feeling heavy and flat on race morning. So running frequency is largely preserved while volume and intensity come down.
That rationale is coaching experience rather than a physiological law, and it is worth treating it as such. Taper research generally supports reducing volume while retaining some intensity; the exact length that suits you is a personal question. Our race-week taper guide covers what the evidence does and does not support.
Who this system suits, and who it does not
The method tends to work well for runners who can commit to running six days a week, already have marathon experience, and whose main problem is fading in the closing 10K rather than getting to the start line. It also appeals to runners who recover poorly from three-hour long runs or cannot spare the time for them.
It tends to work badly for three groups. First-time marathoners may find the trust required by a 16-mile cap difficult to sustain, since nothing in training replicates the race distance. Runners who can only run three or four days a week lose the weekly volume that the whole approach depends on. And runners with a history of overuse injury are taking on more total load, not less—the method reduces the longest single run, not the weekly total.
One misreading is worth naming directly. The plan is not an easier route to the same result. Someone running a single 20-mile long run with the day before and after off covers about 20 miles across three days; the same three days inside a Hansons week commonly total in the mid-30s. The trade is more cumulative running, not less.
How it compares with other marathon plans
The decision between plans is less about which system is better than about which constraint you are willing to accept.
| Hansons | Pfitzinger | Higdon (Novice 1) | |
|---|---|---|---|
| Peak week | roughly 55 to 65 miles | 55 to 85-plus miles, by tier | about 40 miles |
| Running days | 6, plus one full rest day | 4 to 6, by tier | 4, plus one cross-training day |
| Longest run | 16 miles, by design | roughly 20 to 22 miles | 20 miles, once, in week 15 |
| Defining session | Midweek speed or strength work plus a marathon-pace tempo | Midweek medium-long run of 11 to 15 miles | Weekend long run, stepped back every third week |
| Taper | about 10 days | about 3 weeks | 3 weeks |
The three systems disagree about where the weekly load belongs. Pfitzinger concentrates it in volume and threshold work, with a medium-long run in the middle of the week and a long run that can reach 22 miles. Higdon concentrates it in the weekend run and keeps the rest of the week deliberately light. Hansons spreads it across six days and declines the very long outing altogether.
That gives you a fairly clean way to choose. If six running days are not available, neither Hansons nor Pfitzinger’s higher tiers will fit, and a structure like Higdon’s is the honest answer—its mileage is redistributed rather than reduced, with the midweek runs growing as the plan progresses. If six days are available and you have a time goal, the choice between Hansons and Pfitzinger comes down to which load you absorb better: sustained daily running with a capped long run, or fewer and longer outings with a substantial weekend. Runners who fade in the third hour often prefer the first; runners who recover quickly and enjoy a long Sunday tend to prefer the second.
These are three coaching systems making structural choices, not three arms of a comparison trial, so the table describes what each plan asks of you rather than which produces faster times. The honest summary of the trade is this: Hansons removes the long runs some runners need for confidence, Higdon omits most of the race-pace work that builds marathon-specific fitness, and Pfitzinger asks for a weekly volume that many runners cannot hold alongside a job. Each works for the runners it was written for.
If you borrow only one idea
The most transferable element of the method is not the number 16. It is the proportion: keep the longest run to roughly a quarter to a third of weekly volume, treat the weekday runs as training rather than filler, and anchor quality sessions to a pace you have a reason to believe.
If you are not prepared to run six days a week, the honest move is to choose a plan that matches your available days instead of adopting the most quotable fragment of this one. Our discussion of how a long run should fit the rest of your week covers that decision in more detail, and the 80/20 distribution explains why the easy days carry so much of the load.
Persistent pain, a changed stride, or recovery that keeps getting worse are reasons to step back from the plan rather than push through a schedule. Structure is only useful while you can absorb it.
Sources
- Luke Humphrey, A thought on what makes the shorter long run work, 2023. Coaching rationale for the volume proportions and the capped long run.
- Luke Humphrey, What is Cumulative Fatigue? How do I differentiate?, 2016. Definition of cumulative fatigue and the distinction from overreaching.
- Runner’s World, interview with Kevin Hanson on long-run mileage before a marathon. Source for the weekly-proportion argument and the 16-mile cap.
- Humphrey, Hanson, and Hanson, Hansons Marathon Method: Run Your Fastest Marathon the Hansons Way, 2nd edition, VeloPress, 2016. Primary source for the plan structure, the phase lengths, the SOS sessions, and the taper described above.
- Hal Higdon, Novice 1 Marathon Training Program. Source for the four-run week, the 20-mile long run in week 15, the stepback weeks, and the three-week taper.
- Pfitzinger, P., and Douglas, S., Advanced Marathoning, Human Kinetics. Primary source for the mileage tiers referred to by plan length and peak volume, the midweek medium-long run, the marathon-pace long runs, and the three-week taper.
The weekly breakdowns, mileage ranges, pace offsets, phase lengths and taper durations in this article are editorial summaries of published coaching frameworks. They are not study-derived prescriptions, and editions, tiers and pace calculators differ in their exact values. No controlled comparison of these plans against one another exists, so nothing here should be read as a claim that one produces faster marathon times than another.