Ask Tempo

Am I overtraining, or just tired?

Tempo · 5 min read

Short answer: plain fatigue eases after a short stretch of easy running and real sleep; overtraining doesn't let go that fast. The difference isn't how brutal one session felt. It's whether your resting heart rate, your pace at a familiar effort, your sleep, and your mood are all drifting the same direction for days running, even once you've backed off. A rough week is fatigue. A pattern that refuses to release despite rest is a separate problem, and it's worth naming correctly before you train through it.

Fatigue and overtraining start in the same place

Fatigue and overtraining begin as the same signal: your body registering accumulated stress, from training plus sleep plus whatever else the week threw at you. Push past your current capacity on purpose, in a planned way, and you get functional overreaching: a deliberate dip that resolves within days and often leaves you fitter than before, the rebound a hard training block is designed to produce.

Keep stacking load without the recovery catching up, and the same mechanism tips into non-functional overreaching, then overtraining syndrome. The line between them isn't a feeling, it's duration and whether the body still responds to rest the way it's supposed to. A plain hard week answers to a few easy days. Overtraining doesn't answer to that at all.

What plain fatigue looks like

Heavy legs the day of or the day after a hard session. A pace that feels harder than usual on a specific run tied to a specific cause: heat, a late night, a session that went long. Resting heart rate drifts a little and settles back toward baseline within a couple of mornings. You still want to run tomorrow; you're tired, not dreading it. Sleep still does its job even if you went to bed later than planned. Back off briefly and most of it clears on its own.

What overtraining looks like instead

Overtraining isn't session-specific, it's persistent. Resting heart rate stays elevated morning after morning instead of settling back down. A pace that used to feel conversational now takes noticeably more effort or a higher heart rate to hold, even though training volume hasn't gone up. Sleep gets worse despite genuine exhaustion. Mood flattens generally: not just toward running, but toward things you'd normally look forward to. Minor colds and niggles start stacking up because the body's broader capacity to cope is worn down, not just its legs. The tell is that these move together, across many days, and rest days stop fixing them the way they used to.

How to actually tell the difference

The actual test is the trend across a couple of weeks, not one bad run or one bad night: resting heart rate most mornings, how a familiar pace actually felt, sleep, and mood, read together rather than any one of them alone. A dip that recovers within days of a genuine pullback points at ordinary load catching up with you. A dip that survives the pullback, that's still there after rest has had a real chance to work, is a different signal, one where a professional read usually beats another week of guessing. When something specific threw the week off, bad sleep, a heavy stretch of work, an illness, that detail is itself worth acting on: tell Tempo what happened and it re-proposes the week from your race goal, with the reasons on screen, and the call on what happens next stays yours before anything changes.