TrainingPeaks, intervals.icu, Garmin and Training Intel all use the same formula. What differs is what each app is given. Here's what, and how to check yours in two minutes.
Fitness is your average daily training stress over about the last six weeks. Fatigue is the same over about the last week. Each session's stress depends on how long it was and how hard it was against your threshold, so an app with a different threshold, or a different way of measuring effort, gives a different number.
None of them is the one true number. What matters is that one app stays consistent from day to day, because that's what the advice reads: whether you're building, holding or carrying too much fatigue. Ours is scored from the thresholds on your Profile.
Each app scores your sessions against the FTP, threshold pace and threshold heart rate set in that app. An old or default value in one of them changes every session it scores.
Example: an FTP left at 250 W when it's really 120 W makes every ride count for about a quarter of its real effort.
Runs can be scored by pace, heart rate or run power. Pace reacts instantly but is often wrong on a treadmill; heart rate is steady but lags behind short efforts; run power works anywhere.
Example: an easy treadmill run scored by pace came out at near-threshold effort, while the heart rate said easy.
Rides recorded only in TrainerRoad or Zwift often never reach Garmin, so apps that read from Garmin miss them. The same ride from two devices can be counted twice in TrainingPeaks. We count it once.
Fitness builds over weeks, so where an app started counting shows for a long time. With no starting numbers from you, we start from your own first weeks of training, not from zero.
Every session is scored by the most reliable signal it has, against the thresholds on your Profile. Your brief says which one it used.
| Sport | Scored by, in order |
|---|---|
| Swim | Pace against your threshold pace (CSS); heart rate without one. |
| Bike | Power against your FTP; heart rate on rides without a power meter. |
| Run | Run power (Stryd and similar) against your run power threshold; then pace on outdoor runs; then heart rate. A pace score that says far harder than your heart rate does is set aside for the heart-rate one. |
Interval sessions are judged by power or pace when you've given those thresholds, because heart rate lags behind short efforts. When your sessions come from TrainingPeaks itself, we keep its score for them.
Only when you first set up, or after a long gap in your data. Otherwise, no: a reset copies another app's settings into ours, and the gap comes back. Keep your Profile thresholds current and ours stays consistent.