Two athletes with identical FTPs line up for an IRONMAN on the same weekend. One is racing Frankfurt. The other is racing Lanzarote. Same distance, same fitness, same power meter on the bars. By the time they reach T2, they've raced two completely different events — not because one was fitter than the other, but because the course changed what every watt was worth.
A plan that says "hold 210 watts" treats both courses the same. The physics doesn't. Where your watts go — how much fights gravity, how much fights the wind, how much moves you forward — changes with every kilometre of road. A plan that ignores the course isn't a plan. It's a guess with a number attached.
If you raced Frankfurt and Lanzarote back to back at the same power, the difference wouldn't be subtle. It would be jarring.
Frankfurt gives you around 1,200 metres of climbing through the Taunus — sheltered forest roads, rolling terrain, sections where you settle into aero and stay there. When the road is flat and the trees are blocking the wind, nearly everything you produce fights air resistance. Your CdA matters enormously. The faster you go, the more it matters — the power required to overcome aerodynamic drag scales with the cube of your speed, so every fraction of aerodynamic efficiency compounds across 180 kilometres of fast riding.
Lanzarote gives you 2,500 metres of climbing through open volcanic landscape with no shelter at all. The wind is relentless — sustained at 25 to 30km/h, gusting well above that — and it hits you from every direction as the course winds through lava fields and exposed coastal roads. On the long climbs, you're grinding at 15km/h. At that speed, air resistance is almost irrelevant. Gravity is taking nearly everything you produce. Your mass matters more than your drag coefficient. And when the road tips down, the crosswind catches you on open descents where there's nothing between you and the Atlantic.
The same watts. The same IF. A completely different race — because the course decides what those watts are worth.
Here's a number that changes how you think about pacing: 10 extra watts on a 6% climb saves roughly 24 seconds over 2 kilometres. The same 10 watts on a flat road saves about 6 seconds. Same effort, 4x the return — determined entirely by gradient.
The reason is the physics of drag. The power required to overcome air resistance scales with the cube of your velocity — doubling your speed requires eight times the power. At 35 km/h on flat terrain, drag dominates: the lion's share of every watt is going into pushing air aside, and adding power buys diminishing speed in return. On a climb at 15 km/h, drag almost disappears. Gravity takes over 90% of the resistance. Every additional watt goes directly into fighting the gradient, and the speed return is far greater.
That doesn't mean watts on the flat don't matter — they do, and over 180 kilometres the seconds add up. But the return per watt varies enormously across the course. Climbs are where the biggest gains live. Descents are where the smallest ones are. At gradients beyond -6%, the speed you reach by coasting is surprisingly close to the speed you reach by pedalling hard — because at high speed, drag absorbs almost everything you add. The steeper the descent, the smaller the gap between freewheeling and full effort.
This is why holding perfectly steady power across a hilly course is leaving time on the table. You're distributing effort equally, but the course isn't rewarding effort equally. Terrain-adaptive power — pushing harder where the return is highest, easing back where it's lowest — produces faster bike splits at the same average power and the same physiological cost.
The research confirms it. Swain's 1997 study showed 6.7% time savings from terrain-adaptive power on hilly courses. Wells and Marwood confirmed 0.4 to 4.3% improvement with just 5% power variation on moderate gradients. Across a full IRONMAN bike leg, that's the difference between a strong ride and a great one.
But this is triathlon, not a time trial. Terrain-adaptive power is faster on the bike — the question is what it costs on the run.
Variability Index measures how much your power fluctuated relative to the average. In cycling, higher VI often means a faster ride. In triathlon, it means a worse run. Etxebarria and colleagues (2013) measured the cost directly: twelve well-trained triathletes completed two one-hour cycling efforts at the same mean power — one steady, one with substantial within-effort variability — followed by a 9.3 km time-trial run. Same cycling workload on paper. The variable-power runs were 42 seconds slower over 9.3 km, with the decrement concentrated in the first half of the run. The mechanism is consistent with what the headline metrics conceal: power spikes above threshold recruit fast-twitch fibres and elevate blood lactate, and the cost lands on the run. Friel's coaching standard for long-course racing is VI 1.05 or below, and public power-file analyses of recent Kona champions show consistent discipline at that level — Pete Jacobs at 1.05, Lionel Sanders at 1.02 — on a course with around 1,800 metres of climbing. They vary their power with the terrain. They just don't vary it beyond what the marathon can absorb.
The optimal strategy isn't steady and it isn't aggressive. It's terrain-adaptive power within run-safe limits. Push where the return is highest. Ease off where it's lowest. Keep the total variability within the band that protects the run. The balance between bike speed and run readiness isn't something you solve by feel on race day — it's something the course profile, your fitness, and the conditions determine in advance.
Most athletes check the wind forecast the night before a race and form a rough plan: headwind on the way out, tailwind on the way back, it'll even out. It won't.
The first reason is physics. Headwind and tailwind don't cancel. The power required to overcome drag scales with the cube of your velocity through the air — a headwind at race pace costs far more watts than the equivalent tailwind saves. Over an out-and-back course with equal headwind and tailwind exposure, you're always slower than on a calm day. The net effect is always negative, and the stronger the wind, the worse the asymmetry.
The second reason is direction. Wind rarely stays neatly in front of or behind you. As the course turns, the same wind becomes a crosswind, changing the yaw angle between your direction of travel and the apparent wind. That yaw shift changes your effective aerodynamic profile — depending on your wheels and position, it can increase or decrease the power required to hold speed. You don't feel the yaw angle change. You feel the bike get harder or easier and don't always know why.
The third reason is shelter. The forecast says 25km/h from the northwest. But on a section lined with forest, you might experience 12km/h. On an exposed ridge two kilometres later, you get the full 25 — or more, if the terrain funnels it. Same forecast, same course, completely different conditions segment by segment. Frankfurt's tree-lined Taunus roads absorb much of the forecast wind. Lanzarote's open lava fields and coastal sections let it hit you at full force from every direction. An athlete following the same power target through both sections is either under-pacing the sheltered part or over-pacing the exposed part — probably both.
A plan built on a single wind number for the whole course is solving the wrong problem.
Course intelligence doesn't start at T1. A swim course with tight buoy turns and multiple direction changes costs more energy than a simple out-and-back — not from extra distance but from the deceleration and reacceleration at every turn. Each one carries a penalty measured in seconds and effort. A technically complex course accumulates those penalties across dozens of direction changes.
Then there's what you're wearing and how you're swimming. Wetsuit benefit and drafting position both change the relationship between effort and speed — what you feel in the water and what the clock shows are two different numbers. An athlete drafting in a pack with a wetsuit is swimming at a meaningfully different effort-to-pace ratio than one swimming solo without. The gap between effort pace and real pace is course-specific, gear-specific, and race-specific.
That effort comes from the same budget the bike and run draw from. Keiro models swim course complexity, wetsuit benefit, and drafting effect as part of the full race — giving the athlete a realistic time goal based on their profile, their gear, and their race conditions. Because a plan that starts at T1 is already one discipline behind.
If you've read the first two articles in this series, you know the run is where the bill comes due. TSS is the budget. IF is the throttle. VI is the hidden cost. But here's what course intelligence adds: the same numbers on two different courses don't mean the same thing.
An IF of 0.80 on a flat, sheltered course with steady power produces a very different physiological state than 0.80 on a hilly, exposed course where the terrain forced repeated surges on every climb. The TSS might match. The VI might be close. But the pattern of effort — where the surges fell, how long the recoveries lasted, how much time was spent above threshold versus below it — was dictated by the course.
The run doesn't average anything. It responds to the accumulated pattern of every effort the bike demanded. The surges that didn't look significant in the headline metrics. The headwind sections where you pushed harder than planned to hold speed. The climbs where you went with the group instead of holding your target. Course terrain shapes all of it — and if the plan didn't account for the course, those moments weren't planned for either.
This is also why a course-aware plan doesn't optimise the bike in isolation. A flat, fast run course can absorb more bike fatigue than a hilly one in afternoon heat. The same athlete with the same FTP might get a more aggressive bike target for one race and a more conservative one for another — not because the bike course changed, but because the run course did. The plan backs off the bike when the run demands it, because the goal was never the fastest bike split. It was the fastest finish time.
This is the connection between course intelligence and run performance. A plan built for the actual course sets bike targets that account for where the hard sections are, how much they'll cost, and what the run can absorb afterwards. A generic plan sets a number and hopes the course cooperates.
You've spent months getting here. Structured training blocks, threshold sessions, long rides in the rain, bricks that ate your weekends. The fitness is earned. Whether your race is a 70.3 or a full IRONMAN, you're looking at half a day to an entire day on course. That's not an event you show up to and see what happens.
And yet most athletes line up with a race plan that amounts to a power target and a pace — numbers pulled from training, maybe adjusted by feel, applied to a course they've never raced with weather they can't predict. It's not that the numbers are wrong. It's that they don't account for what the course will actually do to them.
A 180-kilometre bike course is thousands of interacting variables: gradient, wind, exposure, surface, cornering — all changing segment by segment. The weather forecast sharpens as race day approaches, and what looked like a calm morning on Monday might show a building headwind by Saturday's update. Temperature, humidity, and wind direction shift with every revision. The swim has its own course complexity. The run has its own elevation and conditions. And all three are connected — every decision in the swim affects the bike, and every kilometre of the bike shapes the run.
No one solves this in their head on race morning. And after months of preparation, no one should have to.
Keiro builds the complete plan before the gun goes off. Your fitness, your gear, the actual course, and the latest forecast — connected across all three disciplines into a single race strategy. So that when the race starts, you're not guessing. You already know how it should unfold. You just have to go and do it.
None of this is meant to make racing feel more complicated. It's meant to give you confidence. When the plan knows the course — every climb, every exposed section, every sheltered stretch — there are no surprises. You know what each section costs. You know where to push and where to save. You know what the run can absorb because the plan was built around it.
The course doesn't change on race day. The physics doesn't change. The only thing that changes is whether you planned for it.
Find your race and start planning.