You feel good. Your last few runs have been strong. You’re thinking about adding a few extra miles this week — maybe bumping your long run from 8 to 10, or throwing in an extra midweek run. You’ve got the energy. Why not?
This is the moment where most training apps say nothing. Your plan was set weeks ago, and if you want to manually add more, that’s on you. No guardrails. No feedback. Just a blank calendar that doesn’t care whether you’re making a smart decision or a dangerous one.
Pacewright won’t let you do that unchecked. Not because it doesn’t trust you, but because how fast you add volume matters, and the right rate of increase depends on how much you’re already running.
Why the 10% Rule Falls Apart
You’ve probably heard it: don’t increase your weekly mileage by more than 10%. It’s one of the most commonly cited rules in running, and it’s a reasonable starting point. But it treats every runner the same, and that’s where it breaks down.
Ten percent of 10 miles is 1 mile. That’s a trivially small increase — barely a warm-up. A beginner running 10 miles per week could safely add more than that without blinking.
Ten percent of 60 miles is 6 miles. That’s a substantial jump for a high-mileage runner — an entire extra session’s worth of stress on top of an already demanding week.
A flat percentage doesn’t account for this difference. What matters isn’t the percentage in isolation — it’s the percentage applied to a specific volume, combined with how long you’ve been running at that volume, combined with how your body is responding.
The evidence behind progression rules is also less settled than their popularity suggests. Nielsen and colleagues tracked 874 new runners for a year and found no overall difference in injury rates between those who increased their weekly distance by more than 30% and those who increased it by less than 10%. What did differ was the kind of injury: the bigger jumps pointed toward more knee, shin, hip and IT band problems, and the researchers called that signal suggestive rather than settled.2 In a separate group preparing for a half marathon, Damsted and colleagues found more injuries three weeks in among runners who increased their weekly distance by 20% to 60% than among those who increased it by less than 20%, though the difference did not hold later in the training block.3
So Pacewright’s mileage-dependent caps are a conservative progression heuristic, not a validated injury line. No study prescribes them. They exist because a flat percentage means very different things at 10 miles a week and at 60.
Mileage-Dependent Caps
Pacewright uses a tiered system where the maximum weekly increase scales inversely with your current mileage. The more you’re already running, the smaller the share you’re allowed to add on top.
Here’s why the tiers work this way.
Low mileage: You’re early in your running journey. Your cardiovascular system adapts quickly at this stage, and the absolute load on your musculoskeletal system is modest. Even a generous percentage amounts to an extra easy run or a slightly longer existing one. Your body can handle that progression, so this is where the allowance is widest.
Building a base: You’re past the beginner phase. Adaptation is still happening, but the absolute loads are getting meaningful, so the allowance tightens.
Substantial mileage: You’re running enough that your body is under significant cumulative load, and every mile you add is landing on a body that’s already absorbing a lot of impact every week. The allowance tightens again.
High mileage: Extreme caution. The margins here are thin. Additional stress accumulates on top of an already heavy weekly load, and runners at this level are more susceptible to overuse injuries because their tissues are already operating closer to their capacity. This is where the allowance is tightest.
The Stability Bonus
There’s a reward for consistency built into the system.
If you’ve held a stable weekly volume for several consecutive weeks, you earn extra headroom on your volume cap. The increase you’re allowed next week is larger than it would be if you had only just arrived at your current mileage.
Why does this make sense? Because a runner who has held steady at 25 miles for a while has demonstrated that their body can handle 25 miles. The tissues have adapted to that load. The tendons, ligaments, and bones have had time to remodel under the current stress. That established base earns a little extra room.
A runner who just jumped from 18 to 25 miles last week hasn’t earned that same confidence. Same volume, but the history is different — and the history matters.
The Single-Session Spike Guard
Volume caps aren’t just about total weekly mileage. How that mileage is distributed across individual runs matters just as much.
Pacewright enforces a single-session spike guard: no individual run may jump far beyond your longest run in the past 30 days.
This catches a specific and common mistake. You’re planning a long run and thinking “I’ll just go a little farther this week.” Your long run has been 8 miles for the past month. You go out and run 12. That’s a 50% jump in a single session, even if your weekly total stayed reasonable.
The spike guard caps it. You can push your long run up, but it has to grow out of what you’ve actually been running, not out of what the calendar says you should be at by now.
This is the limit with the strongest evidence behind it. In the largest study of runners to date, covering 5,205 runners and 588,071 recorded sessions, a session that exceeded the runner’s longest run of the previous 30 days by more than 10% was associated with overuse injury, in every band the researchers measured. The authors’ own advice to runners was to avoid exactly that jump.1
The mechanism is intuitive enough. Single-session load spikes concentrate all the additional stress into one bout. Your body doesn’t distribute the impact evenly across the week. A 12-mile run after a month of 8-mile long runs creates a dramatically different tissue demand than the same extra 4 miles spread across several easy runs.
The Long Run Limit
There’s a related constraint on long runs specifically: your long run is capped as a share of your total weekly volume, so it scales with how much you’re actually running. The share depends on what you’re training for — a marathon build earns the long run a bigger slice of the week than PT-test preparation does, where short-distance speed matters more than long aerobic capacity.
This prevents a pattern that’s especially common among time-pressed runners: running just a few days per week with one massive long run. Three 3-mile easy runs plus a 15-mile long run adds up to 24 miles — a reasonable-sounding total. But that long run is the overwhelming majority of the weekly volume, concentrated into one session. The fatigue from that single effort disproportionately affects the rest of your week’s recovery.
Capping the long run’s share of the week ensures that no single session dominates the training week. Your other runs — your speed work, your tempo efforts, your easy recovery runs — still have room to provide their specific stimulus without being undermined by excessive long-run fatigue.
Recovery Weeks: The Built-In Reset
Volume caps limit how fast you build. Recovery weeks limit how long you build before backing off.
Pacewright builds in planned recovery weeks on a repeating cycle: a run of build weeks, then a week that backs off. Most runners get the longer build cycle. Beginners, older runners, and the injury-prone back off more often, because they need the consolidation sooner.
During a recovery week, your volume drops well below your recent training load. Intensity drops too. The purpose isn’t to stop training — it’s to give your body the time it needs to consolidate the adaptations from the previous build cycle.
This is where the actual fitness improvement happens. Banister’s foundational work on the fitness-fatigue model showed that training produces both a fitness signal and a fatigue signal. During build weeks, fatigue accumulates alongside fitness. During recovery weeks, fatigue dissipates faster than fitness — so when you return to full volume, you’re genuinely fitter than when you started the cycle.
Skipping recovery weeks feels productive in the short term. Over 8-12 weeks, it leads to stagnation, persistent fatigue, and often injury. The planned reset is how you build sustainably.
How the Guardrails Work Together
No single cap tells the whole story. What makes the system work is that the guardrails are checked together on every plan update:
- Single-session spike guard checks whether any individual workout jumps too far beyond your recent longest run. This is the primary one, and the one the runner evidence supports most directly.1
- Weekly volume cap checks whether your planned mileage for next week exceeds the mileage-dependent limit.
- Stability bonus adjusts that limit based on how long you’ve been at your current volume.
- Long run limit checks whether your long run takes too large a share of the week’s total for what you’re training for.
- Your own feedback — your reported effort, how the run felt, and any soreness you log — can pull the plan back regardless of what the other checks allow.
- Periodization determines whether this is a build week (progress) or a recovery week (consolidate).
A workout might pass most of these checks and fail one. That one failure is enough to trigger an adjustment. The explanation tells you exactly which guardrail caught it and why:
“This week’s planned volume of 32 miles exceeds your cap. You’re currently at 26 miles/week, and 32 is a bigger jump than your current mileage allows. Your plan has been adjusted to sit inside the limit.”
Or: “Saturday’s long run of 11 miles exceeds your single-session limit. Your longest run in the past 30 days was 9.5 miles. Your long run has been adjusted to 10 miles.”
Every adjustment is visible. Every number is yours to examine. The guardrails aren’t hidden rules that silently modify your plan — they’re transparent constraints that you can see, understand, and track over time.
Why Constraints Make You Faster
It seems contradictory. If the goal is to get faster, why is the app limiting how much you can run?
Because the goal isn’t to run as much as possible this week. It’s to run as much as possible this year — and the year after that, and the year after that. A big individual week isn’t what makes a runner better over that kind of horizon. Staying consistent and staying healthy enough to keep training is.
A 10-week training block with 8 good weeks and 2 weeks lost to injury produces less fitness than 10 weeks of slightly lower but uninterrupted volume. The volume caps exist to keep you in that second scenario. The constraints aren’t limiting your potential — they’re protecting it.