The short version

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.

1. Different thresholds

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.

2. Different ways to measure a run

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.

3. Missing or doubled sessions

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.

4. A different starting point

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.

How we score your sessions

Every session is scored by the most reliable signal it has, against the thresholds on your Profile. Your brief says which one it used.

SportScored by, in order
SwimPace against your threshold pace (CSS); heart rate without one.
BikePower against your FTP; heart rate on rides without a power meter.
RunRun 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.

Where ours can be off too

Check yours in two minutes

  1. Pick one recent session that shows up in both apps.
  2. Compare its stress score: TSS in TrainingPeaks, Load in intervals.icu, and the stress in your brief.
  3. If they're far apart, compare the thresholds behind them: in TrainingPeaks, Settings → Zones; in intervals.icu, Settings → Sport Settings; with us, your Profile.
  4. Fix whichever one is out of date. Usually that settles it.

Should I reset ours to match?

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.

Check your thresholds →

Numbers still don't add up?

Send us the session and both scores, and we'll look.

Contact Us →