Ask Tempo

What a deload week actually does (and how to know you need one)

Tempo · 5 min read

Short answer: a deload week isn't a rest week where you feel guilty. It's a deliberate drop in training load that lets the fatigue you've been stacking up drain away — so the fitness you already built can finally show up. You don't get faster during hard training; you get faster once you recover from it. A deload is you scheduling that recovery instead of waiting for your body to force it on you. The tricky part isn't the mechanics. It's reading the signals honestly, because the moment you most need one is usually the moment you least want to take it.

What's actually happening under the hood

Every hard week leaves two things behind: a fitness signal (your body adapting — building mitochondria, capillaries, tougher tendons) and a fatigue signal (accumulated stress that temporarily masks all of it). For a while, both climb together and you feel it: strong, a little tired, still improving. But fatigue accumulates faster than it clears if you never back off, and eventually it sits high enough to hide the fitness underneath. That's when you feel slow despite doing everything right. A deload cuts the incoming load so the fatigue side drains while the fitness side barely moves — and what was hidden surfaces. This is why people often run a personal best a week or two after their "laziest" week. Nothing new was built. It was there the whole time.

The signals worth reading

No single number tells you to deload. It's a pattern that stacks. The ones that tend to travel together:

• Stalled or declining performance despite training. This is the loudest one. Paces that used to feel controlled now feel like a fight, or your times drift the wrong way while your effort stays high. Working harder for less is the classic fatigue signature.
• Resting heart rate creeping up. A few beats above your normal morning baseline, holding for several days, often means your body is still busy recovering rather than ready to absorb more.
• Sleep that isn't repairing you. Waking through the night, or sleeping full hours and still feeling flat, is a common companion to deep training fatigue.
• Heaviness that doesn't clear. Legs that feel dead for days rather than bouncing back within a run or two.
• Mood and motivation dipping. When runs you normally look forward to start feeling like a chore, that's data too — the nervous system is part of the picture.
• Niggles quietly accumulating. Little aches that individually mean nothing but keep appearing are often the early edge of doing too much.

One of these on its own is usually just a rough week — a bad night's sleep, a stressful stretch at work, a hot day. It's when several show up at once, and stick around, that they stop being noise and start being a pattern.

How much to pull back

The mistake most people make is thinking deload means stop. It doesn't. Dropping to zero tends to leave you flat and sluggish, not fresh, and it throws away the light stimulus that keeps you sharp. A more useful frame: cut weekly volume by roughly 30 to 50 percent, keep your usual run frequency, and hold on to a small amount of intensity — a few strides, a short session at your normal quality pace rather than the full workout. You're lowering the total stress while keeping the rhythm and the sharpness. How far into that 30–50 percent range you go depends on how deep the hole is and what's coming next: deeper fatigue or a big race approaching argues for cutting more; a mild "just taking the edge off" week can sit at the lighter end.

How long, and how often

A deload is usually a single week — long enough for fatigue to drain, short enough that you don't detrain. As for cadence, a lot of runners find that stringing three or four progressively harder weeks together and then deloading keeps them building without breaking down, but that's a rhythm to test against your own life, not a law. Someone juggling shift work and young kids carries a very different total stress load than someone with a flexible schedule, and your body doesn't know the difference between training stress and the rest of it.

It's a judgement call, not a formula — and it's yours

Here's the honest part: none of this is a rule you can outsource. The signals above are real, but they're read against your baseline — your normal resting heart rate, your normal legs, your normal motivation on a Tuesday. A resting HR that's alarming for one person is just Tuesday for another. What a deload does physiologically is settled; whether this week is the week is a judgement about your body, your goal, and everything else you're carrying right now. If you're weighing it, the useful question isn't "what should I do" — it's "how many of these signals am I actually seeing, and for how long?" Sit with that honestly and the answer is usually already yours. And if any of the signals is real pain, illness, or something that feels off in a way training fatigue doesn't explain, that's a conversation for a doctor or physio, not a training tweak.