A practical guide to auto-regulating training load from readiness data

Auto-regulation is the idea that the prescribed session should bend to the athlete in front of you. Experienced coaches have always done it by eye: a look at the warm-up, a question about the night before, a load adjusted on the spot. Online, you do not have the warm-up. You have data, and more of it than ever: overnight HRV and resting heart rate from the watch, sleep from the phone, and whatever the athlete tells you in a check-in.

The risk is using it badly. A single low HRV reading becomes a rest day; a daily score becomes something to argue with. This guide is a set of simple rules for turning readiness data into load decisions that hold up.

This is coaching guidance, not medical advice. If an athlete reports pain, illness or anything a doctor should see, that conversation comes first.

The signals, and what each is good for

Readiness data falls into two groups.

Objective signals come from devices: heart rate variability, resting heart rate and sleep duration, usually measured overnight. They are consistent and they do not depend on mood. They are also noisy from night to night, affected by alcohol, late meals, travel, heat and how the watch was worn.

Subjective signals come from the athlete: sleep quality, muscle soreness, mood, motivation, a free-text note. They are prone to bias, but they capture things devices miss, like a stressful week at work or a niggle in a calf.

Neither is enough on its own. The most useful picture comes from both, read together.

Rule 1: compare the athlete with themselves

Readiness numbers are only meaningful against the athlete's own normal. One athlete's ordinary HRV is another's very bad night. Before reading any single morning, establish a baseline: a rolling average over the last few weeks for each objective signal.

Then ask one question each morning: is today clearly outside this athlete's normal range? Within the range, it is a normal day, even if the number looks low to you.

Rule 2: never act on one signal from one night

A single low reading is weak evidence. Act when signals agree, or when a change persists.

• Agreement. Low HRV plus short sleep plus high soreness is a stronger case than any one of them.
• Persistence. Two or three mornings below baseline say more than one.
• Context. A known cause (a late flight, a night shift) explains a dip and may not need a change at all.

A useful default: one signal out of range, note it; two or more, or several mornings in a row, adjust.

Rule 3: have three adjustments, not one

Most coaches only have one lever, the rest day, so they either pull it too often or never. Three graded options cover nearly every case:

1. Scale. Keep the session, reduce the load or volume. Drop loads by a modest amount, cut a set, or cap effort at a lower RPE. This is the right answer most of the time.
2. Swap. Move a hard session to later in the week and bring an easier one forward. The week's work is preserved; it is just reordered.
3. Rest. Take the day off and move the session on. Reserve this for strong, agreeing signals or when the athlete tells you something is wrong.

Decide in advance which signals trigger which option, and write it down. Consistency is what makes the athlete trust the decision rather than argue with it.

Rule 4: auto-regulate inside the session too

Readiness data tells you about the athlete before they start. Effort ratings tell you during. Prescribing by RPE or reps in reserve ("3 x 5 at RPE 7") lets the load move with the day automatically: on a good day the athlete works up to a heavier load for the same effort; on a bad day, lighter.

Morning data and in-session effort work well together. Use the morning to choose between scale, swap and rest; use RPE to fine-tune the load once the session begins.

Rule 5: review the week, not the day

Daily decisions should be small. The bigger adjustments (holding a progression, adding a deload, changing the emphasis of the next block) come from the trend across a week or more. When you plan next week's loads, look at:

• How many sessions were scaled, swapped or rested, and why.
• Whether effort ratings for the same loads are creeping up.
• Whether readiness has been drifting below baseline for more than a few days.

If an athlete has needed three scaled sessions in a week, next week's progression should probably wait.

The mistakes that turn readiness into noise

• Too many signals. Ask for four or five things in the check-in, not fifteen. Every extra question lowers the answer rate.
• Daily nagging. If the athlete hears about readiness every morning, they stop listening. Speak up only when it changes the plan.
• Overriding the athlete. If the data says rest but the athlete feels great and the session is light, a scaled session is usually the better call.
• Changing things silently. If the plan changes, tell the athlete why. A session that changes without explanation feels arbitrary.
• Ignoring missing data. No check-in for three days is a signal in its own right.

Making it routine for an online roster

For a handful of athletes, reading readiness each morning is easy. For a roster, it needs to be in front of you without hunting for it. A workable routine:

1. Athletes do a short daily check-in, with device data filling the objective fields where they have a watch or phone that records it.
2. You glance at each athlete's last seven days before changing their next sessions.
3. When you plan progressions, the last week of readiness is part of the evidence, not a separate screen.

On Loadout, the check-in, the seven-day strip on the athlete's page and the progression suggestions are built around that routine; on the coach product, readiness informs your decision and never changes a session by itself. The daily readiness page has the detail.

FAQ

How much should I reduce load when readiness is low?

Start modestly: a lighter load, one fewer set, or a lower RPE cap. Large cuts on weak evidence cost more training than they save.

Is HRV reliable enough to make decisions with?

As a trend against the athlete's own baseline, it is useful. As a single morning number, it is noisy. Combine it with sleep and how the athlete says they feel.

Should readiness data change the plan automatically?

For a coached athlete, a person should approve changes. Automatic proposals make sense where there is no coach, as long as the athlete can accept or dismiss them.

Put readiness next to the plan

Loadout puts each athlete's last seven days of check-ins beside their programme and reads them when it suggests the next load. Try it with two athletes, free: start free.