What Is Training Load? Faster and Slower Recorded-Load Averages
CTL and ATL compare slower and faster averages of recorded training load. Here's what the model describes, what its historical labels mean, what it cannot measure, and how Incredible applies it to cardio and logged lifts.
Training load modeling compares a slower average of recorded load with a faster one. The classic model calls the slower average CTL (Chronic Training Load), the faster average ATL (Acute Training Load), and their difference TSB (Training Stress Balance). The conventional labels "fitness," "fatigue" and "form" are historical shorthand. None of these values directly measures physical fitness, fatigue, recovery, feelings, performance or injury risk.
The Core Idea
The model runs the same daily recorded-load value through two weighted averages. One uses a longer time constant and changes gradually. The other uses a shorter time constant and responds more quickly. Subtracting the faster average from the slower one shows how recent recorded load relates to the longer recorded pattern.
This faster and slower structure comes from the impulse-response model first described by Banister in 1975 and later adapted for practical training analysis by Dr. Andrew Coggan through TrainingPeaks. Its historical language describes modeled responses to training. The values remain mathematical summaries of the load data that goes in.
Think of the two averages as lines drawn with different pens:
- CTL is the slower line. Each recorded day changes it a little.
- ATL is the faster line. Recent recorded days change it more.
- TSB is the vertical gap between those lines. It describes their relationship, not how someone feels or will perform.
The Three Numbers
CTL: the slower average
CTL is an exponentially weighted average of daily training stress with a time constant of about 42 days. Training platforms conventionally call it "fitness," but the value is a slower summary of the recorded load fed into the model.
- Goes up when: You train consistently over weeks and months
- Goes down when: You take extended time off or clearly reduce training
- Changes slowly: A single hard workout barely moves CTL. A single rest day barely dents it.
A higher CTL means the slower average contains more recorded training stress. It does not prove that someone is fitter, can tolerate more training, or will perform better. Values also depend on the load method and data source, so comparisons between people are limited.
ATL: the faster average
ATL is an exponentially weighted average of daily training stress with a time constant of about 7 days. Training platforms conventionally call it "fatigue," but it is a faster summary of recorded load, not a measurement of tiredness.
- Goes up when: You train hard in the past few days
- Goes down when: You rest or do easy sessions
- Changes quickly: One hard session noticeably raises ATL. Two rest days noticeably lower it.
ATL is not inherently bad. It simply gives recent recorded training more influence than older training. A high value does not by itself diagnose overreaching or overtraining.
TSB: the relationship between the averages
TSB is CTL minus ATL. Training platforms may label it "form" or "freshness," but it only describes the relationship between the two modeled averages. It cannot tell how you will feel or perform.
TSB = CTL − ATL (slower average minus faster average)
| TSB value | Model relationship | Cautious interpretation |
|---|---|---|
| Positive (above 0) | CTL exceeds ATL | Recent load is below the slower average |
| Slightly negative (0 to −10) | ATL slightly exceeds CTL | Recent load is slightly above the slower average |
| Moderately negative (−10 to −30) | ATL exceeds CTL by more | Recent load is further above the slower average |
| Very negative (below −30) | ATL far exceeds CTL | A large modeled difference that needs context |
Coaches often use this relationship as one input when reviewing training blocks and tapers. A negative TSB can occur when recent training rises; reducing recorded load lets ATL fall faster than CTL. The number still needs context from the athlete, the sport and the quality of the source data.
A Simple Example
Follow a recreational runner named Alex over four weeks, using made-up "training stress" units. Alex has run about 140 units a week for months, so both averages start near 20. The numbers below come from running the two averages day by day.
Week 1: Easy start
Alex runs three times: Tuesday (stress: 50), Thursday (stress: 40), Saturday (stress: 60). Weekly stress: 150.
- ATL rises a little, to about 21
- CTL barely moves and stays near 20, because one ordinary week is a small part of a 42 day average
- TSB is about −1: the faster average is a touch higher than the slower one
Week 2: Higher recorded load
Alex adds a fourth run and increases intensity. Weekly stress: 220.
- ATL jumps to about 30
- CTL starts climbing, to about 22
- TSB drops to about −8: the faster average is moving above the slower one
Week 3: Highest recorded-load week
Alex's biggest week yet: five runs, one long run, one interval session. Weekly stress: 300.
- ATL peaks at about 39
- CTL keeps climbing, but slowly, to about 25
- TSB is clearly negative, about −13: the gap between the faster and slower averages is larger
Week 4: Lighter recorded load
Alex drops to three easy runs. Weekly stress: 100.
- ATL drops quickly, from about 39 to about 22 in one week
- CTL barely drops, to about 24: it gathered three harder weeks and lost only one easy one
- TSB turns slightly positive, about +1: the faster average has fallen below the slower one
This is the mathematical pattern often seen during a taper. The faster average responds more quickly to the lighter week, while the slower average changes less. Coaches may read that pattern alongside the athlete's goals and direct feedback, but the model alone does not establish someone's physical condition or predict performance.
The Math (Optional but Useful)
If you want to understand the actual calculations:
Daily training stress varies by sport. In cycling, it's TSS (Training Stress Score) based on power output. In running, it's rTSS based on pace. For heart rate based training, it's hrTSS or TRIMP (Training Impulse), based on heart rate, duration and intensity.
CTL = yesterday's CTL + (today's stress − yesterday's CTL) ÷ 42
ATL = yesterday's ATL + (today's stress − yesterday's ATL) ÷ 7
These are exponentially weighted moving averages (EWMA). The 42 and 7 are time constants: they set how quickly each average responds to new recorded load. A longer time constant gives a slower, steadier average. A shorter one gives a faster, more responsive average.
On rest days, training stress is 0, so:
- CTL decays slightly toward 0
- ATL decays more quickly toward 0
- TSB rises because ATL usually falls faster than CTL
On hard training days, training stress is high, so:
- CTL nudges up slightly
- ATL jumps up
- TSB drops because ATL usually rises faster than CTL
The difference in response speed is what makes the two recorded-load patterns useful to compare.
Where CTL and ATL Came From
The model historically known as the fitness-fatigue model began in exercise science research by Banister and colleagues in 1975. It stayed mostly an academic idea until Dr. Andrew Coggan adapted it for practical use in cycling through TrainingPeaks. Power meter data made it possible to calculate a consistent training-stress input from recorded rides rather than laboratory measurements.
TrainingPeaks popularized the Performance Management Chart (PMC), which graphs CTL, ATL and TSB over time. It became a standard tool for endurance coaches planning training blocks and tapers. If you've heard a cycling or triathlon coach talk about "building CTL" or "managing TSB," this is what they mean.
Since then, CTL and ATL modeling has been mostly an endurance sports tool. Cyclists, runners, triathletes and swimmers use it routinely. Strength athletes and hybrid athletes mostly do not, because the standard model has no simple way to express a squat session in the same "training stress" units as a bike ride.
The Problem: Strength Training Doesn't Fit the Classic Model
Traditional CTL and ATL modeling uses heart rate or power output to estimate training stress. Those continuous signals suit recorded endurance sessions.
Strength training breaks this model:
Heart rate does not describe the lifting work. During a set of squats, heart rate may rise, then fall during the rest between sets. A session average does not contain the exercise, weight, repetitions or set type recorded in a strength log.
Power output isn't measured. Cyclists have power meters. Runners have pace-based estimates. There's no standard power meter for a barbell squat. You can calculate work from weight, distance and reps, but turning that into a stress score comparable with cycling TSS needs a different approach.
One aggregate cannot show which muscles worked. CTL and ATL each reduce the load history to one value. That value does not show which exercises were performed or which muscle groups carried the load.
This is why strength work needs its own load estimate before it can join an aggregate model, and why a per-muscle view needs a separate model on top.
How Incredible Uses Recorded Workout Load
Incredible uses one daily load across its training scores. Here's how the pieces connect:
1. Training Load starts with your day's training. Cardio load uses workout duration and heart rate intensity. Strength load comes from your logged sets: the exercise, the weight, the repetitions and the set type. Movement outside a workout counts too: the heart rate during exercise minutes your Apple Watch records outside a workout, such as a brisk walk you didn't start as one. Incredible adds these up and shows the day's Load on a 0 to 100 curve. That number is not a percentage or a physical maximum.
2. Recent Training is the faster average. Incredible keeps a weighted average of daily load with a 7 day time constant. Recent days have more influence, but it is not a simple seven calendar day window.
3. Fitness is the slower average. A second weighted average uses a 42 day time constant. Incredible shows it as Fitness, from 0 to 100, and as the Training Base on the Training Balance page. It reads your Apple Health history, so it can start with months of past workouts. Fitness is training built over time from recorded workouts, not complete physical fitness.
4. Training Balance compares the averages. Training Balance divides Recent Training by the Training Base. With a very small base, for a new or sparse history, it shows No base yet instead of a number. It describes the relationship between recent recorded training and the longer pattern, much as TSB does, but as a ratio rather than a difference. It does not predict injury or overtraining.
5. Cardio Load and Muscular Load split the week. On Progress, Cardio Load shows the last seven days' load on your heart and Muscular Load the load on your muscles, each against your usual week.
6. Muscle Freshness goes muscle by muscle. From your logged sets and your cardio, it estimates which muscles are ready to train and which still need rest, against your own usual. It is an estimate from your training log, not a measurement of the muscle.
7. Readiness brings the signals together. Each morning, Readiness starts from your sleep and overnight measurements: HRV, resting heart rate, body temperature and respiratory rate, each against your own usual range. Through the day, today's training, your movement and daytime stress lower it, and training costs more when Recent Training sits above your base. The score page shows what helped readiness and what lowered it. Blood oxygen is shown as its own vital and does not move the score.
None of these views proves recovery, predicts injury or overtraining, or prescribes a workout.
Apple Watch Series 12 and Ultra 4 now have Apple's own readiness score. Incredible gives you a daily Readiness score on older watches too, free on Series 4 and later. The score shows on the watch itself from Series 6, which runs watchOS 11. Check what your watch gets.
Why This Matters for Non-Athletes
You don't need to be a competitive athlete for training load modeling to be useful. The ideas apply to anyone who exercises regularly:
Comparing short and long patterns. A faster average responds quickly when recorded load rises or falls. A slower average changes more gradually. Their relationship makes a change in the training pattern visible without claiming to diagnose fatigue, injury or overtraining.
Understanding recorded history. A flat slower average means the recorded training history has been stable. It does not prove that physical fitness has plateaued.
Seeing lighter periods. When recorded load falls, the faster average usually falls before the slower one. The model shows that change without predicting how the person will feel or perform.
Returning from breaks. Days without recorded load make both averages decline, with the faster one declining sooner. That describes the training record; it does not decide a safe or appropriate return plan.
Common Misconceptions
"Higher CTL is always better." No. A higher value means more modeled training stress has accumulated. It is not a health grade, a safety threshold or a leaderboard.
"Negative TSB means I'm overtraining." No. It means the faster average is above the slower one. The number alone cannot diagnose overtraining.
"TSB tells me what I should do today." No. It describes recorded load. A training decision also depends on goals, symptoms, pain, professional advice and information the model does not contain.
"A zero-load day is missing data." Not always. A complete day with no training contributes zero. Missing, partial or still-updating workout data is unavailable, not zero, so incomplete logging leaves the picture incomplete.
Getting Started
If you've never thought about training load modeling, here's a practical starting point:
-
Track your training consistently. The model needs data. Record your cardio with an Apple Watch and log your lifts set by set. Gaps in the data create gaps in the model.
-
Watch the patterns, not one daily number. A longer view shows how the faster average has moved relative to the slower one. It does not decide whether physical fitness is building, holding steady or declining.
-
Treat the output as context. Training-load models describe recorded data. They do not prescribe a workout, establish safety, or replace how you feel and advice from a qualified professional.
-
Don't chase numbers. CTL is not a leaderboard. Its value depends on the input method, data coverage and the person's history, so a higher number is not automatically better.
Incredible works out its load from your Apple Watch workouts, your logged strength sessions and your movement outside workouts. You do not need to understand the math to read Load, Fitness, Training Balance, Muscle Freshness or Readiness. Incredible is free. Get Incredible on the App Store.
The Bottom Line
CTL and ATL modeling has long been part of endurance coaching because it makes faster and slower training patterns visible. Applying that idea to strength and hybrid training needs a load estimate for logged gym work rather than treating workout heart rate as the whole session. Incredible combines cardio, logged lifts and everyday movement into one daily load, then reuses it across Fitness, Training Balance and Readiness.
You do not need to become a sports scientist. The useful idea is simple: one average changes quickly and another changes slowly. Their relationship provides context, while sleep and overnight readings add the rest of the morning picture in Readiness. The decision about what to do stays with you.