What Is Training Load in Running? A Plain-English Guide

Training load shows up on most running watches and apps, usually as a number or a chart that claims to capture how hard a runner has been working. The instinct is to treat it as a score to maximise. That is exactly the wrong way to read it. Training load is a planning tool, not a leaderboard.

1. What training load is trying to measure

Training load is an attempt to put one number on the physiological stress of running. Most methods combine duration and intensity, so a long easy run and a short hard workout can produce similar load even though they feel completely different. The point is to make different sessions roughly comparable so a week or a month of training can be summarised.

Because it folds intensity in, training load is more informative than mileage alone. Two runners with the same weekly distance can carry very different loads if one runs everything hard and the other keeps most runs easy.

2. Acute load, chronic load, and the ratio

The most useful framing splits load across two timescales. Acute load is recent, often the last week. Chronic load is the longer-term average, often the last month. Comparing them gives a rough sense of whether training is ramping up too fast.

• Chronic load rising slowly: the sign of healthy, gradual fitness building.
• Acute load close to chronic load: training is progressing at a sustainable rate.
• Acute load spiking well above chronic load: a sharp jump that is associated with higher injury risk.
• Acute load dropping below chronic load: expected during recovery weeks and taper, covered in how to taper for race day.

This is the data version of an old coaching rule: increase gradually, avoid big sudden jumps, and respect that the body adapts on its own schedule.

3. Why it is an estimate, not a measurement

Training load is a model. Different platforms calculate it with different formulas, and it leans heavily on heart rate accuracy and assumptions about how hard a given pace really is. A strap that misreads heart rate, a hot day, or a hilly route can all distort it.

That is why the number should be read as a direction, not a verdict. A trend over weeks is meaningful. A single day's figure is noisy, in the same way watch fitness estimates and recovery scores are, as discussed in running analytics explained.

4. How to actually use it

The practical use of training load is to keep progression honest and to catch spikes before they catch the runner. A few habits make it useful rather than stressful:

• Watch the trend, not the day. Chronic load should drift up slowly across a block.
• Be wary of spikes. A single week far above the recent average is a reason to ease the following week.
• Pair it with feel. Load plus sleep, mood, and how the legs feel is far more reliable than load alone.
• Do not chase a number. Adding junk intensity just to raise load is how runners get hurt.

If you want to put numbers to any of this, the training load calculator works out your weekly load and the acute:chronic ratio from your last few weeks of running, so you can see where the trend actually sits rather than guessing at it.

Load also connects to recovery: a high, rising load is exactly when sleep and easy days matter most, which is the territory of running recovery and HRV training.

5. Where The Running Genie fits

The Running Genie is built around the same principle that makes training load useful: increase gradually and keep most running easy. It turns recent runs and training history into adaptive paces and conservative progression, so the plan builds load steadily rather than in risky jumps. The goal is a plan that respects the gradual-build idea automatically, instead of leaving the runner to police a chart.