Sport Guides
Half Marathon Training with Garmin: A Data-Driven Plan
April 16, 2026
The Half Marathon Is Its Own Discipline
Most runners treat the half marathon as a stepping stone — either a long 5K or a short marathon. Both framings lead to the wrong training. The half marathon is a distinct event with its own metabolic demands, and conflating it with its neighbors is one of the most consistent mistakes recreational runners make.
The 5K is decided primarily by VO2 max. The marathon is decided primarily by aerobic endurance and fat oxidation efficiency. The half marathon lives in neither of those houses. A 90-minute to 2:30 effort sits squarely at the upper edge of your lactate threshold — the pace you can sustain before lactate accumulates faster than you can clear it. Train below that ceiling and you leave time on the table. Train above it too often and you burn out before race day.
This is also the distance where pacing mistakes are most punishing. Go out 10 seconds per kilometre too fast in a 5K and you suffer for eight minutes. Go out 10 seconds too fast in a half marathon and you spend the final 6 kilometres in a metabolic hole you cannot climb out of.
What this means practically: your training needs a clear threshold focus, a solid aerobic base underneath it, and enough VO2 max stimulus to keep the ceiling moving. Get those proportions right and the half marathon rewards you generously.
The Garmin Metrics That Actually Predict Half Marathon Performance
Garmin collects a lot. Not all of it matters equally for the 21.1.
Lactate Threshold Pace and Heart Rate
This is the number. Your lactate threshold — the pace and HR at which lactate starts accumulating — is the single strongest predictor of half marathon performance. A well-executed half marathon is run at 95–100% of lactate threshold pace for most runners, and just above threshold effort for those who have trained the top end.
Your Garmin estimates this automatically from your running history. The estimate improves with more varied effort — a mix of easy, tempo, and hard sessions gives the algorithm better data to work with. If you have done a recent time trial or a race, the estimate will be sharper. Check your lactate threshold pace in the Training Status section of Garmin Connect and treat it as your primary training anchor.
VO2 Max — Important, But Secondary
VO2 max matters more for the 5K than the half. But it still matters here. A higher VO2 max means your lactate threshold pace can be faster before you hit the ceiling. Think of VO2 max as the height of the building; lactate threshold is the floor you actually live on.
You can track your VO2 max estimate in Garmin Connect and watch it respond to training load over weeks. If you want to understand how to push it upward, the details are in the VO2 max improvement guide.
Heart Rate Zones — Get These Right First
Every metric in this article is worthless if your HR zones are misconfigured. Garmin defaults to age-predicted max HR, which is accurate for almost nobody. Before you follow any plan, confirm your zones are set from an actual max HR test or a recent race effort — you can calculate your zones using Karvonen or %MaxHR here. Five minutes of miscalibration compounds across every session for twelve weeks. Fix this first.
Training Load and Load Ratio
Training load ratio — your acute load versus chronic load — tells you whether you are building fitness or accumulating fatigue. For half marathon prep, you want to keep this ratio under 1.3 during build phases and bring it down to 0.8–0.9 in the taper. Garmin flags "overreaching" when the ratio climbs too high. Take that flag seriously.
Long-Run Aerobic Adaptations
Long runs build capillary density, mitochondrial volume, and fat utilization efficiency — adaptations that matter even at half marathon pace. The signal to watch is HR drift: if your pace stays flat but HR climbs significantly over the final third of the run, your aerobic base needs more work before you layer on threshold sessions.
The Beginner Plan: Finish Strong (10 Weeks)
Best for: Runners doing 15–25 km/week, targeting completion or a first finish under 2:30.
The goal here is to build your long run to 16 km, introduce threshold effort gently, and arrive at the start line healthy. Zone 2 makes up roughly 80% of all running. The one weekly quality session is a controlled tempo — not an all-out effort, just sustained discomfort at a pace you could hold for 30 minutes. Read more about why Zone 2 is the foundation.
| Week | Mon | Tue | Thu | Sat (Long) | Total km |
|---|---|---|---|---|---|
| 1 | Rest | 5 km easy | 5 km easy | 8 km Z2 | 18 |
| 2 | Rest | 6 km easy | 5 km easy | 9 km Z2 | 20 |
| 3 | Rest | 6 km easy | 6 km tempo (20 min) | 10 km Z2 | 22 |
| 4 | Rest | 6 km easy | 6 km easy | 11 km Z2 | 23 |
| 5 | Rest | 7 km easy | 6 km tempo (25 min) | 12 km Z2 | 25 |
| 6 | Rest | 7 km easy | 6 km easy | 13 km Z2 | 26 |
| 7 | Rest | 8 km easy | 7 km tempo (30 min) | 14 km Z2 | 29 |
| 8 | Rest | 7 km easy | 6 km easy | 16 km Z2 | 29 |
| 9 (taper) | Rest | 6 km easy | 5 km tempo (20 min) | 12 km Z2 | 23 |
| 10 (race) | Rest | 4 km easy | 3 km shakeout | Race day | — |
Tempo sessions should be run at a pace where conversation is difficult but sentences are possible — approximately Zone 3 on your Garmin. Do not use pace for these sessions. Use perceived effort and HR.
The Intermediate Plan: Sub-2:00 (12 Weeks)
Best for: Runners doing 30–50 km/week, targeting 1:45–2:00.
This plan introduces a proper threshold session, a VO2 max workout every second week, and long runs with race-pace segments. The key unlock at this level is learning to run at lactate threshold pace accurately — not "hard effort" but a specific, reproducible pace your Garmin can help you hold.
Your target race pace for a 2:00 finish is 5:41/km. For 1:45, it is 4:59/km. Threshold training pace is approximately 10–15 seconds faster per kilometre than your target race pace.
| Week | Tue | Wed | Thu | Sat (Long) | Sun | Total km |
|---|---|---|---|---|---|---|
| 1 | 8 km easy | — | 8 km threshold (4×8 min) | 14 km Z2 | 6 km easy | 36 |
| 2 | 8 km easy | — | 8 km easy | 16 km Z2 | 6 km easy | 38 |
| 3 | 9 km easy | — | 10 km threshold (5×8 min) | 17 km (last 4 @ race pace) | 6 km easy | 42 |
| 4 | 8 km easy | — | 8 km easy (recovery) | 14 km Z2 | 5 km easy | 35 |
| 5 | 9 km easy | — | 10 km VO2 max (6×3 min) | 18 km Z2 | 7 km easy | 44 |
| 6 | 9 km easy | — | 10 km threshold (5×10 min) | 18 km (last 5 @ race pace) | 7 km easy | 44 |
| 7 | 10 km easy | — | 12 km threshold (2×20 min) | 20 km Z2 | 8 km easy | 50 |
| 8 | 9 km easy | — | 10 km VO2 max (5×4 min) | 20 km (last 6 @ race pace) | 6 km easy | 45 |
| 9 | 10 km easy | — | 12 km threshold (3×12 min) | 21 km Z2 | 7 km easy | 50 |
| 10 | 9 km easy | — | 10 km threshold (2×15 min) | 18 km (last 4 @ race pace) | 6 km easy | 43 |
| 11 (taper) | 8 km easy | — | 8 km threshold (2×10 min) | 14 km Z2 | 5 km easy | 35 |
| 12 (race) | 6 km easy | — | 4 km shakeout | Race day | — | — |
Pace targets for quality sessions:
| Target finish | Race pace | Threshold pace | VO2 max interval pace |
|---|---|---|---|
| 2:00 (5:41/km) | 5:41/km | 5:20–5:28/km | 4:55–5:05/km |
| 1:45 (4:59/km) | 4:59/km | 4:40–4:48/km | 4:15–4:25/km |
The Advanced Plan: Sub-1:30 (14 Weeks)
Best for: Runners doing 60–80+ km/week, targeting sub-1:30 (4:15/km).
At this level, the training stress has to be specific and the recovery has to be managed actively — not by feel but by data. Your Garmin's HRV status, sleep score, and body battery are inputs you act on, not decorations. A scheduled threshold session on a day when your HRV is suppressed and body battery is below 40 should become an easy run. The plan below is the intended structure; your recovery data governs whether you execute it as written.
Target race pace: 4:15/km. Threshold pace: 3:55–4:05/km. CV interval pace: 3:38–3:48/km.
| Week | Tue | Wed | Thu | Fri | Sat (Long) | Sun | Total km |
|---|---|---|---|---|---|---|---|
| 1 | 12 km easy | — | 14 km threshold (3×12 min) | — | 20 km Z2 | 10 km easy | 56 |
| 2 | 12 km easy | 8 km easy | 14 km CV (8×3 min) | — | 22 km Z2 | 10 km easy | 66 |
| 3 | 12 km easy | — | 16 km threshold (2×20 min) | — | 22 km (8 @ MP) | 10 km easy | 60 |
| 4 (recovery) | 10 km easy | — | 12 km easy | — | 16 km Z2 | 8 km easy | 46 |
| 5 | 12 km easy | 8 km easy | 16 km threshold (3×15 min) | — | 24 km Z2 | 10 km easy | 70 |
| 6 | 12 km easy | — | 16 km CV (10×3 min) | — | 24 km (8 @ MP) | 10 km easy | 62 |
| 7 | 14 km easy | 8 km easy | 18 km threshold (4×12 min) | — | 26 km Z2 | 12 km easy | 78 |
| 8 (recovery) | 10 km easy | — | 12 km easy | — | 18 km Z2 | 8 km easy | 48 |
| 9 | 14 km easy | 8 km easy | 18 km threshold (2×25 min) | — | 26 km (10 @ MP) | 12 km easy | 78 |
| 10 | 14 km easy | — | 16 km CV (6×4 min) | — | 26 km Z2 | 12 km easy | 68 |
| 11 | 14 km easy | 8 km easy | 18 km threshold (3×18 min) | — | 24 km (6 @ MP) | 10 km easy | 74 |
| 12 | 12 km easy | — | 14 km CV (8×3 min) | — | 22 km Z2 | 10 km easy | 58 |
| 13 (taper) | 10 km easy | — | 12 km threshold (2×12 min) | — | 16 km Z2 | 8 km easy | 46 |
| 14 (race) | 8 km easy | — | 5 km shakeout | — | Race day | — | — |
Double-day Wednesdays are optional in weeks 2, 5, 7, and 9. Add them if your training load ratio allows and your recovery data is green. Remove them if either is compromised.
For taper specifics, the race taper guide covers how to read your Garmin's performance condition in the final two weeks.
Race-Day Pacing with Your Garmin
The most common half marathon blow-up has nothing to do with fitness. It is starting too fast because the first kilometre feels easy, which it should — you are fresh and flooded with adrenaline.
The rule: run the first 5 km by HR, not pace. Target 5–8 beats below your lactate threshold HR. Your Garmin's HR field is your only data field that matters in this phase. Ignore your pace. Ignore everyone around you.
Kilometres 6–14 are your working phase. Allow your HR to drift up to your lactate threshold ceiling — not above it. If your HR is already at threshold HR by kilometre 8, you started too fast and need to back off immediately. A small correction at kilometre 8 saves you significantly at kilometre 17.
The final 5 kilometres are your only sanctioned opportunity to go harder. By kilometre 16, you have enough elapsed time data to know whether you have banked effort or spent it. If your HR has been well-managed, the final stretch is where you can progressively increase effort and chase a negative split.
Suggested Garmin data screen for race day:
- Field 1: Heart rate (HR)
- Field 2: Current pace
- Field 3: Elapsed time
- Field 4: Lap pace (set auto-lap to 1 km)
Garmin Connect's race predictor can give you a pre-race time estimate based on your current fitness — you can also estimate your half marathon time from any recent race using the Riegel formula. It is not always perfect, but it is a useful sanity check against the goal pace you have been training toward.
Common Mistakes Your Garmin Data Will Surface
The gray zone problem. Most recreational runners spend too much time in Zone 3 — not easy enough to build base, not hard enough to drive threshold adaptation. Your Garmin's training distribution chart will show this clearly. If your weekly breakdown is clustered in the 130–155 bpm band with nothing easy and nothing hard, redistribute toward Zone 2 and real threshold work.
Under-fueled long runs. If your HR drifts sharply upward after 60–70 minutes on a long run while your pace stays flat or drops, you are running into a glycogen problem. This is not fitness — it is fueling. Half marathon training long runs should include carbohydrate intake for anything over 75 minutes.
Threshold pace not moving. If your lactate threshold pace in Garmin Connect has been unchanged for six weeks, you are not doing enough threshold stimulus. Easy running alone does not move this number. One honest threshold session per week — properly paced, not just "hard" — is the minimum dose.
Ignoring recovery signals between quality days. Two hard sessions in two consecutive days is almost always counterproductive. Your Garmin's HRV status and body battery are not decorative. If both are suppressed on a scheduled quality day, run easy. The adaptation from the previous hard session is still processing — a second hard session competes with it, not adds to it.
A Smarter Way to Manage All of This
Static plans are useful templates. They cannot adjust when you get sick in week 7, when work stress tanks your HRV for ten days, or when your threshold pace jumps unexpectedly and your paces need updating.
That is the gap that AI coaching on your Garmin data was built to fill. Gneta reads your actual Garmin metrics — load ratio, lactate threshold, HRV trend, sleep quality — and uses them to adapt your plan week to week rather than pushing a fixed schedule regardless of how your body is responding. Workout reviews explain whether your last session landed the intended stimulus. Weekly reports flag when your training distribution has drifted off course before it costs you fitness.
Garmin Connect tracks the data well. What Gneta adds is the interpretation layer that turns raw numbers into specific, actionable coaching — without the complexity of a TrainingPeaks setup or the guesswork of going it alone.
Ready to train with a plan that reads your data? See how Gneta works or compare plans and pricing.
Related reading:
