Most runners who get injured aren’t doing anything obviously reckless. They’re not sprinting into a wall or doubling their mileage overnight. They’re adding a few extra miles here, an extra hard session there, maybe jumping back in after a week off with the same workouts they were doing before the break.

The injuries come from a pattern, not a single mistake. And there’s a number that captures that pattern.

What ACWR Actually Is

Your acute:chronic workload ratio compares two things: how much training you’ve done recently versus how much training you’ve been doing over a longer period.

  • Acute load is your training from the past 7 days — what you’ve done this week.
  • Chronic load is your rolling average over the past 28 days — what your body is accustomed to.

Divide acute by chronic, and you get a ratio. That ratio tells you whether your current training is in line with your recent history or whether you’re ramping up faster than your body has been prepared for.

Here’s a concrete example. Say you’ve been running about 20 miles per week for the past month. Your chronic load reflects that 20-mile average. This week, you’re feeling good, so you run 28 miles. Your ACWR would be roughly 1.4 — meaning this week’s load is 40% higher than what your body is used to.

That 1.4 is in the caution zone. Not because 28 miles is inherently dangerous, but because it’s a significant jump from your recent baseline.

The Research (And What It Actually Shows)

Tim Gabbett’s 2016 research in the British Journal of Sports Medicine is the paper that put ACWR on the map. Working primarily with team sport athletes (rugby, cricket, Australian football), Gabbett found a consistent pattern: when ACWR climbed above 1.5, injury rates spiked sharply. The relationship wasn’t subtle — athletes in that high-ratio zone were 2-4 times more likely to get injured than those in the 0.8-1.3 range.

Earlier work by Hulin and colleagues in 2014 showed the same thing with cricket fast bowlers: spikes in acute workload relative to chronic workload were the strongest predictor of injury they measured.

Blanch and Gabbett followed up in 2016 with practical guidelines for return-to-play decisions, using ACWR as a tool to quantify whether an athlete had rebuilt enough chronic load to handle match demands safely.

The Honest Caveat

Here’s where transparency matters. Most of the foundational ACWR research was conducted on team sport athletes — rugby players, cricketers, footballers — not recreational runners. The loads being measured were often collision-sport loads, not pure endurance loads.

There’s also legitimate scientific debate about the method. Impellizzeri and colleagues published a 2020 paper questioning the mathematical properties of the ratio itself, arguing that the ACWR has conceptual issues including spurious correlations (because the acute load appears in both the numerator and the denominator of the rolling average calculation). Williams and colleagues proposed using exponentially weighted moving averages (EWMA) instead of simple rolling averages, arguing it better accounts for how training load accumulates.

So why does Pacewright still use ACWR? Because the underlying principle is solid even if the specific metric is debated. Rapid spikes in training load increase injury risk. That finding is consistent across sports, across methodologies, and across decades of research. ACWR is the best practical tool we have for capturing those spikes — not because it’s a perfect predictor, but because it catches the pattern that hurts runners most: doing too much too soon.

Pacewright uses EWMA-based ACWR (the more sophisticated calculation) and treats it as a guardrail, not a crystal ball.

The Three Zones

Pacewright calculates your ACWR every time your plan updates, and it falls into one of three zones:

Green: 0.8 – 1.3

Your current training is within your established capacity. Your acute load is close to what your body is accustomed to handling. The plan proceeds as written.

This is where you want to spend most of your training time. A ratio near 1.0 means you’re training at almost exactly your recent average. A ratio of 1.2 means you’re pushing slightly above baseline, which is how you make progress — gradual, controlled increases.

Yellow: 1.3 – 1.5

Caution. You’re training noticeably more than your recent history supports. This isn’t automatically dangerous, but it’s the zone where risk starts to climb.

When your ACWR enters yellow, Pacewright may adjust your plan. Common responses include reducing tomorrow’s distance, swapping a hard session for an easy one, or shifting a long run to later in the week when your acute load will have dropped.

You’ll see exactly what changed and why: “Your ACWR is 1.35 — training load this week is 35% above your 28-day average. Tomorrow’s 6-mile tempo has been replaced with a 4-mile easy run.”

Red: Above 1.5 or Below 0.7

Intervene. If ACWR is above 1.5, you’re in the spike zone — the range where Gabbett’s research shows injury risk jumps dramatically. Volume gets cut, intensity drops, and your plan shifts to protect you.

If ACWR is below 0.7, it means your recent training has dropped well below your established baseline. This often happens after illness, vacation, or a period of missed runs. The risk here is different: when you come back, your body isn’t conditioned for what it could handle a month ago. Pacewright ramps you back gradually instead of dropping you back into your old plan.

Why “Below 0.7” Matters Too

Most people think about ACWR in terms of doing too much. But the low end is just as important for runners.

Imagine you’ve been running 30 miles per week for two months. Then life happens — you travel for work, get sick, or just take a break. For two weeks, you run 8 miles total. Your chronic load is still anchored around 30, but your acute load has cratered.

When you come back and try to pick up where you left off, your ACWR spikes immediately. Your body remembers being a 30-mile runner, but your muscles, tendons, and bones have already started detraining. This is exactly the scenario where injuries happen — returning too aggressively after a break.

Pacewright detects this gap and builds you back in. You won’t see your old plan on day one. You’ll see a reduced plan with a clear timeline for returning to your previous volume.

How Training Load Is Calculated

ACWR needs a way to measure “how much” you trained, not just “how far” you ran. Five easy miles and five hard miles aren’t the same stress on your body.

Pacewright calculates training load as:

Duration (minutes) × RPE (1-10)

RPE is your Rate of Perceived Exertion — how hard the session felt on a scale of 1 to 10. A 45-minute easy run at RPE 3 produces a training load of 135. A 45-minute tempo run at RPE 7 produces a load of 315. Same duration, very different stress.

This is a deliberate choice. Duration × RPE works without a GPS watch, without a heart rate monitor, without any gear at all. It accounts for factors that pace and heart rate miss: heat, sleep quality, accumulated fatigue, stress. And it correlates well with more complex measures in the research.

Your acute load is the EWMA of your daily training loads over the past 7 days. Your chronic load is the EWMA over the past 28 days. The ratio of acute to chronic is your ACWR.

What You Can See in the App

Pacewright doesn’t hide the math. You can see:

  • Your current ACWR and which zone it falls in
  • Your acute and chronic load numbers
  • A rolling chart showing how your ACWR has changed over time
  • The specific reason when a workout is modified because of ACWR

If your ACWR triggers a plan change, the explanation is specific: “Your ACWR is 1.42. Your training load this week (acute: 680) is significantly higher than your 28-day average (chronic: 479). Tomorrow’s interval session has been replaced with an easy 3-mile run to bring your ratio back toward the safe zone.”

No mystery. No “trust us.” The numbers are yours.

ACWR Is One Tool, Not the Only Tool

ACWR doesn’t exist in isolation in Pacewright. It works alongside volume caps (which limit how much your weekly mileage can increase), single-session spike guards (which prevent any individual run from being too long relative to your recent history), and your intensity distribution (which keeps the 80/20 balance in check).

A run might pass the ACWR check but get flagged by the volume cap. Or ACWR might be fine while your intensity distribution has drifted too far toward hard running. The guardrails work together.

ACWR is the primary safety number — the one that catches the most common way runners get injured. But it’s not the only one, and we’re honest about its limitations. The science is strong on the principle. The specific number is a tool. Pacewright uses it carefully, shows you the math, and lets you make informed decisions about your own training.