Skip to main content

Injury Risk Heuristic Training Load Calculator

Calculate injury risk heuristic training load with our free tool. Get data-driven results, visualizations, and actionable recommendations.

Reviewed by Daniel Agrici, Founder & Lead Developer

Reviewed by Daniel Agrici, Founder & Lead Developer

Formula

ACWR = Acute Load (this week) / Chronic Load (4-week average)

The Acute:Chronic Workload Ratio divides the current week training load by the rolling 4-week average. An ACWR between 0.8-1.3 is the sweet spot. Session load is calculated as RPE (1-10) multiplied by duration in minutes. Training monotony is mean daily load divided by standard deviation, and strain is weekly load multiplied by monotony.

Worked Examples

Example 1: Pre-Season Training Spike

Problem:An athlete has a 4-week chronic load of 450 AU/week. This week they jumped to 750 AU. Previous week was 500 AU. Today session was RPE 8 for 90 minutes.

Solution:ACWR = 750 / 450 = 1.67 (Danger Zone)\nWeek-to-week change = (750 - 500) / 500 = 50%\nSession load = 8 x 90 = 720 AU\nSafe range next week: 450 x 0.8 to 450 x 1.3 = 360-585 AU\nInjury probability estimate: ~72%

Result:ACWR: 1.67 (Danger) | 50% weekly spike | Recommended: reduce to 360-585 AU next week

Example 2: Well-Managed Progressive Overload

Problem:A runner has a chronic load of 600 AU/week. Current week is 660 AU. Previous week was 620 AU. Typical session: RPE 6 for 50 minutes.

Solution:ACWR = 660 / 600 = 1.10 (Sweet Spot)\nWeek-to-week change = (660 - 620) / 620 = 6.5%\nSession load = 6 x 50 = 300 AU\nSafe range next week: 600 x 0.8 to 600 x 1.3 = 480-780 AU\nInjury probability estimate: ~8%

Result:ACWR: 1.10 (Optimal) | 6.5% gradual increase | Safe to continue progressive loading

Frequently Asked Questions

How is training load calculated?

The most common method is session RPE (sRPE), developed by Carl Foster. You multiply the session duration in minutes by the perceived exertion rating (1-10 scale). For example, a 60-minute session at RPE 7 equals 420 arbitrary units. Weekly training load sums all sessions. More advanced methods include GPS-derived external load metrics (distance, high-speed running, accelerations), heart rate-based internal load (TRIMP), and power-based metrics for cycling. Each method captures different aspects of training stress, and the best practice is combining internal and external load measures for a comprehensive picture.

What is training monotony and why does it matter?

Training monotony is the ratio of mean daily training load to its standard deviation over a week. A high monotony score (above 2.0) means you are doing very similar training every day without adequate variation. Research shows high monotony combined with high total load significantly increases both illness and injury risk. For example, a weekly load of 3,000 AU spread evenly across 7 days (monotony ~3.3) is riskier than the same load distributed unevenly with rest days (monotony ~1.5). Incorporating easy days, cross-training, and complete rest days reduces monotony and its associated risks.

How much should I increase training load per week?

The widely cited \"10% rule\" suggests increasing total weekly training load by no more than 10% per week. However, research suggests this may be overly conservative for well-conditioned athletes and insufficient guidance for beginners. A more evidence-based approach uses the ACWR framework: keep your week-to-week increase within a range that maintains an ACWR between 0.8 and 1.3. In practice, increases of 5-10% per week are safe for most individuals. Increases exceeding 15% in a single week significantly raise injury risk, and spikes above 30% should be avoided entirely regardless of fitness level.

How do heart rate training zones work?

Training zones are percentages of maximum heart rate (estimated as 220 minus age). Zone 1 (50-60%) is recovery, Zone 2 (60-70%) builds endurance, Zone 3 (70-80%) improves aerobic capacity, Zone 4 (80-90%) increases threshold, and Zone 5 (90-100%) is maximal effort.

References

Reviewed by Daniel Agrici, Founder & Lead Developer ยท Editorial policy