Training load is the stress created by training. Learn the difference between external load and internal load, how endurance athletes can measure it, and how to use load trends without chasing one perfect number.
Training load is the amount of stress a workout, week, or training block places on your body. It is not just how far you ran, how long you rode, or how many intervals you completed. It is the relationship between the work you did and how your body responded to that work.
That distinction matters because endurance training is built on stress and adaptation. A workout has to be hard enough to create a useful signal, but not so hard, frequent, or poorly placed that fatigue outruns recovery. Training load is the language athletes and coaches use to describe that balance.
For a runner, training load might include weekly mileage, long-run duration, elevation, pace, heart rate, time in zones, and perceived effort. For a cyclist, it might include ride duration, power, kilojoules, climbing, time in power zones, heart rate, and session RPE. For a triathlete, hiker, skier, or general endurance athlete, it might combine time across several sports with recovery notes and fatigue trends.
The useful version is not one perfect number. A single training load score can be helpful, but it can also hide important context. A 90-minute easy ride in cool weather is not the same as a 90-minute hard ride in heat. A 40-minute recovery run after a good night's sleep is not the same as a 40-minute run done while sore, under-fueled, and stressed from work.
Sports science usually separates training load into two related ideas: external load and internal load. External load is what you did. Internal load is how your body responded. A consensus statement on training-load monitoring describes load monitoring as a way to understand both the work performed and the athlete's response to that work (Bourdon et al., 2017). Impellizzeri, Marcora, and Coutts later emphasized that internal and external training load answer different questions and should not be treated as interchangeable (Impellizzeri et al., 2019).
So when athletes ask, "What is my training load?" the best answer starts with another question: are you trying to measure the work, the response, or the decision you should make next?
Training load is the stress created by training. It has two sides:
External load includes duration, distance, elevation gain, pace, power, speed, weight lifted, number of repetitions, interval volume, route difficulty, and time in training zones. It answers the question, "What did I do?"
Internal load includes heart rate, perceived exertion, breathing, soreness, fatigue, mood, sleep disruption, heart rate variability, resting heart rate, motivation, and how hard the session felt overall. It answers the question, "What did it cost me?"
The same external load can produce different internal loads. Ten kilometers at an easy pace may be routine for one athlete and exhausting for another. A 2-hour endurance ride may feel smooth in cool weather and unusually hard in heat. A threshold workout may be productive after two easy days and too costly after a stressful week.
That is why training load is most useful when you connect both sides. You do not only ask how much work was done. You ask how your body absorbed it.
Training load matters because fitness improves through repeated cycles of stress and recovery. Training creates a disturbance. Recovery allows the body to adapt. If the load is too low for too long, progress stalls. If the load rises too fast or stays too high without recovery, fatigue accumulates faster than adaptation.
This does not mean hard training is bad. It means hard training needs context. A demanding block can be productive when it is planned, supported by recovery, and followed by easier training. The same block can become a problem if it is added on top of poor sleep, missed fueling, high life stress, or a rapid jump in volume.
Training load helps you see patterns that memory misses. Athletes often remember dramatic sessions, races, and bad workouts, but they forget the ordinary accumulation around them. A log can show that three "normal" easy runs were actually faster than planned, that two group rides added more intensity than expected, or that a long-run build jumped faster than it felt in the moment.
It also helps separate useful fatigue from warning fatigue. Some tiredness is normal during a build. Legs may feel heavy the day after a quality session. Motivation may dip late in a hard week. But if fatigue keeps rising while performance, mood, sleep, and easy-session feel keep declining, the load may be too much for the current recovery budget.
Halson's review on monitoring training load and fatigue argues that fatigue is best understood by looking at both the training completed and the athlete's response to it (Halson, 2014). That is the practical value of training load. It is not just a score. It is a way to explain why training feels the way it feels.
For endurance athletes, load tracking can support several decisions:
The goal is not to make the highest training load number possible. The goal is to create enough stress to adapt and enough recovery to absorb it.
External training load is the work performed. It describes the session from the outside, before you judge how hard it felt.
For runners, common external-load metrics include:
For cyclists, common external-load metrics include:
For multisport athletes, hikers, rowers, or skiers, external load may need to combine more than one sport. Duration is often the simplest common metric because it works across activities. Distance alone can mislead when terrain, equipment, wind, altitude, or technical difficulty changes.
External load is useful because it is usually objective. A 75-minute ride is a 75-minute ride. Six 3-minute intervals are six 3-minute intervals. A 20-mile trail run with 3,000 feet of climbing is different from a 20-mile flat road run, and external metrics make that difference visible.
But external load is incomplete. It does not know whether you slept poorly, whether the run was in heat, whether your threshold settings are accurate, whether you fueled well, or whether you were carrying fatigue from earlier sessions. It also does not know whether the same pace or power was comfortable, controlled, or barely sustainable.
This is why athletes can make poor decisions when they only track external load. A runner may see that mileage is stable and assume the week was normal, even though most of the miles drifted from easy to moderate. A cyclist may see the same weekly hours and miss that a group ride added repeated hard surges. A hiker may see the same distance and miss that a route had much more climbing and technical descent.
External load tells you what happened. It does not fully tell you what it cost.
Internal training load is the body's response to the work. It captures the fact that training stress is personal.
Common internal-load signals include:
Internal load is why two athletes can complete the same workout and need different recovery. It is also why the same athlete can complete the same workout on two different days and experience it differently. Heat, dehydration, altitude, illness, menstrual-cycle phase, travel, emotional stress, poor sleep, and under-fueling can all change the internal response.
Heart rate is one of the most common internal-load measures because it reflects cardiovascular response. It can show that a normally easy pace is costing more than usual, or that a long aerobic session is drifting upward over time. But heart rate also has limitations. It lags behind short intervals, responds to heat and hydration, and can be affected by caffeine, stress, and fatigue.
Perceived effort fills part of that gap. Session RPE is especially practical because it asks how hard the whole session felt, usually on a 1-10 scale. Foster and colleagues described a simple session-load method that multiplies session duration by rating of perceived exertion (Foster et al., 2001). A 60-minute session rated 3 out of 10 gives 180 arbitrary units. A 60-minute session rated 8 out of 10 gives 480. The method is not perfect, but it captures a useful truth: the same duration can create very different stress.
Subjective measures should not be dismissed as soft data. A systematic review by Saw, Main, and Gastin found that self-reported measures often reflected changes in athlete well-being at least as well as, and sometimes better than, commonly used objective measures (Saw et al., 2016). For everyday athletes, a simple daily note on sleep, soreness, mood, and fatigue may explain more than another complex score.
Internal load tells you how the work landed. If external load rises and internal response stays stable, you may be adapting well. If external load is steady but internal load keeps rising, something else is increasing the cost.
Volume is part of training load, but it is not the whole story.
This is one of the most important points for runners and cyclists. It is easy to count miles, kilometers, hours, or weekly distance and call that training load. Those metrics matter, but they do not describe intensity, terrain, heat, fueling, or fatigue.
Consider three 60-minute runs:
| Session | External Summary | Likely Load Difference |
|---|---|---|
| Easy aerobic run | 60 minutes mostly in low zones | Low to moderate load |
| Threshold intervals | Warmup, 4 x 8 minutes hard, cooldown | Higher load because intensity is concentrated |
| Hilly trail run | 60 minutes, technical climbs and descents | Higher muscular and mechanical load than flat running |
All three have the same duration. They do not have the same training load.
The same is true on the bike. A 2-hour endurance ride on flat roads is not the same as a 2-hour ride with repeated climbs above threshold. A steady indoor ride is not the same as a group ride with surges, coasting, attacks, and sprint efforts. Average speed may look similar, but the load can be very different.
Volume also misses mechanical load. Downhill running, technical trails, sprinting, plyometrics, and strength training can create tissue stress that heart rate may not fully capture. A short hill-sprint session may not create a huge endurance load score, but it can still leave the calves, hamstrings, or Achilles tendon needing recovery.
This is why useful load tracking combines:
If your log only tracks volume, it will eventually miss something important.
There are many ways to measure training load. The right method depends on the athlete, sport, tools, and level of precision needed.
The simplest method is weekly duration. Count total training time across the week, then compare it with recent weeks. This works well for athletes who train across several sports or on varied terrain. It is not perfect, but it is hard to fake and easy to understand.
Weekly distance is common for runners. It is useful when terrain and intensity are reasonably consistent. It becomes less useful when surface, elevation, speed, or technical difficulty changes a lot. Forty miles on flat roads is not the same as forty miles on steep trails.
Time in zones adds intensity context. Instead of only asking how long you trained, you can ask how much time you spent easy, moderate, near threshold, or very hard. This is especially useful for spotting intensity drift. A base week with a lot of moderate-zone time may not be as easy as planned.
Power-based metrics are useful for cyclists because power measures external output directly. Power responds immediately when effort changes, which makes it especially helpful for intervals and pacing. But power still needs internal context. Producing the same watts at a higher heart rate and higher RPE may signal heat, fatigue, dehydration, or poor recovery.
Heart-rate-based methods estimate load from time spent at different heart-rate intensities. They can work well for steady endurance sessions, but they are less precise for short intervals because heart rate responds slowly. They also depend on accurate zones.
Session RPE is one of the most accessible methods. Rate the whole session from 1 to 10, then multiply by duration in minutes. This gives a simple load estimate that can compare easy runs, hard rides, strength sessions, hikes, and races. It also gives athletes a reason to reflect honestly on how the workout felt.
You can also use a simple category system:
| Session Type | Practical Load Note |
|---|---|
| Recovery | Very low stress, should leave you better |
| Easy aerobic | Low to moderate stress, repeatable |
| Long easy | Moderate stress from duration |
| Tempo or threshold | Higher stress from sustained intensity |
| VO2 max intervals | High stress from intensity |
| Race or hard group session | High stress, often underestimated |
| Strength or hills | Local muscular and mechanical stress |
The best method is the one you will record consistently and review honestly. Complex metrics can be useful, but consistency beats sophistication.
Training load becomes more useful when you look at trends.
An acute load is the recent load, often the current week or last several days. A chronic load is the longer baseline, often the last few weeks. The exact time windows vary by sport, tool, and coaching model, but the practical idea is simple: compare what you are doing now with what you have recently been prepared to handle.
If this week is much higher than your recent baseline, the load spike deserves attention. That does not automatically mean it is dangerous. A planned training camp, race week, or hiking trip may intentionally raise load. But a sudden jump should be matched with recovery, fueling, sleep, and realistic expectations for the following week.
Gabbett's paper on the training-injury prevention paradox argues that athletes need enough training to be prepared for sport demands, while sudden workload spikes and poor load management can create problems (Gabbett, 2016). The practical takeaway is not "never train hard." It is "do not confuse prepared load with random spikes."
Trend-based thinking is also useful because one week rarely tells the whole story. A high-load week after three controlled weeks may be fine. A moderate-load week after six hard weeks may still feel awful. A lower-load week may be a deload, or it may be the result of missed sessions caused by fatigue.
Look for patterns such as:
You do not need a perfect formula to benefit from load trends. You need a repeatable way to notice when training is moving faster than recovery.
A weekly training load review should compare four things: the plan, the completed work, the internal response, and the next decision.
Start with the plan. What was the week supposed to accomplish? A base week, build week, recovery week, taper week, race week, and return-from-break week should not all have the same load pattern.
Then review completed work. Look at total duration, distance, elevation, time in zones, hard-session count, long-session duration, strength work, and any unplanned intensity. Do not only look at the headline number. Ask where the load came from.
Next, review internal response. How did the week feel? Did easy sessions feel easy? Was sleep stable? Did soreness resolve between hard days? Did mood, motivation, or fatigue shift? Did heart rate behave normally at familiar paces or powers?
Finally, make one decision for next week:
| Pattern | Possible Decision |
|---|---|
| Load rose and recovery stayed stable | Progress slightly or hold the new level |
| Load rose and fatigue rose sharply | Repeat, reduce, or add recovery |
| Load was low and recovery is strong | Add easy volume before adding intensity |
| Total load was fine but intensity was messy | Redistribute hard days and protect easy days |
| Load was planned but life stress was high | Adjust expectations and keep the next week conservative |
| Pain appeared after a spike | Reduce mechanical stress and monitor closely |
This review should be practical, not dramatic. Most weeks do not require a complete rebuild. They require one clear adjustment: move a hard day, shorten a long session, add an easy day, reduce intensity, hold volume steady, or keep going.
Kellmann and colleagues emphasize that recovery is part of the training process, not an optional extra (Kellmann et al., 2018). A weekly load review should respect that. The question is not, "Can I survive more?" The better question is, "Can I absorb what I am doing and be ready for the next useful stress?"
Training load becomes clearer when you look at real training situations.
Example 1: the same distance, different load.
A runner completes two 8-mile runs. The first is on flat roads at easy effort, mostly in low heart-rate zones. The second is on rolling trails, with several climbs, a faster finish, and higher perceived effort. The distance is the same, but the training load is not. The second run likely creates more cardiovascular, muscular, and recovery stress.
Example 2: the easy ride that was not easy.
A cyclist plans a 90-minute Zone 2 ride but joins a group. The average power looks moderate, but the ride includes repeated surges above threshold, short climbs, and sprint efforts. The weekly duration does not look excessive, but the internal load is high and the next day's workout feels flat. The issue is not weekly hours. It is hidden intensity.
Example 3: the threshold session that was well absorbed.
An athlete completes a threshold workout after two easy days. Heart rate and perceived effort match expectations, the cooldown feels controlled, sleep is normal, and the next easy session feels easy. The load was meaningful, but it was absorbed. That is productive training.
Example 4: the normal workout with an abnormal response.
A runner repeats a familiar 45-minute easy route. Pace is slower than usual, heart rate is higher, and RPE is 5 out of 10 instead of 2 or 3. The external load is ordinary, but the internal load is elevated. That may be a sign to reduce the next session, check sleep and fueling, or watch for illness.
Example 5: the low-volume week that was still stressful.
An athlete travels for work and trains less than usual. Weekly hours are low, but sleep is poor, stress is high, meals are irregular, and the one hard workout feels terrible. The training load number may be low, but total life stress is not. A smart plan treats the following week carefully instead of forcing a big catch-up.
These examples all point to the same rule: load is not just what the plan says. It is what happened and how your body handled it.
The first mistake is chasing a higher load score. More load is not automatically better. Training load is a tool for making decisions, not a leaderboard. If a number encourages you to add stress when recovery is already poor, the number is being used badly.
The second mistake is comparing your load directly with someone else's. Different athletes have different histories, thresholds, durability, schedules, sleep, injury backgrounds, and recovery capacity. A big week for one athlete may be normal for another.
The third mistake is ignoring internal response. External metrics can look stable while the body is struggling. If your usual easy pace feels hard for several days, that matters even if weekly mileage looks normal.
The fourth mistake is trusting zones that are outdated or poorly set. If your heart-rate, pace, or power zones are wrong, time-in-zone data will mislead you. Review zones after fitness changes, testing, illness, long breaks, or major training shifts.
The fifth mistake is treating life stress as separate from training. Work deadlines, travel, poor sleep, family responsibilities, heat, and under-fueling all change recovery. Your body does not keep a separate stress account for training and life.
The sixth mistake is reviewing only the current week. One week can be noisy. Trends over three to six weeks are usually more useful than a single isolated score.
The seventh mistake is adding intensity when easy volume would solve the problem. If recovery is strong and load is low, many endurance athletes should first add easy aerobic work before adding another hard workout.
The eighth mistake is using too many metrics. More data is not always more clarity. A small set recorded consistently is better than a dashboard full of numbers you do not review.
You do not need a laboratory setup to use training load well. A simple system can be enough.
For each session, record:
For each day, record:
For each week, review:
Then decide:
This is enough for most runners and cyclists. You can add power metrics, HRV, lactate data, or more advanced analysis later, but the foundation stays the same. What did you do? How hard was it? How did you respond? What should change next?
If you use Zone Training Log or another training log, the important habit is not recording everything. It is reviewing the right things at the right time. A load number should lead to a better training decision, not just another chart.
Training load is the stress created by training. The simplest useful definition is this: external load is what you did, and internal load is how your body responded.
Both sides matter. Duration, distance, power, pace, elevation, and time in zones help describe the work. Heart rate, RPE, soreness, fatigue, sleep, mood, and readiness help describe the cost. When you connect them, you can make better decisions about when to build, hold, recover, or adjust.
Do not treat training load as one perfect score. Treat it as a practical review tool. Look at the plan, the work completed, the body response, and the trend over several weeks. Then make the next week more coherent.
The goal is not the highest load. The goal is the right load at the right time, absorbed well enough to keep training consistent.
Related
