Controversial: the fastest path to progress is often smaller steps, not bigger weeks.
Instead of chasing higher numbers, focus on timing, wait until you’ve had at least one stable week or 7 to 14 days since a meaningful change, and let performance, sleep, soreness, resting heart rate and HRV (heart rate variability) sit near your baseline before adding more.
When you add load, change only one variable and keep increases to 5 to 10% per week.
This approach helps you get fitter while cutting risk and making your training easier to judge.
Practical Readiness Check for Adding Training Stress
![]()
Here’s the simple version. Increase only one training variable at a time, and only after you’ve had at least one stable week, or 7 to 14 days since your last meaningful change. Your performance, sleep, soreness, resting heart rate, and HRV (heart rate variability, a measure of how your nervous system is recovering) should sit close to your normal baseline before you add more. When you do increase load, a conservative ceiling of around 5 to 10% per week is a reasonable guardrail. But, and this matters, that number is a maximum to stay under, not a goal to hit every single week.
So what is training load, exactly? It’s really two things combined. There’s external load, which is the actual work you do, your distance, your speed, the weight on the bar, the number of reps. Then there’s internal load, which is how your body responds to that work. Two people can run the same 10 km and end up with very different internal loads depending on sleep, stress, and fitness. Knowing when to increase training load safely comes down to this: match the external push to what your internal system can currently absorb.
Rapid spikes are the real danger here, more than a high but steady workload ever is. A body that’s handled a demanding week for a month is often safer than one that’s jumped into that same week cold.
| Decision | Measurable Criteria | Action |
|---|---|---|
| Increase | At least 7 stable days or 7-14 days since the previous meaningful change; normal performance; no persistent soreness; sleep, resting heart rate, and HRV close to personal baseline | Increase one variable only, staying at or below the conservative 5-10% ceiling |
| Hold | One or more mild deviations from baseline, soreness lasting beyond 48 hours, an unexpectedly hard session, or unclear recovery data | Keep current load steady and reassess after several stable sessions |
| Deload | Declining performance across at least 2 sessions, worsening pain, marked fatigue, soreness lasting more than 72 hours, resting heart rate repeatedly up 5-7 bpm, or HRV notably below baseline for several days | Reduce volume or intensity and consider whether further recovery or professional input is needed |
This is safe training progression in practice, and it leans on timing more than any single app reading. A weird HRV number on a Tuesday morning doesn’t mean much on its own. What matters is the pattern over several days, paired with how you actually feel and perform.
How to Calculate and Interpret the Acute-to-Chronic Workload Ratio
(((alt-img2)))
The acute chronic workload ratio (often shortened to ACWR) is one tool among several for thinking about training stress. It’s not the gold standard, and it’s definitely not a crystal ball for predicting injury. Think of it as a rough snapshot, useful alongside other information, not instead of it.
Here’s the ACWR calculation in three steps:
- Calculate your acute workload, usually the most recent 7 days of training.
- Calculate your chronic workload, usually a rolling 28-day average or a 3 to 6 week window. Pick one method and stay consistent with it.
- Divide acute by chronic. The resulting number tells you how this week compares to your recent normal.
Here’s how that plays out across different sports:
| Sport | Chronic Load | Acute Load | ACWR |
|---|---|---|---|
| Running | 40 km average | 52 km current week | 1.3 |
| Cycling | 500 session-RPE x minutes average | 600 current-week units | 1.2 |
| Team sport | 2,000 session-RPE x minutes average | 3,000 current-week units | 1.5 |
You’ll often see the ranges 0.8 to 1.3, above 1.3, and 1.5 or higher referenced as “safe,” “caution,” and “danger” zones for ACWR. Those numbers come from population-level research, though, not a guaranteed line for you personally. Sport-specific training load varies so much that a 1.5 in team sport sprinting isn’t the same stress as a 1.5 in easy cycling hours.
A few honest limitations worth knowing:
- The result changes depending on which averaging method you choose for chronic load.
- Acute workload is part of chronic workload, which creates a built-in mathematical link between the two numbers (sometimes called mathematical coupling).
- It doesn’t capture everything that matters, things like session intensity distribution, sleep, or stress outside training.
- It has limited power to predict injury for any one individual, even when population trends look convincing.
If you want a fuller picture, pair ACWR with session-RPE, performance trends, recovery data, and a periodized plan. None of these replace the others. They just fill in different gaps.
The 10% Rule, Microloading, and Individualised Progression
(((alt-img3)))
The 10% rule for training says don’t raise your training load by more than 10% from one week to the next. It’s a decent guardrail, especially for beginners, but it was never meant to be a scientifically precise formula that works for everyone. Here’s the tricky part. Even a 5 to 10% increase can be too much if intensity is already high, recovery is lagging, or you’re new to structured training. A weekly percentage increase only tells part of the story.
| Progression Approach | How It Works |
|---|