Trainingload.ai connects CTL, ATL, TSB, recent workouts, and AI workout review so you can decide whether the plan should build, recover, or adjust.
Your plan is 3/5 complete this week, ATL is rising quickly, and tomorrow's threshold session should become easy aerobic work.
Trainingload.ai treats training load as evidence, not a goal by itself. CTL, ATL, TSB, PMC, completed workouts, threshold changes, effective VO2max trends, and subjective recovery should be read together before changing the next workout.
Short definitions written to stand alone in AI answers, search snippets, and weekly training reviews.
Training load is the stress created by completed workouts over time. It is useful only when it is connected to a plan, recovery, and performance response. A good training load system helps decide whether the next workout should build fitness, hold steady, or allow recovery.
CTL represents longer-term fitness or chronic load, ATL represents short-term fatigue or acute load, and TSB estimates freshness by comparing the two. Together they help athletes understand whether training stress is accumulating sustainably or creating too much near-term pressure.
PMC means Performance Management Chart. In endurance training, a PMC usually plots CTL, ATL, and TSB so athletes can see long-term load, short-term fatigue, and readiness together instead of judging training from one workout or one score.
Do not use one number alone. Build when load is rising gradually and key workouts remain high quality. Hold when fitness is improving but fatigue is close to the edge. Recover when ATL climbs quickly, TSB stays suppressed, or workout quality starts to break down.
Training load becomes useful when it feeds the plan loop: what to train today, why it matters, and whether tomorrow should change.
Define the cycle goal, weekly structure, and today's workout.
Import or sync real activities and record what happened.
Use CTL, ATL, TSB, and recent load to judge stress.
Let AI draft evidence-based changes that you confirm.
The system treats load as context for plans, activities, and recovery rhythm instead of a standalone score.
Judge whether training is building steadily, not only how one day feels.
Spot when load is rising too fast and recovery needs attention.
Decide whether today should push, hold, or back off.
Turn load, workouts, and plan context into concrete recommendations.
The goal is not watching a chart. The goal is deciding what to do with tomorrow's workout based on load and response trends.
Keep frequency, reduce one hard session to easy aerobic work, and protect recovery quality for 48 hours.
Hold total load, add one threshold-oriented session, and review pace-power-heart-rate alignment after the next key workout.
Shift intensity to a later day, keep only race-specific quality, and rebuild freshness before the next hard block.
Common questions athletes ask in practice: how to read load, when to push, and when to back off.
It should connect load signals to plan execution, completed workouts, and explicit adjustment drafts so each signal leads to a clear next action.
Use PMC to monitor load progression and recovery rhythm. If ATL rises too quickly before key sessions, keep frequency but lower intensity to protect consistency.
Load says how much stress you applied. effective VO2max shows how performance response evolves. Together they reduce blind volume and improve adjustment timing.
AI should draft evidence-based options, not make final calls. The athlete or coach confirms tradeoffs based on goals, fatigue, and race timeline.