Back to Blog
Product Updates
15 min read

Geofence Alert Setup and Response: TeamMap Configuration Guide

Configure TeamMap geofences for perimeter monitoring, restricted areas, and patrol zones. Covers alert thresholds, notification setup, and response procedures.

Geofence Alert Setup and Response: TeamMap Configuration Guide

Geofences create virtual boundaries that trigger alerts when guards enter or exit designated areas. TeamMap's geofencing enables perimeter monitoring, restricted area alerts, and patrol zone tracking— all without requiring guards to manually check in.

TeamMap geofences automatically trigger alerts when team members cross virtual boundaries. This guide covers setup, alert configuration, and operational use cases for effective geofence deployment.

Geofencing Use Cases

Perimeter Monitoring

  • Alert when guard exits designated patrol area
  • Detect unauthorized entry to restricted zones
  • Monitor construction site boundaries
  • Track warehouse/distribution center perimeters

Patrol Zone Verification

  • Confirm guards entered each required zone
  • Track time spent in specific areas
  • Verify parking lot coverage
  • Monitor building-specific assignments

Safety Applications

  • Hazardous area entry alerts
  • Lone worker zone monitoring
  • Emergency evacuation verification
  • Site arrival/departure logging

Creating Geofences in TeamMap

Step 1: Access the Map Editor

  1. Open TeamMap admin dashboard
  2. Navigate to Shapes or Geofences section
  3. Click "Create New Geofence"

Step 2: Draw the Boundary

TeamMap supports multiple geofence shapes:

ShapeBest ForDrawing Method
CircleSingle point radiusClick center, drag radius
RectangleSquare/rectangular areasClick two corners
PolygonIrregular boundariesClick each vertex point

Tip: For complex property boundaries, use the polygon tool and trace the actual property line. Include a small buffer (10-20 feet) to account for GPS accuracy.

Step 3: Configure Geofence Settings

SettingDescriptionRecommendation
NameDescriptive identifier"Building A Perimeter"
Trigger TypeEnter, Exit, or BothDepends on use case
Alert RecipientsWho gets notifiedSupervisors, dispatch
Dwell TimeMinimum time before alert1-5 minutes to reduce false alerts
Active HoursWhen geofence is monitoredMatch shift schedules
MembersWho is tracked by this geofenceRelevant guards/teams

Alert Configuration

Alert Types

Alert TypeUse CasePriority
Entry AlertRestricted area accessHigh
Exit AlertGuard left patrol zoneMedium
Dwell AlertGuard stationary too long in areaLow-Medium
Absence AlertGuard hasn't visited zone in X timeMedium

Notification Channels

  • In-app notification: Always recommended
  • Push notification: For supervisors on mobile
  • Email: For non-urgent logging
  • SMS: For critical alerts
  • Voice channel announcement: For immediate response

Reducing False Alerts

Common Problem: Too many alerts lead to alert fatigue. Staff stop paying attention when every alert is a false positive.

Strategies for reducing false alerts:

  • Add dwell time: Require 2-5 minutes in/out of zone before alerting
  • Increase boundary buffer: Account for GPS drift at edges
  • Set active hours: Only monitor during relevant times
  • Exclude authorized crossings: If guards regularly pass through
  • Use appropriate trigger type: Don't alert on both entry and exit if only one matters

Geofence Response Procedures

Exit Alert Response

When a guard exits their assigned zone:

  1. Check if exit was authorized (break, incident response)
  2. Contact guard via PTT or call
  3. Document reason for exit
  4. Dispatch replacement coverage if needed
  5. Update geofence logs with explanation

Entry Alert Response (Restricted Area)

  1. Identify who triggered the alert
  2. Verify if entry is authorized
  3. If unauthorized:
    • Dispatch security response
    • Document the incident
    • Follow intrusion response procedures
  4. If authorized but unexpected:
    • Log the entry
    • Update authorization list if needed

Absence Alert Response

  1. Check guard's last known location
  2. Attempt to contact guard
  3. If no response:
    • Dispatch supervisor or backup
    • Consider welfare check
    • Document the gap in coverage
  4. Update patrol schedule if coverage issue

Best Practices for Geofence Design

Sizing Geofences

Use CaseRecommended SizeNotes
Checkpoint verification20-30 meter radiusAccount for GPS accuracy
Building coverageActual footprint + 10m bufferInclude entrances
Patrol zoneFull assigned areaDon't leave gaps
Perimeter alertProperty line + 20m bufferCatch edge drift

Layered Geofences

Create multiple overlapping geofences for sophisticated monitoring:

  • Outer boundary: Site perimeter—exit triggers response
  • Inner zones: Building areas—track patrol completion
  • Restricted areas: Sensitive locations—entry triggers alert

Common Mistakes

  • Geofence too small—constant false alerts from GPS drift
  • No dwell time—alerts on momentary boundary crosses
  • Monitoring 24/7—alerts during off-hours create noise
  • Too many recipients—everyone ignores alerts
  • No response procedure—alerts without action

Key Takeaways

  • Geofences enable automatic location-based monitoring
  • Size boundaries to account for GPS accuracy
  • Use dwell time to reduce false alerts
  • Define clear response procedures for each alert type
  • Layer geofences for comprehensive site coverage

Share this article

TeamMap

Written by

TeamMap

Team

TeamMap builds modern workforce management tools for security teams, helping companies track, communicate, and coordinate their field operations.

Continue Reading