Why Training Load Is Not the Same as Readiness

Training load and readiness answer different questions, and ultrarunners make better decisions when they stop treating them as the same thing. Training load describes how much stress your training has applied. Readiness describes how prepared you are, today, to absorb more stress or execute a demanding session. If you confuse those ideas, you can undertrain when you are actually ready, or force a workout when your body is not in a good position to use it.

This matters more in ultramarathon training than in shorter race prep because the stress you carry is not only cardiovascular. Long climbs, steep descents, back to back long runs, strength work, heat exposure, poor sleep, work stress, travel, and fueling errors all shape whether you can productively train on a given day. Two runners can show the same seven day training load and have completely different readiness. One may be primed for a strong long run. The other may be carrying sore quads, elevated effort at easy pace, poor sleep, and a fading appetite, all signs that the next hard session will cost more than it gives back.

The useful distinction is simple. Load is what went in. Readiness is what condition the athlete is in now.

What training load actually means

Training load is an attempt to quantify the stress of training. Different platforms calculate it differently. Some emphasize heart rate based internal load, meaning the physiological cost to your body. Others emphasize external load, meaning the work completed, such as duration, distance, elevation gain, pace, or power. Some combine these into a single score.

A simple example is session RPE load, developed from research by Carl Foster and colleagues. You rate the session by perceived effort, often on a one to ten scale, and multiply that by duration in minutes. A 90 minute run at an RPE of 5 gives a load of 450. This method is blunt, but useful, because it captures how hard the session was for you, not only what it looked like on paper.

Heart rate based systems try to do something similar through physiology. If your heart rate spends a long time in higher zones, the model assigns more stress. Pace and power based systems look at the mechanical demand and the intensity you sustained. For ultrarunners, no single method is complete. A steep mountain hike can impose major muscular stress with modest heart rate. A hot road run can drive heart rate up even at an ordinary pace. A downhill heavy long run can damage your legs while producing a training score that looks surprisingly normal.

That does not make training load useless. It makes it incomplete.

Load is valuable because it helps you see trends over time. Are you building gradually or spiking too fast? Are your long runs getting longer while the rest of the week also creeps up? Are you carrying three hard sessions in five days and calling it a normal week? Load metrics are good at describing exposure. They are much less reliable at telling you whether your body has recovered well enough to benefit from the next planned stress.

What readiness actually means

Readiness is your current capacity to train effectively. That includes your ability to perform, recover, and adapt. It is not a single biological switch. It is a practical coaching judgment built from several signals.

Those signals usually include some mix of the following:

• Recent training load and how quickly it has changed
• Sleep quantity and quality
• Perceived fatigue and motivation
• Muscle soreness, especially local soreness in the quads, calves, hips, or feet
• Resting heart rate and heart rate variability, often shortened to HRV
• Appetite, mood, and general sense of strain
• Easy run pace at a normal effort
• Cardiac drift, meaning heart rate climbing during a steady effort
• Life stress, travel, illness exposure, and environmental strain such as heat

Readiness is not only about whether your nervous system looks calm on a wearable score. It is also about whether your legs, connective tissue, fueling status, and attention are prepared for what you are about to ask from them.

That is why an ultrarunner can look fine in one metric and still not be ready. A runner may wake up with normal HRV but still have beat up quads from descending. Another may have low motivation and poor sleep after work travel even though their recent training load is modest. Another may be aerobically fresh but glycogen depleted from underfueling a long run. Readiness is broader than one dashboard number.

Why load and readiness drift apart

The biggest reason these concepts get confused is that load influences readiness, but does not determine it. Heavy training often reduces readiness. Light training often improves it. But the relationship is not linear, and it is never one to one.

Think of training load as the size of the bill and readiness as your current ability to pay it.

A runner can handle a high bill when sleep, fueling, and life stress are good. The same bill becomes expensive when those supports disappear. A smaller bill can still be too much if the athlete is ill, under-recovered, or carrying heavy local muscular damage.

Several common ultrarunning scenarios show the gap clearly.

First, local muscular fatigue. Research and coaching experience both point to a basic limitation of many readiness metrics, especially HRV based ones. HRV reflects autonomic nervous system status, not whether your quads are trashed from four thousand feet of descent. In trail and ultra training, peripheral fatigue often decides the day. Your cardiovascular system may be ready. Your legs may not be.

Second, heat and dehydration. A run in hot conditions can produce more cardiovascular strain at the same pace, and that may inflate the apparent load. But the bigger issue for the next day may be residual dehydration, poor sleep, or thermoregulatory stress. If you look only at yesterday's load score, you miss the mechanism that actually matters. If you want a deeper explanation of how heat changes the body, see heat acclimation for ultrarunners.

Third, life stress. Job pressure, relationship stress, new parent sleep, travel, and illness exposure can all reduce readiness without changing training load at all. This is one reason load alone performs poorly as a daily decision tool. It sees the work. It does not fully see the athlete.

Fourth, underfueling. A moderate week can still leave you flat if carbohydrate intake is poor, post run recovery is inconsistent, or long runs become chronic glycogen drains. The load score may look manageable. Your readiness is not.

Fifth, adaptation itself. As fitness improves, a load that once felt demanding may become ordinary. This is the point of training. The same external workload does not always create the same internal cost. Readiness changes as the athlete changes.

What the research supports, and what it does not

Endurance research strongly supports tracking training load over time. Large spikes in load and chronically excessive loads are associated with poorer outcomes, especially when recovery is inadequate. Coaches use load because it helps organize progression and avoid reckless jumps.

Research also supports monitoring athlete state with more than one signal. Reviews on recovery and endurance monitoring repeatedly find that no single marker, including HRV, resting heart rate, wellness questionnaires, or biochemical markers, is sufficient by itself. The better approach is a decision framework that combines objective and subjective data and interprets them against the athlete's own baseline.

That is an important point for ultrarunners. A readiness score can look scientific while hiding major blind spots. HRV can be useful, especially when measured consistently under similar conditions and interpreted as a trend rather than a verdict. But HRV does not directly measure muscle damage, tendon irritation, glycogen status, or race specific soreness. It helps with context. It does not replace context.

The same caution applies to wearable recovery scores. They can be directionally helpful. They are not coaches. They estimate part of the picture from proxies.

The practical lesson is not to reject data. It is to rank data correctly. Load tells you what stress you have accumulated. Readiness asks whether your body can productively handle what comes next.

The ultrarunner's version of readiness

Readiness for an ultrarunner is specific to the task ahead. You can be ready for an easy aerobic run and not ready for downhill repeats. You can be ready for a flat tempo session and not ready for a technical long run on tired calves. You can be ready to add volume and not ready to add intensity.

This is where generic readiness scores often fail. They try to answer one question with one number. Ultrarunning usually asks a more specific question.

For example:

If tomorrow is a threshold workout, the most relevant signals may be sleep, motivation, fueling status, and whether your easy pace and heart rate relationship has been normal all week.

If tomorrow is a long technical descent day, the most relevant signals may be quad soreness, foot tenderness, connective tissue irritation, and how stable your stride has felt on recent runs.

If tomorrow is an easy recovery run, you may not need much readiness at all. The run itself can help restore rhythm if it truly stays easy.

This is one reason experienced coaches often adjust the workout rather than simply cancel it. Readiness is not binary. It is about matching today's body to today's job. A coach who can evaluate every workout is useful here because the value is not a single score, but a consistent read on how your training is landing.

Practical ways to assess readiness without overcomplicating it

Most runners do not need a lab. They need a repeatable short check that catches meaningful changes.

Start with the last three to seven days of training. Ask whether load has been stable, building, or spiking. Then layer in the simplest signs of response.

How have you been sleeping? Not only total hours, but whether sleep feels deep and restorative.

How do your legs feel on stairs, during the first ten minutes of a run, and later in the day? Local soreness matters more than many runners admit.

What happens to easy pace at easy effort? If your normal conversational run suddenly gets much slower at the same perceived effort, or your heart rate rises unusually fast, pay attention. This does not always mean you need full rest, but it often means your current plan needs adjustment. We covered that pattern in why your easy pace suddenly got slower.

What is your motivation like once you begin warming up? Pre run reluctance can come from habit friction, but dead legs that never come around are different.

What do your heart rate signals show? A slightly elevated resting heart rate, suppressed or unusually high HRV relative to your baseline, and exaggerated cardiac drift during easy efforts can all suggest incomplete recovery. None is decisive alone. Together they can be informative. For more on one of those patterns, see cardiac drift in running.

What is happening outside training? Hard work weeks and family stress count. Travel counts. A poor appetite after a long run counts.

A good readiness check is not fancy. It is honest.

Common mistakes ultrarunners make

One common mistake is overreacting to load and underreacting to symptoms. A runner sees a low or moderate weekly load score and concludes they should be fine, even though they have heavy legs, poor sleep, and a rising sense of strain. This often leads to forcing a key session because the spreadsheet says the week was not that hard.

Another mistake is treating readiness as a permission slip to train hard whenever a wearable flashes green. Green can mean your autonomic system looks recovered. It does not mean your tissues are prepared for hard downhill running or that your fueling has been adequate for a big weekend.

A third mistake is assuming any sign of low readiness means you must stop training completely. Often the better move is to reduce the demand. Shift from intensity to easy volume. Shorten the long run. Remove descents. Replace a threshold session with steady aerobic work. Recovery is not always a day off. Sometimes it is a different stress that you can actually absorb.

A fourth mistake is ignoring the specificity of fatigue. In ultras, fatigue is often local before it is global. If your calves are wrecked, that matters even if the rest of your system looks good. If your feet are inflamed, that matters even if your training load score has dropped.

A fifth mistake is chasing readiness with too many gadgets and not enough consistency. The best data come from the signals you can gather repeatedly under similar conditions and interpret over time. A simple morning routine plus honest post run notes often beats a complicated stack of metrics used sporadically.

How to make day to day training decisions

The most useful approach is to let load guide planning and let readiness guide execution.

Load helps you build the block. It shapes how many hours, how much vertical, how often you touch intensity, and when you insert easier weeks. It helps you progress with intent instead of randomness.

Readiness helps you decide what to do today. It shapes whether the planned workout stays as written, gets modified, or gets moved. This is also where it helps to ask the coach about your own training instead of relying on generic recovery scores.

Here is what that looks like in practice.

If load has been rising steadily, sleep is good, motivation is normal, and your easy runs look normal, keep the planned key session.

If load is appropriate but your legs are unusually sore, your easy pace has slowed at the same effort, and cardiac drift is worse than normal, keep the training day but lower the demand. Turn the hill workout into an easy aerobic run, or shorten the session and remove the hard section.

If load is low but life stress is high, sleep is poor, and your warm up feels flat, do not be fooled by the low number. Your readiness may still be poor. A short easy run or rest day can be the more productive choice.

If load is high but all your readiness signals are stable and this week was intentionally built to be heavy, stay calm. Not every heavy feeling requires intervention. The point of training is to carry some fatigue. The question is whether the fatigue is functional or accumulating in a way that degrades the next important session.

If you miss several days and return feeling mixed, avoid trying to read the whole week from one metric. Use recent load to understand what you lost, then use readiness to choose the right re-entry. If that situation is familiar, read how to adjust training after missing three days.

A simple framework you can use each week

At the start of the week, review load. How much stress did you accumulate last week, and how does that compare with your recent norm? Where are the obvious stress points, long run, vertical gain, heat, intensity, strength work?

Before each key session, review readiness. Ask five questions.

First, how do my legs actually feel?

Second, did I sleep and eat well enough to use this workout?

Third, do my easy run signals look normal for me?

Fourth, is there any non training stress that changes the picture?

Fifth, if I do this session today, am I likely to absorb it, or merely survive it?

Then choose one of four actions.

Proceed as planned.

Proceed with reduced demand.

Swap for easy aerobic work.

Rest and revisit tomorrow.

This sounds obvious, but many runners skip the last step. They collect data, then treat the original plan as non negotiable. Good training uses information. It does not decorate stubbornness with charts.

How this plays out across a training block

Early in a block, load is usually modest enough that readiness problems come more from life stress, poor sleep, or carrying fatigue from the previous cycle. Here, the main job is to establish consistency and learn your baselines.

In the middle of a block, load becomes more informative because cumulative stress starts to matter. This is when gradual increases in volume, vertical, and long run strain can quietly outpace recovery if you only look at whether each single day seemed manageable. Readiness checks become more valuable because they catch the difference between productive fatigue and mounting residue.

Near the biggest weeks, expect some reduction in freshness. You are not trying to feel perfect. You are trying to stay inside a zone where key sessions are still actionable, mechanics remain sound, and recovery still occurs between hard days. If readiness degrades across several signals at once, especially easy pace, soreness, sleep, and motivation, that is often the moment to cut back before the next hole gets deeper.

In a down week, load drops on purpose so readiness can rebound. If it does not, that is useful information. It may point to non training stress, illness, underfueling, or a training block that dug deeper than expected.

Late in race preparation, the distinction sharpens further. Tapering reduces load, but readiness does not always rise immediately. Some runners feel flat for several days before they feel sharp. A lower load score during taper does not automatically mean you are fully recovered. The body often needs time to convert reduced stress into better performance.

Across the whole block, the pattern to trust is not a single score. It is the interaction between what you have been doing and how you are responding. Training load tells you the cost of the plan. Readiness tells you whether the athlete in front of you can pay for another day of work, and whether that work is likely to produce adaptation rather than just more fatigue.

Written by Wade Wegner. Train Ultra is a private AI coach that reads every workout from Garmin, COROS, Apple Health, or Health Connect. Try it free.