Source notes

How quickly can a runner increase training without getting hurt? Only four studies met the paper's criteria for examining changes in running load and injury. Three suggested a possible association between increased load and injury, but the findings were not consistent or equally convincing. In the randomized study, injury occurred in about 21% of the graded-program group and 20% of the standard-program group. Average weekly volume increased by about 10% and 24%, respectively. The comparison did not demonstrate that the smaller increase prevented injuries, and the evidence did not establish a reliable universal threshold.

Some findings concerned specific injury categories rather than all running injuries. One estimate for distance-related injuries suggested higher risk above a 30% increase, but its uncertainty range included no difference. The studies also defined a change differently, from week-to-week mileage to vaguely described recent adjustments. These details prevent a simple conversion of the findings into a single percentage that separates safe training from harmful training.

How Does This Show Up in Real Life?

A training plan may present a weekly percentage limit as though it were a proven safety boundary. This paper does not support that level of certainty. It also does not show that sudden increases are harmless. The useful distinction is between a plausible concern about doing too much and evidence for one exact numerical rule. Starting mileage matters when interpreting percentages: the authors note that moving from two to three kilometers is a 50% increase, despite adding only one kilometer. That situation differs from adding the same proportion to a high-volume runner's schedule. The study provides no replacement percentage that works for everyone, so a reader should not interpret its uncertainty as permission to ignore their own training history or symptoms.

The evidence was limited to novice and amateur runners, with varied methods and study quality. Some studies relied on recalled changes, and follow-up periods differed. Few studies established timing and causation clearly enough to test a preventive rule. The available comparisons therefore cannot determine whether a particular progression strategy provides lasting protection across runners of different abilities.

Why We Cite It

Alpekin can use this source to assess how confidently a numerical training rule is presented. It offers a basis for checking whether a recommendation came from an actual comparison of programs or from an assumed mechanism, and for retaining uncertainty when the supporting studies measure different kinds of change.

Treat precise safety cutoffs cautiously when the evidence behind them is thin. The paper is useful for identifying what was still untested, rather than replacing one rigid rule with another. Better definitions and studies of varied runners are needed for more dependable guidance.