Training load management: a practical guide

Every training effect a coach wants, fitness, strength, repeated-sprint capacity, comes from imposing a load the body must adapt to. The same load, applied too fast or carried too long without recovery, is also the most controllable cause of injury and illness in a squad. Training load management is the discipline of holding those two truths at once: pushing adaptation while keeping accumulated fatigue inside a range the athlete can absorb. It is not a spreadsheet chore. It is the difference between a squad that peaks in the right week and one that arrives at it already broken.

The 2017 international consensus statement on monitoring athlete training loads, drawn from a meeting of sport scientists in Doha, set the shared framework most programs now work from. Its central distinction is the one to start with: there is the work you prescribe, and there is the work the athlete actually experiences.

Internal versus external load

External load is the physical work done, measured independently of the athlete: distance covered, sprint count, high-speed running metres, jumps, total tonnage lifted, balls bowled. A GPS unit and a barbell both report external load. It is objective and it is what a session plan specifies.

Internal load is the biological cost of that work to the individual: heart-rate response, blood lactate, and the athlete's own rating of perceived exertion. The consensus statement frames the internal response as the primary determinant of the training adaptation, because two athletes can run identical external loads and pay very different internal prices depending on fitness, sleep, stress, and health.

The practical move is to track both and watch the relationship between them. Session rating of perceived exertion, the RPE multiplied by session duration in minutes, gives a simple, validated internal-load number that needs no hardware and works across every sport in a mixed squad. When external load holds steady but the internal cost climbs, the athlete is fatiguing, getting ill, or under-recovered. That divergence is a signal worth more than either number alone.

Why you monitor at all

Monitoring exists to answer two questions: is the athlete doing the work the plan intended, and is the work producing fitness rather than just fatigue. The consensus statement is candid that no single metric captures load completely, and that the value of monitoring lies in trends and individual baselines, not in absolute thresholds copied between athletes. A readiness and wellness check, sleep, soreness, mood, energy, takes thirty seconds from the athlete and catches the non-training stressors that load data alone misses.

This is where a unified record earns its place. Load means little without the recovery and availability context sitting beside it on the same athlete. A high session load on a well-slept, fully fuelled athlete is adaptation; the same load on someone flagged by the medical staff is a risk the coach should see before the session, not after the injury.

Periodisation: planning the rise and fall

Load is not meant to climb forever. Periodisation is the structured variation of load over time so that hard blocks are followed by recovery, and the whole plan converges on peak readiness at the target competition. The standard nesting runs from the macrocycle (the full season or annual plan), through the mesocycle (a block of roughly four to six weeks built around one objective, typically with progressive overload across the first weeks and a lighter recovery week to close), down to the microcycle (usually a single week, where individual sessions are assigned their intensities and volumes).

The purpose of the structure is recovery designed in, not bolted on. A block that only accumulates load buries the athlete; a block that alternates overload with absorption lets adaptation surface. Periodisation is how a program makes that alternation deliberate rather than accidental.

The acute:chronic workload concept, in brief

The most discussed tool to come out of load monitoring is the acute:chronic workload ratio (ACWR). The idea is simple: compare the load of the most recent week (the acute load, what the athlete just did) against the rolling average of the previous several weeks (the chronic load, what the athlete is conditioned for). A ratio near one means this week looks like recent weeks and the athlete is prepared for it. A ratio well above one means a spike: more work than the recent training has built a base for.

Gabbett's 2016 work in the British Journal of Sports Medicine named the counter-intuitive finding that gave load management its modern shape: it is not high load that predicts injury so much as rapid change in load. A high, well-built chronic load can be protective, while a sharp spike on an underprepared athlete is the danger. That reframing, train hard to build the base, but raise load gradually, is the single most useful principle in this article.

Use the ratio as one input, not a verdict. Since the original proposals, systematic reviews and methodological critiques have shown the ACWR is sensitive to how it is calculated, that single thresholds do not transfer cleanly between sports or studies, and that the ratio can mislead when read in isolation. The honest reading: the underlying principle, avoid sharp, unplanned spikes relative to the athlete's established base, is sound and well supported; the exact number is a flag to investigate, never a rule to obey. Treat any threshold as a prompt to look at the athlete, their wellness, their recovery, and their recent history, not as a decision made for you.

Putting it together

Good load management is a loop, not a dashboard. Plan the load through the season with periodised structure. Prescribe and capture external load each session. Capture internal load and a brief wellness check alongside it. Watch the relationship between intended work and experienced cost, and watch the rate of change in load against the athlete's base. When a signal fires, read it against the athlete's full record, recovery, availability, nutrition, before you act. The squads that stay available are not the ones that train least; they are the ones that raise load deliberately and read the response honestly.