Efficiency Factor and Aerobic Decoupling: How to Read Two Endurance Metrics
5 min read
Learn how to calculate and compare Efficiency Factor and aerobic decoupling with consistent ride windows, clear methods, and no unsupported fitness cutoffs.
On this page
Efficiency Factor compares power with heart rate; aerobic decoupling compares that relationship across ride segments. Use consistent methods, not a single value, to guide your review.
These metrics offer ways to describe recorded rides, rather than complete accounts of your fitness or training needs. The supplied reference is a PubMed search page, not a study validating formulas, thresholds, or training responses. This guide therefore states its calculation conventions explicitly and keeps the practical advice focused on repeatable data review.
Efficiency Factor, often shortened to EF, expresses a chosen power measure divided by heart rate for the same segment. Aerobic decoupling compares that ratio between an earlier segment and a later segment of the same ride.
The distinction is between a summary and a comparison: EF describes one window, while decoupling compares two windows. Neither calculation, on its own, explains why the recorded power-to-heart-rate relationship differs between rides or ride segments.
Start with how power, heart rate, and cadence fit together if you need a broader view of your ride file. Then review how pacing changes between ride halves before treating an early-to-late comparison as meaningful.
These names do not establish a universal scoring system, and the supplied search resource does not validate one. Use them to frame a clear question about your data, rather than to label a ride good or bad.
Photo by Artem Kniaz on Unsplash.
For a transparent manual calculation here, use average power in watts divided by average heart rate in beats per minute. Take both averages from exactly the same selected segment, with the same handling of pauses and missing data.
The convention in this guide is: EF = average power ÷ average heart rate. Save the segment boundaries alongside the result, so you can repeat the calculation without guessing which data you included.
Your platform may use normalized power rather than average power, so check its documentation before comparing displayed values. These are different inputs; matching labels do not make results interchangeable when the underlying power measure has changed.
Keep the platform's result separate from your manual result unless you have confirmed that their calculation methods match. A recorded ratio describes the inputs you selected; it does not establish how efficiently your body uses energy.
Choose average or normalized power, and record which measure you used.
Use heart-rate data from exactly the same ride window.
Save segment boundaries, data sources, and pause handling.
Compare only results calculated with the same method.
In N+One terms: a metric is useful when its inputs and context stay clear.
The supplied PubMed link is a search page, not a specific study, so it does not support precise definitions, thresholds, or physiological…
Data analysis is free, forever. The Dynamic Coach is Pro. Connected to Garmin, Strava, Whoop, and intervals.icu.
Select an early and a late segment from a steady block, preferably using windows of the same length. Calculate the power-to-heart-rate ratio for each window, using the same power measure and data rules in both cases.
This guide defines relative decoupling as the early ratio minus the late ratio, divided by the early ratio. If you express that fraction as a percentage, label it clearly and retain the underlying ratios for checking.
With this convention, a positive result means the later ratio is lower, while a negative result means it is higher. A result showing no difference means the ratios match; it does not mean every part of the ride matched.
Check your platform's sign convention and segment choices before comparing its result with your own calculation. No universal pass-or-fail cutoff is supported by the supplied source, so this guide does not prescribe one.
If the later segment includes less power, inspect how late-ride power losses appear in the file. Decoupling alone cannot tell you whether a changed ratio came from power, heart rate, or changes in both.
Define the early and late comparison windows before calculating.
Use the same power measure and recording rules in both windows.
Save both ratios, the formula, and the sign convention.
Describe the result without assigning a universal fitness grade.
One tactical email with training ideas and product updates. No spam — unsubscribe anytime.
Keep reading
- Peak Power Windows vs Lap Splits: Reading the Right Curve After a Hard Ride — Peak-power windows show best bursts; lap splits show sustained pacing. Learn which curve to trust after a hard ride and how to adjust the next seven...
- Indoor vs Outdoor Training Data: Understanding the Indoor–Outdoor Power Difference — Indoor and outdoor cycling power often disagree. Learn how to run a controlled comparison, find your power gap, and adjust training targets without o...
- Data engineering tips for cyclists — Data engineering tips for cyclists: practical steps to clean training data, prevent duplicates, and ensure time series consistency for better adaptiv...
Start by inspecting the traces rather than accepting a summary value that hides gaps or changes in recording. Confirm which devices supplied power and heart rate, and check whether either source changed during the selected block.
Mark stops, descents, surges, and missing samples so you can see what each window contains before comparing results. Use a lap-by-lap review of the workout when whole-ride averages conceal clear differences between the selected segments.
Record route, weather, perceived effort, and interruptions as context, without claiming that any one note explains the result. A note helps you ask a better question; it does not establish a physiological cause for the pattern.
During autumn, shorter daylight may change your usual route or move a familiar outdoor session onto the trainer. Label that change rather than assuming the new session belongs in the same comparison group as earlier rides.
Build a small record of comparable sessions, keeping the calculation method and ride structure visible beside each result. There is no supported timetable here for how quickly either metric should change, or how much change matters.
Write observations that stay close to the data: the later ratio fell, or this ride's ratio exceeded the previous comparable result. Avoid turning those descriptions into claims that your fitness improved, recovery failed, or training load must change.
If one session looks unusual, your next move is to audit its windows and sensor traces before changing training. When a comparison remains unclear, leave it unclassified rather than forcing the number into a training recommendation.
A useful review also keeps room for what the ratio leaves out, including the session's purpose and your experience. For an unfinished workout, review what the interval file actually shows instead of letting one summary number stand for the session.
Save the calculation method with every result.
Group sessions by similar structure and measurement approach.
Keep notes on changes that weaken the comparison.
Audit unusual files before changing your training.
Before the ride: Choose the ride structure, power measure, and heart-rate source. Define the planned comparison windows and record how you will handle pauses.
During the ride: Keep the selected data sources consistent. Note stops, route changes, or recording problems that could make the windows difficult to compare.
After the ride: Check the traces, then calculate each window's power-to-heart-rate ratio. Calculate decoupling using the stated convention and save the inputs with the result.
When reviewing: Compare only sufficiently similar sessions. If a result looks unusual, inspect the file and context before treating it as a reason to change training.
Efficiency Factor summarizes a power-to-heart-rate ratio; aerobic decoupling compares that ratio across ride segments. Your next move is to standardize the calculation and review comparable files, not chase a cutoff or change training from one reading.