Running Plan Review Runner's World 14-Week Beginner Half Marathon Training Plan

Does it build you up smartly?

Week 2 and week 12 of this plan look almost the same. Three easy runs, a long one on Sunday, three days off. The distances grow, but the kind of running never changes. There are no named phases, and the closing weeks of the build look like the opening ones, only longer.

Each day, at least, is clear. Every run names a distance and an effort, often with a line of coaching, so you always know what today asks of you.

The missing phases are a smaller loss than they sound. In a plan with hard sessions, shifting their focus as the race gets closer tends to beat keeping them the same, and most coaches move from general fitness toward race-specific work. A plan run entirely at easy effort has no hard work to put in order, so the one-shape week costs this runner less than it would cost someone chasing a time.

Does it protect you from injury?

Partly. The build is gentle, but the plan leaves out two protections that matter most for a newer runner.

The first is strength training. The plan mentions it but never puts it on the calendar, so when to do it and what to include are left to you. That's a real gap, because regular strength work cuts injury risk in sport by more than stretching or balance work does. It matters more here than in most plans. Your heart and blood tend to adapt to running within a few weeks, while tendons need weeks to a few months, and bone usually takes longer still. A runner a year or two into the sport is often fitter than their legs are ready for. Lorraine Moller, an Olympic marathon medalist from the Lydiard school, put it as a rule: "you can never progress faster than your slowest part will allow." This plan's gentle climb respects that rule, but the strength work that builds up the slowest part is yours to add.

The second is knowing when to back off. In week 1, the plan asks you to keep a log, including any aches and pains, so you can address them early. That's a good habit, and the log is the right place to spot a pattern. But the plan never says what to look for in it, or what to do when you find something. Runners often describe injury as a sliding scale rather than a switch, from running smoothly to a low-grade ache to something that stops them. Early evidence, from footballers rather than runners, suggests an ache that hangs around from one run to the next may raise the odds of an injury that stops you running. Runners call that kind of ache a niggle, and one club runner in an Irish study drew the line this way: "discomfort can come and go, whereas a niggle is sort of always there." If the same spot shows up in your log two runs in a row, that's the moment to take a day off or cut the next run short, not to push on to stay on schedule.

What the plan does well is avoid the jumps. Sudden rises in running tend to raise injury risk, most clearly when a single run goes well past your longest of the past month, and this plan never makes one. Mileage rises in small steps, never more than about 3 miles from one week to the next, and the long run never goes more than 2 miles past the longest you've run before. Every long run is followed by a Monday off, there are 3 full rest days every week, and the easy days stay easy. Those are the basics, and the plan gets every one of them right.

What the steady climb lacks is a real step back. The only true lighter week is week 12, and it doubles as the start of the taper. Before that, weeks 9 to 11 run 24 to 26 miles back to back. Training that keeps piling up with no relief tends to raise the risk of injury and illness, and a plan you follow on your own needs that relief written in. Instead, the plan pulls back the long run. Four times before the peak, Sunday drops back a step: 7 to 6 in week 3, 8 to 6 in week 5, 10 to 8 in week 8, and again in week 10. The week 8 note gets the spirit right: you may feel strong enough to go longer, but it's best to just do the miles prescribed. But the weekday runs hold steady, or grow by a mile, while Sunday drops only a mile or two, so the weekly total barely moves: 19 miles to 18 in week 3, 21 to 19 in week 5, 24 to 23 in week 8. A real down week cuts deeper. Robert Chapman, as coach of Team Indiana Elite, gave his runners one every fourth or fifth week, and his priority was "dropping mileage 20 percent," he once explained. The dips here are 1 or 2 miles, under 10 percent. Your legs get a shorter Sunday, not an easier week.

What happens when you miss a day?

The plan's rule for a missed run comes in week 4: don't worry about it, stay on the schedule, and don't try to cram the missed miles into the rest of the week. "You can't make up what you missed," says Bill Pierce, co-founder of Furman University's FIRST training program, "and you certainly shouldn't double up on your workouts to catch up with your program." Missing a few miles won't make or break your race, the plan says, but cramming them in can set you up for injury. That's good advice. But it's the only advice. Nothing tells you what to do after a missed week, or how to come back from a cold, or which run to keep when there's only time for 2.

Some of that you can work out for yourself. The long run is clearly the run that matters most, and the plan marks it that way. The shape of the week helps too. With 3 rest days spread across it, there's almost always an open day to move a run into. Many of the easy days offer the same time on a bike or an elliptical as an alternative, which is useful when your legs need a break from the pavement. And because every run goes by effort, there are no paces to fall behind on.

The plan also tries to keep you from missing runs in the first place. Week 3 suggests heading out at the same time each day, so the run becomes part of the schedule rather than something you fit in.

And it does one thing well before you even start: it tells you clearly who it's for. If you've been running 15 to 20 miles a week for a year and have a 5K behind you, week 1 will feel like a normal week. If you haven't, it won't, and you'll know that on day one rather than in week 6.

Will it get you ready for race day?

Yes, if your goal is to finish. The plan builds what a first half asks for, and it times it well.

A first half marathon isn't a speed test. It asks you to keep moving for a long time, and the long run teaches exactly that. Here it climbs to 10 miles in week 7, 10 to 12 in week 9, and 12 in week 11, the biggest week of the plan. That's 3 weeks before the race, which leaves time to recover from it before the start.

Will 12 miles get you through 13.1? For a runner aiming to finish, the plan puts the last mile within reach. Your longest run comes 3 weeks out, so the last mile on race day is new ground. The difference is that the race comes after 3 lighter weeks, and the 12-mile Sunday came after none. And the plan is relaxed about walking. Its week 11 note says walk breaks ease fatigue and help you feel energized when you start running again, and nothing in the note limits them to training. Olympian Jeff Galloway, who spent decades teaching runners to take walk breaks, once answered a runner who asked whether walking in a marathon was cheating: "there are no rules about how much to run and how much to walk." If your first 13.1 needs a walk break or two in the last miles, it still counts as a finish.

Then the running eases off. Week 12 drops the long run to 6 miles, week 13 holds it to 8, and race week is 3 short, easy runs before Sunday. A taper of up to 3 weeks improves race performance compared with running hard right up to the race, and this one is well judged for a beginner. The plan even knows how the last days feel. Saturday's 2-mile run, it says, is more for your mind than your body, for when you're nervous that you've rested too much.

The race-day preparation is good too. The long runs in the middle of the plan double as dress rehearsals, with your race start time and race gear. In week 12, you can swap the long run for a 5K race. The plan asks you to run it at your even, comfortable pace and let the pack go. It's a chance to practice the start line, the crowds, and the urge to go out too fast, before it counts.

Are the workouts varied enough?

Not on the schedule. Every run on it is easy, and that's a deliberate choice, with a fair case behind it.

For a first half, the case is real. Easy running is the base everything else stands on, and a runner building to 13.1 for the first time gets most of what they need from more of it. Keeping every run easy also means you never have to judge whether a workout went well, and each day's run is clear from the grid at a glance.

But a few small additions would cost very little. Strides are 15 to 20 seconds of quick, smooth running at the end of an easy run, with a walk between each one. A handful take about 5 minutes and give your legs regular practice at moving quickly. "I do strides on my easy days after my run," says trail runner Morgan Sjogren, and they remind her body to "practice good form, loosen up any tightness." Any of this plan's 3 weekday easy runs could end with a few. A little strength work would round it out, on top of what it does for injury risk. The plan has neither.

Hills come up only in the notes. Week 6 suggests heading for them rather than avoiding them, and week 12 suggests running a hillier route once yours feels easy. That's useful advice, but it's advice. Hills never appear as a run on the schedule.

The cost shows if you want more from race day than a finish. Nothing in the plan is faster than easy, so running the half faster than your long runs means doing it for the first time on the day. For a runner who wants to finish, that's a fair trade. For a runner with a time in mind, it isn't enough.