Race Analysis: How to Debrief a Race Properly

Your finish time is just a number. What a race really says about your training is hidden in the segments in between: where you went out too fast, when heart rate started to drift, how much you actually ate, and in which third of the race it first started to hurt. Put those four traces together in 20 minutes and you learn more for your next block than from ten weeks of training by feel. This article walks through the process step by step, with the rules of thumb that tell you when something is off.

Why the debrief beats the result

A race is the only test under realistic conditions: full motivation, a real course, real aid stations, real competitors. As a data set it is therefore more valuable than any lab test — provided you read it correctly. The most common mistake is comparing only the finish time to the goal and concluding "the form wasn't there" or "the form was there". That is too crude: two athletes with the same time can have completely different problems — one started too fast, the other could not get anything into the stomach after kilometre 25.

The relevant question is therefore not "was I fast enough?" but "which decision cost me how much, and when?". The structure below is built for exactly that. It works for marathon, half marathon, triathlon and gran fondo; in triathlon the transitions become their own category.

Step 1: Split analysis — the fastest indicator

Divide the course into five to eight segments and compare pace per segment rather than cumulative times. The most important number is the difference between first and second half:

• 0 to 2 percent slower: excellent pacing. This is where very few amateurs land — and the range professionals treat as normal.
• 3 to 5 percent slower: normal for a marathon or gran fondo, especially in heat or on a rolling course. No action needed as long as fuelling held up.
• More than 6 percent slower: there is an explainable error here. Usually a too-fast start, less often low blood sugar or dehydration. The split pattern is the proof: a steady decline from kilometre 30 suggests fuelling, an early collapse after a very fast first third suggests pacing.
• Negative split: realistic mainly over 5 to 10 km and in the half marathon. In a marathon a negative split is possible but rare — it requires very disciplined first 21 km.

A second look is worth giving to the spread: if pace varies by more than 20 seconds per kilometre between segments, you paced by feel instead of by target. That costs measurably more energy at the same average pace, because every change of speed means additional acceleration work. More on race tactics by distance in Race tactics in running.

Step 2: Cardiac drift and heart rate trend

At constant effort heart rate slowly creeps up — that is cardiac drift, caused by fluid loss, rising core temperature and the redistribution of blood flow to the skin. Three to five percent across a race counts as normal.

What matters is the comparison between heart rate and pace: if heart rate rose while pace stayed the same, that was a pure fatigue and environment response. If heart rate rose and pace fell, the body was working against a limit — and then the question is whether it was an energy limit or a heat limit. The fluid balance answers it. How to classify drift properly is covered in Cardiac drift in running.

One signal almost everyone ignores: heart rate in the first ten minutes. If it is markedly higher than in training at the same pace, the start was too nervous — and training data and race data are not comparable. In cool weather after a good taper it should actually start lower than in training.

Step 3: Put the fuelling log next to the data

Most debriefs stop at pace and heart rate — yet fuelling is the lever with the biggest effect at distances beyond two hours. Write down what you actually consumed, not what you had planned:

• Carbohydrates per hour: the target is 60 to 90 grams, up to 100 grams beyond four hours with a trained gut. Below 45 grams per hour a bonk after three hours is almost guaranteed.
• Fluid per hour: 400 to 800 millilitres depending on temperature and sweat rate. In an autumn marathon the realistic range is usually 500 to 600.
• Sodium: 300 to 700 milligrams per litre of drink. Anyone running on water alone while sweating heavily risks cramps and a loss of performance late in the race.
• Gut tolerance: a single feeling word per race third — "fine", "sluggish", "nauseous" — says more than any spreadsheet. Nausea from kilometre 30 onwards is a training gap in the gut, not bad luck.

The decisive test is coincidence: does pace drop exactly when you last ate, or exactly when you did not? For many athletes the collapse sits 40 to 60 minutes after the last carbohydrate intake. That is not a coincidence, it is a measurable relationship — and fixable next block with one more gel per hour. The fundamentals are in Fuelling for the marathon and in the glossary under glycogen.

Step 4: RPE and feel per race third

The objective data tells you what happened; perceived exertion tells you how expensive it was. Note an RPE value from 1 to 10 plus one keyword for each third of the race:

• First third at RPE 5–6: exactly as it should be. At RPE 8 in the first third the start was too ambitious, even if the splits still look right.
• Middle third at RPE 7: controlled hard. This is where the race is decided.
• Final third at RPE 9–10 with stable pace: optimally spent. Anyone who could still chat comfortably there left potential on the table.

The relation to the finish time matters: a race at RPE 10 with a good time is a successful race. A race at RPE 10 with a poor time is a sign of a problem — not of missing fitness. Anyone who fails to separate the two trains more after every weak race instead of smarter.

The five guiding questions

If you do not want to drown in data, work with five questions. They cover 90 percent of the relevant insight and can be answered in 20 minutes:

• Was the start too fast? Compare the first 20 percent of the course to target pace. More than five seconds per kilometre quicker is a mistake.
• Where exactly did it first hurt? Note the kilometre. Anything beyond 60 percent of the distance is normal, anything before it is a signal.
• Did I eat and drink enough? Actual amounts against the hourly targets.
• Was the course what I expected? Elevation, surface, corners, wind. Surprises are planning errors, not a run of bad luck.
• What would I do differently next time — one thing? Exactly one. More than one change cannot be attributed causally.

Triathlon and gran fondo: what to add

In triathlon the transition times become a discipline of their own in the debrief. T1 and T2 are measurable and trainable: whoever loses 90 seconds in the transition zone loses them again in every race, because the cause is almost always the same — badly organised equipment or missing routine. Compare your transition time with the mid-pack of your age group; more than two minutes behind is a training gap, not chance. Details in T1 and T2: the fourth discipline in triathlon.

In a gran fondo the key metric is not average speed but normalised power relative to FTP. Anyone riding above 85 percent of FTP in the first 50 kilometres pays for it on the final climb. A look at the power distribution per segment reliably shows whether you overcooked it on the climb or in the group. For the basics of comparing load, see Understanding CTL, ATL and TSB.

From finding to adjustment: the 15 percent rule

Exactly one consequence follows from the debrief — and it stays small. The rule is: two or three levers at most per training block, each change no more than 15 percent versus your current level. Anyone who raises volume by 30 percent after a weak race mainly raises injury risk; anyone who lifts easy pace by 40 seconds per kilometre destroys the 80/20 distribution.

Typical, defensible conclusions from a race analysis:

• Positive split above six percent: train pace discipline, not endurance. One session per week with fixed splits on the treadmill or behind a pacer.
• Collapse after three hours despite good splits: raise carbohydrate intake by 10 to 15 grams per hour and build a gut-training session into the long run.
• Cardiac drift above eight percent: measure your sweat rate (weigh in and out), adjust fluid intake, check electrolyte content.
• RPE too high in the first third: extend the warm-up and deliberately start the first kilometres one zone lower — not getting faster, but staying even.
• Legs empty from kilometre 30 with no energy signal: strength endurance and eccentric loading are missing. Add downhill runs and strength work for the quadriceps chain, see Strength training for runners.

Topically fitting for the build after the race: the 16-week marathon plan and the deload week, so the debrief does not slide into training that starts too early.

Common mistakes in race analysis

• Analysing on race day. Right after the finish, emotion dominates — either euphoria or disappointment. Both systematically distort how you read the data.
• Looking only at the finish time. The time is the product of dozens of decisions. Without splits, heart rate and fuelling it stays a number without a diagnosis.
• Changing everything at once. Anyone who alters training, fuelling, shoes and tactics simultaneously cannot say at the next race what helped.
• Ignoring feel. RPE and keywords are not esoteric: they explain why the same pace feels different in week 8 than in week 16.
• Analysing and doing nothing. The most common mistake of all. A debrief without one concrete, scheduled change in the plan is a diary entry, not a training stimulus.

How Peakora handles race analysis

In Peakora every race lands in the training log as an activity — with splits, heart rate trend, TSS and a comparison to the planned session. Because the engine tracks your load continuously (CTL, ATL and TSB), it is immediately visible after the race how deep the stimulus actually went and how many days of recovery are realistic. The following week adapts to that instead of running on rigidly by calendar. And because every session carries a written rationale, you can trace back later which training decision led to which race result — exactly the comparability that makes a debrief worthwhile in the first place.

Frequently asked questions