How speed alerts work
Each driver's threshold is set per-member — 80 mph for the new driver, perhaps nothing for the adults. While a trip is in progress, the phone's GPS speed is checked continuously on-device; the instant it crosses the line, subscribed Circle members get a notification with the speed, road and time, and the event is pinned to the trip in driving reports.
Sustained-speed logic filters noise: a two-second blip while overtaking reads differently from three minutes at 90, and you can configure which one you want to hear about.
Choosing a threshold that means something
A good threshold is one that should basically never fire. Set it at the speed your family agreed is genuinely out of bounds — 80 or 85 mph in most of the US — not five over the limit, or you'll drown in pings and mute the feature by Friday. Silence becomes the good news; an alert becomes a real conversation.
Some families run a second, lower 'night threshold' for the first year of solo driving. Both thresholds, like everything here, are visible to the driver.
The conversation that makes it work
Spring speed alerts on a teen and you've installed a tripwire; agree on them in advance and you've set a boundary. The script that works: the threshold is part of the keys deal, the teen knows the number, and an alert means we talk — not we punish from orbit. Teens accept clear, known limits far more readily than ambient suspicion.
And alerts go both ways if you let them. More than one teenager has gleefully forwarded dad his own 88-mph notification. Families that allow that symmetry report the whole system feels fair — because it is.
What speed alerts are not
They're not a speedometer audit. GPS speed is accurate to within a couple of mph in good conditions but can blip near tunnels and tall buildings — which is why sustained-speed filtering exists, and why an alert is the start of a conversation rather than a verdict. They're also no substitute for the slow work of building judgment; they're the guardrail while it builds.
Where the threshold earns its keep
- The first solo highway year. One number, agreed at the kitchen table, standing guard on every on-ramp.
- The borrowed car. Alerts follow the phone, not the vehicle — a friend's GTI changes nothing.
- The long night drive home from college. Silence from 10 PM to 2 AM is four hours of good news.
- The lead foot in denial. Sometimes the new driver isn't the problem; the data is cheerfully impartial.
- Road-trip relay driving. Multiple drivers, one threshold each, zero backseat speed-commentary required.
Stronger together: pairings worth enabling
No FamilyTracking feature lives alone — this one gets noticeably better next to the right neighbors:
- Driving safety reports. Every speed event pins itself to the trip in the weekly report, so the moment and the pattern stay connected.
- Crash detection. Same Premium bundle, same trip engine — the threshold for habits, the detector for the day they fail.
- Scheduled alerts. A night threshold plus a 'home by 11' rule is the complete new-driver curfew stack, both visible to the driver.
The bottom line
A speed alert is a boundary, and boundaries work when they're few, known and meaningful. One agreed threshold — high enough that crossing it is genuinely out of bounds, visible to the driver, attached to a conversation rather than a punishment — does more for a new driver's habits than continuous oversight ever could, precisely because silence remains the default. Resist the urge to set it five over the limit; resist harder the urge to hide it. Set the number together at the kitchen table and let the alert be the rare exception that proves the agreement is real. One last tip from families a year in: when the threshold hasn't fired all semester, say so out loud — the silence was earned, and naming it is how the agreement keeps paying both sides.