Understanding Hal Higdon's Approach
The basics are simple enough. You run most days at an easy conversational pace. You run one long run each week. You take one or two rest days. There is a Wednesday and a Saturday workout day built in, and those are usually speedwork or tempo runs depending on the level. The schedules come in beginner, intermediate, and advanced flavors, and the progression is gradual over 16 weeks. I downloaded the intermediate plan back when I was training for my first half and just started running it. Week one had three run days and a rest day. By week six, I was doing six days of running with a long run of about nine miles on Sunday. It felt doable, but the real question was whether the structure actually prepared you for race day. Here is the thing most people miss when they grab a free PDF off the website. The schedules list distances and days, but they do not tell you what pace to run at on most days. Hal describes this as "conversational pace," but that is vague if you are just starting out. Conversational pace for me was probably around 10:30 per mile. That is slow. It feels too slow. You will want to go faster, especially on those easy weekday runs, because your legs feel fresh and you think you are capable of more. Resist that urge. If you run your easy days too hard, your long run on Sunday suffers and you accumulate fatigue that compounds over the weeks.
The program uses a build phase, an intensity phase, and a taper. Build is roughly weeks one through eight where weekly mileage creeps upward. Intensity covers weeks nine through thirteen, which is where the Tuesday speedwork and Thursday tempo runs become more impactful. Taper is the final three weeks. During taper you drop volume significantly, but you keep some sharpness in your legs with shorter bursts of faster running. Most people taper too aggressively and come out flat on race morning, or they refuse to taper and carry residual fatigue into the start line. A couple of specific details that matter. The long run is non-negotiable. It is the single most important run of the week. If you skip it or cut it short because you are busy, you are undermining the whole plan. The Wednesday and Saturday workouts are scheduled for a reason. Wednesday gives you a repeat session, usually something like six by eight hundred meters or four miles at tempo effort. Saturday is typically the longest or the second longest run in the week. Rest days are not optional suggestions. They are where adaptation happens. I learned this the hard way in week eight when I ran my Tuesday workout, then added a casual three-miler on Thursday because I felt good, and then my Saturday long run felt like a chore for the first time in the program. That was a clear signal I had ignored the recovery principle. I also encountered a specific edge case that the standard schedule does not really address. About week ten, I hit a calf issue on my left leg after a tempo run on Thursday. The plan had a Thursday tempo of five miles at what Hal calls "comfortably hard," which for me is roughly three seconds per mile slower than half marathon race pace. That tempo run irritated the calf. The next day was supposed to be an easy three-mile run before the long run on Saturday. I was sore and not sure whether to push through or sit it out. What I ended up doing was dropping Thursday's tempo run to a brisk jog, replacing Friday's easy run with a walk, and then doing a shortened six-mile long run on Saturday instead of the planned nine. It was not ideal, but it kept me healthy enough to complete the program without a full stop. The workaround was basically honoring the fatigue signal early rather than waiting for it to become a stress fracture or a torn fiber, which is a much more common outcome for runners who ignore these signals.
If you are interested in the actual plan, you can find the free downloadable schedules at halhigdon.com. They have the half marathon plans organized by level, and each one includes a brief guide explaining how to read the calendar notation. The intermediate plan uses a format like R for rest, E for easy, T for tempo, and X for the long run. The PDFs are straightforward. No hidden membership required. There are some limitations worth noting upfront. The intermediate plan caps the long run at 13 miles. For a half marathon that is technically sufficient, but it is not a full simulation of race-length endurance for everyone. Some runners, particularly those with higher weekly mileage coming in, benefit from a longer build-up. You might want to add one or two extra long runs of 11 to 12 miles before hitting the 13-mile peak, or you could extend the plan by a week. The basic beginner plan is even lighter, with a max long run of about nine miles, and that can leave some people underprepared if they jump straight into race day without a solid base already. Another structural issue is that the schedule does not offer much flexibility for people with irregular work weeks. The fixed Wednesday and Saturday workout days are convenient for routine, but if your job requires travel or late shifts mid-program, the plan becomes awkward to adjust. You can shift days around, but then you risk stacking two hard efforts close together, which defeats the purpose of the rest day. When that happened to me in week 12, I moved the Thursday tempo to Friday and skipped the Saturday long run entirely, substituting a rest day. Race week was fine because the taper was already in progress, but it is something to consider if your schedule is unpredictable.
Get the Full Details
The plan also does not include strength training, which is a gap. The original Higdon materials reference it loosely, but the calendars themselves do not integrate it. I would recommend adding two days of lower-body strength work during the build phase, focusing on glutes, hamstrings, and calves. This is not optional if you are over 35 or coming back from an injury. It helps prevent the kind of wear-and-tear problems that show up around week ten or eleven, which is when cumulative fatigue starts exposing weak points. One more practical note about execution. You should test your nutrition and gear on the long runs before race day. The program tells you the distance, but it does not tell you to practice eating gels or drinking sports drink while running. I learned this around week nine when I did my first long run without having eaten anything beforehand, bonked at mile ten, and had to walk the last two miles. After that, I made sure every long run over eight miles included my race-day fueling strategy. It is a small detail that most people overlook until it becomes a race-day problem. Overall, the Higdon half marathon programs are solid for a reason. They are accessible, free, and based on a logical progression that works for the majority of recreational runners. They are not magic. You still have to put in the miles, respect the rest days, and avoid the temptation to run your easy days too fast. If you do those things, the plan will do what it is supposed to do.
