What Change in Running Distance Puts You at Risk of Injury?

By Grant Frost · Physiotherapist • Last clinically reviewed: 19 January 2026

If you're a runner, you've likely heard the old "10% rule" - don't increase your weekly distance by more than 10% per week to avoid injury. It's been a cornerstone of training advice for years, featured in running magazines, coaching plans, and even built into fitness apps. But what if our focus on weekly totals has been missing a more important, immediate risk factor?

A landmark new study published in the British Journal of Sports Medicine is challenging this conventional wisdom. By analysing data from over 5,200 runners across more than half a million running sessions, researchers have proposed a significant shift in how we might think about preventing overuse injuries like knee pain, shin splints, and Achilles tendinopathy. Let's break down what this large-scale research found and what it could mean for your running routine.

What the Study Involved: A Look at the Research

The study was a large, 18-month prospective cohort study involving 5,205 adult runners from over 87 countries. Crucially, running distance was measured objectively via GPS data from Garmin wearables, not self-reported, which adds to the data's reliability.

Runners were followed for up to 18 months, reporting any injuries through weekly surveys. The researchers then analysed three different ways of measuring training load:

1. The Single-Session Spike: Comparing today's run distance to the longest run in the past 30 days.
2. The Acute/Chronic Workload Ratio (ACWR): A popular metric comparing your last week's total distance to your average over the past 3-4 weeks.
3. The Week-to-Week Ratio: Simply comparing this week's total distance to last week's.

The Results: A Clear Risk Scale for Runners

The data painted a clear picture. Out of all runners, 35% sustained a running-related injury during the study. When looking at what preceded those injuries, the 'single-session spike' was the standout predictor.

Perhaps just as importantly, the study found that the widely-used ACWR was not associated with an increased injury risk in this population. In fact, higher ACWR values showed a trend toward a lower risk - the opposite of what the "too much, too soon" theory would predict when applied on a weekly basis. The week-to-week ratio also showed no significant link to injury.

Considering the Study's Scope and Limitations

As a Physio, it's my job to look at research with a critical, balanced eye. This is a strong study due to its huge scale and objective GPS data, but it's important to understand its context.

Strengths: The massive sample size (over 5,200 runners) makes the findings more reliable than smaller studies. The use of wearable tech for distance measurement reduces recall bias, and the 18-month follow-up provides a good picture of injury development over time.

Limitations & Generalisability:

• The runner cohort was predominantly male (78%) and from Europe/North America, so the findings may not apply equally to all runner demographics.
• Injuries were self-reported, which can sometimes lack the precision of a clinical diagnosis.
• The study focused on distance as the measure of load. Other factors like intensity (pace, hills), running form, footwear, and recovery are also important but weren't the focus here.
• It shows an association, not direct causation. We can't say for certain that the long run spike directly caused the injury, only that it was strongly linked to it.

A Physio's Perspective: Load as a Spotlight, Not Just a Cause

This research provides a valuable, data-driven guide for managing training load. However, from a clinical perspective, I often see running injuries through a slightly different lens.

Running itself is a normal, healthy activity. The repetition and load from running aren't inherently bad - they're the stimulus that makes our bones, muscles, and tendons stronger. The issue often arises when that load exposes an underlying vulnerability that was already present.

A sudden spike in distance might not be the sole 'cause' of an injury like patellofemoral pain or medial tibial stress syndrome. Instead, it can be the final stressor that reveals a pre-existing mechanical issue - perhaps a weakness in your hip stabilisers, a restriction in your ankle mobility, or a stride pattern that becomes problematic under fatigue.

Think of the 10% spike not as a dangerous cliff edge, but as a bright spotlight. If you have robust, resilient mechanics, you should be much better placed to handle the spike. If there's a hidden weakness, the spike in load is more likely to expose it, opening the door for pain and injury. Therefore, the best injury prevention strategy combines smart load management (heeding findings like this study's) with building a resilient body through strength, mobility, and technique work.

Practical Takeaways for a Safer Running Journey

1. Respect the Single-Session Limit: Use the 10% guideline relative to your recent longest run as a sensible benchmark for planning your key long runs.
2. Don't Ignore Weekly Volume Entirely: While less correlated in this study, sudden, large jumps in weekly distance can still be stressful. A balanced approach considers both session-specific and weekly load.
3. Listen to Your Body: No formula can replace self-awareness. New niggles or pains are signals to pay attention to, not ignore.
4. Build Resilience Off the Road: Incorporate strength training, especially for the glutes, calves, and core, to help your body withstand running loads.
5. See Load Spikes as Information: If you do get injured after increasing distance, it's an opportunity to ask, "What weakness did that load expose?" rather than just blaming the mileage.