Every year, roughly 50% of recreational runners get injured. That number has stayed stubbornly consistent across decades of research, despite better shoes, better nutrition science, and better access to coaching. The reason is straightforward: most running injuries are not caused by running itself, but by doing too much too soon. And the single best tool we have for quantifying "too much too soon" is training load.
A 2015 systematic review published in the British Journal of Sports Medicine identified training errors as the primary cause of running-related injuries, accounting for 60-70% of all cases. These aren't freak accidents. They're the predictable result of ramping up volume, intensity, or frequency faster than the body can adapt.
Your muscles adapt to new stress within about two weeks. Tendons take four to six weeks. Bones can take months. When you increase your running load faster than your slowest-adapting tissue can handle, something gives. Usually it's the Achilles tendon, the plantar fascia, or the tibial bone (shin splints progressing to stress fractures).
This is where training load monitoring changes the game. Instead of guessing whether you're doing too much, you can measure it.
Training load is a way of quantifying the total stress a workout places on your body. It combines three factors:
The simplest way to calculate it is using session RPE (Rate of Perceived Exertion). After each run, rate the overall difficulty from 1-10, then multiply by the duration in minutes. A 45-minute easy run at RPE 4 gives you a load of 180. A 30-minute tempo run at RPE 8 gives you 240. The tempo run was shorter but harder, and the numbers reflect that.
More advanced methods use heart rate zones, pace-based load (like TRIMP or Training Stress Score), or power meter data. But session RPE is surprisingly well-correlated with these more complex metrics. Research by Carl Foster's group showed correlations of 0.84-0.90 between session RPE and heart rate-based methods. In practice, your subjective feeling of effort is a remarkably good sensor.
Knowing your training load for a single week is useful. But the real insight comes from comparing your recent load to your historical load. This is the acute-to-chronic workload ratio (ACWR), developed by Tim Gabbett and widely used in professional sport since the mid-2010s.
The concept is simple:
An ACWR of 1.0 means you're training exactly as much as your recent average. Above 1.0 means you're doing more than usual. Below 1.0 means you're doing less.
Research across multiple sports has identified three zones:
Let's say you're a runner averaging 40 km per week over the past month. Using distance as a simplified load metric:
Your chronic load is the 4-week average: 40 km. Now, in Week 5, you're feeling great and you run 55 km. Your ACWR is 55 / 40 = 1.375. That's right at the upper edge of the sweet spot — possibly manageable, but you'd want to pull back in Week 6.
If instead you ran 65 km in Week 5, your ACWR would be 65 / 40 = 1.625. You're deep in the danger zone. This is the kind of spike that precedes Achilles tendinopathy, IT band syndrome, or a stress reaction.
The fix isn't to stay at 40 km forever. It's to increase gradually. Going from 40 to 44 (ACWR = 1.1), then from that higher base to 48, then 52 — you reach 65 km eventually, just without the injury.
You've probably heard the advice "never increase weekly mileage by more than 10%." It's not bad advice, but it has limitations. Ten percent of 20 km is just 2 km — an increase that's almost certainly safe even if it were larger. Ten percent of 120 km is 12 km — which might be too much if it's all added as a single long run.
The ACWR is a better framework because it accounts for your individual training history. A runner with a high chronic load can tolerate bigger absolute increases than a runner with a low chronic load. The 10% rule treats everyone the same; the ACWR is personalised to your fitness.
Calculating ACWR manually is doable but tedious. You need to log every session's load, maintain a rolling 28-day history, and compute the ratio each week. Most people won't sustain this in a spreadsheet.
GPS watches from Garmin, Polar, and COROS now build in some form of training load tracking. Running apps can also automate this — PaceGrid, for example, includes an Injury Guard feature that calculates your ACWR automatically and alerts you when you're entering a high-risk zone. The value of automation is that the system catches spikes you might not notice yourself, especially when life disruptions (travel, illness, a busy work week) create unplanned dips followed by compensatory surges.
Training load is the biggest lever, but it's not the only one. Several other variables modulate your injury risk:
Beyond training load, two recovery metrics have strong research support:
Neither metric should override how you feel. If your HRV looks fine but your legs feel like concrete, take the easy day. Subjective fatigue is data too.
The evidence is clear: most running injuries are preventable, and training load management is the most effective prevention strategy we have. Here's the practical summary:
Running is one of the simplest and most effective forms of exercise. The goal of training load management isn't to make it complicated — it's to keep you running consistently, month after month, without the setbacks that derail most training plans.