How to increase running mileage without getting injured
The 10% rule, down weeks and the warning signs that separate progression from injury. A guide to raising mileage safely.
Why running injuries are almost always progression injuries
Shin splints, IT band syndrome, Achilles tendinitis, plantar fasciitis: the most common running injuries rarely come from an accident. They come from load that rose faster than the tissues could adapt. Muscles and heart adapt in weeks; tendons, bones and cartilage take months. Anyone who raises volume at the pace of their lungs, rather than their tendons, gets hurt.
The 10% rule — and its exceptions
The best-known rule of thumb is to not increase weekly volume by more than 10% from one week to the next. It works well between 20 and 60 km a week. Below 20 km, 10% is so little (1 to 2 km) that you can be a bit more generous in absolute terms; above 60 km, 10% is already 6 more km in a week and calls for more caution.
More important than the percentage is consistency: rise 10% for three weeks, step back in the fourth, and rise again from a new baseline. That three-to-one cycle is the pattern that shows up most in successful plans.
The down week: the step nobody wants to take
Every three or four weeks, cut volume by 25 to 35%, keeping frequency and a bit of intensity. That's the week when tissues consolidate the adaptation of the previous three. Skipping the down week because "it's going well" is the most expensive mistake there is: the bill arrives two or three weeks later, in the form of pain.
Volume, intensity and long run: change only one thing at a time
If volume went up, intensity stays the same. If a new interval session came in, the long run doesn't grow that week. Total load is the product of how much, how fast and how long — and the body reacts to the product, not to each factor in isolation. A good thermometer is the week's estimated load (minutes times effort): if it rose more than 15% over the average of the last four, something grew too much.
Warning signs that call for an immediate step back
Pain that appears during the run and gets worse over it. Pain that changes your stride. Localized pain at a point on a bone (shin, foot, hip) that hurts when pressed. Pain present in the morning, on getting up, for more than two consecutive days. Any of these signs calls for stopping running for a few days and, if it persists, professional assessment. Mild muscle stiffness that goes away with the warm-up is normal; pain that doesn't go away isn't.
How PaceOn helps
The rules engine limits volume progression week by week, places down weeks automatically and never lets the long run exceed the safe ceiling for your volume. When you log pain in a run, the plan reduces the next load and explains why — and the progress page shows the estimated load of each week so you can spot the pattern before it becomes an injury.
Plans by distance
Tools
Read next