Long Run Progression for Half Ironman 2026: 12-Week Build to a Strong 21K
Plan a half-Ironman long-run build around recent training, brick sessions, course terrain and recovery, with options to shorten or hold load.
By Lotte
A half-Ironman long-run build should start from recent consistent running and fit around the rest of training. A calendar is only an example; repeat, shorten or change sessions when health and recovery call for it.
Key takeaways
- 1Recent running history matters more than a universal 12-week table or percentage rule.
- 2Brick runs are optional and add to total training load.
- 3Do not cram a missed run or continue through worsening pain or illness.
In this article
- 1Why the half-Ironman run is uniquely hard
- 2The 12-week long-run progression
- 3Adding the brick run
- 4Pacing zones for the long run
- 5Race-week taper for the run
- 6How to prevent injury during the build
- 7Race-day pacing for the half-marathon leg
- 8Use the long run to build durable, repeatable running
- 9Treat a 12-week progression as an example, not a prescription
- 10Add brick running without turning every long run into a race simulation
- 11Pace long runs by effort and terrain
- 12Choose recovery before adding more running
- 13Taper the run while keeping the race routine familiar
- 14Adjust the long run using recent training, not a calendar alone
- 15Practice the terrain and time-on-feet that match your event
- 16Recognize when the planned long run should be shortened
- ⚖Adjust a long run using recovery and training response
- ?Frequently asked questions
Why the half-Ironman run is uniquely hard
A standalone half-marathon starts on fresh legs. The 70.3 half-marathon starts after a 90 km bike ride, low glycogen, dehydration risk, and 3+ hours of accumulated fatigue. Your fastest standalone time means little on race day.
The goal of long-run training isn't running a fast 21K — it's teaching your body to run efficiently on tired legs. Peak long runs of 18–20 km build the durability you need, without the injury risk of chasing full-distance every week.
The 12-week long-run progression
A 12-week calendar is an example, not a safe progression for every athlete. The starting duration and changes depend on recent consistent running, injury history, other training, health and recovery. Repeat, shorten or skip a planned increase when needed. Do not apply a universal weekly percentage rule. If there is too little time to build comfortably, choose a later or shorter event rather than forcing distance.
Adding the brick run
A brick run is an optional way to practise the transition from cycling to running, not a session every athlete needs weekly. Begin with a short, easy effort after a familiar ride and increase only if recovery remains good. A brick adds load to an already substantial day; it does not replace all standalone running or justify running through pain. Coordinate the session with the wider plan and use a coach when unsure.
Pacing zones for the long run
The long run is a Zone 2 session — always. It builds mitochondrial density, capillary networks, and fat oxidation without the recovery cost of high-intensity work.
Zone 2 landmarks:
- You can hold a full sentence conversation
- Nose breathing possible for at least 30 seconds
- HR = 65–75% of max HR
- Pace = 45–75 sec/km slower than your standalone 10K PR
If your Zone 2 pace feels embarrassingly slow, you're doing it right. See heart rate vs power zones for zone-setting.
Race-week taper for the run
Cut long-run volume by 40% at day -10 and by 60% at day -5.
Race week schedule:
- Day -7: 90 min easy long run
- Day -5: 40 min with 4×1 min at race pace
- Day -3: 30 min easy
- Day -1: 15 min shake-out or rest
- Race day: run the plan
Overdoing the last long run is the classic mistake that leaves 2–3 minutes on the finish line. See race-week taper for the full protocol.
How to prevent injury during the build
The #1 cause of missed 70.3 races is a stress reaction, IT band syndrome, or Achilles tendinopathy in weeks 7–10. Prevention:
- Rotate 2–3 pairs of run shoes
- Add 2× weekly strength (squats, single-leg RDLs, calf raises)
- Never increase run mileage the same week you increase bike mileage
- Recovery week every 4th week — non-negotiable
- Sleep 8+ hours during peak weeks
If a pain persists 2+ runs at the same location, cut volume by 50% and reassess.
Race-day pacing for the half-marathon leg
Split the 21.1 km into 3 sections:
km 0–7: Hold back. Target race pace + 10–15 sec/km. Legs feel dead — this is normal. km 7–14: Settle into goal race pace. Fuel every 25–30 min. km 14–21: Push. If you feel strong, gradually build pace. If you're hurting, defend pace.
Most first-timers blow up in km 12–15 by going out too fast in km 1–4. See pacing strategy by distance for detailed race-day math.
Use the long run to build durable, repeatable running
The long run for a half-distance triathlon is one part of a three-sport week, not a test of whether you can cover the half-marathon distance in training. It can develop comfort with sustained running, but its value depends on the athlete’s current running history, other sessions, recovery, terrain and injury risk. A beginner returning from time off needs a different progression from a consistent runner who already completes regular long sessions.
Begin by recording the run you can complete comfortably now, how many days you currently run, how you recover over the next day or two, and whether any pain persists. Use easy effort for most of the long session unless a qualified plan specifies otherwise. Include warm-up and cool-down in the duration, and choose a route where you can shorten the session or get help if needed.
The goal is a routine that can be repeated across weeks, not one dramatic peak. Cycling and swimming add training stress too, and a brick workout may make the same run duration feel harder. Leave enough recovery to maintain the rest of your program. Persistent pain, altered gait, swelling, unusual fatigue or repeated injury should prompt a pause and qualified assessment rather than a more ambitious long-run target.
Treat a 12-week progression as an example, not a prescription
There is no universally safe 12-week long-run table for every half-Ironman athlete. The plan below describes decisions an athlete could make with a coach; it does not assign mileage. Start only if your current training supports it, and adjust or stop if recovery is poor. A beginner may need more than 12 weeks or a run-walk approach, while an experienced runner may maintain a stable long run and focus on other triathlon needs.
| Phase | Training question | Possible decision |
|---|---|---|
| Early weeks | Can I run consistently without symptoms? | Keep duration stable while frequency and easy effort become routine |
| Middle weeks | Is recovery keeping pace with the whole program? | Extend one selected easy run modestly only when recent sessions are well tolerated |
| Race-specific weeks | What course or fueling question needs rehearsal? | Add a controlled brick or terrain-specific session, not several new stresses at once |
| Final weeks | How can fatigue fall while routine stays familiar? | Follow the event taper in your plan; avoid a last-minute long-run test |
A lighter week may be appropriate when fatigue, schedule or accumulated training warrants it, but fixed build-to-recovery ratios are not mandatory. Do not compress missed training into later weeks. A coach can individualize the progression using your history and the event calendar.
Add brick running without turning every long run into a race simulation
Brick runs help you experience running after cycling, but they are not a replacement for all standalone running. A short, easy run after a bike can help practise the transition and reveal whether the bike effort, fueling or equipment needs attention. It should not automatically become a fast run simply because the legs feel unusual.
Choose the session purpose first. If the aim is transition familiarity, keep the run brief and comfortable. If the aim is long-run endurance, protect the run’s duration and recovery rather than adding it after a hard bike. If you are testing nutrition, change only one part of the plan and note the conditions. Running tired can alter mechanics and perceived effort, so do not add a large brick load when you are new to either sport.
Place the brick where it does not compromise the next key session. An athlete who is sore for multiple days may need less running stress, a different bike intensity or more recovery. Stop if pain changes your stride or becomes sharp. Return to the broader brick-workout guide for session design and use this page for long-run planning, not as a demand to simulate the entire race weekly.
Pace long runs by effort and terrain
A long run should generally feel controlled enough that the athlete could continue for a little longer at the end, unless a specific qualified plan has a different purpose. Talk-test, breathing and perceived effort can help when heart rate or pace is noisy. Heat, hills, surfaces, fatigue and wind all change the same pace number. Slow down on a climb or hot day instead of trying to preserve a flat-route target.
Heart-rate zones can provide context if they are based on a suitable assessment, but the number can drift during a long session and varies by conditions. A watch estimate or age-based maximum-heart-rate formula is not a diagnosis or precise training boundary. RPE can complement it. Keep the purpose of the session clear and stop trying to hold a zone if you develop symptoms that call for rest or care.
Walk breaks can be a deliberate pacing choice, especially for newer runners, hot conditions or long-course preparation. They do not make the session a failure. Practise the pattern you may use in the race so aid stations, hills and fueling are familiar. A consistent planned run-walk approach can be more useful than an early pace that cannot be sustained.
Choose recovery before adding more running
Running load includes more than the long-run distance. Count hard intervals, hills, brick runs, strength work and time on your feet at work alongside the long session. If several of these rise together, the total stress can increase even if the weekly long run changes very little. Make one training change at a time and watch how you respond across multiple days.
Sleep, food, hydration and a realistic weekly schedule support recovery, but they do not guarantee injury prevention. Avoid underfueling a demanding training block, and do not use weight loss as a substitute for appropriate training progression. If fatigue persists, performance drops repeatedly or injuries recur, consult a sports clinician or qualified coach; generalized online progressions cannot identify the cause.
Plan for common disruptions. If illness, travel or family responsibilities interrupt a week, do not “make up” the missing long run by doubling duration. Resume from a level that matches your recent training and how you feel. If you had a significant injury or medical interruption, seek appropriate guidance before returning to longer running.
Taper the run while keeping the race routine familiar
A taper reduces training fatigue before the event; it does not create fitness in the final days. The amount and timing of the reduction depend on the full plan, race distance, training history and coach’s intent. Keep short, familiar movement if that is part of your taper, but avoid a new long run, hard test or shoe change close to race day.
Use the final weeks to rehearse practical questions: how the shoes feel after the bike, whether socks are comfortable, where race nutrition is carried and how you will handle a warm or windy run. Keep the long-run route safe and do not chase a missed training goal. If an injury or concerning illness appears, reassess the event with qualified support instead of treating the taper as a deadline to prove readiness.
On race day, start the run at an effort that fits the bike you actually completed, not the bike you planned. Check the official cutoff and aid-station options. For a broader event plan, review pacing strategy, race fueling and the half-distance overview.
Adjust the long run using recent training, not a calendar alone
A long-run build is only sensible in the context of the athlete’s recent running. Someone who has been running consistently may tolerate a different starting point from someone returning after illness, injury, pregnancy, a long break or very little weekly volume. The calendar cannot account for these differences. Before adding distance, look at how many weeks of regular running have been completed, whether easy runs feel controlled, and whether the athlete is recovering between sessions.
Use a simple log that records duration or distance, effort, route, conditions, discomfort and next-day response. One unusually good run does not establish readiness to add a large amount. Likewise, a slow run in heat does not necessarily signal lost fitness. Consider the whole week: swim and bike training also add fatigue, and a brick session can change how the run feels. If sleep, work stress or health changes, adjust the plan rather than treating the long run as a fixed weekly obligation.
A progression should contain options to hold or reduce load. For example, an athlete might repeat a familiar duration for another week after a tiring race or poor recovery rather than automatically advancing. The exact change should reflect training history and, where relevant, advice from a coach or clinician. Do not apply a universal percentage increase or fixed recovery week rule to every runner. Sudden changes in training, pain that worsens as you run, limping or symptoms that persist after stopping warrant reassessment.
The half-distance race run is not a reason to force a long-run distance that exceeds current preparation. A shorter consistent run, alongside appropriate bike and swim work, may be safer than sporadic very long outings. If the athlete cannot build comfortably within the available weeks, consider a later race or a shorter event. The aim is to arrive healthy enough to use training, not to complete a particular spreadsheet at any cost.
Practice the terrain and time-on-feet that match your event
Distance is only one part of long-run preparation. A rolling trail, hot road course, crowded path and flat paved loop create different demands. Choose routes that support safe running and resemble relevant parts of the race when practical. If the event has a long exposed section, learn how sun and heat affect comfort. If it includes hills, practise controlled effort uphill and relaxed downhill movement rather than chasing the same pace on every grade.
Time-on-feet can be a useful description when terrain or run-walk strategy makes distance misleading, but it is not a license to extend a session indefinitely. Long sessions need accessible water and a way to stop or return safely. Tell someone the route and expected finish, carry identification and a phone where appropriate, and adapt for weather and daylight. Follow local rules on shared paths and do not run through lightning, dangerous heat, ice or other conditions that make the route unsuitable.
Practise the equipment and any fueling approach that is appropriate for the planned duration. A long run is a chance to check shoes, socks, clothing, pocket bounce, chafing and how the athlete responds to food or drink. Do not make a long run the first test of a new shoe, supplement or high-intake plan. Athletes with medical conditions, a history of low energy availability, pregnancy, or recurring gastrointestinal symptoms should build the plan with qualified professional support.
Recovery matters after the session. Eat and drink in a way that fits your needs, get adequate rest and notice whether ordinary movement returns comfortably. If pain or unusual fatigue persists, do not add another hard workout simply because the schedule says so. A good progression includes decisions about when not to extend the run. For brick-specific preparation, use the brick workout guide and coordinate the run with your half-distance training plan.
Recognize when the planned long run should be shortened
A planned run can be changed when the athlete’s condition or environment makes the original session a poor choice. Fever, chest symptoms, acute illness, significant pain, limping, dizziness, unusual breathlessness, dangerous heat or unsafe footing are reasons to stop or seek qualified guidance. The calendar is not medical clearance. If symptoms are severe or worsening, obtain appropriate clinical help.
For ordinary fatigue, first decide what the session is meant to develop. If the purpose is easy aerobic time, a shorter relaxed outing may preserve the intent with less strain. If the athlete is carrying soreness from a hard brick, moving the long run or replacing it with rest may be better. Do not turn a reduced session into a faster run to compensate for fewer minutes.
Record why the run changed and what happens over the next day or two. If a minor discomfort eases as you warm up but returns later, that still deserves attention; pain response is not a simple pass/fail test. Recurring pain or a change in gait should be assessed by a qualified clinician or physiotherapist before adding volume. A coach can help modify training but should not diagnose an injury.
Missing one long run does not require adding its distance to the next outing. Resume from the athlete’s recent consistent training and allow recovery. If the event timeline no longer permits safe preparation, select a later race or a shorter distance. Flexibility protects the larger goal of arriving healthy enough to participate.
Adjust a long run using recovery and training response
| What you notice | Practical response | Reason to reassess |
|---|---|---|
| Easy effort and normal recovery between runs | Hold the current long-run load or make only a small planned change | Progress depends on the whole week, training history, and event timeline |
| Fatigue lasts longer than usual or easy pace feels unusually hard | Repeat a familiar load or shorten the session; protect recovery | Persistent fatigue can signal accumulated stress or another issue |
| Pain changes your stride or worsens as you run | Stop the session and seek suitable clinical guidance if needed | Do not progress through pain that affects normal movement |
| Race is near | Follow the taper in the athlete’s wider plan rather than adding a final long run | Late workload cannot reliably make up for missed preparation |
Sources
Sources are listed so readers can verify consequential claims and dated details.
- Training load and injury risk consensus — IOC consensus (accessed September 24, 2026)
- Running after cycling systematic review — Peer-reviewed systematic review (accessed September 24, 2026)
- Training intensity distribution meta-analysis — Peer-reviewed meta-analysis (accessed September 24, 2026)
Frequently asked questions
Do I need to run the full half-marathon in training?
There is no universal requirement. Choose long-run duration and distance from training history, recovery, course demands and qualified guidance.
What should I do if I miss a long run?
Do not add the missed distance to the next session. Resume from recent consistent training and allow recovery.