Why Every Running App Still Uses a Rule Nobody Can Prove Works

All Articles

Open any running app. Sign up for a training plan. Behind the scenes, the algorithm is almost certainly doing the same thing: capping your weekly mileage increase at 10%. Every week. For every runner. Regardless of whether you run 10 km a week or 80.

The 10% rule is the most repeated piece of advice in running. It is also one of the least supported by evidence. And yet it powers the progression logic in nearly every digital training plan on the market.

Where Did the 10% Rule Come From?

The origin of the 10% rule is coaching folklore, not science. Dr. Joan Ullyot included the guideline in her 1980s running books as a simple way to help beginners avoid doing too much too soon. It was sensible advice for its time. But it was never tested in a controlled study before it became the default recommendation in running magazines, coaching certifications, and eventually, software.

The problem is not that the rule is always wrong. The problem is that it treats every runner the same. A beginner running 15 km per week gets the same progression cap as a veteran running 70 km per week. That makes no physiological sense.

Is There Any Scientific Evidence for the 10% Rule?

The most direct test of the 10% rule came from the University of Groningen in 2008. Researchers split 532 novice runners into two groups. One group followed a 13-week plan with 10% weekly increases. The other followed an 8-week plan with increases around 50% per week.

The results were striking. The 10% group had a 20.8% injury rate. The 50% group had a 20.3% injury rate. Despite increases five times larger than the rule allows, injury rates were essentially identical.

This does not mean 50% weekly increases are safe for everyone. But it does mean the 10% rule, as a blanket prescription, has no measurable protective effect in the only large-scale trial that tested it directly.

What Did the Aarhus Study Find About Safe Progression Rates?

In 2012, researchers at Aarhus University tracked 60 novice runners as they trained for their first race. None of them were told to follow the 10% rule. They simply trained and were monitored.

The uninjured runners averaged 22.1% weekly increases. The injured runners exceeded 30%. Two things matter here. First, the "safe" rate was more than double 10%. Second, the danger zone started at 30%, not at 11%.

For beginners at low mileage, the 10% rule is not just unnecessary. It is overly conservative. It holds runners back from building the volume they need to adapt and improve.

Why Does the 10% Rule Fail at High Mileage?

The rule fails in the opposite direction at high volume. Consider a runner logging 80 km per week. A 10% increase means adding 8 km, roughly two extra easy runs. That is a significant jump in absolute load on bones, tendons, and joints that are already under heavy stress.

Now consider a runner at 20 km per week. A 10% increase is 2 km. That is barely a warm-up jog. The percentage is the same, but the physiological demands are completely different.

This is why elite coaches use volume-dependent progression: they scale the increase rate to the runner's current load.

At low volume, runners can handle bigger jumps because their absolute load is modest. At high volume, even a small percentage translates to a large absolute increase that stresses connective tissue near its limits.

What Do Elite Coaches Actually Use?

As Outside Online reported, elite coaches do not follow the 10% rule. They adjust progression rates based on the individual athlete's training history, current load, and response to recent training.

The common pattern among top coaches includes three elements:

1. Volume-dependent increases. Higher percentage jumps at low mileage, smaller jumps at high mileage. The rate adapts to where the runner is, not to a fixed formula.
2. Step-loading with hold periods. After a meaningful increase, hold the new volume for 3 to 4 weeks before increasing again. This gives bones and connective tissue time to remodel. Jack Daniels' equilibrium method is built on this principle.
3. Planned deload weeks. Every 3 to 4 weeks, drop volume by about 25%. This is not lost training. It is when adaptation consolidates.

As Runners Connect notes, training volume increases should be based on how you adapt to musculoskeletal stress. At no point should a single, static percentage dictate how a runner progresses through a training program.

Does Session Spike Risk Matter More Than Weekly Totals?

A 2025 study in the British Journal of Sports Medicine tracked 5,200 runners and found something that reframes injury prevention entirely. Weekly mileage jumps were a weak predictor of injury. The much stronger predictor was single-session spikes: running dramatically farther in one workout than you had recently.

The practical guideline from this research: no single run should exceed 110% of your longest run in the past 30 days. This matters more than whether your weekly total went up by 9% or 12%.

Most running apps do not monitor this at all. They focus entirely on weekly totals and ignore the session-level risk that the research says matters most.

Why Most Running Apps Still Use the 10% Rule

The 10% rule persists in running software for the same reason it persists in coaching advice: it is simple. One number. One rule. Easy to code, easy to explain, easy to defend.

Building a volume-dependent system requires more work. The algorithm needs to know the runner's current volume, their training history, how long they have been at their current level, and when they last had a deload. It needs to monitor individual session distances, not just weekly totals. It needs to adjust the progression rate as the runner's volume changes.

That is harder to build. But it is what the evidence supports.

As research from endurance sport science confirms, progressive overload in running works best when the ramp rate matches the athlete's current training load and individual adaptation capacity. A fixed percentage ignores both.

What Should a Smart Running App Do Instead?

Based on the available evidence, a training algorithm should do the following:

1. Scale the progression rate to current volume. Allow 15–20% increases at low mileage. Drop to 5–8% at high mileage. This matches how bodies actually adapt to training load.
2. Monitor single-session spikes. Flag any planned run that exceeds 110% of the runner's longest session in the past 30 days. This is the strongest injury predictor we have.
3. Build in hold periods. After a volume increase, hold the new level for 3 to 4 weeks. Bones remodel on a 6 to 8 week cycle. Continuous weekly increases do not allow for structural adaptation.
4. Schedule deload weeks automatically. Every 3 to 4 building weeks, reduce volume by about 25%. This is standard practice among elite coaches and is supported by the step-loading research.
5. Adapt to the individual. Two runners at 40 km per week may need different progression rates depending on how long they have been at that volume, their injury history, and their age. A good algorithm accounts for context, not just a number on a spreadsheet.

References

• "The Myth of the 10 Percent Rule." Outside Online. run.outsideonline.com.
• Buist, I. et al. (2008). "No effect of a graded training program on the number of running-related injuries in novice runners." The American Journal of Sports Medicine, 36(1), 33–39. University of Groningen, n=532.
• Damsted, C. et al. (2012). "Are Increases in Running Workload Associated with Increases in Injury Risk?" International Journal of Sports Physical Therapy. Aarhus University. Study of 60 novice runners.
• Frandsen, J.S.B. et al. (2025). "How much running is too much? Identifying high-risk running sessions in a 5200-person cohort study." British Journal of Sports Medicine. PubMed.
• Daniels, J. (2014). Daniels' Running Formula, 3rd edition. Human Kinetics. Step-loading and equilibrium method for bone remodeling.
• "Reassessing the 10-Percent Rule." Runners Connect. runnersconnect.net.
• "A New Approach to the 10 Percent Rule." TrainingPeaks. trainingpeaks.com.
• "Progressive Overload and Ramp Rate in Endurance Training." FasterSkier (2025). fasterskier.com.