Marathon Training for Masters Runners

A 30-year-old can usually survive a marathon plan that stacks stress: Tuesday intervals, Thursday tempo, Sunday long run, plus medium-high mileage. A masters runner may be able to do that week, too... one time. The problem isn't the week. It's doing it for twelve to eighteen weeks without wrecking their legs.

Which is why marathon training after 40 is much less about whether you can do the workout, and much more about a single question.

If the answer is yes, you can keep building. If the answer is no, it doesn't matter how good the workout looked on paper — it cost you more than it gave you. Hold that question in your head for the rest of this guide. It's the lens behind every recommendation below.

Build the week around recovery

Most generic marathon plans are organized around mileage and workouts. A masters plan has to be organized around recovery between hard efforts. There's no Platonic ideal for a block of marathon training for a masters runner — but here's a general framework that can work:

Here's where this differs from a plan for younger runners: it respects rest and recovery days, and it doesn't try to stack too many hard efforts in a row. In fact, the research on older runners is detailed enough that recovery windows range from 24–48 hours in younger athletes to 48–72 hours in masters runners.

Cut the junk, not the volume

Let me kill a myth right away: being older does not automatically mean your mileage has to drop. Plenty of masters runners thrive on real volume. What has to go isn't the mileage — it's the junk.

Think about how the NBA changed. The midrange jumper got eliminated, because the math says you're better off taking threes or high-percentage shots at the rim. The midrange is the least efficient shot on the floor. Marathon training for masters runners works the same way. The mid-range mile — the medium-hard day that's neither a real workout nor a real recovery run — is the least efficient mile you can run. It carries workout-level fatigue with easy-day-level benefit. It's the worst shot on the floor, and most runners take it constantly.

This is the same trap endurance science calls the "moderate intensity trap": too much time at medium effort produces chronic fatigue without building either an aerobic base or real threshold fitness. The fix is to polarize — make easy days genuinely easy and hard days genuinely hard, and let very little live in between.

The long run: put something in it

The long run is the defining workout of marathon training. It's the thing that makes the marathon different from almost every other race distance. For a 5K or 10K, you can often build confidence by breaking the race into pieces — run five 1K repeats well, and you have a pretty good sense you can handle a hard 5K. The marathon is different. You do not get to run 26.2 fast miles in training just to prove you can. I'm not exactly sure what that would even be, but it would not be a workout (unless you're Yuki Kawauchi).

So the long run has to do work that no other run in the week can really do. First, it gives you room. Most runs aren't long enough to include 8, 10, 12, or more miles of sustained quality. The long run is usually your one chance each week to practice extended faster running without turning the rest of the schedule into a circus. Second, it teaches you how marathon effort feels after the early, easy miles — how to stay calm, fuel, hold rhythm, and manage that slow creep of fatigue. Third, it makes fitness feel real. There's nothing quite like struggling through a long run one week, then coming back a couple of weeks later and handling more distance, more pace, or both. That's one of the great little rewards of marathon training: plan the tree today, see it grow tomorrow (just make sure you're watering it).

For length, I use a simple rule of thumb: I generally like the long run to be about twice the average daily mileage of the other six days. If you're running about 10 miles a day Monday through Saturday, a 20-mile long run fits naturally and puts you around 80 for the week. That's not a law — just a useful way to keep the long run proportional to the rest of the week.

I also like to put work inside the long run. Not every long run needs to be hard, but I'm not a huge believer in making every big run just "time on feet." Sometimes that's necessary. Sometimes it's just boring with better branding. Adding structure gives the run a purpose: steady running a little slower than marathon pace, controlled marathon-pace segments, short surges, or a progression over the second half. It doesn't have to be heroic — early in a build, it probably shouldn't be. The goal is to build the ability to run with quality while tired, not to turn every Sunday into a race. And the scheduling matters: if Sunday's long run includes real work, the earlier workout that week should probably be toned down. You do not need to win Tuesday and Friday and Sunday.

For masters runners, the long run is still central, but the measuring stick changes. The question isn't just "How far did I go?" or "How much quality did I fit in?" The better question is: what did this run allow me to do next? If you can recover and run well again by Tuesday or Thursday, the long run probably fit. If you're still carrying it around four days later — no matter how impressive it looked on Strava — it probably wasn't worth it.

Two quality sessions, not three

A marathon plan for a younger runner generally has three quality sessions a week (or more, if you've been Bakken-pilled and believe in the power of double thresholds — more on that in a later article). For my money, a plan for a 50-plus marathoner should generally have two quality sessions per week. Think: a midweek tempo and a Sunday long run with marathon-pace work. Here's how I'd lay it out, depending on the runner and the week.

Option A — the standard masters marathon week

Option B — when the long run has marathon-pace work

The biggest mistake: training for the runner you used to be

If I had to name the single most common error masters marathoners make, it's this: they train for the runner they used to be. They remember what worked at 32 and try to repeat that structure at a slightly slower pace. But pace was never the only thing that changed. Recovery speed changed. Tissue tolerance changed. Strength, the hormonal environment, sleep, injury history, the cost of stacking stress — all of it changed. Adjusting the paces while keeping the old structure is solving the wrong variable.

The race-wreckers I see again and again:

• Too many medium-hard runs
• Long runs that quietly turn into races
• Refusing to take cutback weeks
• Chasing old workout paces
• Adding mileage and intensity at the same time
• Ignoring fueling practice
• Treating strength work as optional until something hurts
• Trusting age-based heart-rate formulas over the athlete's actual HR profile

That last one is worth a flag, because so many plans lean on it. The familiar "220 minus age" estimate of max heart rate isn't really based on a study — and a large analysis of age-predicted formulas found it systematically underestimates max HR in older adults and can miss by 10–20 beats in either direction. Two runners the same age can differ by 30 beats. If your zones are built on a formula instead of your real numbers, you can spend a whole build training in the wrong gears.

Why generic plans don't always work for masters runners

Off-the-rack plans can be a useful starting point for older marathoners. But they often fail because they're organized around mileage and workouts, and they're not much help when a training plan goes sideways. A typical 18-week plan essentially assumes:

• Recovery is predictable
• The athlete can handle a 7-day stress cycle
• Age mainly means slower paces
• Long runs are universally beneficial
• Heart-rate zones can be estimated from age
• Injury history is a footnote — and not even an important one; more like a footnote buried inside a footnote (see: House of Leaves)
• Cross-training is a nice-to-have, not a tool to be used
• Goal pace should be the main driver of plan design

For a masters runner, every one of those assumptions is shaky. The plan needs to take into account the athlete behind the goal. A 57-year-old chasing 3:45, a 70-year-old elite masters runner chasing 3:17, a 72-year-old trying to break 5:00, and a 67-year-old who wants a comfortable final marathon are not four versions of the same spreadsheet with the paces nudged around. They're four different engines. The goal time tells you the destination. It tells you almost nothing about how that particular body should get there.