Running Plan Review Runner's World 8-Week Advanced 5K Training Plan

Does it build you up smartly?

Mostly, yes. The plan is built in a sensible order, though it says less than it could about why.

The order is the plan's strength. Short race-pace pieces come first, longer ones in the middle, and the hardest weeks arrive once you've had a few weeks to get used to the track. Changing what the hard days ask for as the weeks go by tends to beat holding one kind of training the whole way through, and this plan does it without ever naming a phase. Every hard session is written out in full, with its warm-up, the number of repeats, and the jogging between them. But only 2 of the 10 hard sessions explain their purpose, so most weeks you know what to run without knowing why.

Does it protect you from injury?

Not well enough. Two gaps stand out: strength training, and week 4.

The plan never puts strength work on the calendar, so what to do and when to fit it around the track days is up to you. That's a real loss, because strength training substantially lowers injury risk in sport, more than stretching or balance work, and it makes each stride cost less energy too. Physical therapist Dan White puts the trade in racing terms: "If we can decrease the time away from running, that's the win. If strength training buys you consistency and health, that buys you seconds." For a 5K runner chasing seconds, that's the case for adding it to this plan yourself.

Week 4 is where the plan asks the most of your body at once. On Tuesday, the hilly run becomes 3 one-mile repeats. On Thursday, you're back at the track for 5 repeats of 2 laps, and the plan's own note warns you not to be surprised if you feel more tired than in earlier sessions. On Saturday, the long run reaches 10 miles for the first time. The weekly miles only rise from about 27 to 31, but mileage alone doesn't measure how hard you're training, and this is a much harder week than that small rise suggests. Many running injuries appear to start suddenly rather than building over weeks, so a week that adds this much at once is the one to watch most closely. Ida Lindman and Rasmus Østergaard Nielsen, two of the researchers behind that finding, put it plainly: injuries "peaked when a runner ramped up the distance in a single session." In this plan, that session is the 10-mile long run at the end of week 4, a mile longer than anything before it. Week 6 repeats the pattern.

The plan does give you a few checks. It tells you to slow down if you're struggling, and in week 6 it leaves a Sunday open to rest or cross-train depending on how your body feels. But it never names the early signs to watch for. A niggle, the small ache that hangs on between runs, may raise the risk of an injury that stops you running, though that has been measured in footballers rather than runners. Marathoner Nigel Martin knows where running on one leads: "I found I was able to run through it, literally for several months. However, inevitably as it wasn't getting better, it eventually caught up with me." If one shows up in week 4, that's the moment to drop a repeat or swap Saturday's distance, not to hold the schedule.

The spacing is good. The two hard days never fall back to back, every hard session starts with an easy warm-up of 1 or 2 miles, and Friday and Sunday are days off. The first lighter week comes in week 7, once the hardest work is done, a sensible place for it in a plan only 8 weeks long.

What happens when you miss a day?

When a week goes sideways, this plan leaves most of the adjusting to you. It doesn't tell you which runs to protect, and the pace it asks for never moves.

The squeeze is most likely in weeks 4 and 6, the two weeks with a pair of hard sessions. If one of those weeks only has room for 3 runs, nothing says whether the mile repeats, the track session or the 10-mile long run should go. The plan's one concession is useful: the mile repeats can move to a treadmill or a measured, flat stretch of road, so you don't need the track twice in one week. Friday and Sunday also give you open days to shift a run into. But nothing says what to do after a missed week, and only 2 of the 10 hard sessions explain what they're for. Without that, deciding which run to move or drop is a guess. One rule helps. "You can't make up what you missed," says Furman University professor Bill Pierce, "and you certainly shouldn't double up on your workouts to catch up with your program." Here, a missed track session stays missed, rather than landing on top of the next week's hard days.

The pace itself is described well. The track sessions ask for your goal race pace, and if you're not sure what that is, the plan says it should feel like an 8 or 9 out of 10. That's a fair way in. But the target never changes. Whatever pace you settle on in week 1's fartlek is the one you're still running in week 7, even if your fitness has moved past it.

Will it get you ready for race day?

Yes. Race pace every week and a real taper get this part right.

A 5K is short enough that you spend the whole race near the fastest pace your body can keep up. Race-pace work and threshold work (the effort you could hold for about an hour) are different kinds of training, and for recreational runners no study shows one beats the other. This plan leans on race pace, and its habit of returning to it every week is a sound choice. Because the pieces change length from one session to the next, you meet race pace fresh, tired, in short bursts and in longer ones, and by race day you've run it many different ways.

The long run builds to 10 miles, more than three times the race distance. Then the plan backs off properly. The peak week comes 2 weeks out, week 7 is lighter, and race week drops to about 13 miles before the race, with one short session of 4 laps at race pace to keep your legs awake. A taper like that, cutting the running while keeping a touch of speed, improves race performance compared with not tapering. A short race doesn't change that. "There is no evidence to suggest that an 800m runner, or a 100m sprinter for that matter, should be tapering differently than a marathoner," says Iñigo Mujika, a sport scientist who studies tapering. The lighter week 7 and race week here earn their place, even before a race of 3.1 miles.

The race-day note is good advice, too: start slowly, gather speed as you go, and finish feeling strong.

Are the workouts varied enough?

Mostly, yes. The hard sessions change a lot from week to week. They just never go faster than race pace.

Mixing mostly easy running with a few clearly hard sessions may build endurance better than long stretches of steady, moderately hard running, though recent reviews find the edge is small, and this plan keeps that line clear. About 89 percent of the running is easy, and the hard days take 7 different forms across 8 weeks, from a minute-on, minute-off run in week 1 to repeats of 3 laps in week 5. The hilly Tuesday runs add something different again, as long as you keep them easy.

But it's a 5K plan that never asks you to run faster than 5K pace. There are no strides, the handful of fast, controlled 100-meter runs some plans add to the end of an easy day. There are no short hill repeats and no drills. That's a gap. Strides take only a few minutes, and explosive work such as jumps and sprints can make running cost less energy, though strides themselves haven't been tested that way. Trail runner and author Morgan Sjogren does hers after easy runs: "This reminds my body to run fastest at the end of a workout or race, practice good form, loosen up any tightness and prime my body to run fast the next day during my workout." A few strides after Monday's and Wednesday's easy runs would mean race pace is no longer the fastest your legs ever move.