Photo by Maksim Goncharenok on Pexels
You laced up, headed out, and it was awful. Your legs felt like wet cement. Your pace was 45 seconds per kilometre slower than usual. You had to stop and walk — or you bailed entirely after 10 minutes. Whatever happened, you’re home now feeling deflated, questioning everything from your fitness to whether you should even bother.
First: this happens to every runner, at every level. Not occasionally — regularly. Even people mid-marathon training, who’ve done every session, who slept well and ate well, have runs that just fall apart. A bad run isn’t a sign you’re getting worse or that your goals are unrealistic. It’s a sign that you’re a runner.
What matters is what you do next. This article won’t tell you to “stay positive” or “trust the process” in vague terms. Instead, you’ll find out why bad runs actually happen, how to decode yours, and the specific steps that will help you reset — and come back to your next run with some confidence intact.
Why bad runs happen (and it’s usually not what you think)
Most runners blame themselves — too slow, too unfit, too lazy. But the majority of truly bad runs have a physiological explanation that has nothing to do with effort or dedication.
Glycogen depletion is one of the most common culprits. If you ran in a slight deficit for a few days, skipped a meal, or did back-to-back harder sessions, your muscles may simply be low on fuel. Running at what should be an easy 5:45/km pace can feel like threshold effort when your glycogen stores are depleted.
Poor sleep hits harder than most people expect. Research published in the British Journal of Sports Medicine has found that even a single night of disrupted sleep can impair perceived exertion — meaning the same pace feels significantly harder the next day. If you had a 5-hour night and wondered why 6:00/km felt brutal, there’s your answer.
Cumulative fatigue is sneaky. You might feel fine going into Thursday’s run after a hard Tuesday and a solid Wednesday, but the legs remember. If you’re running 4 days a week and doing back-to-back moderate efforts, a dead run on day 4 is normal — not a crisis.
Other factors: heat (even 5°C above your normal running temperature can slow you by 20–30 seconds per km), illness coming on, dehydration, hormonal fluctuations (particularly relevant for female runners), and plain old stress. A bad week at work or a difficult stretch emotionally will show up in your legs whether you like it or not.
How to decode your bad run
Before you can bounce back, it helps to spend two minutes actually working out what happened. Here’s a simple framework:
| Symptom | Likely cause | What it tells you |
|---|---|---|
| Heavy legs from the first step | Cumulative fatigue or poor sleep | You needed rest, not another run |
| Started fine, fell apart after 20–25 min | Low fuel / glycogen | Eat more carbs before longer efforts |
| High heart rate at easy pace | Fatigue, illness, heat, or dehydration | Your body is stressed — back off |
| Couldn’t find a rhythm at all | Mental load / stress | Not a fitness problem |
| Tight, sore, struggling all round | Muscle damage from previous session | You went too hard before recovering |
| Completely fine physically, just quit mentally | Motivation dip or pacing error | Go easier next time; check your goals |
Being honest with yourself here matters. If your legs were wrecked because you ran Thursday intervals at 4:30/km when you’re a 5:30/km 5K runner, that’s useful information. If you bailed because it was drizzling and you’d had a hard week, that’s a different issue entirely — and neither one makes you a bad runner.
What to do in the hours after a bad run
The worst thing you can do immediately after a tough run is either catastrophise (“I’ll never hit my goal”) or go straight back out to “make up” for it. Both responses tend to make things worse.
Eat something with carbohydrates and protein within 45 minutes. If you came home depleted, a bowl of porridge, a banana with peanut butter, or a small chicken and rice meal will begin restocking your glycogen. This isn’t optional — it directly affects how quickly you’ll feel better and how your next session goes.
Write down what you think happened. Even a one-line note in your phone. “Dead legs. Slept 5 hours, did hard intervals Tuesday.” Over time, these notes become genuinely useful patterns.
Don’t reschedule the session immediately. If you had a tempo run planned and it disintegrated, the instinct is to cram it in tomorrow. Resist this. Your body almost certainly needs a day’s recovery more than it needs a make-up run. One missed session in a training block almost never affects your end result — but doubling down on a fatigued body is how minor niggles become real injuries.
For practical recovery support, working through a solid foam rolling routine after hard or failed efforts can help clear some of the residual muscle tension — especially in your quads, calves, and IT band — so your next session starts fresher.
How to approach your next run
The run after a bad one is where many runners make a critical mistake: they go out trying to prove something. They push the pace, or set a new target, or run longer than planned to “cancel out” the bad session.
This almost always results in another bad run.
Instead, treat your next session as a reset. Here’s the approach:
- Go shorter than planned. If you were going to do 10K, do 6K. You’re not going backwards — you’re rebuilding confidence.
- Go slower than you think you should. If your easy pace is around 6:00–6:15/km, run at 6:30/km for the first half. Give yourself an easy out.
- Ditch the watch data for the first kilometre. Start by feel. Let your legs warm up before you start judging yourself.
- Set a micro-goal. Not “run 8K at 5:45/km” but “run for 25 minutes and finish feeling okay.” The bar is deliberately low. Clear it, and you’ll feel better.
The goal is to remind your brain that running doesn’t always feel terrible — not to make up for last time.
When a bad run is actually a warning sign
Most bad runs are one-offs. But some patterns are worth paying attention to.
If you’ve had three or more consecutive rough sessions, or if you’re consistently feeling exhausted, heavy-legged, or unusually slow across a week or two, it might be worth considering whether you’re under-recovering or overtraining. The signs often overlap: elevated resting heart rate, poor sleep, persistent muscle soreness, and a complete loss of motivation to run.
This is different from a single bad day. The NHS guidance on overtraining notes that sustained fatigue and performance decline without adequate rest is a legitimate physiological issue — not a mental one.
If this sounds familiar, a week of easy running — nothing above 65% of your max heart rate, nothing long, nothing intense — will do more for your progress than any workout. Understanding the signs you’re overtraining as a runner before they become a training crisis is worth your time.
Adjusting your training block after a rough patch
If you’re following a structured plan — say, a 16-week marathon build or a half marathon programme — a bad run or two doesn’t mean you need to restart. But it might mean a small recalibration.
What you probably don’t need to do:
– Scrap the plan entirely
– Add extra sessions to compensate
– Move your goal race
What you might need to do:
– Shift a quality session back by 1–2 days
– Drop the next long run distance by 10–15% (e.g., from 22K to 19K)
– Swap one run for a rest day if fatigue is the likely cause
Training plans are frameworks, not contracts. The best runners — at every level — adjust constantly based on how they’re actually feeling. If you’re in a build phase and your body is sending clear signals, listening to them is smart training, not weakness.
The mindset part (briefly, honestly)
This article isn’t going to tell you that every run is a gift or that the bad ones make the good ones sweeter. That’s not particularly useful when you’re standing in your kitchen, soaked and deflated.
What is true: your fitness doesn’t disappear after one bad run. Research consistently shows that meaningful detraining — actual loss of aerobic capacity — takes around 10–14 days of complete inactivity to begin. One bad session, or even a rough week, won’t undo months of work.
It’s also worth separating “I had a bad run” from “I am a bad runner.” The first is a fact about one session. The second is a story you’re telling yourself, and it’s not accurate.
If motivation is the underlying issue — you’re not injured or overtrained, you just don’t want to go — that’s a different problem worth addressing directly, rather than hoping a training plan will fix it on its own.
The honest takeaway
- Bad runs are normal, not diagnostic. One terrible session tells you almost nothing about your fitness trajectory. Don’t let it rewrite your goals.
- Decode it before you dismiss it. Fatigue, poor sleep, low fuel, and heat are the most common causes — and all of them are fixable with rest, food, or timing adjustments.
- Your next run should be shorter and easier than you’re tempted to make it. Prove to yourself that running can feel okay again, then build back from there.
- Three or more consecutive bad sessions is a different story. That pattern warrants a genuine rest period, not more running.
- One missed or failed session in a training block is essentially meaningless. Consistency over months matters. This week’s rough run doesn’t.
Next read: Running motivation tips when you don’t feel like it