Fleet Policy Threshold Wizard
Pick sensible alert thresholds for speeding, idling, harsh events, and after-hours rules—without drowning your team in alerts. Choose a tier (Conservative, Balanced, Strict) and export a policy summary to CSV.
Inputs
| Category | Threshold | Trigger | Action |
|---|
Avoid alert fatigue (the #1 policy mistake)
If your inbox is full of minor alerts, real safety issues get ignored. The best programs use a tiered approach: real-time alerts only for critical safety, and weekly coaching summaries for everything else.
- Realtime alerts: only the events that could cause a crash today.
- Weekly coaching: patterns (speeding streaks, idling habits, harsh event clusters).
- Recognition: reward improvement to keep buy-in.
Policy Threshold FAQ
How often should I change thresholds?
Not daily. Set thresholds, coach for 2–4 weeks, then adjust. Frequent changes confuse drivers and managers.
Should speeding be “over limit” or “absolute speed”?
Over-limit is best when you have posted speed limits. If not, use an absolute threshold (e.g., 80 mph) as a fallback.
What’s a good idling threshold?
Many fleets use 5–10 minutes. Tighten if you have strong capacity and you’re actively coaching.