Diagnosing a Missed Sub-40 Attempt A Step-by-Step Sequence
You just missed sub-40 by a handful of seconds, and you can't tell whether it was pacing, fitness, or just a bad day. Missing sub-40 by a handful of seconds tells you almost nothing on its own — you need to read your splits to find out why. I've sat down with athletes the day after a near-miss more times than I can count, and the pattern is always the same: they know they missed it, but they can't say whether it was pacing, fitness, or the weather. That distinction changes everything about what you do next. This page walks you through your own race data — kilometre by kilometre — to arrive at a specific verdict, rather than a vague sense that "it just wasn't your day."
The Three Usual Suspects — And How to Tell Them Apart Fast
A missed sub-40 traces back to one of three causes, and you can identify which one from your own splits and race conditions. Pacing error shows up as a positive split with a fast first kilometre. Fitness shortfall shows up as even pacing, heart rate maxed out, and pace fading from kilometre 6-7 onward no matter what you try. Conditions shows up as even pacing and controlled effort, but a target that the temperature or wind made unreachable that day.
Here's the fastest check, before you go any deeper: if kilometre 1 was more than 5 seconds/km faster than target and the back half faded, treat pacing as the cause before anything else. It's the most common verdict by a wide margin, and it's also the easiest one to fix.
Reading Your Own Splits to Find the Fade Point
No page walks you through actually reading your own kilometre splits, so here's the protocol I use with athletes. List your km-by-km splits against flat target pace — 4:00/km for a 40:00 goal. Calculate the delta at each kilometre. Then find the fade point: the kilometre where that delta crosses +5 seconds and doesn't recover.
Match your shape against three patterns I see repeatedly in athlete race data, not generic categories invented for this page:
| Pattern | Split Shape | Verdict |
|---|---|---|
| Fast-then-fade | Km1-2 at 3:50-3:55, fade begins km 6, finishes 40:20 | Pacing error — early speed cost more than it banked |
| Flat-then-collapse | Even splits through km 7 at 4:00-4:02, then km 8-10 blow out past 4:15 | Fitness ceiling — aerobic or lactate system ran out regardless of discipline |
| Even-but-slow | Consistent 4:05-4:08 throughout, no fade, no surge | Conditions or an off-day — not a training gap |
Find your own shape in that table before you read any further. Everything below builds on whichever pattern matches your race.
How Much a Fast Start Really Costs You
If your shape was fast-then-fade, here's the number I use when reviewing an athlete's splits: running 10-15 seconds/km faster than target for the first 1-2km costs 30-45 seconds back in kilometres 7-10. This isn't a rounding error — it's non-linear lactate accumulation past steady state. A runner who "banks" 20 seconds in the first 2km typically loses 35-50 seconds later. That's a net loss, even though the clock looked encouraging early on.
Worked example: goal pace 4:00/km, actual km1-2 run at 3:48/km — 12 seconds/km fast. Expected fade cost is roughly 35-40 seconds across kilometres 7-10, turning what should have been a 39:55 into a 40:15-40:30. The fix is straightforward in principle, harder in practice: target even or slightly negative splits, with the first 5K run 2-3 seconds/km slower than target and the second 5K at or slightly under target, rather than banking time early.
Adjusting for Heat and Conditions After the Fact
If your shape was even-but-slow, check conditions before you assume anything about your fitness. Above 18-20°C, expect roughly 1-2% pace degradation for every additional 5°C. A 25°C race morning makes a sub-40 effort functionally a sub-40:24 to sub-40:48 effort, even with perfect execution.
Worked example: target 40:00, race-day temperature 26°C — 6°C above the threshold. Expected degradation is roughly 1.2-2.4%, meaning a genuinely "perfect" effort that day was realistically a 40:30-41:00 performance. That is not a training failure. Wind is a secondary factor worth noting qualitatively too — a sustained headwind for any meaningful stretch of the course adds a comparable cost that doesn't show up in temperature figures alone.
The Full Diagnostic Sequence
Here's how the pieces above fit together into one ordered walk-through. Step 1: calculate your km split deltas against target pace and identify which of the three fade patterns matches. Step 2: check race-day temperature against the threshold — if it was 6°C or more above 18-20°C, weight conditions heavily in your verdict regardless of split pattern. Step 3: cross-reference the fade pattern with conditions.
Fast-start-then-fade in cool conditions means pacing error — train pacing discipline before your next attempt. Flat-then-collapse in cool conditions means fitness ceiling — you need another training block, likely with more threshold or lactate work. Even-but-slow in hot conditions means the day beat you, not your training — a reattempt is the fix, not more training. The verdict maps directly to what you do next, covered below.
Regrouping Mentally After a Near-Miss
Missing by under 30 seconds after a controlled, even-paced effort is a strong signal you're fitness-ready and the gap is now execution or conditions. That's a faster fix than a fitness gap — genuinely good news, not failure, and I'd encourage you to reframe it that way rather than sit with it as a disappointment.
One anonymised example worth sharing: an athlete of mine missed sub-40 by 6 seconds twice, with an even-paced effort both times. It looked like bad luck on the surface. Once I reviewed the splits properly, it was actually a fitness-ceiling issue, not pacing — the fade pattern was flat-then-collapse both times, just a small one. She broke 40 on the third attempt after a repeat focused block, not by simply "trying harder" on race day. The lesson: don't guess at the verdict. Check it.
The concrete action here is simple. Review your split data within 48 hours while the race is fresh, assign a specific verdict using the sequence above, then stop re-running the race mentally. Open-ended rumination without a specific diagnosis is what turns one near-miss into a demoralising pattern across multiple attempts.
When and How to Plan Your Next Attempt
Your reattempt timing depends entirely on your verdict. Pacing-error verdict: reattempt in 3-4 weeks is enough — no new fitness needed, just a pacing-discipline focus, with goal-pace intervals that enforce strict early-km discipline in the interim. Conditions verdict: reattempt as soon as a suitable race and weather window appears — there's no training gap to close, the same fitness already applies.
Fitness-ceiling verdict: this one needs a fresh 6-8 week focused block, or a repeat base cycle if the ceiling was severe, before you reattempt — not just a quick turnaround race. This is Dominique de Rooij's process — the verdict-to-next-step mapping I actually run athletes through after a near-miss, not a generic checklist. Stated plainly: repeatedly reattempting on the same fitness without addressing a fitness-ceiling verdict just produces the same near-miss again.
Frequently Asked Questions
How do I tell if I missed sub-40 because of pacing, fitness, or conditions?
Read your own kilometre splits. A fast first kilometre followed by a back-half fade points to pacing error. Even pacing with heart rate maxed and a fade from km 6-7 onward regardless of effort points to a fitness shortfall. Even pacing, controlled effort, but a target that was simply unreachable that day points to conditions. The fastest check: if km 1 was more than 5 seconds/km faster than target and the back half faded, treat pacing as the cause before anything else.
How much does starting too fast in the first kilometre actually cost me?
Running 10-15 seconds/km faster than target for the first 1-2km typically costs 30-45 seconds back in kilometres 7-10, because lactate accumulation past steady state is non-linear. A runner who banks 20 seconds early often loses 35-50 seconds later — a net loss even though the clock looked good at the start.
How much slower should I expect to run in the heat versus ideal conditions?
Above 18-20°C, expect roughly 1-2% pace degradation for every additional 5°C. A 26°C race morning — 6°C above the threshold — costs roughly 1.2-2.4%, meaning a target of 40:00 realistically becomes a 40:30-41:00 performance even with perfect execution. That is not a training failure.
What should I look at in my own splits to diagnose what went wrong?
List your km-by-km splits against flat target pace, calculate the delta at each kilometre, and find the fade point — the km where the delta crosses plus 5 seconds and doesn't recover. Match the shape against three patterns: fast-then-fade (pacing error), flat-then-collapse (fitness ceiling), or even-but-slow throughout (conditions or an off-day).
How long should I wait before attempting sub-40 again?
It depends on your verdict. A pacing-error verdict needs only 3-4 weeks before reattempting, with a focus on pacing discipline. A conditions verdict needs no training gap at all — reattempt as soon as a suitable race and weather window appears. A fitness-ceiling verdict needs a fresh 6-8 week focused block, or a repeat base cycle if the ceiling was severe, before you go again.
Is it normal to miss a goal time by just a few seconds multiple times?
Yes, if the verdict each time is pacing or conditions — those are execution and circumstance issues, not fitness gaps, and they can recur until you specifically correct them. It is not normal, and worth addressing directly, if the verdict is a fitness ceiling each time. Repeating the same fitness without closing that gap just produces the same near-miss again.
Should I change my training or just my race-day execution for the next attempt?
That depends entirely on your verdict. A pacing-error or conditions verdict means your training is fine — the fix is pacing discipline or timing, not more training. A fitness-ceiling verdict means execution wasn't the problem, and you need another focused training block, typically with more threshold or lactate work, before your next attempt.
How do I stay motivated after narrowly missing a big goal?
Review your split data within 48 hours while the race is fresh, assign a specific verdict, then stop re-running the race mentally. Missing by under 30 seconds after a controlled, even-paced effort is a strong signal you're fitness-ready and the gap is execution or conditions — genuinely good news, and a faster fix than a fitness gap would be.
Some Other Pages You May Like
About the author
Dominique de Rooij (Dom)
Advanced Running Coach certified by Athletics Australia with 20 years of writing about running and over a decade coaching runners — from first-timers to marathoners. Dom's beginner programs have guided thousands of runners and been praised above plans from Jeff Galloway, Hal Higdon, and Runner's World. Now over 50, Dom still loves trail running, parkrun, and the coffee after.
Free weekly coaching • Join 3,500+ runners
Train Smarter, Not Just Harder
Get your free guide when you join the BRT Coaching Letter
No spam, ever. Unsubscribe in one click, any time.
What's New?
-
Why the 10K Is a Lactate Threshold Race | BRT
The 10K is raced 5-10% faster than lactate threshold — here's what that does to your pacing, and how to use it to race smarter. -
The PCr Fast-Start System for 5K Racing: Science & Execution | Best Running Tips
The physiological case for going out slightly fast in a 5K — and the exact execution rule (how fast, how far, what cues) that turns science into a race plan. -
5K Post-Race Debrief: Turn Race Data Into Training Decisions | Best Running Tips
A structured 5-question framework for analysing your 5K: explain the time gap, read your pacing signature, audit in-race decisions, and identify the training adjustment.