An 11-mile run with four 1-minute recoveries showed a training load of 5 and a duration of 4 minutes. The library only counted the steps measured in time, so anything you built in miles or meters barely registered. It also barely registered on your weekly load totals and fitness projections. This release fixes that, along with two other places where the numbers weren’t telling the truth.
Distance steps now count toward TLS and duration
When you save a workout, every distance step now gets an estimated time, based on your team’s average threshold pace or FTP. That time counts toward the workout’s TLS, total duration and intensity. A long run built in miles now looks like a long run.
Estimated values show a * next to the TLS in the workout library. Hover over it to see “Estimated using your team’s average benchmarks.” The number describes your team’s average athlete. Each athlete’s calendar still works out their own estimate from their own benchmarks.
We’ve already updated your existing distance-based workouts, so expect weekly TLS totals and fitness projections to go up if your team trains by distance. Nothing changed in the workouts themselves, only how they’re counted.
A few limits to know about:
- If your team has no benchmarks yet, the estimate uses standard defaults. Once your athletes enter theirs, re-save a workout to refresh its numbers.
- Distance steps with RPE or heart-rate targets can’t be estimated yet.
Team averages now cover FTP and heart rate
Athletes who haven’t entered their own benchmarks are meant to be scaled from the team average. That worked for threshold pace, but not for FTP, threshold heart rate or max heart rate. Those always fell back to a generic default (160 W FTP, for example). They now use your team’s average, as intended, so power and heart-rate targets will change for those athletes. Workouts already sent to Garmin, Coros or Intervals.icu keep the targets they were sent with.
The team average also updates as soon as an athlete saves a benchmark. Before, it could lag by up to three hours.
AI drafts understand real paces
Describe a run the way you’d write it on a whiteboard, such as “threshold 6:05/mile, 4 miles at 6:15 pace, 4 × ¼ mile in 87–88 seconds”. The draft now gets every target exactly right. These prompts used to fail with “The AI produced an invalid workout.”
- Distances stay in your units: 4 mi, not 6437 m.
- If you give paces but no threshold pace, the draft uses the closest training zone, marks that step as assumed, and reminds you to add the threshold pace.
Coaches who build by distance: look at your library after this update. Your long runs and tempo miles finally carry the load they should.