Ask a hundred experienced coaches what kills more amateur race performances than anything else, and the answer will come back with eerie consistency: the first five kilometres. Not fitness. Not fuelling. Not shoes, not weather, not bad luck. Pacing. The runners who started 15 seconds per kilometre too fast. The triathletes who pushed 20 extra watts on the first 30 minutes of the bike. The marathoners who hit halfway 4 minutes ahead of plan and were 12 minutes behind plan at the finish.
The frustrating part is that pacing is not mystical. The physiology is clear, the strategies are well tested, and the margin for error is calculable. This guide is the practical, modern version of how to actually pace an endurance race — from a 5K to an Ironman — and why the people who get it right almost always look like they're running slightly too conservative until the last third.
Why does pacing matter so much?
Endurance performance is constrained by two hard limits that interact in a specific way. The first is your ability to deliver oxygen to working muscles. The second is your stock of carbohydrate — glycogen in the muscles and liver, plus whatever you can absorb from food during the race. Push the first limit and you produce lactate faster than you can clear it, which accelerates the burn through the second limit. Burn through the second limit and you hit the wall, your brain throttles output to protect itself, and the last chunk of the race becomes a survival shuffle.
Pacing is how you ration both limits. A well-paced race spends exactly the right amount of both resources across the full distance — no leftover glycogen at the finish, no catastrophic grey-out before it. A badly paced race wastes the first resource (effort) in the opening minutes and runs out of the second (fuel) far too early.
What is the single most important pacing rule?
Pace for even effort, not even splits. This is the one rule that carries almost every other rule on its back. Running the same split on kilometre one as on kilometre forty of a marathon requires a completely different effort — the first kilometre is effortless at that pace, the fortieth is almost impossible. Effort is what your body actually pays. Splits are what the watch shows.
In practice, even effort usually means starting slightly slower than your target average, allowing the effort to rise smoothly as fatigue accumulates, and arriving at the final kilometre with something left in the tank. It is the opposite of what your adrenaline will tell you to do at the start line. Trust the plan.
What does a negative split really mean?
A negative split means running the second half of the race faster than the first half. It is the rarest and most reliable way to produce a personal best in almost every endurance distance. The logic is direct: if you run the first half 30 seconds slower than your target average pace and the second half 30 seconds faster, your overall time is the same — but the physiological cost distribution is much more sustainable, and the probability of a late-race collapse drops dramatically.
Most recorded marathon world records from the past two decades were run as negative or even splits. Almost no recreational amateur marathon personal best was ever set as a positive split (second half slower than first). When Eliud Kipchoge runs 2:01, his first half and second half are within 30 seconds of each other. When a first-time marathoner hits the wall at kilometre 32, their second half was probably 20 minutes slower than their first.
The honest nuance: on hilly courses, or on courses with a headwind in one direction, splits can mislead. Even effort is still the principle; splits are just one indicator of it.
What should you actually pace against — HR, pace, power, or effort? (Pacing anchors)
Every control variable has strengths and weaknesses. The best racers pick one primary anchor, know its quirks, and use the others as sanity checks. The table below summarizes the four main options.
| Anchor | Best when | Weakness | Typical use |
|---|---|---|---|
| Pace | Flat, still courses, short races | Fails on hills, wind, heat | Road 5K / 10K / half / marathon on fast courses |
| Heart rate | Hilly terrain, hot weather, long events | Lags 30–60s, drifts upward, sensitive to stress | Hot marathons, hilly gran fondos, long course triathlon |
| Power (bike) | Any bike race or leg | Requires power meter | 40k TT, IM bike — always Normalized Power, not raw |
| Running power (Stryd) | Hilly trail runs, variable terrain | Expensive sensor, still maturing | Ultra, mountain races |
| RPE (effort) | Any race, especially ultras, watch failure | Subjective | Backup anchor; primary for ultras |
Pick one primary anchor for your race. Know your target for it. Glance at the other numbers as cross-checks, but don't react to every metric independently. Conflicting instruments in the first 5K are where races unravel.
What are the target intensities by race distance? (Intensity chart)
These are broad ranges that hold for most trained amateur athletes. Your own number depends on your training state, the course, and the conditions. The table below maps each distance to its target intensity as a percentage of FTP or threshold HR.
| Race | % FTP / threshold HR | Primary anchor | Pacing rule |
|---|---|---|---|
| 5K | 110–120% FTP / > threshold HR | Pace / effort | Even split, small kick. 5% too fast in km 1 tanks km 3–5 |
| 10K | 95–105% FTP | Pace / HR | Even splits plus finishing kick |
| Half marathon | 85–90% running FTP / 88–93% threshold HR | Pace / HR | Slight negative split for experienced runners |
| Marathon | 75–85% running FTP / 82–88% threshold HR | Pace / HR + fueling | Conservative first 10k, negative split |
| 40k TT (bike) | 85–95% FTP | Power (NP) | Steady, Variability Index ≤ 1.05 |
| 70.3 triathlon | Bike 75–85% FTP, run marathon intensity | Power (bike), HR/pace (run) | Bike pacing is the race |
| Full Ironman | Bike 65–75% FTP (IF 0.65–0.75), run 80–85% marathon pace | Power (bike), HR/pace (run) | Conservative bike + fueling > heroic watts |
| Ultra marathon | Zone 2 to low Zone 3 | Effort + fueling rhythm | Walk climbs, eat on a clock |
How does fueling interact with pacing?
Pacing and fueling are not two separate problems — they are two sides of the same energy budget. The effort you choose determines how fast you burn glycogen, which determines how much carbohydrate you need to take in per hour, which determines what pace your gut will allow you to hold when your legs are willing to go harder.
The practical version: if your fueling plan is 60 g/h, you cannot sustain a marathon pace that would require 90 g/h of glycogen throughput. You will blow up somewhere after kilometre 25 regardless of how strong you feel at kilometre 10. The best pacing plans are built with the fueling plan, not after it — which is why gut training and pacing rehearsal belong in the same block.
For a marathon, the classic rule is to settle into your effort zone through the first 30 minutes, lock in the fueling rhythm (one gel every 25–30 minutes, with water and sodium), and only allow yourself to assess how you're going after kilometre 25. Anything you feel before then is adrenaline, not signal.
What are the biggest pacing mistakes?
Five traps catch almost every amateur racer at least once.
- Going out too fast. The single most common error, by an enormous margin. If you feel comfortable in the first 5K of a marathon, you are probably already too fast. The first few kilometres are supposed to feel easy.
- Chasing a new PB pace instead of your current fitness. Your fitness is what it is on race day. A pace target that requires perfect weather, perfect pacing, perfect fueling and a new lifetime best should not be your A-target — it should be your stretch reach only if everything falls into place.
- Pacing by GPS pace in the first kilometre. GPS accuracy in dense race starts is often ±15 seconds per kilometre. Trust your HR, power, or effort for the opening 3K — not the pace read.
- Reacting to other runners. Someone surging past you at kilometre 8 is running their race, not yours. The graveyard of marathons is littered with athletes who chased a stranger's pace and paid for it 25 kilometres later.
- Switching strategy mid-race. If your plan was 4:45/km for the marathon and you're on 4:42 at halfway feeling strong, stick to 4:45. Feeling strong at halfway is exactly what a well-paced marathon is supposed to feel like. Save the surge for the last 10K.
How do you practise pacing before race day?
Pacing is a skill, and it has to be rehearsed like any other part of racing. Three practical tools build the skill over a training block.
- Race-pace intervals — blocks of 15–30 minutes inside longer runs or rides, held at exactly your race target. They teach your body what the effort feels like, not just what the pace looks like.
- Race simulation efforts — one or two sessions per training block where you hold race effort for half to two-thirds of the full race duration. For a marathon, that's a 2-hour run at marathon pace. For a 70.3, that's a bike-run brick at race intensity.
- Starting-too-fast drills — brutal but useful. On a training run, start at 110% of your planned race pace and hold it for 15 minutes, then settle. The suffering teaches you exactly why going out too fast is expensive.
Key takeaways
- Pace for even effort, not even splits. Effort is the cost your body actually pays.
- Negative splits — second half faster than the first — are the most reliable path to a personal best.
- Pick one primary anchor: pace, HR, power, or RPE. Cross-check the others but don't react to all of them.
- Know your target intensity band for the distance you're racing, as a percentage of FTP or threshold HR.
- Fueling and pacing are one problem. Your pace cannot exceed what your fueling plan can sustain.
- The first 5K is where races are ruined. If it feels easy, that's the correct feeling.
- Practise pacing in training with race-pace intervals and race-simulation efforts. Don't learn it on race day.
Frequently asked questions
Should I pace by heart rate or by pace on the run?
For most amateurs on a flat, temperate course, pace is easier. On hilly courses, hot weather, or very long races where HR drift and thermal stress become significant, heart rate is more honest — it reports the cost your body is actually paying regardless of terrain. Experienced racers tend to anchor on effort or HR and use pace as a cross-check.
What is cardiac drift and how do I account for it?
Cardiac drift is the gradual rise in heart rate at a constant effort and pace as a long race progresses — typically 5–10% over 2–3 hours. It's driven by dehydration, thermal load, and fatigue. The practical rule: accept some drift, don't chase the earlier HR by slowing down. If your marathon plan had you at 160 bpm in the first hour and you're at 168 bpm in the third hour at the same pace and effort, that's normal drift, not a pacing failure.
How do I pace a race on a hilly course?
Pace by effort or power on the climbs and pace by target on the descents and flats. A common rule is to let your heart rate rise modestly on climbs (5–8% above average) but never redline, and to recover the time on the descents with smooth, relaxed downhill running. Splits will be uneven; effort should stay smooth.
Is it ever right to go out fast?
Rarely, and only in very short races where a hard early surge helps you settle into the leading pack or break away. For any race longer than 10K, the answer is essentially never. A fast start in a half marathon or marathon cashes in future seconds against a much larger late-race loss.
How conservative should my first mile be?
A useful rule for marathons and halves: run the first kilometre at about 5–10 seconds slower than your target average pace, then let the effort rise smoothly into the target range by kilometre 3–5. You will be passed in the opening minutes. You will catch most of those runners back in the final third. This is almost always the right trade.
What if I'm feeling terrible in the first 5 km?
Usually it's adrenaline, nerves, or cold muscles. Slow down 5–10 seconds per kilometre, breathe, settle. The first 15–20 minutes of any race almost always feel worse than they should. If you still feel terrible at kilometre 8, then it's worth reconsidering your target for the day — but don't make that decision in the first 3K.
How CoreRise helps you build and execute a pacing plan
Pacing is one of the specific places where having a coach who knows your training data is dramatically more useful than a generic calculator. CoreRise's AI coach sees your current FTP, your threshold pace, your recent race-pace sessions, your weekly load, and the context of the race you're training for. When you ask for a pacing plan, you don't get a template — you get a range anchored to what you've actually shown you can hold over the last training block.
The plan is built collaboratively inside a Performance Hub for the race. You can store the course profile, the expected conditions, your fueling plan, your target time, and the plan evolves as your training evolves. On race week, the coach reviews the final taper state, adjusts the pacing target if the conditions have shifted (heat, wind, altitude), and walks you through race-day execution. After the race, you debrief with the coach — what happened at kilometre 30, what you'd do differently — and that history feeds into every future race.
- Pacing targets anchored to your real current FTP and threshold pace, not a generic calculator.
- Race-specific Performance Hub stores the course, conditions, and fueling plan in one place.
- The coach adjusts pacing on race week based on taper state and forecast conditions.
- Practise sessions are prescribed with pacing as the explicit focus, not just volume.
- Post-race debriefs are remembered, so your next race starts from what you learned from the last one.
Antoine Boudet is the founder of CoreRise. He finished Ironman 70.3 Oceanside in 2026 and writes the evidence-based Learn hub articles for runners, cyclists and triathletes, drawing on the research literature and his own training.