Race buildup is full of inherited folklore. RunNerd grounds periodization, taper, and pacing in physiology — so you decide on evidence, not by mimicking your fastest friend.
You’ve got a race on the calendar and a goal attached to it, and suddenly every decision is in service of a date. The problem is that race buildup is thick with inherited rules — the 20-miler three weeks out, the giant pasta dinner, “never run race week” — and most of it gets passed down without anyone checking whether it’s true.
RunNerd grounds the choices in physiology. It tags the phase you’re in — base, build, peak, taper — and constrains intensity to it, holding the line on easy running during base even when your fitness is asking for more. It maintains the fitness/fatigue/form trio (CTL, ATL, TSB) and steers your taper so form lands fresh-but-not-flat on race morning. It models the pace you can actually hold from your recent long and tempo runs, then prescribes a conservative first-half buffer, because going out too fast is the single most reliable way to blow a race.
It treats fueling as part of training: long runs over ~75 minutes get a carbs-per-hour note, and it watches late-run pace fade as an under-fueling flag rather than a fitness one — so race day uses food your gut already trusts. And when the forecast turns hot, it softens your prescribed paces rather than holding you to a target you set in cool spring air.
The goal isn’t to follow a schedule. It’s to understand why this taper, this pace, this fuel — and arrive at the line having made evidence-based decisions.
Getting to a start line in shape is one skill. Getting through 5K, 10K, half, or marathon distance without falling apart is another. This pillar pulls together the research on race preparation — how training load should be structured in the weeks and months before race day, how to pace and fuel once the gun goes off, and how conditions like heat and sleep debt should change the plan you wrote months earlier. It's organized roughly in the order these decisions come up: build the engine, protect it from injury, tune it in the final weeks, then execute on race day itself.
A training block isn't just "run more, then run less before the race." It's phases, each doing a specific job. Base work builds mitochondria and capillaries through mostly easy running; skipping straight to hard intervals blunts those adaptations. Build and peak phases shift the stimulus toward threshold and race-specific work. How you split easy-versus-hard time within those phases matters too — polarized training (mostly easy, some very hard, little in between) beats pyramidal on average, but not for everyone, and the research increasingly favors a pyramidal base that shifts polarized in the final 6-8 weeks before racing.
→ Read: Why a 16-week plan beats a 16-week grind — the case for periodization, 80/20 Isn't for Everyone, Pyramidal First, Polarized Later, How Tempo Runs Train Your Body to Clear Lactate Faster
The old "10% rule" for weekly mileage doesn't hold up well under scrutiny — injury rates look similar whether you increase by 10% or closer to 30%. What does predict injury is a single long run that spikes too far past your recent normal: runs over 110% of your longest effort in the past month carry meaningfully higher overuse-injury risk. The long run should also stay easy most of the time. Turning it into a weekly time trial blunts recovery and drags down the workouts that are actually supposed to be hard.
This applies whether you're building a first 10K, a first half marathon, or a marathon block: grow the long run gradually, hold it under roughly 30% of weekly volume, and schedule cutback weeks on a fixed cadence rather than waiting for something to hurt.
→ Read: Forget the 10% Rule — Watch Your Long Run Instead, Long-run development: the slow drift that builds the engine, Why your long run shouldn't always be your hardest run, From 5K to 10K: The 500-Meter Rule, Your First Half Marathon: How to Build the Plan That Gets You There
Under about 90 minutes, water is enough — your glycogen stores cover the work. Past that point, you're racing the clock on fuel, and the science has moved the target upward: most runners should aim for 60-90 g/hr of carbs in a marathon, not the 22-35 g/hr average that leaves people under-fueled and more likely to hit the wall around mile 20. Half marathons need less (30-60 g/hr) since glycogen stores can cover more of the race unaided. Above 60 g/hr, a glucose-fructose blend matters because a single sugar source maxes out gut absorption. None of this should be improvised on race morning — carb-loading in the final 1-3 days tops off stores, and every fueling number should already be rehearsed in training.
→ Read: Mid-run fueling: when carbs start to actually matter, Half Marathon Fueling: The 30-60g Carb Rule That Actually Works, How Many Carbs Per Hour for a Marathon, Why Marathoners Hit the Wall at Mile 20, Why Most Marathoners Leave Time on the Table by Under-Fueling, Race-week nutrition: carb-loading and what to eat before a race
Across distances, the data says the same thing: even or negative splits beat fast starts. Adrenaline and a taper make goal pace feel deceptively easy in the first mile, but going out 5-10% too fast burns disproportionately more glycogen and pushes you past aerobic threshold before you're warmed up — a deficit that shows up as a mile-20 fade or a 10K collapse at kilometer 7. The practical fix is consistent: ease into the first 2-3K, settle into goal pace, and save the last portion of the race for whatever's left. Marathon-specific data goes further — negative splits aren't just safer, they measurably preserve glycogen and control cardiac drift better than even pacing.
→ Read: Your First 10K: Why Starting Slow Wins the Race, The Three-Part Trick to Pacing a Faster 10K, Race-day pacing for your first 5K, 10K, or half, Negative splits aren't a brag — they're physiology, The long-run HR climb: cardiac drift over the marathon distance
Heat doesn't negotiate with a goal time set in cool training — it diverts blood to the skin, raises heart rate at any given pace, and slows everyone. Dew point, not the thermometer, is the number that actually predicts how hard a hot run will feel. Three to five weeks of deliberate heat exposure before a race can offset some of this by lowering resting heart rate and improving VO2max, even for a race run in cool weather. Sleep matters on a similar timescale in both directions: chronic short sleep degrades aerobic performance and injury resilience, but a single night of extra sleep before a key session or race measurably improves next-day output. None of this fitness disappears in a taper — cutting volume 40-60% while holding intensity preserves fitness and dissipates fatigue, which is the entire point of the final two weeks.
→ Read: Adjusting your race goal when it's hot, Why dew point predicts how hard your run will feel, Train Hot, Race Fast, Sleep Is Your Cheapest Performance Drug, One Extra Hour of Sleep Makes You a Better Runner Tomorrow, How to taper for a race without losing fitness, Fitness, fatigue, and form: the three numbers behind a good taper
Two runners can share the same VO2max, threshold, and economy and still finish miles apart — because those numbers don't hold steady under fatigue. Durability, the ability to preserve threshold and economy deep into a race, is now treated as a fourth pillar of endurance performance alongside the classic three, and it's trainable through marathon-pace work done on already-tired legs. Altitude exposure (Live High Train Low) offers a smaller, more logistically demanding edge, mostly relevant to runners who can train or travel at elevation before a goal race.
→ Read: Why You Fall Apart Late in a Race — and How to Fix It, Durability: The Fourth Pillar of Marathon Performance, The Fourth Pillar of Marathon Fitness, Why elite runners sleep high and train low, The 1% Treadmill Trick Doesn't Fully Cancel Out Indoor Running
This pillar sits alongside the other topic clusters on RunNerd's science pages — training load, recovery, and injury prevention each get their own deeper treatment — but race-ready is where those threads converge into the specific decisions that determine how your fitness actually shows up on race day.