Training for an Ironman rewrites the rulebook for your run. The event starts with a 2.4-mile swim. Then comes a 112-mile bike. The day finishes with a 26.2-mile marathon, and that final leg does not begin on fresh legs.
The point of Ironman run training is not to build a standalone marathon. It is to prepare for running long after hours of swimming and riding. Age group athletes often find that their open marathon habits have to change.
The run leg is not a standalone marathon
A typical open marathon plan builds toward 18- to 22-mile long runs and four or five runs a week. An Ironman plan has to fit runs around swimming, cycling, strength work, and recovery. That usually leaves room for three run sessions, or four if you're a stronger runner with a flexible schedule. The long run is often capped by time rather than distance.
Running beyond roughly 2:45 to 3:00 in training adds fatigue without much aerobic return for most age groupers. The bike leg supplies a big chunk of the endurance base. What the run needs is race-specific teaching. You have to run controlled on tired legs. You also need to manage heat and keep fuelling steady enough that the last 10km feel possible.
Ironman's own training guidance points toward race-specific preparation rather than piling up standalone marathon mileage.
Rethink the long run
The long run in an Ironman build often sits between 2:00 and 2:45. Some high-mileage athletes with a history of run volume may run longer once or twice, but the weekly cap stays in that range for the rest.
Use time, not distance, to set the limit. A 2:30 long run that ends with 20 to 30 minutes at goal Ironman effort is more specific than 20 easy miles. The first 70 percent of that run should feel conversational. Then you finish with a race-effort block to teach your legs to change gears.
Long-run priorities for Ironman training look like this:
- Keep the first half easier than your intended Ironman run pace.
- Practise taking in fuel at the same hourly rate you plan to use on race day.
- Run on varied terrain so your stride can adapt after the bike.
- Finish with 20 minutes at controlled race effort, not at threshold.
That structure builds the time on feet you need without wiping out the following week of swim and bike work. You can find structured Ironman run plans through TrainingPeaks.
Brick workouts teach the real skill
A brick is a bike-to-run session. The first 10 minutes of an Ironman run usually feel wooden. Your hip flexors are shortened from the aero position, and your stride turnover drops. Your legs have to find a rhythm after five or more hours of riding. The only way to learn that feeling is to practise it.
Short bricks are more useful than monster long bricks. A 90-minute ride followed by a 20-minute run is a good place to start. Keep the first five minutes easy. Then settle into your Ironman run pace and hold it without looking at the watch too much.
A simple brick progression over a month might go like this:
- Week 1: 60-minute bike, 15-minute run off the bike.
- Week 2: 75-minute bike, 20-minute run with the last 10 minutes at goal pace.
- Week 3: 90-minute bike, 25-minute run off the bike, first five easy.
- Week 4: 2-hour bike, 30-minute run with 2 x 8 minutes at goal Ironman effort.
Change shoes fast and keep the transition simple. You are rehearsing the feeling more than chasing a specific pace.
A sample Ironman run week
This is a week from the middle of the build, not a recovery week. The volume assumes you have been training consistently for four or five months.
| Day | Run focus | Note |
|---|---|---|
| Monday | Easy run 45–60 minutes | Keep it conversational, last 10 min brisk. |
| Tuesday | Brick 20–30 min off a 90-min bike | Settle into goal Ironman pace after 5 min. |
| Wednesday | No run | Swim and bike only. |
| Thursday | Tempo intervals 3 x 12 min at threshold | Jog 4 min recoveries. |
| Friday | Easy run 30–40 min or short brick | Use as a shakeout. |
| Saturday | Long bike 4–5 hrs, short run 15–20 min off | Practise race fuelling. |
| Sunday | Long run 2:00–2:30 | Last 20 min at goal effort. |
Pace by effort, not by watch
After five or six hours of racing, GPS pace can lie. Heat, fuelling, bike position, and cumulative fatigue change how hard a given pace feels. A better anchor is rating of perceived exertion, usually on a 10-point scale. The first 20 miles of the Ironman marathon should sit around a 4 to 5, which feels controlled and conversational.
That is slower than most age groupers want to run. Starting the marathon too fast is one of the most common failures. You can burn through your glycogen in the first 10km and then walk the last 10. Reserving effort early lets you run more of the back half.
Use heart rate zones as a backup, not as a strict governor. If your training zones are right, the Ironman run typically falls in the upper part of zone 2 or the low end of zone 3. Heat and caffeine can push heart rate higher than usual, so RPE should win when the two disagree.
Race-day run strategy
Start the run at a deliberately slow pace. A good opening 5km is 10 to 15 seconds per kilometre slower than your goal pace. Walk 15 to 30 seconds through each aid station from the very first one. That buys time to drink, pour water over your head, reset your posture, and settle your stomach.
Sodium matters just as much as water. Take a steady intake of electrolytes, around 500 to 700 milligrams per hour, adjusted for heat and your sweat rate. That range is common in triathlon fuelling plans, but it should be tested in training first.
The race-day run often rewards a negative split. Keep the first 16 miles controlled and steady. Then use the last 10km to move, but only if your stomach and legs allow it. The finish line is a long way from transition, and the decisions you make in the first 3 miles determine what you can do in the last 3.
Photo by Mario La Pergola on Unsplash
