A Performance Management Chart puts longer-term load, recent load, their difference, and the acute:chronic workload ratio on one timeline. Trainingload.ai then connects the chart to the plan, completed workouts, source activities, and AI review so you can build, hold, recover, or investigate the data.
Trainingload.ai treats PMC as load context, not a direct measurement of fitness, fatigue, readiness, or injury risk. CTL, ATL, TSB, and ACWR locate a change; the plan, completed workouts, source activities, threshold and load-source settings, subjective signals, and performance response determine whether a training adjustment is justified.
Start with the terminology map, then continue to each metric's formula, useful questions, limitations, and combined interpretation.
A PMC fitness chart is a Performance Management Chart used to compare long-term fitness, short-term fatigue, and current form. It usually combines CTL, ATL, and TSB so athletes can decide whether to increase load, maintain the plan, or recover before quality drops.
CTL, or chronic training load, shows the longer-term direction of training stress. Rising CTL can indicate building fitness, but it should not be chased blindly. The useful question is whether CTL is increasing while workout quality and recovery remain stable.
ATL, or acute training load, reflects recent training stress and fatigue pressure. High ATL is not automatically bad during a build phase, but it becomes a warning when key workouts suffer, recovery markers decline, or load rises faster than planned.
TSB, or training stress balance, estimates form and freshness by comparing chronic and acute load. A low or negative TSB can be normal in training blocks, but persistent suppression before key sessions may suggest holding load or adding recovery.
ACWR is the acute:chronic workload ratio. Trainingload.ai calculates it as current ATL divided by current CTL. It can flag a fast change in recent load relative to the longer baseline, but it cannot independently predict injury, recovery, or race readiness.
All 4 metrics come from the same daily training-load series, but they answer questions at different time scales. Understand each calculation and limitation before combining them.
CTL is a slow exponentially weighted moving average of daily training load. Trainingload.ai uses a 42-day smoothing period, so CTL is most useful for describing load direction over several weeks: is the current block building, holding, or declining? Interfaces often label CTL as “fitness,” but it measures modeled load history—not how much training the body has absorbed and not a fitness score that can be compared across athletes.
decayCTL = exp(-1 / 42)
CTLtoday = CTLyesterday × decayCTL
+ daily load × (1 − decayCTL)Read CTL direction and slope against the training block. A gradual rise with stable key-session execution suggests load is accumulating as intended. A sudden jump should trigger a check for an unusual activity, threshold edit, duplicate record, or load-source change. There is no universal ideal CTL value.
Do not misread it：Rising CTL does not prove successful adaptation, and higher is not automatically better. The same CTL can come from different sports, intensity distributions, and data sources.
Read the full metric docsATL is the fast exponentially weighted moving average of the same daily load series. Trainingload.ai uses a 7-day smoothing period, making it sensitive to recent sessions and useful for locating when short-term training pressure rose or fell. Interfaces often call ATL “fatigue,” but ATL does not read sleep, pain, illness, or subjective fatigue. It provides fatigue context rather than a physiological diagnosis.
decayATL = exp(-1 / 7)
ATLtoday = ATLyesterday × decayATL
+ daily load × (1 − decayATL)When ATL rises quickly, inspect the last 7–14 days of long sessions, quality workouts, races, and unplanned activity. Decide whether the increase matches the plan. ATL normally falls faster than CTL during a recovery week. The important question is whether the ATL change also coincides with worse execution, subjective state, or pain signals.
Do not misread it：High ATL is not automatically dangerous, and low ATL does not prove good recovery. It describes recent load, not measured fatigue.
Read the full metric docsTSB is the difference between current CTL and ATL. It describes where recent load sits relative to the slower load trend. A negative value means ATL is above CTL, which is common during a build; a positive value means ATL is below CTL, which is common during recovery or tapering. TSB is often labeled “form” or “freshness,” but it remains a mathematical relationship between 2 load models.
TSBtoday = CTLtoday − ATLtoday
Use TSB as timing context. During a taper, ATL falls faster and TSB rises; during a build, ATL rises faster and TSB becomes negative. Before a key workout or race, compare the pattern with the athlete's own history, plan purpose, execution quality, and subjective state rather than applying universal positive or negative bands.
Do not misread it：Positive TSB does not prove peak readiness, and negative TSB does not diagnose overtraining. A fixed “optimal range” is not portable across athletes and load models.
Read the full metric docsACWR, also written as A:C Ratio, compares recent load with the longer load baseline. Trainingload.ai divides current ATL by current CTL, which is not the same as every 7-day-total / 28-day-average implementation found online. A higher ratio only confirms that modeled recent load is higher relative to the longer baseline; it is useful for locating a ramp or a possible data anomaly.
ACWRtoday = ATLtoday / CTLtoday if CTLtoday = 0, return 0
Read the ATL and CTL absolute values before the ratio. ACWR can rise because of a planned overload, one abnormal activity, a small denominator after a long break, a threshold edit, or a duplicate import. After verifying the data, combine sport impact, pain, illness, sleep, and workout quality before changing training.
Do not misread it：ACWR is not an injury predictor, and no universal “safe sweet spot” applies to every athlete. Display bands are review prompts, not medical or training clearance.
Read the full metric docsA single number rarely decides the workout. A stronger process identifies the curve pattern, traces it to source activities, then validates it against the plan purpose and athlete feedback.
CTL rises gradually; ATL is periodically above CTL; TSB is moderately negative; ACWR stays near the athlete's recent pattern.
Load is accumulating without an obvious acceleration signal.
If key-session quality, subjective state, and recovery remain stable, keep the plan. Do not add load merely to make the chart look better.
ATL rises quickly; CTL lags; TSB drops; ACWR rises at the same time.
Recent modeled load is clearly above the longer baseline, but the cause and athlete response still need verification.
Trace the source workouts and rule out duplicates or threshold changes. If key-session quality also declines, change only one variable: intensity, duration, or timing.
ATL falls faster than CTL; TSB rises; ACWR falls; CTL usually holds or declines slowly.
Recent load is decreasing and modeled freshness is rising, but peak condition is not proven.
Validate with a comparable key session, subjective feedback, and event demands. Do not panic-add load because CTL dipped slightly.
ATL and CTL both fall; TSB may become positive; ACWR is low or distorted by a small CTL denominator.
The model sees less training load but cannot distinguish planned rest, missing records, injury, or a schedule interruption.
Check activity completeness and load sources first. Do not treat positive TSB as proof of good form.
PMC appears normal while pace/power execution, sleep, pain, or subjective fatigue keeps worsening.
The load model is missing important context; the chart alone cannot justify more pressure.
Treat the conflict as an investigation signal and keep changes conservative. Prioritize health and qualified advice for pain, illness, or abnormal symptoms.
A useful PMC tool should show where the numbers came from, which workouts they describe, whether the load matched the plan, and what—if anything—should change next.
The Free plan includes PMC, CTL–ATL–TSB charts, the metrics hub, and the deeper dashboard workspace. Evaluate the workflow with your own history before paying for core load analysis.
Trainingload.ai documents its 7-day ATL, 42-day CTL, TSB, and ACWR formulas. Activity load can use power, heart rate, pace, or session RPE according to your thresholds and source priority.
The chart is not an isolated smooth line. Connect a PMC change to planned sessions, completed work, missed workouts, and source activities before explaining what changed.
PMC describes applied pressure. Effective VO2max, threshold trends, workout quality, and subjective signals help test whether the expected response occurred—reducing the temptation to chase CTL alone.
When load and execution evidence support an adjustment, the AI coach can draft a conservative change inside the current plan. Review the reason, exact edit, and validation point before applying it.
Read pressure, readiness, and execution together. Make one conservative change, then validate on the next key session.
CTL is your long-term load trend. Use it to confirm whether the block is building as intended.
ATL shows short-term stress pressure. High ATL is not automatically bad; it must be read with session quality.
TSB helps decide whether to keep, move, or downgrade a key workout before quality drops.
When chart signals and execution diverge, change one variable first (intensity, duration, or timing), then review again.
Clear answers to common questions about PMC, CTL, ATL, TSB, and ACWR.
In endurance training practice, yes. The common fitness-fatigue-form chart is the Performance Management Chart built from CTL, ATL, and TSB.
No. If CTL rises while key-workout quality and recovery keep deteriorating, the current build may not be working. The goal is sustainable progress, not a nonstop CTL climb.
Keep monitoring, but avoid reactive cuts. Confirm with the next key workout and recovery markers before making a large change.
Not necessarily. ATL often sits above CTL during a training build, so a negative TSB is common. Consider how long it lasts, key-workout quality, and how you feel before reducing load.
No. ACWR only shows whether recent modeled load is high relative to the longer baseline. It cannot predict injury by itself or replace coaching and medical judgment.
Check for duplicate activities, threshold changes, a different load source, or an unusually large activity load. Data changes can move CTL, ATL, and ACWR together.
Yes. PMC can only use load recorded in the system. Missing workouts understate ATL and CTL; adding them later recalculates the following dates.
You do not need to watch it constantly. A weekly review, recovery week, race taper, or a clear mismatch between plan and execution are better times to check it.
Last updated:
