Training Stress Score and Performance Management: How to Read CTL, ATL, and TSB Without Being Misled

The Logic of the Three Curves

The Performance Management Chart originates from Banister’s impulse-response model, which quantifies each training session as a Training Stress Score (TSS) and then applies two exponentially weighted averages:

• CTL (Chronic Training Load, fitness): A TSS weighted average with a long time constant (commonly 42 days), representing the accumulated “fitness base.”
• ATL (Acute Training Load, fatigue): A TSS weighted average with a short time constant (commonly 7 days), representing recently accumulated “fatigue.”
• TSB (Training Stress Balance, form) = Yesterday’s CTL − Yesterday’s ATL: A positive value indicates freshness, a negative value indicates fatigue.

How TSS Is Calculated and Where Its Blind Spots Lie

TSS estimates the stress of a single session by squaring intensity (relative to threshold) and multiplying by duration, giving high intensity appropriate weighting. But there are plenty of blind spots:

• Depends on correct thresholds (FTP/LTHR/critical speed): If thresholds are set wrong, all TSS values become distorted accordingly, and the CTL trend may look good while being wrong.
• Poor comparability across disciplines: Running TSS, swimming TSS, and cycling TSS are not equivalent in terms of actual physiological stress; summing them directly for multi-sport athletes can mislead.
• Does not account for non-training stress: Mental fatigue, sleep deprivation, illness, and life stress do not enter TSS (see the mental fatigue article), yet they all consume recovery.
• Individual time constants differ: The default 42/7 days may not be accurate for everyone; older individuals, beginners, and those under high stress clear fatigue more slowly.

Common Misinterpretations

• “Higher CTL means stronger”: CTL is a measure of load, not performance. Piling it up without limits often ends in injury or overtraining. CTL’s value lies in accumulating it “sustainably and progressively” and converting it into good form on race day.
• “A positive TSB always means good form”: An excessively positive value (long-term undertraining) can leave you “flat.” The optimal pre-race TSB is a moderate positive value (individualized, with the common range varying by person), paired with a taper that preserves intensity.
• “High ATL always means rest”: It should be interpreted alongside HRV, resting heart rate, and subjective ratings (see the HRV-guided article). Looking at ATL alone can lead to overreaction or underreaction.

Correct Usage

• Treat it as a trend and communication tool, not gospel: Look at the CTL slope (progression rate) and the relative changes in ATL/TSB, rather than single-day absolute values.
• Calibrate thresholds: Update FTP/LTHR/critical speed regularly; otherwise, the entire chart is built on sand.
• Triangulate: Cross-check against subjective feelings, HRV/RHR, and actual performance tests. When data and your body disagree, trust your body.
• Adjust TSB before racing: Use a taper to push TSB to an individualized moderate positive value while retaining intensity stimulus (see the taper week article).

CTL/ATL/TSB are a handy dashboard, not a medical report. Their greatest danger is not inaccuracy but “looking accurate”—with mis-set thresholds, life stress excluded, and the same constants applied to everyone, you can train on a beautiful but deceptive curve. Treat them as trends and use your body as the calibration.

Related Reading

• What Exactly Are TSS, CTL, ATL, and TSB Calculating? The Capabilities and Limitations of Training Load Quantification Models
• Training Load and Fatigue Management: Applications of CTL, ATL, and TSB
• The Complete Guide to TSS, CTL, ATL, and TSB: Calculation Principles and Applications of Training Stress Index
• The TSS and CTL Training Load Model: Why Numbers Lie and How to Read Them Correctly