Monitoring by exception
Arrival notifications tell you when things happen; scheduled alerts tell you when they don't. That inversion is the calmest form of family awareness there is: instead of receiving — and mentally processing — every routine arrival, you define what 'fine' looks like and hear about deviations only.
A parent running 'home by 10 on school nights' as a rule checks nothing, receives nothing, and worries about nothing for the 95% of nights the rule passes silently. The alert exists for the other 5% — and arrives at 10:00:01, not whenever someone happens to look.
The rules you can build
Rules combine a person, a condition and a time: at [time], if [member] is / is not at [place], alert [recipients]. The greatest hits: not-home-by curfews, didn't-arrive-at-school by 8:30, didn't-leave-for-work by 9 (the oversleep detector), and grandma's missed morning check-in.
Each rule carries its own weekday schedule — school-night curfews that ignore Saturdays — and its own recipients. When a rule fires, the alert includes the member's current or last known position, so the next step is informed, not frantic.
Rules are visible, like everything else
A curfew rule about a teen is visible to that teen: what the rule is, when it checks, who gets told. That's not a concession — it's the mechanism. A known rule shapes behavior at 9:40 ('I should head back'); a secret tripwire just generates conflict at 10:05.
Many families let teens see the rule pass, too — a quiet 'made it' on their own phone at 10:00 builds the autonomy the curfew is scaffolding toward.
Designing rules that age well
Good rules are few, meaningful and renegotiated. Three or four standing rules cover most households; twenty creates noise and resentment. Revisit them each school year — the 10 PM rule that fit a 14-year-old should loosen by 16, visibly, as trust compounds. The endpoint of a well-run rule system is its own retirement, one graduated alert at a time.
The standing rules families run
- The school-night curfew. 'Not home by 10' — the flagship rule, silent 29 nights out of 30.
- The morning arrival. 'Not at school by 8:30' catches the missed bus while it's still fixable.
- Grandma's quiet morning. A missed 9 AM check-in alerts the siblings rota — hours before anyone would have called.
- The oversleep detector. 'Hasn't left home by 9 on workdays' — self-applied by more adults than will admit it.
- The late-shift bookend. 'Not home by 12:30 after closing shift' lets the waiting parent actually sleep until then.
Stronger together: pairings worth enabling
No FamilyTracking feature lives alone — this one gets noticeably better next to the right neighbors:
- Geofencing & place alerts. Rules check against saved places — 'home', 'school', 'work' — so good geofences are the vocabulary your rules speak.
- Check-in requests. A fired rule's quick actions include requesting a check-in — the gentlest possible follow-up to 'not home yet'.
- Battery monitoring. When a rule fires against a dead phone, the earlier battery alerts supply the explanation before worry fills the gap.
The bottom line
Scheduled alerts are the graduate level of family awareness: you stop consuming information and start defining exceptions. Three good rules — the school-night curfew, the morning arrival, the grandparent's check-in — cover a household's genuine worries while generating near-zero notifications, because the rules pass silently almost every time. Keep them few, keep them visible to the people they're about, and renegotiate them yearly as trust compounds. The endpoint of a well-run rule is its own retirement; until then, 10:00 PM checks itself so you don't have to. Write the first rule tonight — the curfew one — and notice next week that you checked the map less. That's the feature working: not more information, but better silence.