The Pacing Plan Problem Nobody Talks About Until Mile 20
Same athlete, different name — I keep seeing this one.
Strong training block. Fitness is there. Then race week hits, and the pacing plan comes from a goal number — not from what the data actually says about that day.
Back half falls apart. Not from lack of fitness. From a plan that was never built on the athlete's real numbers in the first place.
This shows up constantly, and it's rarely a training gap. It's a data gap. → Threshold pace isn't the same as goal pace. → Fatigue-adjusted splits aren't the same as flat splits. → "What I think I can hold" isn't the same as "what my last 3 sessions say I can hold."
I built a free Race Preparedness Checklist to help athletes catch this — and four other blind spots — before race day, not after. It covers baseline data, fueling, recovery, race execution (pacing under fatigue included), and strength/durability. Takes a few minutes, and flags exactly where your prep has a gap.
And if pacing-under-fatigue is the piece you're missing: I'm finishing an 8-week Race-Ready Playbook that sits on top of whatever training plan you're already running — it walks through baseline testing, fueling, a race simulation dress rehearsal, and a full pacing/execution strategy so the back half doesn't come down to guesswork. Dropping soon — comment below to get it first.
