Chronic Training Load (CTL)

You can think of Chronic Training Load (CTL) as a slow-moving average of how consistently you’ve been training. It’s commonly calculated over roughly 42 days, so it changes slowly and is better for long-term trend than day-to-day fluctuations.

CTL is often used as a practical proxy for long-term fitness base, but it is still a model of accumulated load rather than a direct measurement of performance. Two athletes can have the same CTL and very different race readiness, depending on intensity distribution, sport type, sleep, nutrition, and recent fatigue.

Example card: values and percentages are for UI preview only. Interpret them with your own data and trends.

Core Concepts

• Slower response: CTL is not very sensitive to a single workout. Raising CTL requires weeks of consistent training.
• Long-term accumulation: with a 42-day time constant, today’s training only contributes about 1/42. Fitness is built through long-term consistency.
• Use it or lose it: if you stop training, CTL decays exponentially, matching the intuition that detraining reduces fitness.
• Input compatibility: CTL is computed from “daily load”. That can be power-based TSS or heart-rate-based TRIMP. Trainingload.ai can support either or both, as long as you keep your measurement standard consistent.

How to interpret and use it

• CTL rising slowly: usually means your recent total load has stayed above your current CTL. Watch weekly change and avoid ramping too fast (injury risk).
• CTL falling slowly: usually means training dropped or you entered a recovery/taper period. You may feel fresher short-term, but prolonged low load can reduce fitness.
• Monitor ramp rate: faster weekly CTL growth generally increases risk (especially in high-impact sports like running).
  • Safer: +3 to +5 per week
  • Aggressive: +5 to +8 per week (higher risk)
  • Risky: > +8 per week (injury/illness risk)
• Use with ATL/TSB: CTL alone can hide short-term fatigue and freshness. Pair it with Fatigue | Acute Training Load (ATL) and Form | Training Stress Balance (TSB).

Trainingload.ai note: don’t chase CTL endlessly. For most amateurs, keeping CTL around 60–80 and improving “quality” (e.g., raising FTP) is often more effective than simply piling on more volume to raise CTL.

What CTL can and cannot tell you

CTL is useful for judging whether your training base is rising, stable, or declining. It is less useful for deciding whether you are ready for a hard workout tomorrow.

• Good use: checking whether weekly load is building gradually over several weeks.
• Poor use: assuming a higher CTL always means better performance.
• Important context: CTL should be read with ATL, TSB, and the type of work that created the load.

How Trainingload.ai uses CTL

Trainingload.ai uses CTL as a long-term context signal. If CTL is rising steadily, the plan may be tolerating the current build. If CTL is flat or falling unintentionally, the AI coach can review missed workouts, reduced volume, or inconsistent load before suggesting changes.

CTL is most useful when it helps answer: “Is the plan building a sustainable base, or just creating short-term fatigue?”

Calculation Formula

CTL is an exponentially weighted moving average (EWMA) of daily training load (TSS or TRIMP). In classic PMC, CTL usually uses a longer time constant (commonly 42 days) to represent long-term fitness:

CTL_today = CTL_yesterday + (TSS_today - CTL_yesterday) / 42

• TSS_today: today’s TSS or TRIMP.
• 42: time constant (~6 weeks). Larger means smoother and less sensitive to single workouts.

Where it fits in a training cycle

• Base: focus on raising CTL with a steady upward slope.
• Build: maintain CTL or rise slowly while shifting focus toward intensity.
• Race / taper: allow a slight CTL drop to raise TSB (freshness).

References

• The Science of the TrainingPeaks Performance Manager (Andrew Coggan)
• Modeling Human Performance (Fellrnr)