Demystifying cycling telemetry: a practical guide to power and the PMC
How normalized power, TSS, and the Performance Management Chart (CTL, ATL, TSB) turn noisy sensor data into actionable training signals.
Francesco Castaldi7 min read

Modern road cycling is one of the most sensor-rich endurance sports in existence. A typical weekend ride streams millions of data points into your head unit: strain-gauge pedal force, cadence, heart rate, GPS coordinates, barometric altitude, and ambient temperature.
Yet collecting data is trivial; transforming volatile raw numbers into genuine physiological insight is where many athletes stumble. Looking at average speed or average heart rate often obscures what your body actually experienced. By understanding the core telemetry models, specifically Normalized Power, Training Stress Score, and the Performance Management Chart (PMC), you can replace guesswork with reproducible fitness progression.
The flaw of average power: why Normalized Power matters
On a stationary trainer held at a flat pace, your average power reflects your effort accurately. On open roads, however, average power falls apart.
Consider two distinct one-hour rides:
- Ride A: A steady, disciplined Zone 2 endurance spin holding exactly 200 watts from start to finish.
- Ride B: A punchy group ride featuring twenty steep 500-watt hill surges interspersed with zero-watt tucks on descents, finishing with a raw mathematical average of 200 watts.
While both rides show identical average power on your head unit, Ride B induces vastly greater glycogen depletion, neuromuscular fatigue, and lactate accumulation. Human physiology does not respond to mechanical work in a linear fashion; physiological strain scales exponentially with intensity.
To resolve this limitation, exercise physiologist Dr. Andrew Coggan developed Normalized Power (NP). The calculation mimics how your cardiorespiratory system and metabolic pathways react to variable workloads:
- Calculate a 30-second rolling average of power output to smooth high-frequency noise.
- Raise each 30-second value to the 4th power, reflecting the disproportionate physiological cost of high-intensity efforts.
- Average these 4th-power values across the entire activity duration.
- Take the 4th root of the final average to bring the figure back into watts.
[!NOTE] The fourth-power weighting is not arbitrary. It closely approximates the relationship between exercise intensity, blood lactate concentration, and glycogen oxidation rates across endurance efforts.
By comparing your Normalized Power to your average power, you obtain the Variability Index (VI = NP / Average Power). A steady time trial or solo endurance ride typically registers a VI between 1.00 and 1.05. In contrast, a chaotic criterium or punchy mountain route often yields a VI above 1.20, indicating severe metabolic fluctuations.
| Metric | Calculation | What it tells you |
|---|---|---|
| Average Power | Sum of all watts / Total seconds | Raw mechanical work output |
| Normalized Power (NP) | 4th-power weighted rolling algorithm | True physiological cost of the effort |
| Variability Index (VI) | Normalized Power / Average Power | Smoothness and pacing discipline of the ride |
| Intensity Factor (IF) | Normalized Power / Functional Threshold Power (FTP) | Relative intensity scaled to your current fitness |
Table 1: The core power telemetry metrics used to evaluate cycling efforts.
Quantifying session load: Intensity Factor and TSS
Knowing the metabolic difficulty of a ride allows us to calculate total training load. Two variables govern physiological adaptation: how hard you rode and how long you rode.
The relative intensity of an effort is quantified by the Intensity Factor (IF):
$$\text{IF} = \frac{\text{NP}}{\text{FTP}}$$
Where Functional Threshold Power (FTP) represents the highest power output you can sustain in a quasi-steady state for approximately sixty minutes. An IF of 1.00 represents riding at your absolute limit for one hour, while an endurance recovery spin sits comfortably below 0.65.
Combining Intensity Factor with duration produces the Training Stress Score (TSS):
$$\text{TSS} = \frac{t \times \text{NP} \times \text{IF}}{\text{FTP} \times 3600} \times 100$$
Where $t$ is duration in seconds. By definition, holding your FTP for exactly one hour ($t = 3600$, $\text{IF} = 1.00$, $\text{NP} = \text{FTP}$) generates exactly 100 TSS points. A steady two-hour Zone 2 ride might generate 110 TSS, whereas a brutal four-hour granfondo can exceed 280 TSS.
[!WARNING] Garbage in, garbage out. Because both IF and TSS depend directly on your FTP setting, an outdated or overinflated threshold will distort every training load calculation across your entire season. Re-test your threshold periodically with standardized protocols.
The Performance Management Chart: balancing fitness and fatigue
A single workout does not make an athlete fit; the accumulated sequence of workouts and recoveries does. In the 1970s, sports scientist Eric Banister introduced the mathematical impulse-response model of athletic training. In modern cycling software such as Intervals.icu and TrainingPeaks, this model is realized as the Performance Management Chart (PMC).
The PMC tracks three continuous variables over time:
1. Chronic Training Load (CTL) or Fitness
CTL models your long-term training foundation. It is calculated as an exponentially weighted rolling average of your daily TSS over a 42-day time constant:
$$\text{CTL}{\text{today}} = \text{CTL}{\text{yesterday}} + (\text{TSS}{\text{today}} - \text{CTL}{\text{yesterday}}) \times \left(1 - e^{-1/42}\right)$$
Because the decay constant is six weeks, CTL rises slowly when you train consistently and falls gradually during breaks. It represents your aerobic engine and capacity to absorb work.
2. Acute Training Load (ATL) or Fatigue
ATL models short-term fatigue. It uses the same mathematical exponential smoothing formula, but over a sharp 7-day time constant:
$$\text{ATL}{\text{today}} = \text{ATL}{\text{yesterday}} + (\text{TSS}{\text{today}} - \text{ATL}{\text{yesterday}}) \times \left(1 - e^{-1/7}\right)$$
A heavy weekend with back-to-back long rides will spike your ATL rapidly, reflecting immediate muscular soreness, glycogen depletion, and nervous system tiredness.
3. Training Stress Balance (TSB) or Form
Form is the difference between your historical fitness and your current fatigue:
$$\text{TSB} = \text{CTL} - \text{ATL}$$
When you train hard for several consecutive days, your short-term fatigue (ATL) exceeds your chronic fitness (CTL), pushing your TSB into negative territory. You are fit, but you are tired. When you rest or execute a structured taper, ATL decays roughly six times faster than CTL, allowing TSB to rise into positive numbers.
| TSB Range | Physiological State | Practical Guidance |
|---|---|---|
| Above +25 | Detraining risk | Extended inactivity; fitness is beginning to decay noticeably |
| +10 to +25 | Fresh / Peaked | Optimal window for key races, granfondos, and target time trials |
| -10 to +10 | Neutral / Transition | Sustainable maintenance; good for solid mid-week training blocks |
| -10 to -30 | Productive training | Overload phase; building fitness effectively when paired with sleep |
| Below -30 | High fatigue warning | Risk of non-functional overreaching, illness, and chronic exhaustion |
Table 2: Training Stress Balance (TSB) operational zones for road cyclists.
[!IMPORTANT] A high CTL alone does not win races. Arriving at the start line with a high CTL but a deeply negative TSB (e.g., -25) will leave your legs feeling heavy, slow, and unresponsive. The goal of a proper taper is to shed acute fatigue while preserving chronic fitness, bringing your TSB between +5 and +15 on race morning.
Practical application: building your telemetry pipeline
To put these models to work without getting bogged down in manual calculations, a streamlined automated pipeline is key:
- Hardware Capture: Use dual-sided power pedals or a spider-based power meter paired with your head unit. Calibrate your zero-offset before every ride.
- Automated Ingestion: Configure your cycling computer to sync automatically via Wi-Fi or Bluetooth to platforms like Intervals.icu.
- Monitor Ramp Rate: Track the rate at which your CTL grows each week. A sustainable ramp rate is between 3 and 7 CTL points per week. Ramping faster than 8 points per week sharply escalates injury risk without granting additional aerobic gains.
- Schedule Deload Weeks: Every third or fourth week, reduce weekly TSS by roughly 40-50% while maintaining a few short intensity touches. This brings TSB close to zero and lets your adaptations consolidate.
[!TIP] Do not judge a workout solely by how high you pushed your normalized power. The most valuable training rides are often quiet Zone 2 volume blocks that accumulate consistent TSS with low cardiac drift and zero drama.
The signal beneath the noise
Data never turns the pedals for you, nor does it replace listening to your body. On days when work stress is high or sleep is poor, subjective perceived exertion must always take precedence over numbers on a screen.
However, when applied systematically, telemetry transforms training from an anxious guessing game into an observable, iterative process. By decoupling fatigue from fitness through the Performance Management Chart and respecting the true physiological cost of your efforts with Normalized Power, you can line up on the road confident that every pedal stroke was spent with intent.
- #cycling
- #telemetry
- #data
- #training
- #power
Share article
Zero tracking, no cookies, privacy-respecting.