Workload Monitoring

The 10% Rule vs. ACWR: Comparing Two Workload Monitoring Approaches

· 7 min read · Yariv Katz

Two rules, one question

Every load-management conversation eventually lands on the same question: how fast can I safely increase training? Two models dominate the answer. The 10% rule — never increase weekly load by more than 10% over the previous week — has been handed down between coaches for decades. The acute:chronic workload ratio (ACWR), popularised by Tim Gabbett's research, compares this week's load against what the athlete has actually been prepared for over the past month. They look similar on paper. In practice, they catch very different problems — and only one of them has a real baseline.

What the 10% rule actually says

The 10% rule is a ceiling on week-over-week progression: if your athletes ran 100 kilometres or accumulated 3,000 arbitrary units (AU) of sRPE load last week, cap this week at 110 km or 3,300 AU. Its appeal is obvious:

  • It's simple. One number, one comparison, no spreadsheet gymnastics.
  • It scales to any metric. Kilometres, throws, minutes, sRPE load — the rule doesn't care.
  • It prevents the classic blunder. Most overuse spikes are not 10% jumps; they're 40–80% jumps caused by a postponed match, a double session or an enthusiastic returning athlete. A hard ceiling catches most of those.

For a beginner in steady, monotonous training, the rule works reasonably well. The problem is that very few real athletes live in steady, monotonous training.

Where the 10% rule breaks down

Problem 1: it ignores the athlete's history

The rule only looks at last week. It has no memory. An athlete who trained 4,000 AU per week for a year, then took a two-week holiday, can follow the 10% rule perfectly — 1,000 AU, 1,100 AU, 1,210 AU — and still be training at a quarter of their prepared level, losing fitness with every conservative week. Worse, the rule invites the opposite failure: once the athlete claws back to their old level, the rule permits a permanent +10% climb, week after week, with nothing ever anchoring the number to what the athlete's tissues can actually tolerate. Ramps of 10% per week compound relentlessly: six compliant weeks is a 77% increase.

Problem 2: it punishes athletes returning from injury

Rehabilitation is exactly where load management matters most, and it's exactly where the 10% rule is most misleading. A player whose chronic load is 3,000 AU resumes at 1,200 AU after a hamstring tear. The rule happily approves 1,320, 1,452, 1,597 AU — a mathematically compliant ramp that still leaves the athlete at half their chronic load for weeks, undertrained and deconditioned, before a single full session then delivers a 60% spike that no weekly rule ever saw coming. The dangerous spike isn't a violation of the 10% rule — it's the return to normal training that violates it. The rule flags the wrong moment.

Problem 3: it treats a spike and a dip identically

A week at −30% (travel, illness, deload) followed by a "return to schedule" week at +43% triggers the rule's alarm — even though that athlete's 28-day load is unchanged and their body is prepared for exactly that session. Meanwhile a genuinely risky pattern — five weeks of creeping load, each inside 10%, stacked on top of an already-high baseline — passes every check.

What ACWR does differently

The acute:chronic workload ratio replaces "last week" with a baseline: the athlete's own recent average.

  • Acute load = total load over the last 7 days (plus today's session)
  • Chronic load = average weekly load over the last 28 days
  • ACWR = acute ÷ chronic

An ACWR of 1.0 means this week matches what the athlete is prepared for. The research-backed zones are:

  • Below 0.8 — under-training; fitness is drifting (common after layoffs)
  • 0.8–1.3 — a commonly cited reference range
  • 1.3–1.5 — caution; watch recovery, sleep and soreness
  • Above 1.5 — a large increase relative to recent load; review with staff. ACWR and sRPE are monitoring tools, not medical diagnoses or universal safety thresholds.

Why the baseline matters

Chronic load is a *personal* number. A 3,500 AU week is routine for a professional midfielder and catastrophic for a returning youth player — and the 10% rule cannot tell them apart, because it never asks who is doing the training. ACWR does. It also answers the return-from-injury question directly: instead of guessing "10% of what?", you ramp deliberately toward the chronic number, keeping each week's ratio inside the commonly cited range until the athlete is genuinely re-prepared.

Head to head

10% RuleACWR
Reference pointLast week only28-day personal baseline
Data needed2 weeks4 weeks to establish
Experienced athletesPermits endless +10% compoundingAnchored to prepared load
Return from injuryFlags the wrong momentGuides the ramp back to baseline
Detects under-trainingNoYes (ACWR < 0.8)
Detects load spikesOnly >10% week-over-weekAny spike above the personal norm
IndividualisationNoneFully athlete-specific
Setup effortNear zeroLow with the right tool

How should the two approaches be used?

The honest answer: the 10% rule is a crude subset of what ACWR measures. Every load spike that violates the 10% rule also drives ACWR above the commonly cited range — but not every dangerous ACWR pattern violates the 10% rule. The compounding six-week climb, the under-trained athlete returning to full sessions, the post-illness rebound — all invisible to a week-over-week ceiling, all flagged by the ratio. Gabbett's surveillance studies associate ACWR spikes above 1.5 with substantially raised injury risk in subsequent days; no equivalent evidence base exists for the 10% figure, which originated as a practical guideline for novice runners, not a validated threshold.

Use the 10% rule for what it's good at: a quick sanity check for novices in steady training, and a simple conversation starter with athletes. But the moment your squad includes experienced athletes, congested fixtures, or anyone coming back from injury — which is every real team — the ratio is the model that sees the risk.

Running both without drowning in spreadsheets

You don't need to choose in theory; you need one number per athlete per week in practice. The workflow that survives a real season:

1. Collect sRPE after every session — duration × RPE (1–10), ten seconds per athlete. The sRPE calculator does the arithmetic.

2. Check the ramp weekly — the 10% rule calculator gives you the classic green/yellow/red read on week-over-week change.

3. Let the ratio decide — ACWR, zone badges and spike alerts update automatically on the FitLoad team dashboard.

Ten percent keeps you from the obvious mistakes. The ratio keeps you from the ones that actually end seasons.

🤖 Ask FitLoad AI about this topic

Got a question about this article? Our sports-science assistant answers in seconds.