Running Plan Review Pete Pfitzinger Advanced Marathoning 12 Week, Up to 55 mi/wk

Does it build you up smartly?

This is a marathon built in stages, and each one changes what the hard running asks of you. Endurance comes first, harder work is layered on top, and the last block aims everything at the race. Training that shifts its emphasis like that tends to produce better race results than holding the same training the whole way.

Pfitzinger's stages are clear, and the sessions inside them are written out in full. Every hard run spells out the total distance, how long or how far you run at effort, and what that effort is. Even the first Sunday tells you exactly what it wants: 12 to 13 miles, 8 of them at goal marathon pace, before you've run a single threshold session.

The blocks are named on the calendar, too, so you always know which stage you're in. When week 8 opens the race preparation block, with tune-up races where the long runs at goal marathon pace used to be, the name tells you why the work has changed.

Does it protect you from injury?

Mostly, yes. The week-to-week climb is gradual, every hard session opens with an easy warm-up, and no two hard days ever fall back to back. But three things deserve your attention before you start.

The first is the starting line. The book asks for 25 miles a week or more before this tier, and week 1 is about 35, with 8 miles at goal marathon pace on the very first Sunday. The usual coaching advice is that a plan's first week should sit near what you already run, not what you're building toward. For a runner at 25, week 1 is a jump, and very large jumps in weekly running tend to raise injury risk. Pfitzinger says as much himself: "the body adapts well to small increments, and isn't very good at assimilating larger increases." By week 7, that runner is running more than double where they started.

The second is week 6. It comes straight out of the lighter week, brings your first 5K-effort repeats, and ends with 12 miles at goal marathon pace. Week 7 follows with the plan's biggest total. Fitness tends to arrive within weeks, while tendons and bone usually take longer to catch up. Two new demands at once tend to find whichever of those is behind.

The third is strength. Chapter 4 of the book sets out a full strength routine alongside its cross-training advice, but the calendar never gives it a day. You decide where it goes, and on a week with a threshold run, a medium-long run and a 20-miler, that's a real decision. It's a choice that pays off, because strength training cuts sport injuries more than stretching or balance work does.

The book does help you notice when something is going wrong. It covers the signs of overtraining and illness and gives recovery runs a ceiling. But it has no plan for coming back from a specific injury, and a niggle that lingers may be an early warning of one that stops you running. One club runner told Irish researchers how that change feels: "If it happens again the next week, and the next week, it doesn't become a niggle anymore, it becomes a problem where you know it is not going to go away." Treat the small ache that's still there on Tuesday as a reason to back off.

What happens when you miss a day?

Every plan meets a week that doesn't go to plan. What helps then is knowing which runs to protect, and having a rule for coming back.

This book is good at both, mostly. Its chapter on run types explains each one: what it does, how hard it should feel and the mistake runners usually make with it, with heart-rate ranges for all but the fastest work. Threshold work comes in minutes, so it fits whatever pace you run. And for time off, the book has a table. Miss under 10 days and you pick the schedule back up. Miss more, and you rethink your goal, depending on how close the race is. Neither rule asks you to win back the lost runs. "You can't make up what you missed," says exercise scientist Bill Pierce, whose own marathon plans use just 3 runs a week, "and you certainly shouldn't double up on your workouts to catch up with your program." The week itself has slack too. Two or three days are marked rest or cross-train, so a missed run has somewhere to go.

But the book tells you what matters in principle more than in practice. Endurance comes first, then threshold, then the faster repeats, then speed. It's a sound order, but there's no list of what to drop when a week shrinks to three runs, and the guidance is spread across two chapters. A short plan also leaves little margin. From week 5 on, the race is 8 weeks away or less, and by the book's own table, 10 days off at that point is enough to revise your goal. On this plan, a lost fortnight is a sixth of the training.

Will it get you ready for race day?

Partly. The plan builds real marathon endurance and tapers well, but its peak is bigger than most marathoners at this level need, and its practice at race pace comes early.

The long runs are right. They reach 19 to 20 miles in week 7 and 19 to 21 in week 9, three weeks before the race, and longer long runs go with faster marathon finishes, though nobody has tested whether shorter, faster sessions could do the same. The taper is right too: race week drops to about a third of the biggest week, the kind of cut that tends to help runners race better than training straight through.

The race preparation block has a weekend you'll remember. In weeks 8 and 10 you race a tune-up on Saturday, then run 16 to 17 miles on Sunday, the second run on legs that still feel the first. No study has tested whether tune-up races make the marathon itself faster, but they're a real start line, and a good place to practice starting under control in a crowd. Sports scientists who study race pacing make the same case for everyday runners: "several 10-km races or half-marathons," run at an even pace, before the marathon itself.

But the biggest week, about 54 miles in week 7, sits above the range most marathoners at this level need. Some runners will handle it fine. Others will spend the race preparation block recovering from it.

The race-pace practice is the other gap. The long runs at goal marathon pace, 8, 10 and 12 miles of it, come in weeks 1, 3 and 6. Pfitzinger keeps them few on purpose. Marathon-pace runs are "tough on the body," he told one interviewer, and the trick is fitting in just enough "so that you're not really flattening yourself." After that, the late weeks are carried by repeats at 5K effort and the tune-up races, and goal pace only returns as 2 miles in race week. So the last time you hold your race pace for a long stretch is 6 weeks before you need it, and the feel of goal pace on legs that know the distance is something you'd want fresher.

Are the workouts varied enough?

Yes. The hard sessions change from block to block, and the easy days carry small doses of speed.

About four in every five miles are easy, and that easy running is the base the harder training stands on. Barry Smyth, a Dublin professor who studies marathon data, says of his own running: "I was surprised, even now many years later, at quite how much of my running is done at a very gentle pace. There really is no need to go fast." On top of it, the plan rotates through long runs at goal marathon pace, steady threshold runs, repeats of 600 meters and 1 kilometer at 5K effort, and two tune-up races. Hard days stay hard and the rest stay easy, which tends to help trained distance runners improve more than a steady diet of medium effort.

The small stuff counts too. Most weeks end an easy run with a handful of fast, relaxed 100-meter runs, and on three Tuesdays those runs also include six 10-second sprints up a hill. Short, explosive efforts like those hill sprints can make your running more economical, though the evidence is mixed and strides themselves haven't been tested directly.

The schedule itself is easy to follow. Each day names the kind of run and its distance in both miles and kilometers, so a glance tells you what's next.