Nobody enters a first Ironman with the same legs they will have at mile 18. The run comes after a 2.4-mile swim and a 112-mile bike, and by then your glycogen and your runnable posture are both under attack. A beginner who tries to run the marathon like a standalone road race usually gets a brutal lesson around mile 16. The latest long-course coaching does not try to make the run fast. It tries to make the run finishable without turning it into a survival march.

That distinction is the whole answer to where you put your energy.

Learn the Cutoff Math First

Ironman races close the full course at 17 hours from the official start, and the run course is part of that global cutoff. If you leave the bike in seven hours, you still have ten hours on the clock, but your body is already deep into a very long day. The marathon becomes less about pace and more about managing the remaining budget.

Finishing the marathon in six hours means averaging 13:44 per mile. That number matters because it includes aid-station walks, a toilet stop, and a stretch at mile 20. The goal for most first-timers should be to stay runnable in the final 10K, not to run a particular split in the first 10K.

The Run-Walk Method Has Become the Default Starting Point

Coaches used to present walking as a failure mode. Now it is one of the first pacing tools a beginner should learn. A common approach is to run four minutes and walk 30 seconds from the first aid station, or simply walk 30 to 60 seconds at every aid station no matter how good you feel. The value is not the walk. It is that the pattern protects your stomach and your stride before the damage piles up.

80/20 Endurance describes run-walk as a pacing strategy rather than a concession. For Ironman first-timers that framing is now standard. Start the intervals in the first mile. A forced walk later costs far more emotionally and physically.

Spend Training Energy on the Bike-Run Connection

A beginner's missing link is rarely the long run. It is the ability to run after three to six hours of riding. A brick workout, a bike session immediately followed by a short run, teaches your legs to switch from cycling's short hip extension to running's longer ground contact. You do not need long brick runs. Twenty to forty minutes after a hard bike is enough, and it is more specific than a separate marathon-length run.

Your long run should still build gradually, but it should not copy a standalone marathon program. Two and a half hours is a sensible cap for most first-timers. Beyond that the recovery cost eats into the bike and swim volume that also have to happen that week.

Put Race-Day Energy Where the Race Actually Happens

The first 10K of the Ironman run should feel almost too easy. The bike finish leaves most athletes with heavy quads, and the opening miles are where you reboot your rhythm and settle your heart rate while you take in water. If you track pace, the opening six miles probably need to be 60 to 90 seconds per mile slower than your open marathon pace, and even slower on an exposed or hilly course.

From roughly mile 6 to mile 16, the job is to hold effort steady and protect your gut. That means salt and small portions of plain food. Flat cola helps if your stomach has turned sour. After mile 16, the race becomes a decision-making contest: can you keep the math simple, accept walking when the running form breaks, and keep moving forward? The energy you saved in the first half is spent here, and it is the only reason the finish line remains a plan rather than a panic.

A Training Snapshot That Fits a Working Beginner

The schedule below is not a complete plan. It is the shape of a week that puts energy into the two places that matter most for a first Ironman: the bike-to-run transition and a long aerobic base.

• Two to three runs per week, one long run building from 70 minutes to 2.5 hours over 16 weeks
• One brick session on the weekend, with a 40-minute run immediately after a long or hard bike
• A weekly swim that you do not skip, because swim fitness tends to show up as relaxed shoulders on the bike, not as heavy legs
• A weekday run of 3 x 8 minutes at a comfortably hard effort, with full recovery between repeats

This is the current centre of gravity in long-course coaching: less junk volume and more specific fatigue, with shorter sessions that keep a working athlete healthy. That trend has grown as more age-group athletes arrive at Ironman from marathons or sprint triathlons and need to convert existing fitness rather than start from zero.

Nutrition Is Energy Management, Not a Sidebar

No pacing plan survives a missed calorie target. The gut is the first thing to fail in iron-distance racing, and the run is where that failure becomes visible. A beginner should rehearse fueling in every long brick. You want to know how many grams of carbohydrate per hour you can absorb while running after a hard bike, not just while cycling.

Keep the run menu simple: cold water, electrolyte mix, a gel every 30 to 40 minutes, and flat cola late in the day. The exact amount is personal, so test it before race week. A fuel plan that works at mile 3 and wrecks you at mile 15 is not a fuel plan.

Aid Stations Are Your Pacing Clock

Use every aid station as a forced reset. Walk in, drink, walk 20 steps, then resume running. This shifts control away from panic and gives your stomach a predictable rhythm. It also means you never have to make a grand decision to walk at mile 18. The walk has been part of the plan since mile 2.

Beginners who adopt a fixed run-walk rhythm from the first aid station are less likely to describe the final 10K as a collapse. They describe it as hard but legible. Put your energy into a slow first 10K and a boringly consistent middle. The fuel plan you rehearsed in training is non-negotiable.

TrainingPeaks has a pacing library if you want to build your own race plan.

Photo by Mario La Pergola on Unsplash