How to Structure a Recovery Week

Ask a self-coached runner about their taper and they can usually describe it. Ask about their recovery weeks and you'll often get a shrug - "I just take it easier sometimes." That vagueness is exactly why recovery weeks are the piece of a training block most likely to get quietly skipped, and skipping them is one of the more reliable ways to turn a good block into a stalled one.

Not the taper - the other unload

The taper is a one-time, progressive unload in the final two to three weeks before a specific race, and it deliberately keeps some intensity to avoid arriving flat.

A recovery week is a different tool: a recurring reset that happens every three to four weeks throughout an entire training block, not just once. Where a taper is about arriving fresh for one day, a recovery week is about letting three weeks of accumulated load actually convert into fitness before you ask for more. Conflating the two - or worse, only ever doing the version right before a race - is why a lot of self-coached blocks feel like a slow grind toward burnout rather than a staircase of improving fitness.

Why the unload is where the fitness comes from

Training doesn't make you fitter. Recovering from training does.

A hard week creates a training stimulus and, alongside it, fatigue. Fatigue temporarily masks the fitness gain underneath it - your legs feel heavy, sessions feel harder than they should, and if you judged your fitness purely by how you felt in week three of a build, you'd conclude you were going backward. You aren't. You're accumulating a stimulus that hasn't had room to express itself yet.

A recovery week removes enough load for that masking fatigue to dissipate, and what's left afterward is the fitness the previous three weeks actually built. Skip the unload indefinitely and the fatigue just keeps stacking on top of itself, eventually flattening out or reversing the very adaptation you're training for - the mechanism behind both overreaching and a lot of preventable injuries and illness in the middle of a build.

How much to cut, and what to cut

Volume: down to roughly 60% of the preceding week. This is the same ratio used across the first 50K framework and the vertical gain guide - every fourth week dropping to about 60% of what came before, whether the load being tracked is distance, time, or elevation gain.

Intensity: let it drop too, more than you would in a taper. This is the one place a recovery week and a taper genuinely diverge. A taper protects a small amount of race-effort work because you're days away from needing to perform. A recovery week has no such deadline - there are more build weeks still ahead to rebuild sharpness, so it's fine, even useful, to let the hard sessions mostly disappear for a week rather than trying to preserve them.

Frequency: keep it, roughly. Running four days on a recovery week instead of five is fine; dropping to one long slog and calling it recovery isn't. Consistency of easy movement helps more than a big single block of complete rest for most runners - similar to why the taper guide recommends against multiple consecutive full rest days.

Vertical gain, if you track it separately: cut it hard too, and disproportionately if the preceding weeks leaned heavily on climbing - descending in particular carries eccentric damage that a recovery week should be actively unloading, not repeating at a slightly gentler pace.

Signals it's time, beyond the calendar

Every third or fourth week is the default, but the body doesn't always cooperate with a fixed schedule. Watch for:

• Resting heart rate elevated 5-10 beats above your normal baseline for several consecutive mornings.
• Poor sleep quality despite adequate hours - restless, unrefreshing sleep even when you're in bed long enough.
• Persistent heaviness or soreness that doesn't resolve with a single easy day.
• A session that should have felt moderate feeling genuinely hard, with no obvious external cause.
• Declining motivation or irritability that's out of character.
• Performance on a repeated benchmark session trending down across consecutive attempts rather than staying flat or improving.

Any one of these showing up a week early is a legitimate reason to pull the recovery week forward rather than grinding through to the calendar date. None of them showing up is not, by itself, a reason to skip the week that's already scheduled - which is the mistake that causes the most damage.

What a good recovery week actually looks like

Not a week off. A week of the same shape at a lower volume, mostly without the hard session.

The point isn't to do nothing. It's to remove the load that's currently outpacing your recovery, while keeping enough consistency that you don't lose the rhythm of training altogether.

What not to do with it

Don't skip it because you feel good. This is the single most common mistake, and it's a trap precisely because it feels like good judgement. Feeling strong in week three of a build is often the fatigue not having caught up with you yet, not evidence that it isn't there. The runners who skip recovery weeks on a good-feeling streak are frequently the same ones who get hurt or sick in week five or six, once the accumulated debt finally comes due.

Don't use it to catch up on missed sessions. A recovery week that quietly turns into "let me squeeze in the long run I skipped last Tuesday" isn't a recovery week - it's just a normal week with worse planning.

Don't take several consecutive full rest days. For most runners, easy movement through the week aids recovery more than total inactivity does, and a sudden full stop can leave legs feeling flatter and stiffer when training resumes than a genuinely easy week would.

Don't schedule it to land awkwardly around your biggest session of the block. A recovery week works best positioned after your hardest push, not interrupting the build-up to it.

I had an athlete two seasons ago, building for her first 100K, who skipped her week-eight recovery week entirely because "the training was going too well to stop." She held on until week eleven, when a minor Achilles niggle that had been quietly present since week nine turned into a real problem that cost her ten days entirely off running - considerably more disruption than the recovery week she'd skipped would ever have cost her. Her next block, she took every scheduled recovery week regardless of how she felt going into it, including one she genuinely didn't think she needed. She finished that build injury-free and ran a personal best. The recovery weeks weren't lost training. They were the only reason the training either side of them actually counted.

Fitting it into a full block

For a standard 16-week build using three-build-one-recovery blocks, that's roughly four recovery weeks across the plan - typically landing around weeks 4, 8, and 12, with the final taper functioning as an extended fifth unload rather than a normal recovery week. Longer builds toward a 100K or 100 mile scale the same 3:1 ratio across more blocks rather than changing the ratio itself.

If recovery weeks keep getting skipped in your own training despite knowing better - or if you're not sure whether what you're feeling is normal fatigue or something a recovery week won't fix - that judgement call is exactly what 1:1 coaching exists to make from outside your own training log.