Mileage alone doesn't measure your load
High confidence
Two runners can each log 50 km in a week and stress their bodies very differently. A single run that jumps well past your recent longest run carries injury risk that the weekly total hides, and how fast and hard the miles are run changes the strain too. Distance counts the volume, not everything inside it.
Why it works
Tissue load builds run by run, not just week by week. One run much longer than your body is used to concentrates that load in a single session, and a weekly total spreads it out on paper. Faster or harder running adds strain per mile that distance alone does not record.
What it means in practice
Track more than mileage. Keep any single run within about 10% of your longest run in the past month, and watch how hard the runs felt and how your paces are spread across the week. An easy 30 km week and 30 km of mostly tempo share the same total but stress the body very differently.
The evidence
-
Weekly running distance captures some mechanical, cardiovascular and perceptual load and is partially predictive of distance-running success, but on its own it can vastly obscure the cumulative training stress of different days. Training stress has external components (volume, pace) and internal ones (session RPE, heart rate, blood lactate). The authors argue monitoring should increasingly pair biomechanical external-load metrics from wearables with internal-load metrics, while noting that research confirmation is still needed before these improve injury-risk stratification.
-
Across 23,047 runners, running-related injury incidence was 26.2%, rising from 14.9% in novices to 26.1% in recreational runners and 62.6% in competitive runners. The knee (25.8%), foot/ankle (24.4%), and lower leg (20.9%) were injured most often. Evidence tying any single parameter (distance, duration, frequency, or intensity) to injury risk conflicted across studies, as did evidence for recent training changes. The 10% rule went unsupported: an RCT in novices found near-identical injury rates for graded (<10%/wk) and standard (>10%/wk) progression (20.8% vs 20.3%), and definitions of injury varied widely across the pooled studies.
n=23047
-
1820 of 5205 runners (35%) sustained a running-related injury. Single sessions longer than the longest run of the previous 30 days raised the overuse-injury rate for small (>10-30%), moderate (>30-100%) and large (>100%) spikes. The ACWR showed a negative dose-response and the week-to-week ratio showed no relationship with injury. The authors conclude that injury rate rose significantly once a single session exceeded the 30-day longest run by more than 10%.
n=5205
Why we call confidence high
Frandsen's 2025 study followed 5,205 runners' Garmin data for 18 months: injury rates rose whenever a single run went more than 10% past the longest run of the previous 30 days, while week-to-week changes in total distance showed no such link. Paquette's 2020 clinical commentary argues that distance should be paired with pace and internal-load measures such as session effort and heart rate. Fredette's 2022 systematic review found that no single training parameter, distance included, cleanly predicts injury.
Where it applies
All adult runners.
Plans that respect this
Plans that scored well on the rubric measures informed by this claim.
- 10-Week Advanced 10k Training (5 days)
- 10-Week Run a Faster 10k (3 days)
- 10-Week Run a Faster 10k (4 days)
- 10-Week Run a Faster 10k (5 days)
- 10-Week Run a Faster 10k (6 days)
- 10-Week Run a Faster Half Marathon (3 days)
- 10-Week Run a Faster Half Marathon (4 days)
- 10-Week Run a Faster Half Marathon (5 days)
- 10-Week Run Your First 10k (3 days)
- 10-Week Run Your First 10k (4 days)
- 10-Week Run Your First Half Marathon (3 days)
- 10-Week Run Your First Half Marathon (4 days)
Last reviewed Oct 14, 2026. See how we score.