Coaches set the zone percentages for the whole team in Team Settings → Team Zones. Each athlete’s own thresholds live on their Benchmarks page, and Smagpie combines the two, so a workout written in zones becomes personal paces, heart rates or watts for every athlete.
The team’s zones
In Team Settings → Team Zones, a coach chooses the zone set for each sport: pace, heart rate and power for Running, Cycling and Swimming, plus a shared heart-rate set for every other sport. You can start from a predefined zone system and preview it. There’s no fixed “Zone 2 = 65–79%” in Smagpie; the team’s settings decide.
Each athlete’s benchmarks
An athlete’s thresholds are on their Benchmarks page:
- Running: threshold pace (you can calculate it from a race time), threshold heart rate and functional threshold power (FTP).
- Cycling: FTP and threshold heart rate.
- Swimming: threshold pace (you can calculate it from a CSS test).
- General: resting heart rate and max heart rate.
Change a value and click Save.
Who can see Benchmarks
- Athletes find Benchmarks in the menu. It needs an Athlete Pass; without one, it isn’t in the menu.
- Coaches open an athlete’s benchmarks from that athlete’s dashboard: in Athletes, click the athlete, then go to their health metrics section. You can also get there from the athlete popup on Coach Hub.
How do I see how an athlete's FTP or threshold pace has changed over time?
- Coach
- Athlete
On the Benchmarks page, tap the history icon beside a benchmark. The dialog opens with the current value, In effect since, Set by, and how far it has moved in the Last 12 months. Below that is every value the benchmark has had, newest first.
Reading the list
- Each entry shows the change from the one before it. Pace changes are in seconds per km or mile (or per 100 m or yd for swimming), in your team’s units, and faster counts as an improvement.
- A chip shows who set each value: the athlete, a coach or a device import. A test date appears when one was entered.
- Values that were already in Smagpie before benchmark history started are shown muted as Carried over.
- A period when the benchmark was cleared appears as Team average. During that time, workouts were scored from your team’s average.
- A benchmark that has never been set shows No history yet.
From Coach Hub
In an athlete’s benchmarks popup on Coach Hub, tap a benchmark that’s set to open its history. It’s read-only there. To correct an entry, open the athlete’s Benchmarks page.
Open the benchmark’s history, tap the pencil on the wrong entry, type the right value and click Save. The entry’s date stays the same, so the fix isn’t treated as a new change and adds no icon to the Fitness chart.
Who can correct
Whoever can set the benchmark can correct it: athletes for themselves, and coaches for athletes on their team. Each correction is recorded with the old and new value.
Correct or change?
- Correct when a value was typed wrong, for example an FTP of 28 instead of 280.
- Change the value on the Benchmarks page and click Save when the athlete really got fitter or slower, for example after a new test. That starts a new entry from today.
Correcting the current value updates the field on the Benchmarks page right away. Your other unsaved edits on the page are kept.
Each amber icon on the Fitness / Fatigue / Form chart, with a faint dashed line, marks a day one of the athlete’s benchmarks changed. Only benchmarks that affect training load are marked: running threshold pace, cycling FTP and threshold heart rate, swimming threshold pace, max heart rate and resting heart rate.
Seeing the change
Hover the day (or tap it on a phone) to see one line per change, for example “Running Threshold Pace 4:05 → 3:58 /km · Coach”. A first value, or one that was cleared, shows Team average on the side with no value of its own. Under the chart, links take you to the history behind each change in the range.
What isn’t marked
- Corrections to a typo. They fix an old value; they don’t change it.
- Values carried over when benchmark history started.
- Changes to your team’s average.
”Load estimated from team average”
When some of the load in the chart’s range was scored with your team’s average, because the athlete had no benchmark set for that sport, a caption under the chart names the sports. Set the athlete’s benchmark to make future workouts personal.
Which benchmarks are used to score a workout synced after a threshold change?
- Coach
- Athlete
Smagpie scores each activity with the benchmarks the athlete had on the day of the workout, not today’s. If an athlete raises their FTP on Friday, a ride from Tuesday that syncs on Saturday is still scored with Tuesday’s FTP.
What this covers
- Activities uploaded as FIT files, and those synced from Garmin, COROS or Intervals.icu as FIT files.
- Weight, for rides scored without a power meter: the latest weigh-in on or before the ride.
If the athlete had no benchmark of their own on that day, Smagpie uses your team’s current average, then a default.
What it doesn’t change
Load that was already scored stays as it is. Loads copied directly from Intervals.icu, and Session Tracker and manual loads, aren’t affected.
The athlete’s completed run, ride or swim went well off the workout you assigned. A red ↑ means over plan and a blue ↓ means under plan, on load (how much work the session was) or intensity (how hard it was). Athletes who did what you planned get no arrow.
Seeing the numbers
On a computer, hover over the arrow. You’ll see something like “Load 94 / plan 70 (+34%)”, and an intensity line too if that was also off. On a phone, the Coach Hub shows one arrow, for whichever miss is bigger compared with its tolerance. Tap it to see both numbers.
What counts
- Only sessions linked to a workout you assigned. A run nobody assigned won’t show an arrow.
- Runs, rides and swims. Strength sessions are ignored.
- Load is the day’s total across the athlete’s assigned sessions. Intensity is the hardest single session.
How far off is “too far”
In Team Settings → Compliance:
- Load uses your team’s Yellow tolerance (%) under Endurance Compliance (20% by default). The arrow appears only beyond it.
- Intensity has its own Intensity tolerance (%) (10% by default). One training zone is roughly 10%, so the default flags a session run about a zone too hot or too easy.
For a workout written in distance (“8 miles easy”), the plan is worked out at the athlete’s own pace: the threshold that scored the run, or their current benchmarks if the run didn’t record one. A fast runner who ran the full distance isn’t flagged as under plan just because they finished sooner. Workouts written in time, and workouts logged with Complete as planned, use the workout’s own planned load. If an athlete’s thresholds are out of date, their arrows will be too.
Looking back at an earlier day
Pick any day other than today on the Coach Hub and every completed row says how it went against plan, even without an arrow:
- A grey line such as TLS −7% EI +5% when the session was within your tolerances, the arrows when it wasn’t, or no plan for a workout nobody assigned. Rest days and missed workouts stay blank.
- On a day with more than one sport, each run, ride or swim gets its own line, with the sport’s icon. Strength sessions are left out.
- A blue asterisk means the numbers were scored on a borrowed threshold (the team average or a default), because the athlete had no benchmark of their own for that sport yet. Hover it, or tap it on a phone, to see which.
- The benchmark column header reads [benchmark] · now: it shows today’s value, not the one from that day. Open the athlete’s benchmarks from that day to see a since then box with the threshold that scored the session, the value now and the change.
Today’s Coach Hub works as before.