Half Marathon Training With Apple Watch: A 12-Week Plan That Uses Your Data

A half marathon is 21.1 km, which puts it in an awkward spot. It's long enough that you can't fake it on enthusiasm, and short enough that you don't need to run 30 km on a Sunday to finish. That gap is where most training plans go wrong.

The typical failure isn't laziness. It's that every run ends up at the same medium effort. Medium is comfortable enough to repeat, so people repeat it, and then they arrive at race day with a decent engine and no idea how to pace it. Meanwhile their easy days were never easy, so they never built the base that makes 21 km feel manageable.

Your watch already collects everything you need to avoid that. It measures effort honestly, it tracks whether your easy runs are actually easy, and it tells you when a week was too much. What it doesn't do is decide what to run on Thursday. That's what the plan below is for.

TL;DR: Train for 12 weeks, four runs a week, with roughly 80% of the running genuinely easy. One quality session, one long run that peaks at 16 to 18 km about two weeks before race day, and a taper of 10 to 14 days. Keep weekly volume increases near 10% and take a lighter week every fourth week. The evidence on running injuries is blunt: in one prospective study of 261 runners preparing for a half marathon, jumping weekly distance by 20% to 60% produced significantly more injuries within three weeks than smaller increases. Your Apple Watch gives you the zones, Cardio Fitness trend, Training Load and heart rate recovery to run this plan by effort instead of by ego.

YouTube: Related video

What a half marathon actually asks of you

Three things, in order of importance.

An aerobic base. The vast majority of your race is fuelled aerobically. That's built by time spent at low intensity, not by hard intervals. This is the part people skip.

A pace you can hold just under threshold. For most recreational runners, half marathon pace lands somewhere around 80% to 88% of maximum heart rate, or right about where talking becomes a sentence at a time instead of a conversation. It's uncomfortable but sustainable. You can't train it if you never touch it.

Legs that tolerate 21 km of impact. Cardiovascular fitness improves faster than tendons, bone and fascia adapt. This mismatch is why so many runners get hurt in the final four weeks of a plan, when fitness feels great and the long runs get serious.

That last point is worth sitting with. In a 16-week prospective study of 161 runners preparing for the Utrecht half and full marathon, nine out of ten reported a running-related injury or illness symptom at some point, with new injuries showing up in 5.6% to 14.8% of runners every two weeks. The most common sites were the lower leg and the knee. Nobody in that cohort was undertrained on paper. They were just running a load their tissues hadn't signed off on yet.

The three runs that build a half marathon

Every week in this plan has the same skeleton. You can move the days around, but don't merge the purposes.

A fourth run is optional when you're starting out. Three runs a week will get a first-timer to the finish line. What won't work is three runs a week where two of them are hard.

If you're currently running less than about 15 km a week, give yourself four to six weeks of easy base building before starting week one, or use a couch to 5K ramp first. Twelve weeks is enough time to prepare for a half marathon from a running habit. It is not enough time to build a running habit and prepare for a half marathon.

The 12-week plan

The structure assumes you can already run 5 km comfortably and are averaging roughly 20 to 25 km a week. Long run distances are the anchor; the rest of the week fills in around them.

Four rules hold this together:

• Volume rises by about 10% a week at most. The week 9 jump is the biggest in the plan, and week 10 is only slightly bigger.
• Every fourth week is lighter. Weeks 4 and 8 drop by roughly 25%. You will feel like you're losing fitness. You're not.
• Never put the long run and the quality session back to back. Separate them by an easy day.
• The long run is not a race. If you're finishing it wrecked, it's too fast.

Set your zones before week one

The plan only works if "easy" is a number you can actually see. Two ways to get there, in order of preference.

Use heart rate reserve, not just max heart rate. Apple Watch calculates zones from max heart rate by default, but the more accurate method is the Karvonen formula, which accounts for your resting heart rate. It matters: two runners with the same max but resting rates 20 bpm apart get very different Zone 2 ceilings. The zone setup walkthrough covers the exact steps in the Watch app and the Health settings.

Sanity-check it with the talk test. Zone 2 should feel almost too easy for the first two weeks. If you can't speak in full sentences on an easy run, either your zones are set too high or you're running too fast. Both are common and both are fixable.

If you don't know your max heart rate, don't trust 220 minus age. It's a population average with a standard deviation of about 10 to 12 bpm, which means it can be wrong by a whole zone. How to find your max heart rate has field protocols that are unpleasant but honest.

How Apple Watch fits into this plan

The watch does four jobs here, and it's worth knowing what each one can and can't do.

1. Effort display during the run. Start an Outdoor Run in the Workout app and the current heart rate zone appears on screen. What Apple's native app won't do is alert you when you leave a zone, which is exactly the alert you want on easy days. Most people solve this with a glance every few minutes, or a third-party app that buzzes on zone exit. Either works. The point is to catch yourself drifting into Zone 3 on a recovery run, which is the single most common mistake in half marathon training.

2. Cardio Fitness (VO2 max) as a trend, not a score. Apple estimates VO2 max only during outdoor walks, runs and hikes of at least 20 minutes, so it will update through this plan, unlike a plan built on indoor cycling. Treat the number as directional. A rise of a point or two over 12 weeks is meaningful; a single reading that drops after a hard week is noise. My breakdown of what the estimate really means covers why it's less precise than a lab test and how to make it more reliable.

3. Training Load for the big weeks. If you're on watchOS 11 or later, Training Load compares your 7-day load against your 28-day load and labels the week above, well above, below or well below your usual. In this plan, weeks 5 to 10 should read "above" or "well above" and that's intentional. If week 6 reads "well above" and your resting heart rate has climbed for four days, that's your cue to take the down week early. Training Load explained goes deeper on the calculation.

4. Heart rate recovery after intervals. After a hard rep, your heart rate should fall quickly in the first minute. A 1-minute drop of 20 to 30 bpm is typical for reasonably fit runners; a number that shrinks week over week is an early sign you're accumulating fatigue. Heart rate recovery after exercise explains the measurement and the caveats.

What the watch can't do is tell you whether your left shin is angry. That's still a conversation with your own body, and it wins every argument.

The injury maths, and why the 10% rule exists

The 10% rule gets mocked as folklore, but there's decent prospective data behind the general idea.

In the Danish half marathon cohort, 261 healthy runners were tracked for 14 weeks with GPS watches and weekly injury questionnaires. Fifty-six of them, 21.5%, picked up an injury. The key finding: 21 days into the study, runners who had increased their weekly distance by 20% to 60% were significantly more likely to be injured than those who increased by less than 20%, a risk difference of 22.6 percentage points. Interestingly, the difference didn't hold at 56 or 98 days, which suggests the risk is concentrated in the weeks right after a jump, not spread evenly across a training block.

Two practical translations:

• Cap the increase. Somewhere near 10% is a reasonable ceiling for most runners, and 20% is where the data gets uncomfortable.
• Front-load caution. The weeks after a volume jump, and the weeks after a holiday or illness, are the risky ones. That's when to add an extra easy day rather than push through.

The Clin J Sport Med review of three years of half and full marathon race data adds a second angle: injury patterns differ between the two distances, and cramping and lower limb issues dominate race-day problems. Race-day risk is mostly a pacing and fuelling question, not a fitness question.

Strength work, without wrecking the week

Two short sessions of 20 to 30 minutes is enough. The goal isn't hypertrophy, it's tendon and hip stability: calves, glutes, hamstrings, single-leg control.

Put them after an easy run or on a rest day, never the day before a long run or quality session, and never as an extra hard session stacked on top of a hard week. Bodyweight or light weights, two to three sets, controlled tempo. If you're new to it, strength training for longevity has a simple template that won't interfere with running.

Cross-training is useful for the aerobic system but doesn't prepare your legs for impact. Cycling or swimming can replace an easy run when you're sore. They can't replace the long run.

Race week and pacing

Three things decide your race more than your fitness does.

Don't go out too fast. The first 3 km should feel almost too easy. Almost everyone who blows up in the last 5 km did it in the first 5. Use your watch to hold back, not to chase.

Turn auto-pause off. On a crowded course, auto-pause creates gaps in your data and, worse, teaches you to trust a pace that stops when you slow down.

Plan your battery. A GPS run plus music plus always-on display can drain a watch faster than a 2-hour race allows. Low Power Mode during the race, and a charge the night before, is the boring fix.

On effort: hold Zone 3 for the first third, allow Zone 4 in the middle, and expect the last 3 km to sit near threshold whether you planned it or not. Heat pushes heart rate up by 5 to 15 bpm at the same pace, so pace by feel and by zone rather than by a number you picked in cool weather.

The taper

The last 10 to 14 days cut volume by roughly 40% to 60% while keeping some intensity. Week 11 drops your long run from 18 km to 14 km and keeps one short race-pace session early in the week. Race week is easy running plus a couple of short efforts to keep the legs awake.

What to expect in your data: resting heart rate often dips slightly, HRV often rises, and sleep can get worse because of nerves. If HRV drops sharply in taper week alongside a rising resting heart rate, that's usually early illness rather than fitness loss. HRV down and resting heart rate up has the decision tree.

Don't add sessions because you feel fresh. Feeling fresh is the point of a taper, not a signal to train.

The five-minute weekly check-in

Once a week, same day, look at four numbers. Not daily. Weekly averages.

The last one is the most useful and the most ignored. Apple Health shows time in each heart rate zone for every workout, and you can add the zone chart to a summary. If your easy runs are landing in Zone 3, the whole plan is running at the wrong intensity and you'll feel it around week 8.

Common mistakes

• Running the easy days at medium pace. The single biggest one. If in doubt, slow down.
• Adding the long run and the quality session in the same week you jump volume. Pick one stressor per week.
• Skipping the down weeks because you feel good. The down week is where adaptation happens.
• Chasing VO2 max readings. The estimate moves with terrain, heat and route. Watch the 12-week trend.
• Racing your long runs. A long run run too fast costs you the quality session three days later.
• Starting the plan with an injury you're managing. Twelve weeks of load won't fix it. Get it looked at first.

The short version

• Twelve weeks, four runs a week, 80% of it easy.
• Long run peaks at 16 to 18 km about two weeks out, then taper for 10 to 14 days.
• Keep weekly increases near 10%, with a down week every fourth week.
• Set zones using heart rate reserve, then verify with the talk test.
• Use Apple Watch for zone display, Cardio Fitness trend, Training Load and heart rate recovery.
• The injury data says the weeks right after a volume jump are the dangerous ones, so be conservative exactly when you feel strongest.
• Check four numbers weekly, not daily: resting heart rate, HRV, sleep, time in Zone 2.

Twenty-one kilometres is a distance you can absolutely prepare for on four runs a week. The trick isn't more training. It's making sure the easy days are genuinely easy, so the hard days can actually be hard.

If you want one place to see whether the plan is working, Century AI turns your HRV, resting heart rate and sleep into a daily recovery picture, so a bad week shows up before race day does.

This isn't medical advice. If you have an injury, a heart condition, or you're returning to running after a long break, check with a clinician or a physio before starting a training block.

Century AI helps you understand your body with a daily health score, recovery score, and sleep insights — using the watch you already wear.