The Mileage Trap: How Fast Should You Build Running Volume?

Most runners don't get hurt because one week was ambitious. They get into trouble because several small increases stack up until the body is being asked to absorb a load it hasn't earned yet.

That's the mileage trap. A weekly increase that looks harmless on paper can become a very different plan once it compounds across a marathon block.

The most familiar guardrail is the "10% rule." It says: if you ran 40 km (25 miles) last week, this week shouldn't be more than 44 km (27 miles). Simple, memorable, and useful as a first check. Also not a law of physiology. This guide covers what the rule actually means, what the research does and doesn't support, and how to think about volume progression without turning one percentage into a commandment.

Why the Rule Became Popular

The 10% rule is usually traced to Dr. Joan Ullyot, a physician and runner whose 1980 book Running Free described a "rule of 10's." It spread because it solved a real coaching problem: runners needed a simple way to avoid the classic pattern of doing too much, too soon.

That origin explains both the rule's strength and its weakness.

The strength is practical. A runner can apply the rule without a coach, lab test, or wearable. It turns a vague warning into a number.

The weakness is that the number became more famous than the reasoning behind it. The useful idea isn't that 10% has magical protective power. It's that next week should be sized against what the body has recently adapted to.

The 10% Rule in Plain English

The rule is a week-to-week cap on total running volume. If last week was 40 km (25 miles), a 10% increase is 4 km (2.5 miles), so this week is 44 km (27 miles). Next week's increase isn't another 4 km. It's 10% of 44 km, which is 4.4 km. The week after that, 10% of 48.4 km.

That detail matters because progression is compound, not flat.

After seven increases, the runner is almost doubling weekly volume. That may be reasonable for someone rebuilding to a level they've handled before. For a new runner, or someone coming back from a long break, it can be a lot.

So the first lesson isn't "10% is safe." It's "small percentages can become large changes."

What the Research Says

The 10% rule has been tested directly, and the evidence for it as a specific injury-prevention number is thin.

The clearest direct test is Buist et al. 2008, the GRONORUN trial. Researchers assigned 532 novice runners to either a standard 8-week program or a more gradual 13-week program built around the 10% rule. Injury rates were nearly identical: 20.8% in the 10%-rule group, versus 20.3% in the standard group. The rule, by itself, did not reduce injuries.

Nielsen et al. 2014 followed 874 novice runners with GPS watches and grouped them by weekly progression: under 10% (or decreasing), 10-30%, and over 30%. Overall injury rates were similar across all three groups. The authors did note slightly elevated risk of certain knee, hip, and shin injuries in the over-30% group, but called the finding exploratory rather than conclusive.

A 2018 systematic review by Damsted et al. reviewed the running-specific evidence and concluded: "no evidence was found to support the use of the so-called '10% rule', which is commonly used by runners, coaches and clinicians."

That doesn't mean progression doesn't matter. It means the 10% line is a coaching heuristic, not a proven biological cutoff.

The broader load-management research points in the same direction, but with an important caveat. Gabbett's 2016 paper looked mostly at team-sport athletes, not runners. In that data, steady weeks were associated with lower injury risk, while bigger week-to-week jumps were associated with higher risk.

So treat it as a principle, not a running-specific rule: bodies usually handle gradual exposure better than sudden spikes.

The Better Question: What Are You Adapted To?

Two runners can both add 8 km (5 miles) next week and face very different risks. For a runner averaging 80 km (50 miles) per week, that's a 10% increase. For a runner averaging 20 km (12 miles), it's 40%. The same distance change creates very different load relative to recent history.

That relative load is the heart of volume progression. Your aerobic system tends to feel ready before your bones, tendons, and connective tissue are ready. Fitness can improve in weeks; tissue remodeling takes months. Overuse injuries often appear in the gap between the two.

Which is why the peak number alone isn't enough. A 90 km (56 miles) peak can be a natural extension for one runner and a major leap for another. The difference is the starting point, recent history, and the number of real progression weeks available.

Recovery Weeks Change the Math

A marathon block isn't a straight line from week 1 to race day. Most plans include recovery weeks (deliberately reduced-volume weeks) every 2-4 weeks, in patterns like 2:1, 3:1, or 4:1. In a 3:1 pattern, three work weeks are followed by one recovery week.

Recovery weeks deliberately reduce volume rather than continuing the climb. Their job is to make room for adaptation, not to help the weekly mileage graph look smooth.

Recovery weeks aren't progression weeks, and they shouldn't be counted as such. Peak and taper weeks aren't ramp weeks either.

That changes the math. If a 12-week ramp includes 3 recovery weeks, you only have 9 weeks where volume is actually going up. So a 40 km (25 miles) to 65 km (40 miles) build has to happen across 9 progression weeks, not 12 calendar weeks. The real weekly increase is about 5.6%, not 4.6%.

What To Do With the Number

Once you calculate the required weekly increase, don't treat it as a verdict. Treat it as pressure.

A lower number means the plan has more margin. A higher number means the plan depends on more things going right: consistent weeks, good recovery, no early niggles, and a body that has already been exposed to similar training stress.

The number becomes useful when it makes you inspect the assumptions behind the plan:

1. Have I handled this peak volume recently?
2. Are the progression weeks real, or am I counting recovery and taper weeks as if they were build weeks?
3. If I miss a week or fatigue shows up early, does the plan still have room to adjust?

If the required increase feels too steep, the fix isn't to argue with the formula. Change one of the inputs:

• Start from a higher base before the block begins
• Lower the peak target
• Choose a later race or longer training window

The point isn't to worship 10%. The point is to avoid sleepwalking into a plan where the math already says every week has to go right.

Sources

1. Buist et al. 2008. No Effect of a Graded Training Program on the Number of Running-Related Injuries in Novice Runners (GRONORUN RCT). PubMed.
2. Nielsen et al. 2014. Excessive Progression in Weekly Running Distance and Risk of Running-Related Injuries: An Association Which Varies According to Type of Injury. PubMed.
3. Damsted et al. 2018. Is There Evidence for an Association Between Changes in Training Load and Running-Related Injuries? A Systematic Review. PMC.
4. Gabbett 2016. The Training-Injury Prevention Paradox: Should Athletes Be Training Smarter and Harder? PubMed.
5. Ullyot, Joan. 1980. Running Free: A Guide for Women Runners and Their Friends. Putnam, New York. (Internet Archive scanned copy.)