Am I Overtraining? How to Know Before Your Body Breaks Down

The 10% Rule Is a Myth — And It's Injuring You

You've probably heard it: don't increase your weekly mileage by more than 10% per week. It sounds evidence-based. It is not. The 10% rule has never been validated in a controlled study. It appeared in running magazines in the 1980s and became gospel by repetition, not research.

The real problem with the 10% rule is that it measures the wrong thing. Weekly mileage averages out your load — a 40-mile week with a 20-mile long run is very different physiologically from a 40-mile week spread evenly across 7 days. The number tells you how much you ran. It doesn't tell you how hard your body is actually working to recover.

Worse, the 10% rule fails in both directions. A 40-mile-per-week runner can safely add 5 miles in a given week. A 15-mile-per-week runner adding 1.5 miles might be overreaching if they just came off an illness, ran their first race, or increased intensity. Flat percentages ignore your current recovery state — the factor that actually determines injury risk.

What Actually Predicts Injury: Acute:Chronic Workload Ratio

Sports scientists have spent the last decade developing a better model. It's called the Acute:Chronic Workload Ratio (ACWR), and while it was developed for team sports, the underlying principle is directly applicable to running.

The concept is simple: compare what you've done recently (your acute load — typically the last 7 days) against what your body has adapted to(your chronic load — typically a rolling 4-week average). The ratio tells you whether you're asking more of your body than it's prepared to give.

ACWR: The Zones

< 0.8

UndertrainingYour body is adapting to less than it can handle.

0.8–1.3

Sweet spotEnough stress to adapt, not so much you can't recover.

1.3–1.5

Caution zoneRisk begins rising. Monitor symptoms closely.

> 1.5

Danger zoneInjury risk climbs sharply. Ease off immediately.

Research from Tim Gabbett and colleagues in elite sport found that athletes with an ACWR above 1.5 had injury rates 2–4× higher than those in the 0.8–1.3 range. You don't need to track your ACWR precisely to benefit from this framework — you just need to understand that sudden load spikes are the real enemy, not absolute mileage.

The Hidden Load Multipliers Most Runners Don't Count

Training load isn't just miles. Your body doesn't distinguish between stress sources — it only knows whether it has enough resources to recover. Several factors multiply your effective load without touching your mileage:

Sleep debt
A 2019 Stanford study found that athlete injury risk doubled when they averaged fewer than 6 hours of sleep per night. Tissue repair, muscle protein synthesis, and glycogen restoration all peak during slow-wave sleep. Three nights of 5-hour sleep is equivalent to adding 20–30% extra effective load.
Race or time-trial efforts
A 5K race at threshold pace creates 2–3× the muscular damage of an easy run at the same distance. If you ran a race last weekend and are resuming your normal training schedule this week, you are already in a high-ACWR state — even if your mileage looks normal.
Life stress
Cortisol from work stress, travel, illness, or disrupted routines directly suppresses immune function and slows tissue repair. Your body doesn't prioritize muscle recovery when it perceives systemic threat. High-stress periods require lower training load — not the same load with "more mental toughness."
Surface and terrain changes
Switching from roads to trails, adding hills, or moving to a harder surface (concrete vs. asphalt) increases the mechanical stress on joints and tendons — even at identical paces. New terrain is new load.

The Most Common Overtraining Pattern in Recreational Runners

Here's the injury scenario that sports medicine clinics see on repeat, every spring and fall:

A recreational runner signs up for a race — a half marathon, a 10K, their first marathon. Training starts fine. Then life gets busy. They miss two weeks. Feeling behind, they compress three weeks of training into one. They do a long run that's 40% longer than their previous longest. They feel fine afterward. They do it again the next week. Two weeks later: shin splints, IT band syndrome, or a stress reaction.

This is the spike pattern. The injury didn't come from the hard week. It came from the cumulative effect of asking already-fatigued tissue to absorb another high-load week before it had recovered. The body's warning signals — the heavy legs, the slight soreness that "warms up" — were there. But runners are trained to push through discomfort, and there is no reliable way to distinguish normal training soreness from early-stage injury development without paying close attention to the right signals.

6 Warning Signs You're in the Injury Window

Check the boxes that apply to your last 7 days.

Resting heart rate 5+ BPM above normal

Check it first thing in the morning before getting out of bed for three consecutive days.

Sleep quality dropping despite being more tired

Overtraining activates the sympathetic nervous system, making it harder to reach deep sleep.

Mood is flat or irritable between runs

Chronic cortisol elevation affects serotonin and dopamine — this is physiological, not psychological.

Legs feel heavy past mile 2 every run

Not normal soreness. If glycogen-depleted muscles never fully recover, the heaviness doesn't go away.

Pace dropping on what used to be easy efforts

When your aerobic system is overtaxed, 'easy' pace slows as your body protects itself.

Any sharp or nagging pain that persists after warming up

Dull soreness 24–48h post-run is normal. Pain during a run that doesn't warm off is not.

If you checked 2 or more:you're likely in the warning window. This doesn't mean stop running — it means reduce intensity and volume by 20–30% for 5–7 days and monitor whether symptoms resolve. If 4 or more boxes are checked, take a full rest day today and re-assess tomorrow.

What To Actually Do When You Suspect Overtraining

The instinct most runners have is wrong: they either ignore the signals and push through, or they panic and stop training entirely. Neither is optimal.

The research-backed approach is called load management, and it looks like this:

01
Reduce volume first, not intensity
Cut weekly mileage by 20–30%. Keep at least one quality session if you feel capable. Total rest creates detraining faster than a modified week; the goal is to reduce acute load while maintaining chronic fitness.
02
Sleep is training
Prioritize 7–9 hours for at least 5 consecutive nights. This is not optional recovery. If you're in a high-cortisol period (travel, work stress, illness), your sleep quality matters more than your mileage.
03
Add easy movement, not passive rest
Walking, swimming, or easy cycling improves blood flow to recovering tissue. Complete sedentary rest is less effective than gentle movement at clearing metabolic waste from fatigued muscle.
04
Monitor, don't guess
Track your resting heart rate, perceived exertion on easy runs, and sleep quality for 7 days. If metrics improve, you can begin building again. If they plateau or worsen, extend the reduced-load period.

The Bottom Line

Overtraining injuries don't happen because you ran too much. They happen because you ran too much relative to what your body had recovered from. The gap between those two things is where every recreational runner's most frustrating injury lives.

The good news: the warning signals come days before the injury. Your resting heart rate, your sleep quality, your perceived effort on easy runs — these are your body's early warning system. You just have to know what to look for and how to interpret the combination of signals you're seeing.

That's exactly what the InjuryOS free assessment does: it takes your current training load, sleep quality, pain signals, and recovery patterns, and tells you where you sit on the risk spectrum right now — before anything breaks down.