Training load is the demand created by your training, not simply the number of kilometres in the week. Its meaning depends on volume, intensity, recent training history and how sessions are arranged. The same workout can be routine for one runner and a large jump for another because load is always relative to what came before.
Mileage is useful, but it only tells you how far you ran. To understand what the week asked from you, you also need to know how hard the running was and how that demand compares with what you have been doing recently.
That is why training load becomes useful when the distance looks ordinary but the week does not: more intensity, a much longer long run, or several demanding sessions close together can all change the picture.
But distance only describes part of what you asked your body to do.
Forty kilometres of mostly easy running does not create the same training demand as 40 kilometres containing several hard sessions. Likewise, two runs of the same duration can place very different demands on you if one is easy and the other contains sustained threshold work.
This is why training load matters.
The same workout does not mean the same thing to every runner
A 16-kilometre long run may be routine for a runner who has spent months running 45 to 55 kilometres a week. For someone whose longest recent run is 10 kilometres and whose weekly total has been closer to 25 kilometres, the same session represents a much larger change.
That is why load is relative. The useful comparison is not only the absolute workout; it is the workout in relation to the training the runner has recently absorbed.
Training load accumulates across sessions
Workouts do not happen in isolation. A long run completed after several demanding days can create a different overall week from the same long run placed after easier training.
This is also why making up a missed hard session can change more than the calendar. Session order affects recovery time and the amount of demanding work clustered together.
Progression matters more than chasing a perfect number
There is no single training-load score or weekly percentage that can tell every runner exactly how much is safe. Reviews of running injuries have found inconsistent relationships between many common training parameters and injury, while newer prospective evidence suggests that large jumps in single-session distance deserve particular attention.
The practical implication is not to avoid load. Marathon fitness requires progressively greater training demand. The goal is to increase that demand at a rate the runner can continue to absorb.
What this means inside SmartRunning
SmartRunning uses recent training context when deciding what should come next rather than treating weekly distance as the only signal. Volume, intensity, progression and the pattern of completed training provide different pieces of information.
The point is not to give the runner another dashboard to interpret. It is to make the next training decision more informed while keeping the guidance simple.
See how SmartRunning uses the training around the number, not just the weekly kilometre total, when deciding what should come next.