Rest Day or Run Day? It's Not About What Day It Is
Most training plans slap "rest day" on a fixed slot — every Monday, say — like your body runs on a weekly grid. It doesn't. Whether you should rest today is really a function of three things stacking up at once: how hard yesterday's session was, how much volume you've piled on this week, and how you actually feel this morning.
That third input gets dismissed as "just being tired," but it's doing real work. A single bad night of sleep after an easy day usually isn't a red flag — you can still run, just dial back the ambition. But when subjective fatigue starts stacking on top of a heavy training week, or on the heels of a genuinely hard effort (think intervals or a long run), that's a different signal entirely. The body's telling you it hasn't absorbed the load yet, and running through it just delays adaptation instead of building it.
The research behind this is less about a magic formula and more about pattern recognition: runners who treat rest as reactive — responding to the actual state of their body — recover faster and get injured less than runners who treat it as a scheduling formality. A rest day inserted because "it's Monday" might be wasted if you're actually fresh, and a missing rest day on a day you desperately needed one is how niggles turn into injuries.
The practical shift is to start checking in with yourself before you check the plan. Ask: how did yesterday go, what's this week looked like, and how do I feel right now? If all three point the same direction — hard effort, high volume, rough morning — that's your rest day, wherever it falls on the calendar. If it's just one off night, lace up, but keep the effort honest and the distance short.
RunNerd flags 3+ days of easy pace feeling hard, RHR 5-7 bpm above baseline, or dropping HRV and prescribes full rest; one rough night just gets an easy-effort, half-distance cap.