The rule everyone repeats
Increase your weekly mileage by no more than 10% a week. It appears in every beginner’s guide, it sounds precise, and it has the great virtue of being easy to remember. When someone tested it properly, though, it failed.
A randomized controlled trial of a graded training program1 compared a 13-week plan applying the 10% rule against a standard 8-week program in novice runners. The injury rates came out at 20.8% versus 20.3%, effectively identical. Applying the rule made no measurable difference.
That result doesn’t mean progression is unimportant. It means the specific number is arbitrary, and that something more useful is going on underneath.
What the evidence does support
The most informative study here is a 2014 prospective cohort of 874 novice runners published in the Journal of Orthopaedic & Sports Physical Therapy (JOSPT).2 It tracked runners with GPS watches over a year and grouped them by how fast they increased weekly distance: less than 10% (or a reduction), 10–30%, and more than 30%.
Runners who increased weekly distance by more than 30% over a two-week window had higher rates of a specific injury cluster: patellofemoral pain, iliotibial (IT) band syndrome, medial tibial stress syndrome, patellar tendinopathy, greater trochanteric bursitis, and gluteus medius or tensor fasciae latae (TFL) injuries.
The 10–30% band did not stand out as dangerous. So the evidence supports avoiding large spikes rather than hitting a precise weekly gradient. Somewhere above 30% you are meaningfully raising your risk; below that, the exact number matters far less than people believe. The goal stops being 10% and becomes avoiding the spike.
Why bone and tendon set the pace
Load progression matters because different tissues adapt at different speeds.
Your cardiovascular system responds quickly, with meaningful aerobic adaptation within weeks, and muscle adapts fairly quickly too. Tendon, ligament and bone adapt over months, and bone remodeling in particular involves a phase where the tissue is temporarily weaker before it becomes stronger.
That mismatch causes most of the trouble. Four to six weeks into running, your fitness has improved noticeably and your connective tissue has not caught up. You feel able to do considerably more than your skeleton is ready for, and the feeling is accurate as far as it goes; it’s just measuring the wrong system.
Every sensible progression scheme is a way of letting the slowest-adapting tissue set the pace.
A progression that works
Increase one variable at a time. Adding distance, frequency and intensity in the same week is the most reliable way to produce a spike without noticing, so pick one.
Early on, add frequency before distance. Going from three runs to four at the same duration is generally better tolerated than making three runs longer, because it spreads the load out instead of concentrating it.
The most useful habit is to hold rather than climb: repeat a week instead of always increasing. A pattern of three weeks building and one week reduced (a “down week” at roughly 70–80% of the previous week) gives connective tissue a chance to consolidate. Most people skip the down week, and it’s the part that matters most.
Judge by two-week windows rather than single weeks. Since the evidence concerns two-week windows, a single big week matters less than a sustained climb. A useful check is whether this two-week period is more than about 30% above the previous two weeks. If it is, hold.
Finally, cap the long run. A common failure is a long run that grows into a disproportionate share of the week. Keeping it under roughly a third of weekly volume stops one session from becoming the spike.
In percentage terms, a four-week block might run: week 1 at your current volume, weeks 2 and 3 each a modest step up (somewhere around 5–10%), then a down week at 70–80% of week 3. The next block starts from a slightly higher base than the last. It’s unremarkable and sustainable, and it stays well inside the safe zone.
The signals that you’re going too fast
Load progression errors usually show up before they become injuries, if you know what to look for:
- Soreness that doesn’t clear within 48 hours. Normal training soreness resolves; soreness still present at the next session means you haven’t recovered from the last one.
- Any pain that is localized, sharp, or on a bone. Diffuse muscular ache is fine, pinpoint pain is not.
- Easy pace drifting slower at the same heart rate, or heart rate elevated at your usual easy pace.
- Sleep disruption, irritability, or unusual appetite changes. These show up before performance does.
- Dread. Persistent reluctance to run, in someone who was enjoying it, is a legitimate load signal.
The correct response to any of these is a down week. That costs seven days, where an injury costs six weeks or more.
Coming back after a break
Time off is where a lot of injuries start, because people resume at the volume they stopped at. Your cardiovascular fitness does decline, but slowly, and your tissue tolerance declines faster than your enthusiasm does.
Rough guidance by length of layoff:
| Time off | Resume at |
|---|---|
| Up to 1 week | Where you left off |
| 2 weeks | ~80% of previous volume, build back over two weeks |
| 1 month | ~50%, rebuild over a month |
| 3 months or more | Start close to the beginning; treat yourself as a returning beginner |
If the break was caused by an injury rather than a vacation, be more conservative than the table suggests, and reintroduce one thing at a time: duration first, then hills, then speed.
Illness deserves its own rule. The common guidance is that symptoms above the neck (a head cold, mild sore throat) are compatible with easy running, while anything below the neck, such as chest congestion, fever or body aches, means no running at all. Running with a fever is one of the few dangerous things on this list, not just an unproductive one.
Things that let you carry more load
Progression isn’t only about restraint. Some things raise the load you can tolerate.
Strength training is the best-supported non-running intervention for injury prevention; see core workouts for runners. Keeping easy runs easy matters too, since moderate-intensity running adds tissue load without proportional benefit (more in why easy runs should feel easy). Sleep and adequate fueling count as well: under-recovery and under-eating both quietly reduce the load you can absorb. And cross-training such as cycling and swimming adds aerobic work without impact. See active recovery vs rest days.
Planning your next build
The 10% rule failed its randomized trial, so don’t treat the number as meaningful. What the evidence supports is avoiding increases above ~30% over a two-week window. The spike is the risk, not the gradient.
Connective tissue adapts in months while fitness adapts in weeks, and feeling ready is not the same as being ready. Change one variable at a time and take a down week every third or fourth week; it’s the part people skip and the part that works. If soreness lasts beyond 48 hours, pain becomes localized, or your easy pace drifts, back off now.
This article is general information, not medical or coaching advice.
References
- Buist I et al. No effect of a graded training program on the number of running-related injuries in novice runners: a randomized controlled trial. The American Journal of Sports Medicine, 2008. pubmed.ncbi.nlm.nih.gov
- Nielsen RO et al. Excessive progression in weekly running distance and risk of running-related injuries: an association which varies according to type of injury. Journal of Orthopaedic & Sports Physical Therapy, 2014. jospt.org
