Ask Tempo

What to do the week after a race?

Tempo · 4 min read

Short answer: the week after a race is recovery, not full rest and not a restart into training. Muscle damage and immune suppression peak in the first two to three days. Glycogen refills within a day or two once you eat enough carbohydrate, but the connective tissue around your joints and tendons takes longer to catch up, often a week or more depending on distance. Easy movement, sleep and food matter more than the calendar.

What your body is dealing with

A race is a different animal from a hard training run, even at the same distance. Pushing at or near your limit creates more muscle damage, more inflammation and a bigger dent in immune function than training alone usually does, and the harder or longer the effort, the deeper that dent goes. The first two to three days afterward are usually the roughest: legs feel wrecked, resting heart rate runs a touch high, and catching a cold in that window is more common than people expect, because the immune system is busy on repair instead of defense.

Underneath the soreness, slower repairs are running too. Glycogen stores refill within a day or two once you eat enough carbohydrate, but the microscopic damage to muscle fibers and the connective tissue around joints and tendons takes longer, one to two weeks for a shorter race and well beyond that for a marathon. That mismatch, feeling fine on the surface before the deeper tissue has caught up, is exactly how people talk themselves into training too soon.

Why doing nothing isn't the better choice

Complete rest sounds like the safe choice, but low-intensity movement actually speeds the cleanup. Easy walking or a very light jog increases blood flow to damaged tissue, which helps clear waste products and deliver what the body needs to rebuild, without adding meaningful new damage. Full rest protects against overdoing it, but it does nothing extra for the repair itself, and days spent completely still can leave legs feeling stiffer rather than fresher.

The useful version of rest here is relative, not absolute: short, easy efforts at a pace that feels almost too slow to count, swimming or cycling if the legs need a break from impact, and ordinary daily walking. None of that competes with the rebuild happening underneath. It just keeps blood moving while that rebuild finishes.

Why the timeline isn't fixed

Plenty of runners have heard the old guideline of one easy day for every mile raced, which scales fast: a short race buys a handful of easy days, a marathon buys several weeks. It's a reasonable starting estimate, but it was built on averages, and your race wasn't average. How hard you pushed, the heat, how trained you were going in, your age and your sleep in the days after all shift the real number in either direction.

A better read than the calendar is your own signals: resting heart rate back in its usual range, sleep that feels restorative rather than just long, soreness fading rather than holding steady, and a mood that isn't flat or irritable. When those line up, the tissue is probably ready for more than easy movement. When even one is off, the body is still asking for time, regardless of what day of the week it is.

What this week actually looks like

Day one or two usually calls for nothing beyond walking and stretching the legs out, with food and sleep doing the real work. From there, short easy efforts can return gradually once soreness is fading and resting heart rate looks normal, while anything resembling intervals, hills or a hard long run waits until those deeper signals say so, not the calendar.

What matters is weighing this week against your own race distance and effort, not a generic rule borrowed from someone else's race. The honest move is to let the signals, not the number of days since the start line, make the call on when the next hard session happens.