Who ran it too hot?
Every coach knows the athlete who turns an easy recovery day into a tempo run, and the one who quietly cuts the hard session short. Until now, the Coach Hub told you who finished the workout, but not how they ran it.
Now a small arrow appears beside an athlete’s Form on the Coach Hub when a completed run, ride or swim went well off plan:
- Red ↑ means over plan: more load, or harder intensity, than you prescribed.
- Blue ↓ means under plan: too short, or too easy.
Everyone who did what was planned gets no arrow, so the Hub stays quiet and the arrows stand out.
On a computer, hover over the arrow to see the numbers, for example “Load 94 / plan 70 (+34%)”. On your phone the Hub shows one arrow (the bigger miss) to save space, and a tap shows both.
What counts
Only sessions linked to a workout you assigned count, so a shakeout run or an extra spin nobody assigned won’t set off an arrow. Strength sessions are ignored.
You decide how far off is too far
Load uses the compliance tolerances your team already has (by default, an arrow appears beyond ±20%).
Intensity gets its own setting, because running one zone too hot is a real miss even when the total load looks fine. Set it in Team Settings → Compliance → Intensity tolerance. The default is 10%.
80/20 libraries, ready on day one
New teams now start with the 80/20 Endurance running, cycling and swimming libraries already in their workout library. That’s hundreds of structured workouts you can schedule in your first week, with no searching and no subscribing.
Don’t coach swimmers? Hide that library in Workout Library. Smagpie now asks you to confirm before hiding, and hiding a library no longer touches workouts you’ve already scheduled or added to a training plan. They stay in your plan, still sync to watches, and still open in the Session Tracker.
Plus
- Team Settings → Compliance is now translated into every language Smagpie supports.
Open the Coach Hub after your next hard workout and see who lit it up. If the arrows show up too often (or not enough) for your team, adjust the tolerance and tell us what worked in Discord.