ACWR Calculator for Runners: What It Is and How to Use It

The Acute-to-Chronic Workload Ratio (ACWR) is a training load metric that compares your recent workload to your longer-term baseline. Introduced by sports scientist Tim Gabbett in his influential 2016 paper "The training-injury prevention paradox," ACWR has become the standard framework for understanding why athletes get injured.

The formula is simple: ACWR = acute load (last 7 days) / chronic load (average of last 28 days). An ACWR of 1.0 means you're training exactly at your baseline. Above 1.0, you're doing more than usual. Below 1.0, you're doing less.

The "sweet spot" is between 0.8 and 1.3. In this range, you're training hard enough to build fitness but not so far above your baseline that injury risk spikes.

Gabbett's research across multiple sports found that athletes with an ACWR above 1.5 were 2-4× more likely to sustain an injury in the following week. Critically, athletes with an ACWR below 0.8 (undertrained) were also at elevated risk — the training-injury prevention paradox.

For runners specifically, Maupin et al. (2020) applied ACWR to distance runners and found that spikes above 1.3 in weekly mileage correlated with a significant increase in overuse injuries, particularly tibial stress injuries and Achilles tendinopathy.

The practical implication: you need to train consistently (keeping chronic load high) and increase progressively (keeping acute-to-chronic ratio below 1.3). Boom-and-bust training — big weeks followed by rest weeks — is the highest-risk pattern.

When you connect Strava or Garmin to injury.vision, we import your activity history and compute training stress score (TSS) for each session based on duration, distance, and intensity (normalized pace relative to your functional threshold pace).

Your ACWR is recalculated daily: - Acute load: sum of TSS from the last 7 days - Chronic load: exponentially weighted moving average of TSS over 28 days - ACWR: acute / chronic

We use the exponentially weighted moving average (EWMA) method rather than the simple rolling average, as Menaspà (2017) showed EWMA is more sensitive to day-to-day fluctuations and produces fewer false negatives.

Your ACWR is one of five components in your overall injury risk score. The others — TSS spike, intensity risk, cumulative fatigue, and injury history — each capture a different dimension of injury risk that ACWR alone can miss.

The "10% rule" (never increase weekly mileage by more than 10%) is running's most popular safety guideline, and also its most oversimplified. The rule doesn't account for:

- Your individual training history — a runner with years of 80km weeks can handle a 10% jump more safely than a beginner at 20km - Intensity changes — adding a tempo run at the same mileage can spike load more than adding easy miles - Recovery context — returning from 2 weeks off, a 10% increase from zero is meaningless

ACWR solves all three problems. It's personalized (based on your actual training history), load-sensitive (uses TSS, not just distance), and context-aware (your chronic load reflects recent consistency or lack thereof).

1. Check your ACWR before planning your week. If it's above 1.2, keep the next few days easy. If it's below 0.8, you may be detraining. 2. Use the What-If Planner. injury.vision lets you input a planned run (distance + pace) and see how it would change your risk score before you run it. 3. Build chronic load steadily. The best way to stay in the safe zone is to train consistently. A high chronic load means a bigger denominator, which means you can handle bigger individual sessions without spiking ACWR. 4. Respect the return window. After time off (illness, injury, travel), your chronic load drops. Even a normal training week can spike your ACWR. Use RTR protocols that account for detraining.