Your fitness is already decided over the last fourteen days. The only thing still in your hands is how much accumulated fatigue you carry to the line.
- A workout turns into performance weeks after you run it, while the fatigue it produces lands immediately: two weeks out, every session you add pays the cost and never collects.
- Cut volume. Paces and the number of weekly runs stay exactly where they are.
- First week, roughly a third fewer miles. Final week, close to half, with only two short race-pace sessions.
- The heavy legs of the last few days show up even when everything is going the way it should.
Fourteen days out, something predictable happens: the build block ends, two apparently empty weeks are left over, and the feeling of not being ready asks to fill them. One more long run for peace of mind. A confirmation interval session. A 10K (6.2 miles) test to see where you stand. Then you reach the corral with legs that answer half a second late, and no plausible explanation.
The Week When Adding Makes Everything Worse
Over the last fourteen days you build nothing. The work that carries you through the race is the work you already did in the months before: a session becomes performance weeks later, while the fatigue bill arrives the same day. A workout added now pays the price and has no time to collect the return.
The reverse holds too, and that’s the part that frightens people most. Cutting back erases nothing. In the first two weeks of reduced load the decline is minimal and touches variables that restore themselves within days. The soft legs on the Thursday before the race are clearing fatigue, and clearing fatigue is the only work left on the schedule.
The taper is where you decide how much freshness reaches the line.
What Gets Cut and What Stays
Volume comes down, everything else stays put. The paces are the ones you always run, the weekly sessions stay the same number: what shrinks is the length of each one. As a starting reference, the first week loses about a third of your usual mileage and the last one gets close to half, with the numbers scaled to your normal load rather than to a universal chart.
Same route, lighter pack. The paces you know stay in your legs. What disappears is the portion of work that existed to accumulate stimulus and would now produce only tiredness.
Race-pace segments hold the mechanics and your sense of pace together, and cutting volume while leaving intensity and frequency untouched is the combination that produces the best results in the available research. One caution: the quality work in these two weeks is short by definition, four or five reps where you used to run eight.
The confirmation test ten days out is the least useful thing you can do right now. If it goes well it tells you what you already knew. If it goes badly it brings you to the line with a doubt and a hard session in your legs. The same logic applies to long mileage: the last genuinely productive long run happened weeks ago, and next Sunday’s exists only to keep the movement open.
The Plan, Day by Day
The calendar starts on the Monday that falls thirteen days before the race and assumes a Sunday start. Intensity appears twice in two weeks, always at the pace you’ll race and always over short distances. If you train four times a week instead of six, drop the easy days and leave the two quality sessions and the long run intact.
| Day | Session | Purpose |
|---|---|---|
| Mon (W1) | Rest or 30 min very easy | Closes out the build block |
| Tue (W1) | 5 × 1,000m at race pace, 2 min recovery | Pace unchanged, session volume down by a third |
| Wed (W1) | 40 min easy | Holds the weekly frequency |
| Thu (W1) | Full rest | First clean cut to volume |
| Fri (W1) | 45 min easy + 5 × 80m strides | Fast legs at no metabolic cost |
| Sat (W1) | Rest or 30 min easy | Sets up the next day’s long run |
| Sun (W1) | Final long run, a third shorter than the cycle’s longest, all easy | Keeps the feel of the distance without adding fatigue |
| Mon (W2) | Rest | Absorbs the long run |
| Tue (W2) | 35 min easy + 6 strides | Wakes the mechanics back up after the rest day |
| Wed (W2) | 8 × 400m at race pace, 90 sec recovery | Last quality session, half the volume of the first Tuesday |
| Thu (W2) | 30 min easy | The worst-feeling day, with no consequences |
| Fri (W2) | Rest | Last full recovery |
| Sat (W2) | 20 min very easy + 3 strides | Opens the legs without loading them |
| Sun (W2) | Race |
The last three days are where discipline counts most, because there’s nothing left to do and time stretches out. The nights that weigh on performance are Thursday’s and Friday’s, not the one before the race, which almost nobody sleeps well: lose a few hours on Saturday night and the rest you need is already banked. If the wait on the day before starts to take up space, Saturday morning’s short run is the right place to unload it, provided it stays short. Three miles is more than enough.
Heavy Legs Two Days Out, and Why You Shouldn’t Read Them
They almost always show up between three and two days before the race: wooden legs, a stride that feels short, breathing that arrives sooner than expected across twenty minutes of easy running. In that window the body is still rebuilding after the cut in volume, and the sensation lags behind the real state. What to do about it: ABSOLUTELY NOTHING. The signals that deserve a different decision are different ones, and you recognize them without effort — localized pain that changes the way you land, a fever, an active respiratory infection. Everything else is background noise across these forty-eight hours.
What Changes If It’s Your First Race
Anyone running three times a week arrives here with far less accumulated fatigue, and so with less to clear. The cut gets smaller, around a quarter of your usual volume, and it compresses into seven to ten days instead of fourteen: two weeks of reduction on low mileage costs more rhythm than it removes tiredness. The rule that stays identical is frequency. Runs get shorter, they don’t disappear, because at this level the real risk is showing up at the line after four days without running and discovering in the corral that your pace has become a hypothesis.
Distance matters too. On a 10K, most of the accumulated fatigue clears in a week or so, while on a marathon the weight of the last long run takes longer to absorb and the two-week window is the reasonable minimum.
The only work left to you is reaching the start without accumulated fatigue. Everything else is already in the bank.