BETA
Triathlete running in a race
← KNOWLEDGE HUB

Race Pacing Explained

Most run blow-ups are decided on the bike — set targets once in the Race Simulator so race day is execution, not mental maths.

Triathlon pacing is one system: the swim sets up the bike, the bike sets up the run. Run blow-ups are rarely only a run problem — wrong training, nutrition, or fatigue all play a part — but pacing too hard on the bike is one of the biggest ways to guarantee a rough run.

Race pacing targets are what you plan to hold on race day — swim, bike, and run as % of CSS, FTP, and FT: CSS (Critical Swim Speed), FTP (Functional Threshold Power), and FT (Functional Threshold pace).

Current thresholds matter — the same CSS, FTP, and FT behind your Training Zones and Workout Intensities. Set them using our Test tool — see How to Test Your Thresholds for protocols — or sync from a clean race in the Race Vault. Then open the Race Simulator: pick your distance, see swim, bike, and run targets and a predicted finish time, and lock in numbers well before race day.

On WattX

The Race Simulator applies targets from your profile — e.g. Olympic 100% CSS / 85% FTP / 100% FT; 70.3 95% / 80% / 95%; Ironman 85% / 70% / 89%. Update thresholds on our [Test](/test) tool or from a clean race in the Race Vault.

Conserve to Perform

Triathlon rewards restraint — even more as distance increases. Holding back on the bike to run well beats hammering the bike and walking. On the run, aim for even or negative splits — second half at least as fast as the first.

WattX Targets by Distance

Sprint
  • Swim105% CSS
  • Bike95% FTP
  • Run104% FT

Short, near-maximal — restraint still matters on the bike.

Olympic
  • Swim100% CSS
  • Bike85% FTP
  • Run100% FT

See Olympic Race Explained.

70.3
  • Swim95% CSS
  • Bike80% FTP
  • Run95% FT

Restraint on the bike is the skill.

Ironman
  • Swim85% CSS
  • Bike70% FTP
  • Run89% FT

Fuel and run legs trump bike heroics.

These are average targets over the full leg. You will go above target on climbs and below on descents; what matters is the average power or pace for the whole bike (and the whole run), not chasing every 30-second reading. The Race Simulator percentages are built around that idea.

For Olympic-specific execution, see Olympic Race Explained.

Swim: Controlled Start

First 200 m
Easy
Adrenaline pushes pace too high
Target
CSS
Pace you could hold 2× race distance
Drafting
−25%
Drag at same speed — practise in squad

Bike: The Critical Decision

First 20 min
Hold
Power drifts 10–15% high without notice
VI target
1.02–1.06
NP ÷ avg power — smoother is better
VI warn
>1.10
Too spiky — heavy run legs likely

On climbs sit above target briefly; keep the leg average near plan. On descents, ease off — do not bank time you pay on the run.

If you cannot ride with power, use RPE 6–7/10 — comfortably hard, not a crit.

T2: Do Not Sprint Out

Cycling legs make early run pace feel easier than it is. Check pace in the first 200 m and deliberately slow if you are ahead of plan.

Run: Patience, Then Build

First 3 km
Below
Target — let posture and gut settle
Split aim
Even −
Second half ≥ first half pace
Final surge
2–3 km
Only if pacing and fuel were correct

If Nutrition was right, the last quarter should feel increasingly strong.

Before and After Race Day

  1. Lock targets in the Race Simulator weeks out — not in transition.

  2. Study the course: bike route, run sections, transition flow.

  3. Feed predicted splits into Nutrition Strategy.

  4. After the race, log in the Race VaultRace Analysis Explained compares execution and can suggest threshold syncs.

For kit and race-week logistics, see Race Week Explained.

FAQ

What if GPS pace disagrees with my plan out of T2?

Trust power or effort for the first kilometre — GPS often lags near transition. Let pace settle before you chase numbers.

Should I race with a power meter?

Yes — on the bike, a power meter is the best way to hold your target. Watts are the cleanest real-time signal. Run power exists but is less common; pace and RPE work well on the run. Dial heat into your targets in prep, not only on the day — see the heat FAQ below.

How do I adjust for heat?

Before race day, reduce swim, bike, and run targets in the Race Simulator roughly 3–5% per 5°C above your training norm. Start the run extra conservative in hot races.

What is the biggest pacing mistake on race day?

Starting too hard on any leg — swim, bike, or run. The earlier you mis-pace, the sooner you pay for it. Over-swimming is a common example; an over-biked leg is another.

Can very fit athletes ignore conservative bike pacing?

Higher fitness raises sustainable percentages, but glycogen and run mechanics still punish an over-biked leg — especially at 70.3 and Ironman.

ATHLETE PROFILE

Syncing secure connection...
waves SWIM
directions_bike BIKE
sprint RUN
online_prediction RACE SIMULATOR
SET ANCHOR