Running Plan Review Runner's World Break 2:30 Half Marathon Training Plan

Does it build you up smartly?

The plan's outline is sound. Two easy weeks give your legs a base, the goal-pace work builds from there, and the final weeks turn toward the race. Building in stages like this, with a different emphasis in each, tends to beat training the same way from start to finish.

Thursday is where the plan is at its best. Each goal-pace run is written out in full: an easy mile to warm up, the miles at goal pace, an easy mile to cool down. The workout key also says what those miles are for: more lung power, a more efficient stride, and the mental toughness a race asks for. You always know what Thursday is and why you're running it. Coach Bill Pierce, co-founder of the FIRST program behind the magazine's 3-day plans, found that rare: "With most runners, when I ask them what they're hoping to accomplish on a given run, they look back at me with a blank stare." On this plan, the workout key answers that question for every Thursday.

Week 5 is the one week shaped differently. It has no goal-pace run, and it's the same week the long run first reaches 10 miles. It reads as a trade, an easier Thursday to make room for a bigger Sunday.

Does it protect you from injury?

Halfway. The plan keeps its hard runs apart, but it misses several of the other ways a plan can protect you, and one week asks for far more than the weeks before it.

That week is week 7. After 3 weeks at 17 miles, it rises to 23, and most of the rise comes on Sunday, when the long run goes from 8 miles to 13. That's three miles past anything the plan has asked of you so far. Sudden jumps in running load tend to raise the risk of injury, and a weekly rise of more than about 30%, like this one, is a warning sign. Many injuries that look like slow wear seem to start suddenly, often right after a single run that goes past what the legs are used to. In a study of more than 5,000 adult runners who logged their runs on Garmin watches, injuries climbed when "the distance of a single running session exceeded 10% of the longest run undertaken in the last 30 days," researchers at Aarhus University found. Week 7's 13 miles is 30% longer than the 10-miler in week 5. A runner a year into the sport may have the heart and lungs for 13 miles before the legs are ready, because bone adapts to running slowly, over months, and bone stress injuries are thought to come when impact rises faster than bone can rebuild. The Sunday can feel fine, and the sore shin can show up on Tuesday.

The build also never takes a real step back before the taper. 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. This plan keeps you at full load from week 3 until the last 3 weeks.

Strength training is the next gap. The plan never mentions it or puts it on the calendar, so finding the days and deciding what to do falls to you. That's a real loss, because strength training substantially lowers injury risk in sport, more than stretching or balance work do. "If strength training buys you consistency and health, that buys you seconds," says Eugene, Oregon, physical therapist Dan White. With 3 rest days most weeks, there's room for a short session or two, and on a plan built around a time goal, the healthy weeks are where those seconds come from.

Nor does the plan say what to watch for. Many runners notice that a niggle, an ache that lingers from one run to the next, can come before an injury that interrupts training, though the evidence is early. That makes it worth treating as an early warning, a reason to ease off before the next run. Nothing here says so. "If it happens again the next week, and the next week, it doesn't become a niggle anymore," one recreational runner told researchers at Dublin City University, "it becomes a problem where you know it is not going to go away." When an ache is still there on your next run, ease off, even though the plan won't tell you to.

What the plan gets right is the spacing. The goal-pace run is always followed by an easy day or a rest day, it always opens with an easy mile, and the rest days come with suggestions for relaxation, light mobility, and easy yoga.

What happens when you miss a day?

Picture the third goal-pace mile on a Thursday in week 8, the one that's supposed to feel controlled. If it feels like racing instead, the plan doesn't tell you what that means. Goal pace is a fixed number from week 3 to race week, with no description of how it should feel and no point in the build to check whether the goal still fits. Asked whether one workout can predict a half marathon, former elite marathoner and coach Jo Wilkinson was skeptical: "the best indicator of race times is training as a whole." So read the Thursdays together. One rough run means little, but if goal pace still feels like racing in week 8, after 5 of them, the goal may be too fast.

The same silence covers missed runs. Nothing says what to do after a skipped long run, a missed Thursday, or a few days off sick, and every run is presented as equally important. So in a short week you have no guide to which run to keep. Most weeks have 3 rest days, so there's usually space to move a run. But deciding what to move, and what to drop, is left to you.

The plan is clear about one thing: who it's for. At least a year of running and about 15 miles a week is a plain starting line, and it tells you before you begin whether the first weeks will fit.

Will it get you ready for race day?

Yes. This plan builds the fitness a half marathon asks for, and it times it well.

The goal-pace run carries most of it. It starts at 3 miles at the pace you plan to race and grows to 5 by week 9, so the effort of the race becomes something your body has practiced. It also becomes familiar. With steady running, your heart rate at the same pace tends to come down, and by race week the goal is less a number on the watch than a rhythm you know.

The long run reaches 13 miles in week 7, three weeks out, so race day asks for only a tenth of a mile more than you've already run. Weekly mileage peaks at 23, plenty for a half at this level.

Then the plan eases off over the last 3 weeks, and cutting volume in the final weeks while keeping some faster running improves race performance compared with not tapering. Race week's Thursday is 3 miles at goal pace, the same run as your first goal-pace session back in week 3. It makes a good before and after: the same miles, with 7 weeks of practice behind them.

Are the workouts varied enough?

Partly. The easy running is well judged, but the hard running never gets truly hard.

About 4 of every 5 miles are easy, and the workout key describes them well: slow enough to hold a conversation, started gently so you finish strong. That's the right foundation, because easy running is the base the rest of the week is built on.

But across all 10 weeks, not a single mile is run faster than goal pace. Every hard session is the same goal-pace run, a little longer or shorter, and for most runners half marathon pace is moderately hard work rather than hard. Mostly easy running mixed with a few clearly hard sessions may build endurance a little better than steady, moderately hard running. This plan has the easy part and the moderate part, and nothing harder. Pierce learned the cost of sameness as a runner. "I used to run the same speed workout week after week," he recalled. "After a while, I would start to dread that workout." Here, every hard day in the 10 weeks is a version of one run, so if you want variety, you'll have to add it.

Strides are missing too. These are a few brief, fast pickups at the end of an easy run, and many plans use them to keep a stride quick. Short, explosive efforts can make runners more economical, though strides themselves haven't been tested directly. Even so, they're a cheap way to practice running fast, and they take only a few minutes.