Fitness, fatigue and form (CTL, ATL, TSB) explained
How fitness (CTL), fatigue (ATL) and form (TSB) are calculated from training load, how to read them, and a worked two-week example with real numbers.
Fitness, fatigue and form are three numbers drawn from one input: how much training you did each day. They answer the questions every endurance athlete asks in some form. Am I getting fitter? How tired am I right now? Am I ready to race? They're also easy to over-read, so this guide covers what each number is, the arithmetic behind it, and what it can and can't tell you.
In training apps you'll see them as CTL (chronic training load, "fitness"), ATL (acute training load, "fatigue") and TSB (training stress balance, "form"). Fit File Forge's Training page shows them under the plain names first.
Where the idea comes from
In 1975 Eric Banister and colleagues proposed that every training session does two things at once: it builds a little lasting fitness, and it leaves a larger, shorter-lived dose of fatigue. Performance on a given day is the first minus the second. Both effects fade over time, fatigue much faster than fitness. That's the whole insight, and it explains why you're slower the week after a big block and faster after a taper.
Banister fitted his model with athlete-specific weights and time constants. The version most athletes use today, popularized by Andrew Coggan and TrainingPeaks as the Performance Management Chart, keeps the shape and fixes the defaults: 42 days for fitness and 7 days for fatigue, with equal weights.
Step one: a training load for every day
Everything starts with a daily load number: one number per session, bigger for longer or harder work. The best-known version is Coggan's Training Stress Score (TSS®), where an hour at exactly your threshold scores 100. It's built from intensity squared times duration, so an hour at 90% of threshold scores 81, not 90.
Fit File Forge computes its own training load per activity, using the best method the data allows:
- Power, for rides with a power meter and an FTP: the classic power-based score.
- Pace, for runs with a threshold pace (grade-adjusted), and for swims with a CSS.
- Heart rate, against your LTHR. With only a max heart rate, it uses 90% of max as a stand-in and marks the load as an estimate.
- Duration as a last resort, also marked as an estimate: about 60 per hour for a run, 55 for a ride or swim, 40 for strength and 30 for a hike. Each step down the list costs accuracy, which is why entering real threshold numbers (in Settings, or with the training zones calculator) matters more than anything else on this page.
Step two: two moving averages
Each day, fitness and fatigue move a fraction of the way toward that day's load:
fitness_today = fitness_yesterday + (load_today − fitness_yesterday) / 42
fatigue_today = fatigue_yesterday + (load_today − fatigue_yesterday) / 7
form_today = fitness_yesterday − fatigue_yesterday
These are exponentially weighted averages. With a 42-day constant, about two-thirds of your fitness reflects the last six weeks; with 7, about two-thirds of your fatigue reflects the last week. That difference in speed is the point: one hard day barely moves fitness and moves fatigue a lot.
From a steady 50 a day, a single day of 100 raises fitness by about 1.2 and fatigue by about 7.1. Fitness is the slow number you build over months; fatigue is the fast one you can change in a week.
Form uses yesterday's numbers. That makes it a morning reading: how fresh you are before today's session, not after it.
A worked example
Take a runner who has trained at a steady load of 50 a day (350 a week) for two months, so fitness and fatigue both sit at 50 and form at 0. Then comes a hard week of 500 (a threshold session Tuesday, intervals Thursday, a long run Saturday, easy mileage Sunday) followed by an easy week of 180. These are typed-in numbers run through the same calculation as the Training page:
Two lessons hide in those tables. Form swings quickly; fitness doesn't. And rest isn't free: a whole easy week gave back more fitness than the hard week built. A taper trades a little fitness for a lot of freshness, which is exactly the trade you want before a race and the wrong one three times a month.
Reading form
Fit File Forge's Training page puts form on one scale:
| Form (TSB) | Training calls it | Roughly |
|---|---|---|
| 5 or more | Fresh | ready to go |
| −10 to 5 | Balanced | steady load |
| −30 to −10 | Building | adapting |
| below −30 | Overreached | needs rest |
Some practical readings:
- Building (−10 to −30) is where most productive training weeks live. Seeing it most of the time during a build is normal.
- Fresh (+5 and above) is where you want to be on race morning. Very high form for weeks on end usually means fitness is draining away.
- Below −30 means fatigue is far ahead of fitness. One day there after a big weekend is common; a week there is a reason to back off.
- Fitness rising slowly is the goal. A jump of several points in a week usually means the week was too big for what came before.
What the numbers can't tell you
These numbers know only what you did. They don't know how you feel, how hot it was, or whether you were sick, so use them alongside how training actually goes. They also depend on your threshold numbers: if your threshold pace or FTP is stale, every session's load is off by the same factor, and so are all three lines.
And they need history. With under six weeks of data, fitness is still warming up; Fit File Forge starts from the average of your first two weeks and says "Calibrating" until there are about two weeks of sessions with a load.
How the Training page computes them
When Garmin activity sync is on, each synced activity gets a training load by the method above, loads are summed per calendar day, and fitness, fatigue and form are computed for every day, rest days included (a zero-load day still moves both averages). Change your threshold numbers in Settings and every activity's load is recomputed, so the whole history moves at once.
Sessions that move these numbers
Sources
- E. W. Banister, T. W. Calvert, M. V. Savage, T. Bach. A systems model of training for athletic performance. Australian Journal of Sports Medicine 7: 57–61, 1975.
- TrainingPeaks. What is the Performance Management Chart?. TrainingPeaks.
- Hunter Allen, Andrew Coggan, Stephen McGregor. Training and Racing with a Power Meter (3rd ed.). VeloPress, 2019.
- Joe Friel. Joe Friel's Quick Guide to Setting Zones. TrainingPeaks.
Written by Caleb Wetherell; drafted with AI assistance and checked against the sources below.
Training information, not medical advice.
Want this at your paces, on your watch?
Describe it in plain words: your coach builds it at your numbers, ready to send to your Garmin.
Your coach drafts your first week free, from your Garmin training. No card.