Half-Ironman Nutrition Plan - Fuel Your 70.3 Success

A strong half-Ironman nutrition plan is less about chasing perfect numbers and more about keeping energy, hydration, and stomach comfort stable for the full 70.3 distance. The bike and run punish small mistakes, so the real job is to arrive topped up, fuel early, and keep the intake steady enough that you never fall into damage-control mode. That is what this article covers: race-week carbs, race-morning food, hourly fueling targets, hydration, sodium, gut training, and the mistakes that usually cost time on race day.

What this plan has to solve on race day

The main challenge in a half Ironman is not simply “getting enough calories.” It is managing glycogen depletion, dehydration, and GI distress at the same time while riding and running at a pace that feels uncomfortable but sustainable. If you underfuel, the late-race fade shows up quickly: heavy legs, poor concentration, and a pace drop that feels bigger than the effort should justify.

If you overfuel, the problem changes shape. Too much concentration, too much fiber, or too many new products can leave you bloated, sloshy, or stuck making bad decisions at aid stations. The best race plans are boring on purpose: familiar foods, simple timing, and a dose you can repeat without thinking. Once that problem is clear, the next step is choosing the actual numbers to start with.

The targets I would start with

Here is the framework I use when I build a 70.3 fueling plan. I would not treat it as a rigid prescription, but it is a strong starting point for most age-group athletes. IRONMAN’s current guidance starts around 60-70 g of carbs, 400-600 mg sodium, and 24-28 oz of fluid per hour, with lower starting points for athletes who are new to race fueling or have a sensitive stomach.

I usually tell athletes to earn the right to push the top end. A Triathlete breakdown points to 60-90+ g of carbs per hour, especially on the bike, but that range only works well when the athlete has practiced it, tolerates the product blend, and knows what the stomach does at race intensity. If that is not you yet, a clean 60-70 g/hour plan is often the better choice. From here, the next question is how to eat in the 48 hours before the gun goes off.

Race week and race morning are about topping off glycogen

In the last two days before the race, I want carbs to become the dominant fuel source, but I do not want the menu to become chaotic. That means more rice, potatoes, pasta, bread, fruit, cereal, and sports drinks, with lower fiber and lower fat than usual. The goal is to fill the tank without irritating the gut, not to eat a giant, uncomfortable meal the night before.

A practical race-week pattern in the US often looks like this: familiar breakfast foods, a carb-heavy lunch, a simple dinner, and hydration spread through the day instead of saved for the evening. Keep protein moderate, but do not force huge salads, high-fiber granola, or rich restaurant meals into the final 24 hours. I would rather see an athlete slightly under-ambitious on variety and fully confident on digestion.

On race morning, eat 1-4 g of carbohydrate per kg of body weight 1-4 hours before the start, depending on how early the race begins and how nervous your stomach is. For many athletes, that means something like a plain bagel with jam, a banana, and a sports drink; for others, a smaller liquid-heavy breakfast works better when the start time is very early. If you tolerate it and have trained it, a small caffeine dose can fit here too, but I would never introduce it for the first time on race day. Once the start is close, the focus shifts from loading to executing.

The bike is your main fueling window

The bike is where I want most athletes to do the heavy lifting. Heart rate is usually lower than on the run, breathing is steadier, and swallowing is easier, so carb absorption is more reliable. That is why the bike should carry the bulk of the calories, not the last 20 minutes of the run when your stomach is bouncing and decision-making is worse.

My default is to start fueling within the first 15-20 minutes of the bike, then repeat small doses every 10-15 minutes rather than waiting for hunger or energy to dip. Small, frequent intake is easier to absorb than big rescue doses. If you are using drink mix, gels, and chews together, the point is not variety for its own sake; it is making sure the total hourly carb count lands where it should without overloading any single product.

1. Keep the first hour simple. Use the products your gut already knows and avoid “special” foods just because you feel fresh.
2. Build around your bottle math. If one bottle gives you half an hour of fuel, know exactly what replaces it.
3. Use solid or semi-solid food early only if it is trained. That usually means the middle of the bike, not the final hour.
4. Save the last 60-90 minutes for the easiest products. Sports drink and gels are usually safer than bars when fatigue rises.
5. Match concentration to conditions. Hot days and high sweat loss usually reward slightly more dilution and more sodium.

A good race-day bike hour might be 1 bottle of carb mix, 1 gel, and a few sips of water, repeated on a schedule rather than guessed in the moment. If you have ever missed fuel because a course got crowded or a climb felt harder than expected, you already know why this needs to be automatic. The next challenge is simplifying that same logic for the run.

The run plan should be simpler, not fancier

On the run, intensity goes up, the gut gets less cooperative, and the margin for error gets smaller. I usually lower the complexity here rather than trying to force the same bike strategy onto a moving target. For many athletes, 30-60 g of carbs per hour is a realistic run target, mostly from gels, chews, or sports drink. Some athletes can tolerate more, but I would rather see a steady 40 g/hour executed well than a fragile 80 g/hour plan that falls apart at mile 4.

The run is also where aid stations matter. I want athletes to know in advance whether they will take water at every station, sports drink at selected stations, or both. If the stomach feels full, I reduce the carb concentration and keep the fluid small but frequent. If the stomach feels empty and energy is fading, I do the opposite and tighten the timing. In both cases, the rule is the same: never wait for a crisis before you eat or drink.

During the run, I like a short decision tree. If the pace is steady and the stomach is calm, take a gel on schedule and follow it with water. If the stomach feels sloshy, skip the extra solids and stick to smaller sips. If energy drops suddenly, it is usually a timing problem first, not a willpower problem. That is why you need to train the gut long before race week.

Heat, sweat rate, and gut tolerance change the math

No two athletes lose fluid, sodium, or carbohydrate in exactly the same way. That is why a generic one-size-fits-all plan breaks down fast in hot weather or humid conditions common in parts of the United States. If you sweat heavily, need salt on your kit after long sessions, or finish training with a large body-weight drop, your hydration plan should probably be more aggressive than the average athlete’s.

The easiest way to personalize this is to test yourself in training. Weigh in before and after a long brick session, record what you drank, and notice how your stomach responded. If the session was hot and you ended up light-headed, cramping, or unusually thirsty, you likely need more fluid and sodium next time. If your stomach sloshed and you felt bloated, the opposite is probably true: the concentration was too high or the fluid volume came too fast.

• High sweat rate: increase fluid gradually in training and use sodium deliberately instead of guessing.
• Sensitive gut: reduce concentration, lower the size of each serving, and build volume over several weeks.
• Cold race day: you may need less fluid than your summer training numbers suggest, even if the carb target stays similar.
• Hot race day: keep the sodium and fluid plan more conservative than a cool-weather setup only if your training proves you can tolerate that change.

The point is not to force your body into a number from a chart. It is to know which parts of the chart fit you and which parts need adjustment. That brings us to the mistakes I see most often, because most bad race nutrition is surprisingly predictable.

The mistakes that ruin a good race plan

• Starting too late. If you wait until you feel empty, you are already behind.
• Trying a new product on race week. Novelty is fine in training, not in a 70.3.
• Copying someone else’s carb numbers. A bigger athlete, a hotter course, or a faster bike split changes the math.
• Using too much fiber or fat before the start. These slow digestion when you want the exact opposite.
• Taking in huge doses instead of small, frequent doses. The stomach usually prefers consistency.
• Ignoring the bike-to-run transition. A plan that works on the bike can still fail if you do not simplify it for the run.
• Underestimating sodium in heat. When temperatures rise, fluid alone is not always enough.

The athletes who race best usually do not have magical products. They simply repeat a workable pattern often enough that nothing feels experimental on race day. That is the final piece of the puzzle, and it is the one I would keep on a checklist.

The checklist I would actually use before a 70.3

If I were building a race-week plan from scratch, I would keep it short and controllable. I would choose one bike drink mix, one gel brand, one run backup, and one breakfast I already trust. Then I would rehearse the timing in long training sessions until the sequence felt automatic rather than theoretical.

• Lock in one race-morning breakfast and eat it at least twice in training.
• Practice your bike fueling at the exact hourly target you plan to race.
• Test your run gels at the pace and body temperature you expect on race day.
• Build the final 48 hours around low-fiber carbs and normal hydration, not a last-minute food experiment.
• Set reminders on your bike computer or watch so you do not fuel by mood.
• Pack one backup gel in transition in case a bottle or pouch gets lost.

The best version of a half-Ironman race plan is not flashy. It is specific, repeatable, and calm under stress. If you keep your carbs steady, your fluids disciplined, and your stomach out of trouble, you give yourself a much better shot at running the final 10K with something left in reserve.