What everyone believed about running injuries
Conventional wisdom in running said this: overuse injuries build up gradually. You accumulate a bit too much mileage over a few weeks, your body hits a tipping point, and the injury surfaces. The logical solution was to track your weekly mileage and never increase it by more than 10% from one week to the next — the Acute:Chronic Workload Ratio, or ACWR.
A study of 5,205 adult runners — the largest of its kind — just seriously challenged that picture. And its findings have immediate implications for how you plan your training runs.
What the large-scale study found
Researchers tracked 5,205 adult runners, primarily men in Europe and North America, over an extended period, recording every session and every injury. Their question: what actually predicts overuse injury risk?
The surprising finding: it's not the week-to-week increase in total mileage that best predicts injury. It's the increase in distance within a single session relative to the runner's usual sessions. The critical threshold sits around a 10% spike in single-session distance. Beyond that, risk rises. When a single session's distance more than doubled compared to usual, injury risk shot up sharply.
Translation: most running injuries don't accumulate slowly over multiple weeks. They frequently start in a single session where something exceeded what the body was adapted to handle.
The ACWR method questioned
This finding also has important implications for a widely-used methodology: the Acute:Chronic Workload Ratio. This approach, built into many training plans and running apps, compares your last 7 days of training load to your average over the past 28 days. If the ratio spikes, you're supposedly in the danger zone.
The study tested whether this ratio actually predicts running injuries. Answer: not significantly. The ACWR was originally developed for team sports, based on a study of just 28 participants. Its application to running was never on solid ground — and this large study confirms it.
The real lever: managing per-session distance
If weekly mileage isn't the primary factor, what should you track? The distance of each individual session compared to what you typically run.
In practical terms, this changes a few things:
- If you've taken a week off and you're getting back at it, don't run your usual distance on your first session back. Your body has lost some adaptation. Work back to your typical distance over 1-2 weeks.
- If you're marathon training and you're adding a long run for the first time this season, that long run is potentially your highest-risk session — not the cumulative weeks before it.
- The day you feel great and decide to go a bit further than planned is exactly the day to watch. That's often where injuries start.
What this doesn't mean
This study isn't saying that total mileage or weekly progression don't matter. It's saying that per-session distance is a more direct predictor of injury risk than the weekly metrics most runners use.
It also doesn't mean other factors — wrong footwear, accumulated fatigue, lack of strength training — don't count. Injury prevention is multifactorial. But if you want one simple, immediately actionable lever, this is it: know your typical session distance and don't exceed it by more than 10% in a single jump.
How to adapt your training plan right now
If you run with GPS or a tracking app, you already have all the data you need. Calculate your average distance per session over the last four weeks. That's your baseline. Don't exceed it by more than 10% in your next session.
It sounds conservative. That's exactly the point. In running, the athletes who last the longest aren't the ones who progress fastest — they're the ones who stay on their feet. If you want to build mileage more intelligently over time, Zone 2 training principles offer a useful framework for sustainable progression.