Setting Up a Half Marathon Training Plan on Your Garmin
I have used Garmin's training planner for four years now, and it does the job better than most people expect once you stop expecting it to work like a smartphone app. The system lives inside Connect and Connect Mobile. From there, you can push a full 8 to 14 week plan directly to any Garmin watch that supports structured workouts, which covers everything from the Forerunner 55 up through the 965 and the Fenix and Epix lines. Open the Connect mobile app or the desktop website. Tap Training Plans. Search for Half Marathon. You will see several options, usually 8 weeks, 10 weeks, and 12 weeks, each tagged by fitness level. Pick the one that matches your current race pace goal and your recent weekly mileage. Confirm the start date, let it generate the schedule, and then tap Send to Device. That is it. The workouts appear in your watch calendar exactly as planned. The workouts themselves use Garmin's structured format, which means each run contains target heart rate zones, target pace bands, or both. A typical Tuesday interval session might read: 10 minute warm up, six times 800 meters at threshold pace with 90 second jog recovery, 10 minute cool down. Your watch beeps or vibrates at the right moments. You follow the paces. Nothing fancy about it.
A Problem I Hit and How I Fixed It
My biggest headache happened during a 10 week plan when I was training for a spring race. The watch insisted on displaying every interval in meters, but I run on a mix of road and trail where distance is approximate anyway. Garmin does not let you swap the workout unit from meters to kilometers after the plan is generated. The workaround is simple but not obvious: go back into the plan before it syncs to your watch, open the individual workout settings, and change the unit display to kilometers. Then resync. I did this once and spent about ten minutes editing each interval by hand across the full plan, which is tedious but takes less time than the alternative of restarting the whole schedule. Garmin calculates training load based on normalized power or heart rate data depending on your sensor setup, and the body battery metric tracks accumulated fatigue. These numbers are useful but only when you understand the lag time. Garmin's acute to chronic workload ratio improves slowly over two to three weeks. If you push hard in week four and see your load spike without feeling faster, that is normal. Your fitness markers usually surface around week six to eight, which is why most plans include a three to five day taper before race week. Skipping the taper because you feel fresh is the most common mistake I see. The plan assumes you will not feel dramatically faster until the final week, and beating that assumption tends to produce a flat last few miles on race day. Another detail beginners miss is that the smart intervals feature inside Garmin Connect automatically adjusts the target pace or heart rate based on your recent performance history. If your recent half marathon pace test is slower than the plan expects, the workout recalculates downward. This is helpful, but it can also mask poor recent fitness if you have not updated your race result in months. Make sure your current data matches your actual fitness before you start a plan, or you will end up racing slower workouts than you should be doing.
Limitations and When It Fails You
Garmin's training planner is not built for runners who need highly individualized pacing based on terrain or weather. It treats every interval as flat and predictable. If you live in a hilly area or train mostly on trails, the target paces will drift. I have run flat threshold intervals on a hilly route and found myself forty seconds per kilometer slower than planned, which defeated the purpose of the session. In those cases, switching to heart rate based intervals produces better results because pace will always lag on an uphill regardless of effort. You can switch the workout target from pace to heart rate in the workout editor before syncing, but you need to do this for each run you want adjusted. Another limitation is the sync delay. Plans created on desktop sometimes take up to twenty four hours to appear on older watch models like the Forerunner 245. Newer watches sync within minutes. If you create a plan the night before and expect it on the watch that morning, it probably will not be there yet. Plan ahead by at least a day. If you need more customization, the Garmin ecosystem pairs well with Third Party training platforms. TrainingPeaks and Runna both export workouts that Garmin watches can ingest as custom intervals. This takes more manual setup but gives you control over exact segment lengths, warm up distances, and pace adjustments that Garmin's built in planner does not offer.
Get the Full Details
Practical Setup Steps
Create your account at connect.garmin.com or open the Connect Mobile app. Go to Training and then Training Plans. Filter for Half Marathon and select the duration that matches your timeline. Set your current 5K, 10K, and half marathon pace estimates based on a recent test or a recognized race result. Confirm your target race date. Review the generated plan and note any weeks that look too aggressive or too easy for your current fitness. Edit individual workouts if needed. Tap Save and Send to Device. Wait for the sync to complete. Check your watch calendar to verify the workouts appear. Run the first week, record the session, and review the training load report afterward to see whether the plan is tracking toward your goal or drifting. The link to the official plan library is connect.garmin.com/training-plans. That is the source. No third party tools required unless you want more granular control.
