Running Plan Review Runner's World Go Fast Go Far Marathon

Does it build you up smartly?

A good training calendar needs two things: an order that builds one kind of fitness on another, and sessions written clearly enough that you know what each one is for. This plan gets the order right, but most of its sessions come without a reason.

The larger shape is sound. Plans that shift their focus from one block to the next tend to beat plans that train the same way throughout, and this plan's phases are labelled on the calendar and come in a sensible order: the weekly rhythm first, then the climb to the longest runs, then a short sharpening block and the taper.

But most sessions are written as a single line: the reps, the pace, the rest, and nothing on why the workout is there. Asked about the biggest mistake marathoners make, Patrick Sang, Eliud Kipchoge's coach for more than 20 years, put it this way: "Not listening to their bodies very well," he said. "And not understanding what they are supposed to do." On most days of this plan, working out what a session is for is up to you. The four named workouts are the exception, and they're the best-written part of the plan. Each comes with its history and a reason, from rehearsing tired legs to checking your marathon fitness.

Does it protect you from injury?

Partly. The plan builds carefully from week to week and keeps its hard days apart, but it leaves out strength work and any guidance on pain, and its first lighter week comes late.

Start with what's in place. Injury risk tends to climb most when a single run goes well past your longest of the past month, or a week jumps by more than about 30%, and this plan never goes that far. The two hard weekday sessions never land on back-to-back days, each opens with a warm-up, and a recovery run or an optional day follows each one.

Week 11 is the step to watch. Mileage rises by about a fifth over the week before, a new kind of session arrives (a 5-mile run that speeds up as it goes), and the long run grows from 15 miles to 20 or more. Your blood and muscle energy systems tend to adapt within the first few weeks, while tendons take weeks to a few months and bone takes months. So a run like that can feel manageable on the day and still ask more of your legs than they've been built for. "We previously believed that injuries develop gradually over time," says Rasmus Nielsen, a Danish researcher who led a study of running injuries, "but it turns out that many injuries occur because runners make training errors in a single training session." That's why week 11's long run, more than the week's total, is the run to watch.

The pauses come late, too. For the first 12 weeks, every week has the same three demanding days: a track session, a second hard session on Thursday, and a long run. Mileage eases slightly in week 10, but both hard days stay, and the first real lighter week is week 13, with the race 2 weeks away. That's a long stretch to carry. Training load that piles up without relief tends to raise the risk of injury and illness, and a runner following a fixed plan needs that relief built into the schedule, most often as a lighter week every 3 to 5 weeks. "Athletes often feel sluggish and have lower energy during this week," says Pete Rea, a coach whose runners cut back every third week. "Nonetheless I find the level of workouts is elevated thereafter, that workouts are more effective and staleness prevented." On this plan, the first week like that is week 13.

The peak of about 43 miles a week looks moderate for a marathon. But distance alone undercounts how hard you're training. Pace adds strain that a mileage total doesn't show, and this plan has fast running on the track every week.

Strength is the clearest gap. The plan mentions it but schedules none, so placing it in the week, most likely on Wednesday or Saturday, and deciding what goes into it are up to you. Strength training lowers the risk of sport injuries more than stretching or balance work alone. It helps your running too, and about two sessions a week is enough for most runners to get that performance benefit. Marathon great Eliud Kipchoge wrote about his own gym work in those terms: "In my mind the gym work helps to chase away the injuries and train the muscles." With this plan, that work is yours to add, and the open days are where it fits.

Nothing in the plan says what pain means or when to back off, either. Many runners notice that a niggle, the low-grade ache that hangs around between runs, can come before a full injury, though the evidence is early. The plan has no rule for that moment, so the choice to cut a run short or take a day off is yours to make.

What happens when you miss a day?

No 14-week block survives untouched. A cold, a late shift or a trip will move something, and what helps then is a plan that tells you what to keep and what to let go.

This plan has the room for it, but not the instructions. Nothing in it covers a missed run, a missed week, or coming back after a few days off, and it doesn't say which sessions to protect when a week gets crowded. The shape of the week gives some clues. The two hard days and the long run carry the training, and the optional Wednesday and Saturday runs are the obvious first to go. Those open days also give a missed session somewhere to land, as long as you keep an easy day between it and the next hard one. But working out the rest is up to you.

The pace guidance has a gap of its own. Nearly every hard session is set at your current race pace for some distance, from the mile to the half marathon. Apart from the hills, the fartlek and the Yasso 800s, there's no effort to fall back on if you don't know those paces. And as you get fitter, nothing tells you when or how to update them. Training that adjusts to the runner tends to match or beat a fixed template, but here the adjusting is yours to do.

The plan does say clearly who it's for, which helps the right runner find it.

Will it get you ready for race day?

The race preparation is excellent, and the long run leads it.

Coaches treat the long run as the center of marathon preparation, and early evidence links longer long runs to better marathons, though no one has tested whether shorter, faster sessions could do the same job. This plan's long run peaks at 20 miles or more in week 11, 3 weeks before the race, which leaves time to recover from it. A peak week of about 43 miles gives a strong marathon enough to stand on.

Midweek, the half marathon pace work runs close to your threshold, the point where running stops being something you can keep up for a long time and starts to tire you quickly. For most recreational runners, marathon pace sits well below that point, so those sessions and the goal-pace miles are different kinds of training, and either is a reasonable way to prepare. This plan gives you both.

Goal marathon pace has its own place in the plan. Four times in the build, a long Sunday run carries 3 miles at goal pace after 7 to 9 easy ones. It's a rehearsal of the second half of the race: holding a steady pace when your legs have already done a lot. Week 11 adds a 5-mile run that starts at marathon pace and finishes at half marathon pace, and race week has a short session at goal pace to remind your legs of the rhythm. Week 12's Yasso 800s give you a fitness check before the final stretch. Does the workout really predict a marathon time? Jess Movold, one of this plan's two coaches, gave a careful answer: "My answer is yes and no." The workout, she wrote, "is not the golden ticket to your goal marathon finishing time." So read a good week 12 alongside your long runs and goal-pace miles, not instead of them.

Mileage then falls across the last 3 weeks, and race week is a real taper. A taper of up to 3 weeks, cutting volume while keeping some faster running, improves race performance compared with not tapering, and this one lands where it should.

Are the workouts varied enough?

Yes. Across 14 weeks you'll run 19 different interval sessions, and there's an interval day every week, right up to the marathon.

There are cut-downs, where each rep is a little faster than the last, ladders that mix long and short reps, hill repeats, a fartlek of shrinking surges, and a run that speeds up as it goes. The Michigan, in week 3, takes you from the track to the road and back, switching between hard track reps and steady road miles. Almost every Tuesday is a session you haven't run before, so the weeks rarely feel like copies of each other.

The mix underneath is sound. About 80 percent of your running stays easy, and those easy miles are the base of the week. The hard days then stay clearly hard, and mixing mostly easy running with a few clearly hard efforts may build endurance a little better than long stretches of steady, moderately hard running. "The mistake I made was doing a lot of the same type of training and not mixing it up," recalls Brad Hudson, a former marathoner who went on to coach. "I made my easy days a little too moderate and my hard days not hard enough." This plan steers clear of both: the sessions change almost every week, and the easy days are written as easy.

Strides come every Monday until race week, 8 of them most weeks, on a soft surface. They're a cheap way to practice running fast, and short, explosive efforts can make runners more economical, though strides themselves haven't been tested directly. They land the day before Tuesday's track session, when a little sharpness helps.