Geofence-related alerts and events

On the web map, unit transitions into or out of a geofence can surface in the tactical log and in unit intelligence copy.

On mobile, entering a restricted zone may trigger a local notification for the operator; behavior depends on location permission and features.geofences.

Each time a unit crosses a geofence border, Sentinel can record the transition as an event in the tactical log and, if the zone is restricted, trigger a notification in the operator's app. That mechanism lets you build concrete operational rules without monitoring the map second by second.

The tactical log receives entries like 'Unit 12 entered South Perimeter' or 'Unit 5 left North Operations Zone'. Those lines are short and self-explanatory if geofences and units are well named (which is why we keep insisting on clear naming). Admins can filter the log by unit, zone, or time range to reconstruct the timeline of events in a later incident.

For the field operator, the alert is local: a system push notification when entering a restricted zone. Latency is typically a few seconds, depending on GPS quality and evaluation intervals. The app can also show a brief overlay on opening, reminding the operator they're inside an active-rule zone.

The most common mistake in adopting geofences is generating too many events: miscalibrated zones that fire entries and exits with each GPS jitter, or too many restricted zones that end up saturating the operator with irrelevant notifications. The cure is periodic review: if a zone generates events nobody acts on, shrink it or convert to operations. Keep restricted zones for situations where alerting the operator really impacts the operation.