Sports science platforms like Fast Talk Labs and Stryd have spent the last two years pushing coaches to abandon the single, static threshold number. They are right about the physiology: two riders with the same Functional Threshold Power can have completely different fatigue profiles two hours into a race. Relying on one 20-minute snapshot to govern a four-hour endurance ride ignores how your body actually breaks down over time.
Where that advice usually goes wrong for an amateur training six to twelve hours a week is in the execution. You are told to build multi-dimensional power profiles, track W-prime depletion, and cross-reference torque curves. Instead of clarity, you get a dashboard you do not have time to read. To make durability actionable without drowning in charts, we translate multi-dimensional fatigue into one number already sitting in your workout summary: Pw:HR in TrainingPeaks. To feed that ratio clean wattages across a road bike, a time trial rig, and an indoor trainer without recalibrating three different cranks, I move a single pair of Garmin Rally RS210 pedals between bikes in a few minutes and pair them with a chest strap.
We already covered the underlying physiology of the ratio in our guide to aerobic decoupling. This article is the operational protocol: how to pull the number out of TrainingPeaks correctly, how to separate true aerobic decay from simple plasma volume loss in the heat, and the exact decision rules we use on Monday morning to adjust your training week when the ratio spikes.
Why static FTP misses the decay
Your threshold is an anchor for setting cycling zones, not a guarantee of endurance. As we explained when breaking down why static threshold drops on long rides, a fresh test only measures what you can produce when your glycogen stores are full, your core temperature is normal, and your slow-twitch muscle fibers have not yet started failing.
During a three-hour steady ride in Zone 2, external power stays flat while internal cost quietly rises. Two distinct mechanisms drive that rising cost:
- True neuromuscular and metabolic decay: Your fatigued Type I (aerobic) fibers lose contractility. Your nervous system recruits less efficient Type IIa fibers to maintain the same wattage, demanding more oxygen and raising your heart rate for the exact same pedal stroke.
- Cardiovascular drift from plasma depletion: As you sweat, your blood plasma volume drops. With less fluid returning to the heart on each beat (lower stroke volume), your heart has to beat faster to pump the same amount of blood to your legs and skin.
A static FTP number cannot see either of these happening. Pw:HR catches both by measuring the divergence between the external work you are doing (power) and the internal cost of doing it (heart rate).
How to read Pw:HR in TrainingPeaks without corrupting the file
When you open a completed cycling file in TrainingPeaks, the summary box displays Pw:HR as a percentage. The software splits your selected workout—or a highlighted lap—exactly in half by time. It calculates the ratio of Normalized Power to average heart rate in the first half, compares it to the same ratio in the second half, and outputs the percentage shift.
How to read the TrainingPeaks Pw:HR number:
Under 5% = coupled. Your aerobic system held the load across the duration.
5% to 7.5% = borderline drift. Check fueling, cooling, or accumulated weekly fatigue.
Over 7.5% = decoupled. The internal cost climbed significantly faster than the power output.
Negative percentage (e.g., -2.4%) = your heart rate dropped relative to power in the second half, usually because you started the ride without a warm-up or rode into a cooler headwind later in the session.
The mistake most athletes make is reading the whole-file summary number right off the calendar card. Whole-file Pw:HR is almost always garbage data. It includes the first 15 minutes while your heart rate is still waking up, the coffee stop where your pulse dropped to 90 bpm, and the final 20 minutes coasting through traffic lights.
The 3-step clean selection protocol
When we review files during our Monday feedback loop, we never look at the whole-ride summary unless the entire session was ridden nonstop on an indoor ergometer. To get a valid Pw:HR reading in TrainingPeaks, do this:
- Click and drag across the steady Zone 2 belly of the ride: Exclude the first 20 minutes of warm-up and the final 10 minutes of cool-down. Heart rate lags behind power; including the warm-up artificially inflates your first-half efficiency and makes your second-half decoupling look worse than it is.
- Verify the Variability Index (VI) is 1.05 or lower: Look at the VI metric in the TrainingPeaks selection pane. If VI is 1.12 because you were surging up short hills and coasting down the other side, Normalized Power and heart rate will decouple simply because your cardiovascular system responds differently to stochastic spikes than to steady torque.
- Check for zero-averaging errors: If you stopped for three minutes to refill bottles in the middle of the selection, split the ride into two separate laps and compare the raw Efficiency Factor (EF = NP / Average HR) manually rather than letting a zero-power pause skew the second half.
Differentiating aerobic failure from plasma depletion
Once you have a clean Zone 2 selection with a VI under 1.05, a Pw:HR reading above 5% means your heart rate climbed relative to your watts. Before you conclude that your aerobic fitness is poor—or worse, that you are overtrained—you have to separate muscular decay from thermoregulatory drift.
Looking at a single Sunday ride cannot do this. You have to look at the trend across three variables in TrainingPeaks: temperature, fueling rate, and cadence.
1. The plasma volume check (hydration and heat)
If your two-hour indoor ride on Tuesday showed a Pw:HR of 2.1%, and your three-hour outdoor ride on Saturday in humid conditions showed 9.4% at the exact same Zone 2 wattage, your aerobic engine did not disappear in four days. You lost plasma volume.
When core temperature rises and blood gets diverted to the skin for cooling, venous return drops. Your heart rate climbs 8 to 15 beats per minute just to maintain cardiac output. If you weigh yourself before and after the ride and lost more than 2 to 3 percent of your body weight, that 9.4% Pw:HR is a hydration and cooling failure, not a training load failure. Before cutting volume, run the conditions through our heat calculator and audit your sodium and fluid intake.
2. The glycogen and fiber-shift check (true aerobic decay)
If the weather is cool, fluid loss is minimal, you are taking in 60 to 80 grams of carbohydrates per hour, and your Pw:HR still crosses 6% after 90 minutes in low Zone 2, you are looking at true muscular durability limits.
You can confirm this inside the TrainingPeaks chart by adding the cadence and left/right balance channels (if you ride dual-sided pedals like the Garmin Rally RS210). When plasma depletion drives heart rate up, your pedaling mechanics usually stay smooth until you are severely dehydrated. When muscular fatigue drives decoupling, your self-selected cadence typically drops by 5 to 8 rpm in the second half of the selection as you shift from spinning with fatigued slow-twitch fibers to mashing the pedals with larger motor units. If you are recovering from an old knee or hip issue, you will often see your left/right balance drift by 2 or 3 percent toward your dominant leg at the exact moment Pw:HR starts climbing.
How we use Pw:HR in our Monday adjustment rules
Data without a decision rule is just entertainment. Every Monday morning at 8:00 AM, we review the previous week's files and athlete feedback before editing the four-week rolling block loaded in TrainingPeaks. Decoupling trends govern two specific decisions: how we progress long rides, and how we diagnose systemic fatigue.
The Lengthen-Before-You-Accelerate Rule:
Do not raise your Zone 2 wattage target—or add threshold blocks to the final hour of a long ride—until you can complete the current duration with a clean Pw:HR under 5%.
If an athlete has a three-hour Zone 2 ride prescribed at 200W and finishes with a clean Pw:HR of 7.8% in cool weather, we do not bump next week's ride to 3.5 hours, and we certainly do not raise their FTP. We hold the duration at three hours until decoupling drops below 5%. Moving the duration up while the engine is still decoupling just teaches the athlete to survive the final hour on stress hormones and fast-twitch compensation.
When decoupling flags systemic fatigue or post-illness lag
What if an athlete normally holds 2.5% decoupling on a three-hour ride, and suddenly spikes to 8% on a standard two-hour session alongside a complaint of "heavy legs"?
This is where our adjustment rules separate peripheral (muscular) fatigue from central (nervous-system or post-viral) fatigue. We cross-check the Pw:HR spike against two questions:
- Did you just come off a cold or flu? If an athlete had a fever, they do not train at all until fever-free with good sensations. If they only had head congestion without a fever, we keep them moving in Zone 1 and low Zone 2, but their Perceived Exertion (RPE) and Pw:HR will often run unusually high for a week. When we see Pw:HR climb above 6% on an easy post-cold ride, any key threshold session later that week is immediately downgraded to an RPE-gated Zone 2 ride. Forcing intervals while your cardiovascular system is still showing drift after a virus digs a hole that takes three weeks to climb out of.
- Are you hiding in Zone X on easy days? When an athlete complains that they are not improving or feels flat despite normal weekly Training Stress Scores (TSS), we check the intensity distribution of their easy days. Riding in the upper half of Zone 2 (what we call Zone X) accumulates disproportionate autonomic stress. Over three weeks, that hidden fatigue shows up as an upward creep in Pw:HR on routine endurance rides before your threshold power actually drops.
Inside All-Access, members pair their TrainingPeaks calendar with our load management decision tool, which maps these exact weekly volume and recovery adjustments when illness, travel, or unexpected fatigue disrupts a block.
When you should ignore Pw:HR completely
Because TrainingPeaks calculates a Pw:HR percentage on every single workout card by default, the temptation is to treat every number above 5% as a red flag. That is the strongest argument against using aerobic decoupling: in the real world, outside of an indoor trainer, rides are rarely steady enough for the math to hold up.
Critics of the metric point out—correctly—that wind shifts, rolling terrain, group dynamics, and elevation changes alter the relationship between power and heart rate constantly. If you ride out for 90 minutes with a tailwind on the flats and ride back for 90 minutes into a stiff headwind up a false flat, your muscular torque demand changes even at the exact same wattage. Worse, during a threshold interval session (like 3 × 15 minutes at 100% FTP), your Pw:HR across the whole workout might read 12% or -8% depending on how long you soft-pedaled before the cooldown.
That criticism is completely valid if you read the metric blindly. You should ignore Pw:HR completely on interval days, recovery spins under 60 minutes, group rides where you spend 30% of the time coasting in the draft, and hilly routes where your Variability Index exceeds 1.06.
Yet the protocol holds because you do not need every ride in your calendar to measure durability. You only need one clean, repeatable 90-to-180-minute steady Zone 2 segment per week—or a dedicated long ride lap on flat-to-rolling terrain—to see how your physiology is absorbing the block. Strip out the warm-up, check the Variability Index, account for the heat, and that single percentage gives you the earliest warning system available in endurance training—without buying a single lactate strip or building a custom chart.
