Acting on a smart alert
Alerts exist to flag the athlete who needs you days before it becomes an injury. Here is what triggers them, how they reach you, and how to respond without overreacting.
Smart alerts watch every athlete's metrics against your team thresholds and surface the ones drifting in the wrong direction. The point is early warning: catch the decline on Tuesday so you can ease the load before Saturday.
What triggers an alert
Out of the box, the engine watches a range of conditions. The main ones, with their default lines:
| Signal | Monitor (watch) | Protect (act) |
|---|---|---|
| Low recovery | Below 67 | Below 34 |
| HRV drop vs baseline | 20 percent below | 30 percent below |
| High strain | 14 and above | 16 and above with low recovery |
| Sleep debt | About 2 hours | Sustained over 3 days |
| RHR above baseline | 12 percent above | - |
| Stale sync | No data for 36 hours | - |
It also watches slower-burning patterns: HRV staying suppressed for two days or more, sleep debt running chronic across three days, and any athlete whose recovery sits about 15 percent below the team average.
How alerts reach you
Alerts surface two ways. They appear as flags directly on the roster, against the athletes they concern, and they are bundled into an email digest so you do not have to be staring at the dashboard to catch them. Email alerts are on by default and each coach can switch their own off.
How to respond
- Triage Protect (red) flags first; those are today's decisions.
- Open the athlete and read the trend, not the single day. One bad night is not a reason to change a plan.
- Talk to the athlete. The data tells you where to look; they tell you why.
- Adjust the load, not the athlete. Ease volume or intensity, protect sleep, and watch the flag clear over the next few days.