You've put in 16 weeks of training. You've done the long rides, the brick sessions, the open water swims. You're fit enough to have a great race.
But here's the uncomfortable truth: fitness only gets you to the start line. What happens between the start cannon and the finish arch is execution — and most age-group triathletes get it wrong.
We analyzed over 840,000 triathlon race results across all distances, and the pattern is striking: the difference between a good race and a bad one almost never comes down to fitness. It comes down to three decisions made in the first 90 minutes — how hard you start the swim, how much power you push on the bike, and whether you actually ate enough before the run.
This guide covers everything you need to execute a 70.3 properly: swim pacing, bike power strategy, run targets, nutrition timing, weather adjustments, and the transition details that save real minutes. Every recommendation is backed by data, not vibes.
Before Race Morning: The 48-Hour Window
Race execution doesn't start at the swim start. It starts two days out.
Carb loading done right. Increase your carbohydrate intake to 8-10g per kilogram of body weight for the 48 hours before race day. For a 75kg athlete, that's 600-750g of carbs per day — significantly more than you'd normally eat. Focus on simple, low-fiber carbohydrates: white rice, pasta, bread, pancakes, pretzels. Your muscles can store roughly 400-500g of glycogen when fully loaded, and this is the fuel tank you'll draw from during the race.
Hydration preloading. Drink to thirst, but add sodium. A preloading protocol of 500-700mg sodium with 500ml water the evening before and the morning of race day ensures you start optimally hydrated. Avoid over-drinking — hyponatremia (low blood sodium from excessive water intake) is a real risk in endurance events.
Race morning breakfast. Eat 2-3 hours before your wave start. Target 100-150g of easily digestible carbs: a bagel with jam, white rice with honey, or oatmeal with banana. Keep fat and fiber low — your gut needs to be calm, not working hard on digestion. Sip 300-500ml of water or sports drink in the hours before the start.
Swim Pacing: Controlled Effort, Not a Sprint
The 1.9km swim in a 70.3 is the shortest discipline by time, but it sets the tone for the entire race. The most common mistake is going out too hard in the first 200-400 meters.
Target intensity: 80-85% of your threshold swim pace. If your CSS (Critical Swim Speed) is 1:40/100m in the pool, your open water target should be approximately 1:50-1:55/100m. Open water swimming is inherently 8-12% slower than pool swimming due to sighting, navigation, chop, and the absence of walls.
The first 400 meters matter most. Adrenaline and crowding push most athletes to start 10-15% too fast. This burns through your anaerobic reserves early and elevates your heart rate for the rest of the swim. A better approach: swim the first 400 meters at an intentionally easy effort (RPE 6/10), then settle into your target rhythm once the field spreads out.
Drafting saves 15-25% energy. If you can find feet to draft behind in the first few minutes, do it — but only if the person ahead is swimming at roughly your pace. Don't surge to catch a faster swimmer's draft; the energy cost defeats the purpose.
Wetsuit advantage. In wetsuit-legal races (water under 24.5°C for IRONMAN events), expect a 3-5% speed boost from the added buoyancy. Adjust your target pace slightly faster, but don't change your perceived effort.
Sighting every 8-12 strokes. Swim in a straight line. A 5% navigation error on a 1.9km swim adds ~100 meters. That's 1-2 extra minutes for no reason.
T1: Swim to Bike Transition
Target time: 3:00-5:00 (depending on race venue layout).
The key principle in T1 is "don't rush, don't dawdle." Age-groupers lose the most time not from slow hands but from disorganization — fumbling with gear they didn't lay out properly.
Strip your wetsuit to the waist as you run from the water to transition. Have your helmet open and facing up on your aerobars. Sunglasses inside the helmet. Shoes pre-clipped to the bike (or right next to it if you don't do flying mounts). Socks are optional in a 70.3 — most athletes skip them to save 30-60 seconds.
The overlooked detail: Apply anti-chafe cream the night before to areas that will rub during the bike — chamois area, underarms, neck. You will not want to stop and deal with chafing at kilometer 60.
Bike Pacing: The Discipline That Makes or Breaks Your Race
The 90km bike leg is where 70.3 races are won or lost. Not by who rides fastest, but by who rides smartest. Our data from 840,000+ race results shows a consistent pattern: athletes who ride above 78% of FTP for the bike leg lose an average of 8-12 minutes on the run compared to their predicted time. The bike-to-run energy transfer is the single most important variable in 70.3 performance.
Target intensity: 68-76% of FTP. This is lower than most athletes instinctively ride. It should feel "too easy" for the first 30km. That's exactly right. The run will feel hard enough regardless — your job on the bike is to preserve glycogen and keep your core temperature manageable.
Here's how the range breaks down by athlete level:
- Beginner (first or second 70.3): 65-70% FTP. Err on the conservative side. A comfortable bike sets up a runnable run.
- Intermediate (sub-6:00 target): 70-75% FTP. You have the fitness to push slightly, but discipline matters more than watts.
- Advanced (sub-5:00 target): 73-78% FTP. The upper range is achievable if you have strong run-off-bike experience and dialed nutrition.
If you don't have a power meter, use heart rate as a secondary guide: stay in Zone 2 to low Zone 3 (roughly 70-80% of max HR). But heart rate drifts upward with heat, dehydration, and fatigue — so if your HR is climbing but your power is steady, trust the power.
Course-specific adjustments:
- Climbs (gradient >4%): Increase power by 5-10% above your flat target. Standing for 15-20 seconds every 5-10 minutes on long climbs helps distribute muscular load.
- Descents (gradient <-3%): Reduce power significantly (50-60% FTP) or soft-pedal. Use descents as micro-recovery. Don't chase speed downhill — the aero benefit is minimal and the recovery cost is real.
- Headwind sections: Reduce target power by 5%. Fighting a headwind at full power is metabolically expensive for minimal speed gain. Accept the slower speed, maintain the effort, and know you'll gain it back on the return.
- Tailwind sections: Don't increase power. Let the wind do the work while you enjoy free speed at the same effort.
Pacing by segments, not average. A flat 70.3 course and a hilly 70.3 course require the same average power but very different execution. On hilly courses, your Normalized Power (NP) will be higher than Average Power (AP) because of the variability. Aim for a Variability Index (NP/AP) below 1.05. Higher than that means you're surging too much on climbs and coasting too much on descents.
Read our detailed guide: 70.3 Bike Pacing Strategy →
Nutrition on the Bike: Your Race Fuel Strategy
Start eating within the first 15 minutes on the bike. Do not wait until you feel hungry — by the time hunger signals arrive, you're already in glycogen debt.
Target intake for a 70.3 bike leg:
- Carbohydrates: 60-80g per hour. This is the range where most athletes can absorb and utilize fuel effectively. If you've trained your gut, 80-90g/hr is achievable using a 2:1 glucose-to-fructose ratio.
- Sodium: 500-700mg per hour in temperate conditions. In hot conditions (above 25°C / 77°F), increase to 700-1000mg per hour.
- Fluid: 500-750ml per hour. Adjust up in heat, down in cold. Your body can rarely absorb more than 1L per hour, so drinking more than that leads to sloshing and GI distress.
Practical execution: For a 2:30-3:00 bike leg, that means roughly 6-8 gels (or equivalent from drink mix, bars, or chews) plus 1.5-2L of fluid. Set a timer on your bike computer for every 20 minutes as a nutrition reminder.
Caffeine timing: Take your first caffeine dose 45-60 minutes into the bike. A dose of 2-3mg per kilogram of body weight (150-225mg for a 75kg athlete) improves power output and reduces perceived effort for the run. Don't take caffeine in the last 30 minutes of the bike — let it absorb before T2.
The most common nutrition mistake: Eating too little on the bike because "I feel fine." You will not feel the calorie deficit until the run. By then, it's too late to recover. Eat on schedule, not on feel.
Read our detailed guide: 70.3 Nutrition Timeline →
T2: Bike to Run Transition
Target time: 2:00-3:00.
Rack your bike, remove your helmet (after racking — many races require this order), put on your run shoes, grab your race belt with number, and go. Visor or hat if it's sunny. Apply sunscreen if you didn't pre-race.
The critical T2 detail: Take your first run nutrition (a gel or a few swigs of sports drink) immediately as you leave T2. Your gut is already processing bike nutrition, and the transition to running mechanically shifts blood flow away from digestion. Getting one more dose in while you're still walking-to-jogging out of transition gives it the best chance to absorb before the run gets hard.
Run Pacing: Execute the Negative Split
The 21.1km run is where the race comes together or falls apart. After 1.9km of swimming and 90km of cycling, your legs are carrying significant fatigue, and your glycogen stores are partially depleted. The goal is a controlled negative split: slightly conservative first half, slightly faster second half.
The "brick effect." Your run pace off the bike will be 5-12% slower than your standalone running pace, depending on how hard you rode. For an athlete who runs 5:00/km in a standalone half marathon, expect 5:15-5:30/km for the first few kilometers of a 70.3 run. This is normal. Don't panic and don't try to force your standalone pace.
Pacing strategy:
- Kilometers 1-3: Run 5-8% slower than your target 70.3 run pace. Your legs are transitioning from cycling mechanics. Let them adapt. Walk through the first aid station to get fluids and fuel in.
- Kilometers 4-10: Settle into your target pace. This should feel like a "comfortably hard" effort (RPE 7/10). You're running on tired legs, so a lower pace than training is expected and correct.
- Kilometers 11-16: If you feel good, begin a gradual increase — 2-3% faster than your target pace. If you don't feel good, hold steady. Don't accelerate if you're struggling.
- Kilometers 17-21: Leave everything out there. This is where the race is decided. The athletes who rode conservatively have energy left. The athletes who overdid the bike are walking.
Heart rate guidance: Expect your heart rate to be 5-10 beats higher on the run than the same RPE effort in training. This is the cumulative fatigue effect. Don't chase HR zones — use perceived effort and pace.
Walk breaks are a strategy, not a failure. For athletes targeting 2:00+ on the run (>5:40/km pace), planned walk breaks at aid stations can actually produce a faster overall time than continuous running. Walk for 30-60 seconds at each aid station to eat, drink, and let your heart rate settle.
Run Nutrition: Maintenance Mode
On the run, your goal is to maintain blood sugar and hydration, not to reload glycogen. Your gut is compromised from hours of exercise and the mechanical jostling of running makes absorption harder.
Target intake:
- Carbohydrates: 30-60g per hour. Less than on the bike because absorption capacity drops during running. Liquid calories (cola, sports drink) are often better tolerated than gels on the run.
- Sodium: 400-600mg per hour. Electrolyte capsules are easy to carry and take at aid stations.
- Fluid: 400-600ml per hour. Drink at every aid station but don't over-drink. Pour water over your head and neck for cooling instead.
The cola strategy. Flat cola at aid stations is a 70.3 staple for good reason: it provides sugar (glucose), caffeine, and tastes good when everything else sounds revolting. After 4+ hours of gels, a cup of cola is a psychological and physiological boost.
Weather Adjustments: When Conditions Change Your Plan
Weather is the variable most athletes ignore and the one that derails the most race plans.
Heat (dew point above 16°C / 60°F):
- Reduce bike power by 3-5% for every 5°C of dew point above 16°C
- Increase sodium intake by 200-300mg per hour
- Increase fluid intake by 200-300ml per hour
- Run pace slows 3-8% per 5°C above 20°C
- Use ice at aid stations: in your hat, down your trisuit, in your hands
Wind:
- Headwind on the bike: reduce power 5%, don't chase speed
- Tailwind: maintain power, enjoy free speed
- Crosswind: stay low, grip the bars, expect slower speeds even with adequate power
Rain:
- Bike handling becomes critical — wider lines on corners, brake earlier
- Nutrition may be harder to grip — pre-open gels or use drink mix
- Body temperature drops — run effort may feel easier but muscular efficiency decreases
Altitude (above 1,500m / 5,000ft):
- Reduce all intensity targets by 5-8%
- If you haven't acclimated for at least 10 days, add another 3-5% reduction
- Increase fluid intake — you dehydrate faster at altitude
Read our detailed guide: 70.3 Weather Adjustments →
Your Pre-Race Checklist
The night before:
- Lay out all race gear
- Pin your race number to your belt
- Charge all devices (watch, bike computer, headunit)
- Check tire pressure (inflated the night before, top off in the morning)
- Set two alarms
Race morning:
- Eat breakfast 2-3 hours before start
- Apply anti-chafe cream, sunscreen
- Set up transition area: helmet open on bars, shoes laid out, nutrition ready
- Program target power/pace into your devices
- Warm up: 10-minute easy jog + dynamic stretches, 5-minute easy swim
On the bike (mental checklist):
- First 15 min: start eating
- Every 20 min: nutrition alarm → eat/drink
- Halfway point: check power average — are you on target?
- Last 10km: take final caffeine, final solid food, switch to liquids
On the run:
- First aid station: walk, drink, eat
- Every aid station: fluid + electrolytes
- Halfway: assess — can you push, or hold steady?
- Last 5km: leave it all out there
The Most Common 70.3 Mistakes (and How to Avoid Them)
Riding too hard on the bike. The #1 race-ruining mistake. If your bike split is a PR but your run split is a disaster, you didn't have a great bike — you had a terrible race strategy.
Not eating enough on the bike. You will feel fine at hour 1. You will bonk at hour 4. Eat on schedule, not on feel.
Starting the run too fast. The first 2km off the bike always feel deceptively good. Adrenaline and the crowd will push you faster. Resist. Start slow, finish fast.
Ignoring heat. A 30°C race is a completely different event than a 20°C race. Adjust power, pace, and nutrition — or pay for it on the run.
Trying new nutrition on race day. Every gel, every drink, every bar should be tested in training. Your gut is unpredictable under race stress — don't add variables.
Skipping aid stations early in the run. "I feel fine, I'll drink at the next one." This is how dehydration builds. Stop at every single aid station for the first half of the run.
Read our detailed guide: 70.3 Common Mistakes →
Build Your Personalized 70.3 Race Plan
This guide gives you the framework. But every athlete is different — your FTP, your threshold pace, your race course, and your race-day weather all change the numbers.
RaceDayAI builds a personalized race execution plan using your actual fitness data, your specific course profile, and real-time weather forecasts. Enter your details, and get segment-by-segment power targets, a nutrition timeline, and an AI-generated strategy tailored to your race.
Build Your Free 70.3 Race Plan →
FAQ
How long should a 70.3 take? It depends on your fitness. The average age-group 70.3 finish time is approximately 5:30-6:00. Competitive age-groupers finish in 4:30-5:00. Elite athletes finish in 3:45-4:15. Your finish time is determined primarily by your cycling FTP, run threshold pace, and race-day execution.
What percentage of FTP should I ride in a 70.3? 68-76% of FTP for the bike leg. Beginners should stay at 65-70%, intermediate athletes at 70-75%, and advanced athletes at 73-78%. Going above 78% significantly increases the risk of running poorly.
How many calories do I need during a 70.3? Plan for 60-80g of carbohydrates per hour on the bike (240-320 calories) and 30-60g per hour on the run (120-240 calories). Total calorie intake for a 5-6 hour race is roughly 1,200-1,800 calories from nutrition, against a burn of 3,500-5,000+ calories. You cannot and should not try to replace all calories burned.
Should I use a power meter for a 70.3? A power meter is the single most valuable race execution tool for the bike leg. It removes guessing, prevents over-pacing on fresh legs and downhills, and gives you a concrete target. If you don't have one, use heart rate as a secondary guide — but power is more reliable.
What if it's hotter than expected on race day? Reduce bike power by 3-5% per 5°C above what you trained in. Increase sodium by 200-300mg/hr. Increase fluid by 200-300ml/hr. Slow your run target by 3-8%. Use ice at every aid station. Accept that your time will be slower — a smart hot race beats a blown-up hot race every time.
How do I know if I'm going too hard on the bike? If your power is above 78% of FTP, you're likely too hard. If your heart rate is drifting above Zone 3, you're likely too hard. If you can't comfortably eat and drink, you're definitely too hard. The bike should feel "boringly easy" for the first hour.
Last updated: March 2026. Data sourced from 840,000+ triathlon race results. For a personalized plan based on your fitness and your race, try RaceDayAI — it's free for your first race.