Weekly Running Mileage Planner
Plan your running base using the 10% rule.
Enter current weekly mileage and goal to get a week-by-week schedule with cutback weeks.
The 10% rule — where it came from
The most widely-quoted injury-prevention guideline in distance running: never increase weekly mileage by more than 10% from one week to the next.
The rule first appeared in Runner’s World in the 1980s. Joe Henderson, a longtime running writer, credited it to Joan Ullyot’s 1980 book Running Free. It wasn’t research-derived initially — it was practical wisdom from coaches observing injury patterns.
The formula:
Next week’s mileage = This week’s mileage × 1.10
Example progression starting at 15 miles/week:
- Week 1: 15 mi
- Week 2: 16.5 mi
- Week 3: 18.2 mi
- Week 4: 20.0 mi
- Week 5: 22.0 mi
- Week 10: 35.4 mi
- Week 15: 57.1 mi
- Week 20: 91.9 mi
To reach a specific goal from a starting point, the math:
Weeks = log(Goal ÷ Current) ÷ log(1.10)
So going from 20 mi/week to 40 mi/week takes about log(2)/log(1.10) = 7.3 weeks of straight build.
Does research support the 10% rule?
Surprisingly, the 10% rule has weaker direct research support than its widespread use suggests. Several studies have looked specifically at training load progression:
Buist et al. 2008 (BJSM): tested the 10% rule in 532 novice runners over 8 weeks. Found NO significant difference in injury rates between graduated (10% rule) and accelerated training groups.
Nielsen et al. 2014 (BJSM): studied 873 novice runners. Found that runners who increased weekly mileage by 30%+ in single weeks had higher injury rates, but found no protective effect of strict 10% adherence.
Drew & Finch 2016: meta-analysis suggested acute:chronic workload ratio (ACWR — current week vs prior 4 weeks) matters more than absolute weekly increase.
The current consensus among sports scientists is more nuanced than the simple 10% rule:
- Sudden large jumps (>25-30%) clearly increase injury risk
- Steady moderate progression is safer than abrupt spikes
- The exact percentage matters less than consistency and recovery
- The 10% rule is a useful guideline, not a precise mathematical law
Why the rule exists despite mixed research
The 10% rule persists because:
- It’s simple to remember and implement
- It’s conservative (errs on the side of injury prevention)
- Coaches observe injury spikes when athletes violate it
- It accounts for the fact that connective tissue adapts slower than cardiovascular fitness
Most runners are better served by following the 10% rule loosely than by ignoring progression entirely. The science is murky; the practical wisdom holds.
Cutback weeks — the often-skipped key
Most progressive training plans include cutback weeks every 3rd or 4th week. Cutback weeks reduce volume by 20-30% to allow recovery and fitness consolidation.
| Week | Mileage |
|---|---|
| 1 | 30 mi |
| 2 | 33 mi |
| 3 | 36 mi |
| 4 (cutback) | 29 mi |
| 5 | 36 mi |
| 6 | 40 mi |
| 7 | 44 mi |
| 8 (cutback) | 35 mi |
Without cutback weeks, fatigue accumulates and injury risk climbs. Many runners feel great in week 3-4 and skip the cutback — only to break down by week 6-8.
The biology: during high-load training, micro-damage in connective tissue accumulates. Cutback weeks allow this damage to repair faster than new damage accrues. Skip them, and you’re constantly behind on repair.
The connective tissue adaptation lag
Different tissues adapt at different rates:
- Cardiovascular fitness: 1-3 weeks for noticeable improvement
- Muscular adaptations: 2-6 weeks
- Tendons: 8-12 weeks
- Ligaments: 6-10 weeks
- Bone: 6-12 months for full remodeling
This is the underlying logic of progressive training. Your aerobic system can handle more miles long before your bones, tendons, and ligaments can. If you push miles faster than connective tissue can adapt, you get:
- Stress fractures (especially metatarsals, tibia)
- Achilles tendinopathy
- Plantar fasciitis
- IT band syndrome
- Patellofemoral pain
- Shin splints
These overuse injuries account for ~50-70% of running injuries per season.
The “rule of 7”
A complementary guideline from coach Hal Higdon: long runs should not exceed 33% of weekly mileage, and back-to-back long runs are dangerous.
Example: if you run 40 mi/week, your long run should max at 13 miles. Marathon training plans that schedule 20-mile long runs in 30 mi/week schedules are mathematically violating this and often produce injuries.
Acute:Chronic Workload Ratio (ACWR)
Modern sports science uses the Acute:Chronic Workload Ratio, popularized by Tim Gabbett’s research in Australian rugby:
ACWR = Current week’s load ÷ Average of past 4 weeks’ load
| ACWR | Injury risk |
|---|---|
| 0.8-1.3 | “Sweet spot” — low risk |
| < 0.8 | Detraining; risk on return |
| 1.3-1.5 | Elevated risk |
| > 1.5 | “Danger zone” — significantly elevated risk |
So the 10% rule corresponds roughly to ACWR of 1.0-1.1, well within the safe zone. Sudden 30-50% jumps push ACWR to 1.3-1.5 (danger zone).
Coming back from injury or break
After any layoff of 1+ weeks, don’t return to your previous peak. General guidelines:
- 1 week off: resume 80-90% of previous mileage
- 2 weeks off: resume 70-80%, build back over 3-4 weeks
- 4 weeks off: resume 50-60%, build back over 6-8 weeks
- 8+ weeks off: start essentially fresh, build over 8-12 weeks
This is where many comeback injuries happen. A runner who was at 50 mi/week before injury, sidelined 6 weeks, comes back trying to hit 50 immediately — and gets re-injured within 2 weeks.
Build cycles for specific race distances
Typical mileage build durations:
| Goal | Base needed | Build duration | Peak weekly mileage |
|---|---|---|---|
| 5K (recreational) | 15 mi/week | 6-8 weeks | 25-30 mi |
| 5K (competitive) | 25 mi/week | 8-12 weeks | 40-50 mi |
| 10K | 20 mi/week | 8-12 weeks | 35-50 mi |
| Half marathon | 25 mi/week | 12-16 weeks | 40-60 mi |
| Marathon (first) | 30 mi/week | 16-20 weeks | 50-65 mi |
| Marathon (competitive) | 40 mi/week | 16-20 weeks | 60-90 mi |
| Ultramarathon (50K-100K) | 50 mi/week | 20-26 weeks | 70-110 mi |
For first-time marathoners, follow a proven 18-20 week plan (Hal Higdon, Hansons, Pfitzinger) rather than trying to wing your own progression.
Time-based vs mileage-based progression
Some coaches prefer time-based weekly load (e.g., “5 hours of running per week”) instead of mileage. Advantages:
- Accommodates pace differences (a slow runner gets less mileage at the same time)
- Easier to plan around work schedules
- Less ego-driven
Disadvantages:
- Doesn’t reflect distance-specific demands (marathon training does need long miles)
- Pace creep can sneak in (runs get faster, not longer, with time-based plans)
Most US coaches use mileage; many European coaches use time. Either works if you’re consistent.
The most common 10% rule mistakes
- Jumping back from a race: ran a 26-mile marathon Saturday, back to 35 mi/week Monday. Should be 50-60% of normal for 2 weeks post-marathon.
- Ignoring cutback weeks when feeling good: this is exactly when cutbacks matter most
- Treating long runs as separate from total mileage: long runs are part of your weekly load
- Forgetting weeks count from zero after injury: post-injury mileage is essentially starting over
- Adding intensity AND volume simultaneously: increase one or the other, not both
- Ignoring sleep: under-recovered runners need slower progressions
Bottom line
The 10% rule (max 10% mileage increase per week) is a useful injury-prevention guideline, though direct research support is mixed. The underlying principle holds: connective tissue adapts slower than cardiovascular fitness, so progression must be gradual. Build cycles with cutback weeks every 3-4 weeks. ACWR (current week vs. 4-week average) of 0.8-1.3 is the modern “sweet spot.” After breaks, restart at 50-80% of previous peak. For first-time race builds, follow proven plans rather than designing your own progression. The most important factor isn’t precise percentages — it’s consistency, sleep, and listening to your body when fatigue accumulates.