How to Use Your Past Race Data to Set a Realistic Finish Time Goal
by The Next Race
Most triathletes set their race goals the same way: they pick a number that sounds good and work backwards.
Sub-2:30 for an Olympic. Sub-5:00 for a 70.3. Round numbers, aspirational but not obviously impossible. The problem isn't the ambition — it's that the number has no relationship to the actual training being done or the performances already on record. It's a wish dressed up as a goal.
There's a better way. Your past race data — splits, training load, conditions — contains a much more accurate prediction of your next performance than any number you can pull from the air. You just need to know how to read it.
Start with your splits, not your finish time
Finish time is a summary. Splits are the story.
Pull your last two or three races and look at each discipline separately. What did you swim? What did you ride, in watts or pace? What did you run, and — critically — how did that run pace compare to your standalone run pace in training?
The ratio between your training run pace and your race run pace is one of the most honest indicators of how well your race is going. Athletes who run close to their training pace off the bike have executed well. Athletes who run 30–45 seconds per kilometre slower than their training pace have either gone too hard on the bike, under-fuelled, or both.
If your run consistently falls apart, your goal time needs to account for that — not ignore it and hope this time will be different.
The training-to-race translation
Your training data predicts your race performance more reliably than last year's race result, because training data is unaffected by bad days, mechanicals, heat, and the hundred other variables that make individual race results noisy.
Look at three metrics from your most recent build phase:
Your functional threshold power or pace on the bike — the effort you can sustain for roughly an hour. A well-calibrated athlete can hold approximately 70–75% of FTP for an Olympic-distance bike leg. If your FTP is 220 watts, your target race power is around 154–165 watts. That translates directly to a predicted bike split.
Your lactate threshold run pace — the pace you can sustain for 40–60 minutes at hard but controlled effort. Your Olympic run is 10km. Most athletes can hold roughly threshold pace minus 10–15 seconds per kilometre for a 10km off the bike, assuming the bike was ridden at the right effort.
Your open water swim pace from training. Not your pool pace — your open water pace, with a wetsuit if you're wearing one, sighting every 8 strokes. This is almost always slower than your pool pace and is a much better predictor of race swim time.
Add up the predicted splits. Add 3–5 minutes for transitions. That's your data-backed finish time.
What the comparison tells you
Now compare that number to your aspirational goal.
If they're within 5 minutes of each other, your goal is realistic. Train to it.
If your data-backed prediction is 10–15 minutes slower than your goal, you have a gap to close. That gap is useful information — it tells you exactly where the time needs to come from. A 10-minute gap at Olympic distance is roughly: 2 minutes in the swim, 5 minutes on the bike, 3 minutes on the run. Each of those requires specific training interventions, not just general fitness.
If your data-backed prediction is faster than your aspirational goal, you've been sandbagging. Raise the target.
The goal-setting mistake
Athletes set finish time goals and then train generically. They don't connect the goal to specific split targets, and they don't connect the split targets to specific training adaptations.
A goal time is only useful if it's decomposed into splits, and splits are only useful if they're connected to training metrics you can actually measure and improve. The chain needs to run all the way through — from finish line back to Tuesday's threshold session — or the goal is just a number on a spreadsheet.
Your data makes that chain visible. Use it.