TL;DR
- Optimal volume cut: 55% across 2 weeks. Week minus 2 holds 80 km with long run shortened to 36 km; week minus 1 drops 60% to 32 km.[3]
- Intensity retention 90%, frequency cut 20%. Keep race-pace work sharp; cut session duration rather than intensity.
- The taper is a recovery window, not a fitness window. All adaptation has already happened; the taper just lets the body absorb the prior 12 weeks' work.[1]
The taper is one of the most-debated parts of marathon training: too long and fitness slides; too short and the runner arrives over-fatigued. The published meta-analyses converge on a 2-week structure with a sharp volume reduction in the final week. Here is what the engine returns for a representative 80 km/week peak runner.
The scenario
A trained marathoner with a peak weekly volume of 80 km. Two intensity sessions per week throughout the build (tempo plus VO2 work). Wants the optimal volume reduction pattern for the final 2 weeks before a marathon, including the long-run length for the pre-race weekend.
What the calculator returns
Running the inputs through the Race Week Taper tool:
Engine input
peak_volume = 80 km
peak_intensity = 3 (high intensity sessions/week)
taper_start_weeks_before = 2
race_distance = marathon
Engine output
optimalVolumeCutPct = 55%
raceDistance = marathon
taperStartWeeksBefore = 2
intensityRetentionPct = 90%
frequencyReductionPct = 20%
Weekly plan:
Week -2 volumeKm = 80 volumeCutPct = 0%
intensitySessions = 2
longestRunKm = 36
"Cut weekly long run by ~25%; keep intensity sharp"
Week -1 volumeKm = 32 volumeCutPct = 60%
intensitySessions = 2
longestRunKm = 14.4
"Race week — short shakeout efforts, no new stimulus,
prioritize sleep and carbs" Two weekly templates. Week -2 holds the same overall weekly volume (80 km) but cuts the long run from typical 42+ km down to 36 km. Week -1 drops to 32 km — a 60% volume reduction — while retaining two short intensity sessions and a 14.4 km longest run on the weekend before race day.
Reading the numbers
The volume reduction curve is steep in the final week and modest in the second-to-last week. This matches the published recommendation from the Bosquet/Mujika meta-analysis: 41 to 60% volume reduction across 2 weeks produces the largest performance gain on race day[1].
Two-week taper math
Pre-taper weekly volume 80 km
Week -2 weekly volume 80 km (no cut, but shorter long run)
Week -1 weekly volume 32 km (60% cut)
Long run sequence:
Week -3 40 km (peak long run)
Week -2 36 km (10% cut from peak)
Week -1 14.4 km (60% cut from week -2)
Race day 42.195 km
Frequency:
Pre-taper 6 runs/week
Week -1 ~5 runs/week (20% reduction) The week -2 long run at 36 km is the last "fitness" stimulus of the cycle. Week -1's 14.4 km longest run is a "shake-out" — enough to maintain stride mechanics without adding fatigue. Some runners cut this further to 10 to 12 km; the published recommendation lands around 14 km for an 80 km/week peak.
Where the formula breaks
Low-volume runners taper too much. A runner at 50 km/week peak does not need a 60% reduction in the final week. Cutting from 50 km to 20 km feels lethargic; better to drop to 30 to 35 km with the same intensity touches. The engine's 55% cut is calibrated for mid-volume marathoners.
High-volume runners taper too little. A runner at 130 km/week peak benefits from a 3-week taper rather than 2 weeks. The accumulated fatigue from sustained high mileage takes longer to clear. Above 100 km/week peak, push the taper start to week -3.
The intensity assumption. The engine assumes the runner's peak weeks include 2 to 3 intensity sessions. A "long, slow, easy" marathon build with no quality work does not need the same intensity retention; in those cases, 2 light hard sessions during the taper add stimulus that was missing rather than maintain fitness.
The race week itself
The engine's week -1 prescription expands into a day-by-day plan:
Mon (race -6) 4 km easy + 4 × 100 m strides
Tue (race -5) 6 km easy + 5 × 30 sec @ marathon pace
Wed (race -4) Off, or 30 min easy spin
Thu (race -3) 4 km easy + 4 × 100 m strides
Fri (race -2) 3 km easy + 3 × 100 m strides
Sat (race -1) Off, or 20 min easy shakeout
Sun RACE
≈ 17 to 20 km total
+ race Short runs every day except Wednesday and Saturday. Strides keep neural patterns sharp without adding fatigue. The 17 to 20 km of pre-race running matches the engine's 14.4 km longest weekly run plus shorter sessions on other days.
Sleep, hydration, and stress during taper
The taper is also a behavioral block, not just a training block. Three high-impact practices:
- Add 30 to 60 min of sleep per night. Sleep is when most of the supercompensation actually happens; running 8 to 9 hours instead of the usual 7 to 7.5 maximizes the adaptation window.
- Add 500 to 700 ml of fluid per day starting week minus 1. Marathon-day glycogen storage binds water; under-hydration in the taper week shows up as 1 to 2 kg of "missing weight" on race-day morning compared to a properly-loaded runner.
- Avoid new stressors. No new shoes, no new race-day nutrition test, no travel that breaks sleep patterns past 1 hour. The body's adaptation system is already busy.
Cross-checking against carbohydrate loading
The taper week is also the carb-loading window. From Wednesday onward, daily carbs should climb to 7 to 10 g/kg of bodyweight. Pair the taper with the Macro Cycling Calculator for a race-week macro plan. Under-eating during taper is the most common race-week error; the body is doing less work but needs more substrate to top off muscle glycogen.
Related tools and follow-ups
- Race Week Taper — the engine used here.
- Running Pace Calculator — convert race-pace targets into per-kilometer splits.
- Marathon Pace Elevation — final course-specific pacing plan.
For broader context: Marathon taper volume reduction curve, Marathon pace elevation validated, and How to plan a deload week cover the broader recovery-cycle framework.
FAQ
How much should you cut volume in the marathon taper? The engine returns an optimal volume cut of 55% for a 2-week marathon taper from 80 km/week peak. Week minus 2 holds 80 km with the long run cut by 25%; week minus 1 drops to 32 km (60% cut).
Should intensity drop during the taper? No. The engine returns 90% intensity retention through the taper. Keep race-pace and tempo sessions sharp; reduce only the duration. Cutting intensity along with volume causes performance regression on race day.
How long should a marathon taper be? 2 weeks for trained marathoners is the central recommendation. 3 weeks works for high-mileage runners (over 100 km/week peak); 1 week works for lower-mileage runners (under 50 km/week peak). The 80 km/week peak in this case sits squarely in the 2-week band.
References
- 1 Effects of tapering on performance: a meta-analysis (Bosquet, Mujika) — Medicine and Science in Sports and Exercise (2007)
- 2 Tapering and performance: a critical review (Mujika, Padilla) — Sports Medicine (2003)
- 3 Methodology — Race Week Taper — AI Fit Hub