If you've followed this series, you already know the pieces. Fatigue compounds across disciplines. TSS, IF, and VI determine whether you arrive at the run ready to race or ready to survive. Course terrain changes what every watt is worth. Weather shifts the ceiling on what your fitness can express.
This article connects them. Not as theory — as a framework for building a race plan that accounts for all of it. If you're landing here first, everything you need is in the sections below, with links to the deeper explanations where they matter.
A plan that holds up starts from a direction most athletes don't expect: the finish line.
A famous coach once taught me: "We measure shit at the finish line." Not the swim split. Not the bike power. The finish line. A triathlon isn't three separate performances loosely connected — it's one result that depends on how well all three work together.
The run is where that result is decided. Everything before it — every swim stroke, every pedal stroke — either protects your ability to run or erodes it. A plan that holds up starts there.
What can you realistically run off the bike? Not fresh, not on a good day — after the swim, after the bike, in the conditions you'll face. That answer defines a TSS ceiling for the bike. Exceed it and the run degrades — not linearly, but compounding with every point over budget. (Why Most Triathletes Blow Up on the Run explains the mechanics in detail.)
The TSS ceiling sets your IF range. The IF range, shaped by the course and the forecast, becomes specific power targets. The plan builds backwards from the run because that's the direction the consequences flow on race day.
The bike and run aren't separate problems. They're one optimisation: what combination of bike effort and run pace produces the fastest time from T1 to the finish line?
Push the bike too hard and the run degrades by more than the bike gained. Back off too much and you've left time on the road that the run can't recover. The sweet spot depends on everything at once — your IF and VI on the bike, the terrain on both courses, the weather across both disciplines, and how all of it feeds into the fatigue you carry into T2.
This is why the same athlete with the same fitness gets different bike targets for different races. A flat bike course followed by a flat, cool run can absorb a more aggressive bike effort. A hilly bike into an exposed afternoon run in the heat demands more restraint — not because the athlete is less fit, but because the coupled cost of the bike and run shifts with course and conditions. (Why Course Intelligence Changes Everything and Race Day Weather and What It's Really Doing to Your Pacing Plan go deeper on both.)
The distribution of effort on the bike matters too. Terrain-adaptive power — pushing harder on climbs, easing on descents — is faster at the same average output. But variability has a run cost. VI above 1.05 accelerates glycogen depletion at a rate the averages don't capture. The goal is the most time-efficient power distribution that keeps the total bike-to-run degradation within what produces the fastest finish. (TSS, IF, and Variability Index explains how these metrics interact.)
Fitness sets the range. Course and weather shape the targets. The run outcome determines how aggressive the bike can be. It's one connected system — not a bike plan with a run plan bolted on.
The bike-run system doesn't start at T1. It starts at the swim.
Exceed your CSS and you arrive at the bike with elevated heart rate and accumulated lactate. That elevation compounds directly onto IF and VI. The bike targets were set for a clean start. A hard swim means those targets are too aggressive before you've turned a single pedal — and the recovery you'd take to clear it at low intensity isn't available at race pace. You carry it forward. (Why Most Triathletes Blow Up on the Run explains the full mechanism.)
Course complexity adds cost most athletes don't plan for. Turn geometry, buoy placement, direction changes — each one carries an effort penalty that doesn't show in your pace per hundred. Wetsuit benefit and drafting position both shift the ratio between effort and speed. What the swim feels like and what it actually costs are two different numbers — and it's the cost, not the feeling, that the bike inherits.
The swim's job is to deliver you to T1 at the planned effort. Not faster. Not heroic. On budget — so that everything downstream starts where the plan expects.
The logic of a good plan doesn't change on a hot day. The run still determines how aggressive the bike can be. The bike still shapes what the swim needs to look like. The framework is the same whether it's 18°C and overcast or 32°C with 70% humidity.
What changes is every number inside it.
Heat lowers the ceiling on sustainable power. Humidity compounds it. Duration makes it worse as the race goes on. The run threshold is lower than the bike threshold, so conditions that feel manageable on the bike may already be costly on the run. A race at 26°C follows the same logic as a race at 18°C — the run still anchors everything — but the IF range is narrower, the power targets are lower, and the run projection is slower. Not because the athlete is less fit. Because the conditions won't let the same fitness express itself.
This is also where forecast timing matters. A week out, you get a range — maybe 24-28°C, moderate humidity, wind from the west. Useful, but not precise. Three days out, it sharpens: 27 degrees, humidity climbing through the afternoon, wind shifting northwest by midday. Now the numbers mean something. The bike power ceiling adjusts. The run projection shifts. A good plan sharpens with the forecast — not locked in from ten days ago hoping the weather cooperates. The athlete who planned for 22°C and races at 30°C isn't unlucky. They're unprepared. The conditions were knowable. The plan just didn't account for them.
Every article in this series has made the same point from a different angle: a triathlon is one event, not three. The swim affects the bike. The bike determines the run. Conditions shift every target. Course terrain changes what every watt is worth.
A plan that treats these as separate problems will get some of them right and miss the connections between them. A connected plan means one input change ripples through everything — different weather, different bike targets, different run projection, different swim approach. That's not complexity for its own sake. It's how the race actually works.
This is where the right tool changes what's possible. Explore a course before you've ever set foot on it. See what five or ten extra watts of bike power does to your run projection. Compare a conservative strategy against an aggressive one and understand exactly what the trade-off costs. Test what five fewer kilos of body weight or a better CdA could do to your finish time. Adjust for the forecast as it sharpens and watch every target update together.
Keiro connects all of it into one model — your fitness, your gear, the course, the conditions. One plan where every target knows about the others. Not to tell you what to do, but to show you what's possible and let you race with confidence.
Racing is hard. It's also the best thing you do all year. The early mornings, the structured blocks, the long weekends on the bike — all of it comes down to one day on one course in whatever conditions show up.
A plan that holds up doesn't make the race easy. It makes it yours. You know the targets. You know the trade-offs. You know what the course demands and what the conditions allow. When the gun goes off, you're not managing uncertainty. You're racing.
Find your race and start planning.