Most athletes approach race fueling by asking one question: How many grams of carbohydrate per hour should I take? They get an answer — maybe from a coach, maybe from a nutrition brand, maybe from a forum thread — and they build their plan around that number. Sixty grams an hour. Ninety. Whatever the figure is, it becomes the plan.

Here's the problem with that. A grams-per-hour target is a tool. It's not a plan. And it's not the right place to start.

The right place to start is the full picture: what you have on board when the gun goes off, what the race is going to cost you by segment, what you can realistically take in while swimming, biking, and running — and whether those numbers add up to a needle that stays above danger. That's inventory management. That's how a real fueling plan gets built.

The Balance Sheet

Think of your race-day carbohydrate situation exactly like a bank account. You start with a balance. The race makes withdrawals — the swim takes some, the bike takes a lot, the run takes even more. You can make deposits during the race, but only at certain windows and only up to a point. The gut has a ceiling on what it can process. You cannot deposit faster than the body can absorb.

At the end of the day, what matters is whether the account stayed solvent. Not whether you finished with a full tank — nobody does. Whether you avoided hitting the point where performance becomes fragile, intensity becomes unsustainable, and the race shifts from execution to survival.

That point isn't a precise number we can nail down to the gram. But every experienced long-course athlete has been there. The legs go heavy. RPE spikes for no apparent reason. Pace slips. The math on the back half of the run stops working. That's a tank that got too low. The goal is simple: don't let it get there.

Your Starting Assets: The Carb Load

The carb load is not a pre-race ritual. It's not pasta dinner tradition. It's inventory replenishment — the act of filling the tank before you leave the garage. Everything downstream of this decision depends on it.

A well-executed carb load gives the average athlete somewhere in the range of 400–500 grams of stored glycogen, depending on body size. Smaller athletes start with less. Larger athletes start with more. As a rough working estimate: a well-loaded athlete carries approximately 7–8 grams of glycogen per kilogram of body weight. A 55 kg (~120 lb) athlete starts with around 400–440 grams. A 73 kg (~160 lb) athlete starts with closer to 510–580 grams.

Underload — skip the protocol, eat light in the days before, show up to the start line on half a tank — and you've created a deficit before the race starts. There's no on-course fueling strategy that compensates for it. The math doesn't allow it.

The Race Cost: Swim, Bike, Run

Every segment draws down the account. How much each one costs depends on your body size, how long the segment takes, how hard you're working, what the terrain is like, and whether it's hot. A bigger athlete burns more. A harder effort burns more. A hilly or hot course burns more — heat in particular drives carbohydrate use higher than most athletes expect, because the body shifts away from fat as a fuel when it's managing thermal stress alongside physical load.

There's no universal number here. But there are useful ranges based on real athlete data, and the pattern matters more than any specific figure:

The swim is the smallest withdrawal — but it happens before you can make any deposits. You exit the water already in a hole relative to where you started. The gel you take 15 minutes before the gun is your only pre-swim deposit. That's it.

The bike is where the bulk of the cost lands. On a full IRONMAN, the bike segment alone accounts for the majority of total carbohydrate expenditure — sometimes more than half the day's total burn. It's also the segment where you have the most realistic opportunity to take in meaningful nutrition. That's not a coincidence. It's the window.

The run is the most expensive segment per minute. Running is less mechanically efficient than cycling — the body pays a higher metabolic cost per unit of work — and carbohydrate reliance increases. At the same time, the run is the hardest place to take in nutrition effectively. Gut motility slows. The jostling of running makes some athletes feel sick. Most people can tolerate less on the run than on the bike, and many tolerate significantly less. Plan for that reality. Don't build a fueling plan that requires the same intake rate on the run as on the bike. It may not happen.

The Deposit Windows

You have five realistic opportunities to add carbohydrate during a triathlon. Most athletes think about two of them.

Pre-race. The gel 15 minutes before the start. Small, but it matters — it tops off blood glucose right before the first withdrawal begins.

T1. Often overlooked completely. You're moving, but you're not swimming and you're not yet riding. A gel in T1 takes ten seconds. It's a deposit that costs nothing in effort. Use it.

The bike. This is your primary fueling window. You're in an aerodynamic position, effort is sustained but not chaotic, and the gut generally tolerates nutrition well at cycling intensities. This is where the account gets replenished — or doesn't. Most of the work of staying solvent happens here.

T2. Same principle as T1. Another small deposit opportunity that most athletes ignore. A gel going into the run changes the math on the first few miles. Take it.

The run. You can still deposit here, but capacity is limited. Plan for 45–65 grams per hour as a realistic target for most athletes — some can do more, some considerably less. The point is: if your fueling plan requires the run to carry a heavy load, you've already built a plan that depends on things going perfectly. They often don't.

Why the Bike Plan Has to Be Built Backward

Here's where most fueling plans fail. Athletes set a bike target in isolation — "I'll aim for 70 grams an hour on the bike" — without accounting for what the run can realistically deliver and what the overall balance sheet requires.

The right way to build the plan runs in reverse. Start with what the full race demands. Subtract your starting inventory. Subtract what you can reasonably expect to take in during the run. Subtract T1 and T2. What's left is what the bike has to provide.

Sometimes that number is higher than an athlete expects — particularly for smaller athletes on long, difficult courses. That's important information. It means the bike fueling target isn't arbitrary. It's derived. The bike isn't just fueling the bike. It's protecting the run.

Working It Backward: One Athlete, One Race

Here's where this stops being theoretical. A competitive 160-pound male athlete racing an IRONMAN 70.3. A race distance where the math is more forgiving than a full IRONMAN — but still unforgiving enough to bite athletes who don't take it seriously.

We know his expected carbohydrate cost from real data: roughly 105 grams in the swim, 493 grams on the bike, and 354 grams on the run. Total race cost: approximately 952 grams.

A well-loaded athlete of his size starts with somewhere in the neighborhood of 545 grams on board. That leaves a deficit of roughly 407 grams that has to come from what he takes in during the race.

Now here's where the choice part comes in — because that's exactly what it is. Every deposit window in this race is a decision the athlete makes. Nobody forces a gel at T1. Nobody makes him eat on the run when his stomach is protesting. These are choices. And the math shows exactly what each choice is worth.

Plan for the Hard Version. Be Grateful When It's Not.

One more thing worth understanding about that 493-gram bike cost. That's the expected number — what the math projects based on his size, his effort level, and the course. The actual number in the race came in around 365 grams. Easier conditions, a little less output than anticipated, a race that gave back some watts.

That's a surplus of roughly 128 grams he didn't have to replace. The needle ended up higher than planned. That's a good problem. A reserve that made the run easier. A body that had more to work with in the final miles.

Now flip it. Build the plan around 365 grams and have the race come in at 493. You're 128 grams in the hole with no way to recover it. The bike is over. The run is already compromised before it starts.

This is asymmetric risk. Plan for the expensive version of the race. If the race is generous — better weather, better pacing, a day where the effort just didn't cost as much — that surplus stays in the tank and works for you. You don't need to do anything with it. Plan for the hard version. Be grateful when it's not.

Keep the Needle Above the Danger Zone

107 grams per hour on the bike keeps this athlete technically solvent — just above empty at T2 if everything goes to plan. But solvent isn't the goal. The goal is to arrive at T2 with something still in reserve. Enough that when the run gets hard — and it will get hard — there's still fuel in the system to respond.

We're not trying to finish with a full tank. That's not possible. What we're trying to avoid is the point where the tank gets so low that the body starts making hard tradeoffs. Pace drops. RPE spikes. The legs go heavy for no apparent fitness reason. Every athlete who has ever been there knows exactly what that feels like. It's not a fitness problem. The fitness is fine. The tank just got too low.

Think of it as a quarter-tank reserve. Not a precise threshold — you can't measure it on the road, and it varies from athlete to athlete. But a useful mental target: never let the gauge drift into the red. Keep enough in the system that when the race asks something difficult of you in the final miles, you still have something to give.

For our 70.3 athlete, keeping the needle above that reserve means pushing the bike target above the bare minimum — not wildly, but meaningfully. Closer to 80–90 grams per hour rather than the floor of just-above-zero. The difference is a few extra gels. A few extra choices made in those deposit windows. A run that gets to be a race instead of a march.

What To Do With This

The sequence isn't complicated. It just has to happen before race morning.

1. Start with a full tank. Execute the carb load. Not a rough approximation of it — actually do it. Everything downstream depends on the starting balance.

2. Estimate your race cost by segment. Work from the ranges in this article as a starting point. A reasonable estimate is all you need. The exact number matters less than having a number to build from.

3. Set your run intake conservatively. Be honest about what your gut can actually handle while running under race stress. If you've had trouble taking in nutrition on long runs in training, don't build a plan that requires perfect run fueling. Plan for the realistic version.

4. Count your T1 and T2 deposits. These are choices. Make them consciously, not casually. Each one reduces the load on the bike and the run. They cost nothing in effort and take seconds to execute.

5. Work backward to the bike target. Total deficit minus T1, T2, and run intake. What's left is what the bike has to provide. That's your number — derived from your race, not borrowed from someone else's plan.

6. Build in a buffer above the floor. The minimum bike target keeps you barely solvent. The real target keeps you above the quarter-tank reserve. Push above the floor. Aim to arrive at T2 with something left, not just enough to technically survive the run.

7. Plan for the expensive version of the race. Use expected conditions, not optimistic ones. If the race comes in easier than projected, the surplus is a gift. If it comes in harder, you were ready for it.

8. Train the gut. The gut is adaptable. Higher intake rates become tolerable with consistent practice in training. If your bike target feels aggressive, train it. The race is not the place to find out your gut can't handle it.