70.3 Training Plan: How to Prepare for Your First Half-Ironman

A 70.3 sits at an odd point in the sport. It's twice the distance of an Olympic race, but it's usually finished in well under half the time of a full Ironman, and that combination changes what actually matters in training. Somewhere between roughly five and seven hours of racing, depending on your pace and the course, this becomes the first distance where a fueling strategy stops being a nice-to-have and starts deciding whether your run happens at all. This guide covers a realistic 70.3 build: how many hours a week it actually takes, how the phases fit together, how to progress a long ride and long run without wrecking yourself, why nutrition suddenly matters this much, and the mistakes that show up specifically at 70.3 distance rather than at sprint or Olympic.

What a 70.3 actually asks of you

A half-Ironman covers a 1.9km swim, a 90km bike, and a 21.1km run, roughly double an Olympic-distance race across every leg. Doubling the distance doesn't just double the discomfort; it changes the category of problem you're solving. A sprint or Olympic race is largely a fitness and pacing question you can answer in an hour or two of hard effort. A 70.3 adds a durability question on top: can your body keep processing fuel, keep your form together, and keep your head in the right place for several hours straight. If you've raced shorter distances before, the biggest adjustment isn't going faster. It's learning to hold a pace you can sustain for hours rather than minutes, and building the aerobic and fueling systems that make that possible.

For general planning advice that applies at any distance, from balancing swim, bike, and run to structuring a training week, see the full guide to building a triathlon training plan. If a 70.3 is your very first triathlon rather than a step up from shorter racing, the sprint-distance guide covers the basics this one assumes. What follows here is specific to what changes once your race stretches past the three- or four-hour mark.

Realistic weekly hours for a 70.3 build

Most 70.3 builds land somewhere in the 8-10 hours a week range, consistent with what general hour ranges by distance suggest for this distance. That number isn't flat across the whole plan. Early base weeks typically sit lower, often in the 5-6 hour range while you're establishing aerobic volume without much intensity. Weekly hours climb through build and peak into that 8-10 hour band, sometimes nudging just past it during your heaviest weeks, before dropping sharply for the taper.

Where you personally land inside that range depends heavily on your starting point. Someone arriving from an Olympic-distance background with a solid aerobic base across all three disciplines can often build efficiently near the lower end of the range. Someone building bike and run volume from a much smaller starting base usually needs more time in each week, not because the race demands more from them specifically, but because the safe rate of increasing training load is roughly the same for everyone, and they're starting further back.

The phase-by-phase build

A sensible 70.3 build follows the same periodized shape as any longer-course plan, just stretched to fit a longer race and a longer runway:

1. Base. Weeks of mostly easy, aerobic (Zone 2) volume across swim, bike, and run, with technique work layered on top, especially in the swim. This phase builds the tank everything later draws from. Skip it or shorten it too much and the rest of the build has nothing to stand on.
2. Build. Volume keeps climbing while race-pace and threshold work gets introduced, first in small doses, then more substantially. This is where your long ride and long run start progressing toward their peak lengths, and where brick workouts start showing up regularly rather than occasionally.
3. Peak. Your heaviest training block, where weekly hours and long-session length both sit at their highest point of the entire plan. Race-specific pacing work matters more here than raw volume increases; this is where you rehearse the actual effort you'll hold on race day, not just accumulate more time on your feet.
4. Taper. Volume drops while some race-pace and threshold work stays in place. A real taper week lands somewhere between roughly 30% and 55% of your peak week's training load, not lower. Cut further than that and you're not tapering anymore, you're detraining, showing up undertrained instead of fresh. A 70.3 taper typically runs two to three weeks: longer than the week or so a sprint or Olympic race needs, shorter than what a full Ironman build often calls for. Race week itself isn't just the last, lightest taper week; it usually calls for a short, sharp opener effort to keep your legs primed rather than more volume cut on an already-tapered base.

A sample long-ride and long-run progression

Long-session progression is where a 70.3 build differs most visibly from shorter-distance training. The table below is an illustrative shape to adapt to your own build, not a fixed template; your actual numbers depend on your starting fitness, your timeline, and how your body responds along the way.

Notice that the long ride typically peaks well beyond your actual 90km race bike time. That's deliberate: a longer training ride builds broader aerobic durability and time-in-the-saddle tolerance than race-pace effort alone would, since training rides are usually done well below race intensity. The long run tells a different story. It usually peaks lower relative to race duration, often capped somewhere around two to two and a half hours regardless of the race you're building toward, because running impact accumulates on joints and connective tissue far faster than cycling load does. Pushing the long run past that just to "match" the bike's proportional buildup is one of the more common ways athletes injure themselves late in a 70.3 build.

Why fueling becomes make-or-break at this distance

Nutrition strategy separates 70.3 from everything shorter in triathlon. A sprint race is often over before glycogen depletion becomes a real factor. An Olympic-distance race sits right at the edge where it starts to matter for some athletes. A 70.3, at five to seven hours, is squarely inside the window where how you fuel decides whether your run leg happens on your terms or falls apart underneath you.

General sports nutrition guidance for endurance events lasting longer than roughly two and a half hours points to an intake target of 60-90 grams of carbohydrate per hour, using a blend of glucose and fructose (often called "multiple transportable carbohydrates") rather than a single sugar source, because a blend lets your gut absorb carbohydrate through more than one transport pathway at once. That guidance is documented by the Gatorade Sports Science Institute and reflects a substantial body of research on exogenous carbohydrate oxidation during exercise. Highly trained athletes who've specifically practiced eating at higher rates during training can sometimes tolerate more, up toward 90-120 grams an hour, but that ceiling is earned through repeated practice, not assumed on race morning.

The number matters less than the rehearsal. Whatever intake target you land on, test it repeatedly during your longer training rides and runs well before race day, not for the first time in the race itself. Gut tolerance for higher carbohydrate intake is trainable, typically improving over a few weeks of deliberate practice, and a fueling plan that's never been tested under real training fatigue is a plan you're guessing at. The same goes for hydration and sodium: what works for someone else's sweat rate and the conditions on their race day won't automatically match yours.

The classic first-timer mistake: burning your run before it starts

If there's one signature failure mode at 70.3 distance, it's this: riding the bike leg harder than it can sustain, then discovering the cost only once the run starts. The bike leg at 70.3 distance is long enough that an unsustainable pace feels completely fine for the first hour, sometimes longer, which is exactly what makes it dangerous. By the time it stops feeling fine, the damage is already done, and it shows up as a run that falls apart in the first few kilometers rather than one that simply gets harder late.

The fix isn't complicated, even if it's hard to execute in the moment: pace the bike off your own numbers, not off how good you feel or who's passing you. A power meter gives you the most objective ceiling, letting you cap your effort against your own threshold rather than your competitive instincts. A heart rate strap works as a reasonable substitute if you don't have power. Either way, the goal is the same: leave the bike leg with legs that can still run, not legs that were merely fast for 90km.

Other first-timer mistakes at 70.3 distance

A few other patterns show up often enough at this distance specifically to be worth naming directly:

• Treating the swim as an afterthought. A 1.9km open-water swim is long enough that poor sighting, panic in a crowded start, or an inefficient stroke can cost real time and energy before the bike even begins. It deserves more than a token warm-up lap the week before the race.
• Never rehearsing race nutrition under real fatigue. Testing a gel or a sports drink on a fresh, easy ride tells you almost nothing about how your gut handles it three hours into a hard effort. Rehearse under conditions that resemble race day, not conditions that are easier than it.
• Skipping brick workouts because the distances feel manageable. The bike-to-run transition still feels genuinely strange at 70.3 distance, arguably more so than at sprint distance, because the fatigue underneath it runs deeper. Regular short bricks throughout the build remove most of that surprise before race day.
• Cutting the taper too aggressively out of nervous energy. Some athletes, worried about losing fitness, keep training hard right up to race week. That tends to produce tired legs on the start line rather than fresh ones. Trust the taper; the fitness built over months doesn't evaporate in two or three lighter weeks.
• Copying someone else's plan wholesale. A training partner's 70.3 build was shaped around their starting fitness, available hours, and injury history, not yours. A similar goal doesn't mean a similar path to it.

Why a fixed template struggles at 70.3 distance

A 70.3 build runs long enough, typically several months, that the odds of at least one disrupted week are close to certain: a work trip, a cold, a missed long ride because of weather or life. A static, printed-out plan handles that badly, because it has no mechanism for absorbing a missed week other than either skipping ahead or trying to cram the lost volume back in, both of which tend to backfire at this distance specifically, where long-session progression and fueling rehearsal both depend on steady, repeated exposure rather than occasional heroics.

This is the actual, mechanical argument for an adaptive plan over a fixed one, not a marketing line: Triathlify's plans regenerate around what you actually completed rather than a fixed calendar, and they won't generate a plan below the minimum training days your specific 70.3 goal and timeline genuinely require, the same coaching-rules gate described on the methodology page. See current pricing if you're ready to start building toward your first half-Ironman with a plan that adjusts to your actual weeks instead of assuming every one of them goes perfectly.

Frequently asked questions