If you’re dealing with a niggle, shin pain, ITB pain, or that “mystery knee pain” that comes and goes, you’ve probably thought:
“Maybe I should just stop running for a while.”
Sometimes a short reduction is the right call — especially if pain is escalating or your running form is clearly changing.
But here’s the pattern I see all the time:
Rest can calm symptoms… while your capacity drops quietly in the background.
Then you return to the same training pattern, and the pain comes straight back.
So the solution isn’t “never rest.” It’s smart load management for runners: adjusting the right training variables at the right time so your body keeps adapting instead of constantly getting irritated.
What “load management for runners” actually means
When runners hear “load,” they often think only about mileage. But training load management for runners is broader than that. It’s the total stress your body is dealing with from:
- distance (volume)
- intensity (pace, intervals, hills)
- frequency (how many runs per week)
- surface/terrain changes
- how close hard sessions are to each other
- and what’s happening outside running (sleep, stress, life)
Two runners can both run “30 km per week,” but one is steady and the other has a big long run spike plus hills plus a hard session on tired legs. Same weekly number — very different load.
This matters because injury risk often follows the pattern of your load, not just the total.
→ Click here to learn more about your risk of developing a running injury 🔍
The big mistake: focusing on weekly mileage instead of single-run spikes
Most runners try to be sensible by watching their weekly total.
That’s good. But one of the strongest “real-world” findings we have is that one single run that jumps too far above what you’ve recently done can be a big trigger.
A large cohort study tracking 5205 runners across 588,071 sessions looked specifically at when runners got injured relative to their training patterns. They found that injury rates increased when a single run was a noticeable jump compared with what the runner had recently been prepared for.²
“Okay… what counts as a spike?”
In that study, a “spike” meant a single run that was a noticeable jump compared with what you’ve recently built up to — specifically compared with your longest run in the last 30 days.²
What they found was:
- If a run was about 10% to 100% longer than your recent longest run, the injury rate was about 1.5 to 1.64 times higher than the baseline.²
- If a run was more than double your recent longest run, the injury rate was about 2.28 times higher.²
The practical takeaway is simple: once a single run jumps well above what you’ve recently done, risk increases — and the biggest jumps are the clearest red flag in load management for runners.²
What that means in plain English (example)
Let’s say the longest run you’ve done in the last month is 10 km.
- A run around 11 km is roughly that “10% above your recent max” zone.
- Jumping to 12–13 km is a bigger leap.
- Jumping to 20 km (double) is a huge leap if you haven’t done it recently.
And here’s the nuance I really like from this paper:
Even if each increase looks “reasonable” in isolation, you can still overload yourself by stacking increases too close together. The authors point out that progression isn’t only about the numbers — recovery time between loading days matters.²
That’s why runners often flare during a week that looks fine on paper, but includes:
- a longer long-run,
- plus a hard session,
- plus hills,
- plus poor sleep and life stress.
Same runner. Same body. Very different load story.
The “training–injury prevention paradox”: why doing less isn’t always safer
This idea explains the stop–start cycle so many runners get stuck in.
Tim Gabbett describes what he calls the “training–injury prevention paradox”: athletes who build high chronic workloads (built up over time) can actually have fewer injuries than those training at lower workloads — as long as the training plan is appropriate.³
The key issue isn’t training itself. The key issue is usually how training changes:
- excessive load
- rapid increases
- poor programming that spikes stress faster than the body can adapt³
And there’s another point in that paper that’s important for runners who “rest a lot” every time something niggles:
If you always train below what you need to adapt, you may never build the physical qualities that help protect you. In other words, sometimes under-training can leave you more vulnerable when you eventually do push the pace or distance again.³
So the goal isn’t “train harder no matter what.”
It’s build capacity gradually so normal training stops feeling like a threat.
12-Week Running Training Block
Progressive overload with planned recovery weeks — the foundation of injury-free running
Why long rest can make your return harder (detraining)
This is where “rest-only” plans often backfire.
If you fully stop running for weeks, you may feel less sore — but you can also lose some of the fitness that makes running feel easy. When the engine dips, the same run can feel like a bigger stressor.
Two sources you provided summarise this clearly:
- VO₂ max starts to decline after roughly 10 days without training, and meaningful reductions commonly occur in the 2–4 week window.⁴
- Studies show VO₂ max can drop by about 6% after ~2 weeks without running (and more with longer breaks).⁵
So if you shut running down completely for a month, it can create a frustrating return:
- pain is quieter,
- but capacity is lower,
- and the first “normal” week back becomes a spike.
That’s why, when it’s clinically appropriate, I usually prefer:
- modify running (shorter/easier, fewer stressors), and/or
- keep fitness with cross-training,
instead of a total shutdown.
Bone stress injuries are the clearest example: “optimal loading” beats guesswork
If you want a clean example of how clinicians think about load management for runners, bone stress injuries (like tibial/metatarsal stress injuries) are it.
A clinical reasoning paper on managing these injuries describes a structured, symptom-guided approach:⁶
- There’s often an initial period of load reduction to settle symptoms.
- You can maintain fitness with cross-training while unloading the injured area.
- A return-to-run program can start once you’re pain-free in daily activities.
- Early progression prioritises increasing volume before speed.
- “Optimal load” is the dose that produces no symptoms during, after, or the next day.⁶
Even if you don’t have a bone stress injury, the concept is useful because it gives you a simple way to think:
“What amount of loading can my body handle without a delayed flare — and how do I build from there?”
That’s load management for runners in its purest form: not “rest forever,” but the right load at the right time.
Pain science: pain is real — and it’s not always a perfect “damage meter”
Runners are generally tough and practical. The problem isn’t motivation — it’s uncertainty:
“Is this pain a warning sign I should respect… or just a sensitive system reacting to load?”
A pain science article aimed at athletes explains pain as an output of the brain — a protective response influenced by perceived threat, context, and sensitivity — not a perfect real-time measurement of tissue damage.⁷
t also discusses nervous system hypersensitivity and why graded exposure can matter when pain becomes persistent or disproportionate.⁷
Practical takeaway:
- Pain deserves respect.
- But panic-rest followed by a sudden comeback can keep you stuck.
- A smarter approach is often graded exposure: gradually rebuilding confidence and tolerance by adjusting load in a controlled way for load management for runners.⁷

The runner-friendly, load management for runners plan (educational, not rigid)
This isn’t a one-size-fits-all program. It’s a framework to help you make better decisions without guessing.
1. Keep running — if you can do it without provoking a flare
A useful idea from the bone stress “optimal loading” model is to watch your delayed response — not just “how it felt during the run,” but how it feels later that day and the next morning.⁶
That delayed response often tells you whether the dose was too high.
2. Protect against the #1 trigger: single-run spikes
Use your longest run from the last 30 days as a simple reference point.
The cohort study suggests injury rates rose when a single session was more than ~10% above that recent longest run — and bigger spikes were linked with a higher injury rate overall.²
Also: don’t get trapped by “math-only progression.” The paper highlights that even repeated smaller increases can overload you if recovery spacing is poor.²
3. Build chronic capacity gradually (the paradox done properly)
The paradox is basically: being trained is protective, but rapid jumps are risky.³
So the long-term goal is consistent training that expands what you can tolerate — without the “boom-bust” cycle.
4. Be cautious with long layoffs unless you truly need them
Because detraining is real:
- VO₂ max decline can start around day 10 and become meaningful over 2–4 weeks.⁴
- A drop can already be noticeable after about two weeks off.⁵
This isn’t anti-rest. It’s just explaining why long breaks can make the comeback harder than expected.
5. If pain becomes persistent or confusing, consider the sensitivity angle
Pain isn’t only tissue. It’s also the nervous system’s protective response.⁷
That’s why graded exposure and calmer progression can be so effective for runners who get stuck in recurring flare-ups.⁷
Conclusion
If you want to stay injury-free long-term and master load management for runners, the target usually isn’t “more rest.”
It’s better load decisions:
- Avoid big single-session spikes — this is one of the clearest risk points we can see in large runner data.²
- Build fitness gradually so training becomes protective, not threatening.³
- Use symptom-guided loading principles (especially when bone stress is a possibility).⁶
- Remember: pain is information, not a verdict — and in persistent cases, graded exposure often beats stop–start cycles.⁷
About the Author
Daniel da Cruz is a physiotherapist in Sandton who regularly treats running-related injuries in clinical practice. He commonly works with runners dealing with issues such as ITB syndrome, knee pain, hip pain, and shin pain, using evidence-based rehabilitation, progressive strength training, and movement retraining to help them return to running safely and confidently.
References
- Schuster Brandt Frandsen, J., Hulme, A., Parner, E. T., Møller, M., Lindman, I., Abrahamson, J., Sjørup Simonsen, N., Sandell Jacobsen, J., Ramskov, D., Skejø, S., Malisoux, L., Bertelsen, M. L., & Nielsen, R. O. (2025). How much running is too much? Identifying high-risk running sessions in a 5200-person cohort study. British journal of sports medicine, 59(17), 1203–1210. https://doi.org/10.1136/bjsports-2024-109380
- Gabbett T. J. (2016). The training-injury prevention paradox: should athletes be training smarter and harder?. British journal of sports medicine, 50(5), 273–280. https://doi.org/10.1136/bjsports-2015-095788
- Mantak M. All About Detraining [Internet]. TrainingPeaks; [cited 2026 Jan 15]. Available from: https://www.trainingpeaks.com/blog/how-much-down-time-is-too-much-the-concept-of-detr/
- Fitzgerald M. Losing Running Fitness: A Scientific Look at How Much You’ll Slow Down When Not Able to Run [Internet]. Runners Connect; [cited 2026 Jan 15]. Available from: https://runnersconnect.net/losing-running-fitness/
- Warden, S. J., Edwards, W. B., & Willy, R. W. (2021). Optimal Load for Managing Low-Risk Tibial and Metatarsal Bone Stress Injuries in Runners: The Science Behind the Clinical Reasoning. The Journal of orthopaedic and sports physical therapy, 51(7), 322–330. https://doi.org/10.2519/jospt.2021.9982
- True Sports Physical Therapy. Pain Science for Athletes: Why No Pain, No Gain Sabotages Recovery [Internet]. True Sports Physical Therapy; [cited 2026 Jan 15]. Available from: https://www.truesportsphysicaltherapy.com/blogs/pain-science-for-athletes-why-no-pain-no-gain-sabotages-recovery


Leave a Reply