Geofencing
Two Types of Zones. One System That Knows the Difference.
Fleet Command Center splits geofences into primary business zones you manage and secondary dispatch zones it creates for you. Both are polygon-precise, schedule-aware, and wired straight into your alerts and dispatch.
The Two Types of Geofences
Most platforms treat every zone the same. FCC doesn't. Primary and secondary geofences are built differently, do different jobs, and are managed separately.
Persistent, named zones around the places that matter to you. Draw them as custom polygons in any shape or size.
- Shops & Yards
- Know the moment a vehicle leaves or returns
- Customer Sites
- Track arrival, departure, and dwell time at every job
- Fuel Stations
- Confirm authorized fill-ups and flag off-route stops
- Restricted Areas
- Set no-go zones and get an instant alert if a vehicle enters
- Service Areas
- Define your coverage area and see who is working inside it
Built automatically when you create a route. Every stop gets a circular geofence with a configurable radius, centered on the stop.
You don't manage these. They give dispatch precise arrival detection at every stop, with no button-pressing from the driver.
Deduplication
When two routes share a stop within a configurable proximity threshold, the system reuses the existing zone instead of duplicating it. Your map stays clean.
Lifecycle
Tagged as route-generated and scoped to their routes, so they never clutter your primary zone view.
Drawing Zones
Geofences are stored as GeoJSON polygons, a standard format that powers fast, accurate spatial queries on MongoDB's 2dsphere index.
When you draw a zone, every coordinate is validated and processed automatically.
- Coordinate validation
- Latitude −90 to 90, longitude −180 to 180
- Ring closure
- First and last point must match (GeoJSON requirement)
- Centroid calculation
- Computed and stored for map label placement
- Area computation
- Approximate area in acres using a standard geometric formula
Each zone stores metadata that powers analytics and map rendering.
- Vertex count
- Number of boundary points
- Area in acres
- For reporting and coverage analysis
- Centroid
- Center point for proximity queries and labels
Entry & Exit Detection
Every GPS position runs geofence detection automatically in the background. It is non-blocking, so it never slows down your live tracking.
- 01Load the vehicle's last known zone state
- 02Run a spatial query: which active zones contain the vehicle right now?
- 03Compare the current zones to the previous ones
- 04Newly inside a zone: Entry event
- 05No longer inside a zone: Exit event
- 06Update the vehicle's zone state in Redis (24-hour TTL)
When a vehicle hovers near a boundary, per-zone per-vehicle cooldown locks stop alert floods. After an entry alert fires, no repeat fires for that vehicle and zone until the cooldown expires.
- Default cooldown
- 5 minutes (configurable per zone)
- Maximum cooldown
- 24 hours
- Scope
- Per-geofence, per-vehicle, with independent locks
- Applies to
- Both entry and exit alerts separately
Alert Configuration
Set a zone to push on entry but only web-alert on exit, or email your manager on entry and stay quiet on exit. Every combination is supported.
- Entry alerts
- On / off per zone
- Exit alerts
- On / off per zone
- Cooldown seconds
- How long to suppress repeated alerts
- Channels
- Web dashboard (Socket.IO), mobile push (FCM), email (SES)
Not every zone matters around the clock. Outside the active window the event is still recorded, but no alert fires, which kills off-hours false positives.
- Enabled / Disabled
- Toggle schedule enforcement (off = 24/7 alerts)
- Timezone
- America/Chicago, America/New_York, US/Mountain, etc.
- Active days
- Any combination of days (e.g., weekdays only)
- Time window
- e.g., 06:00 to 22:00
Speed Limits Inside Zones
Any zone can carry its own speed limit. Go over it inside the boundary and a zone-specific violation alert fires, separate from your general speeding alerts. Zone, vehicle, and fleet speed limits all work at once and fire independently.
Yard speed limit
5 mph inside your shop or yard
School zone flag
Reduced limit near a customer next to a school
Job site
Temporary reduced limit inside an active work site
Vehicle & Group Scoping
Control exactly which vehicles trigger a zone and who gets notified. One zone can serve different crews with different rules.
Scoped by Vehicle Group
Tie a zone to specific vehicle groups and only those vehicles trigger entry and exit events. A zone set for your reefer trucks stays quiet when a dry van rolls through the same spot.
Scoped by User Group
Filter alert recipients by user group, so only the right people get notified. Handy when not every manager needs to see every zone event.
Fleet-Wide Default
Leave the scope empty and the zone covers all vehicles and notifies everyone relevant. The usual choice for company-wide zones like your main yard.
Real-Time Zone Analytics
Live vehicle counts, trigger history, and dwell time, all built on the geofence event stream.
Who's Inside Right Now
Every zone shows a live vehicle count, recalculated on each page load from current vehicle locations. No stale numbers.
Dwell Time Analysis
Paired entry and exit timestamps give you dwell time for any vehicle at any zone: how long did this truck sit at the customer? Which sites eat the most time?
Total trigger count and the latest trigger time stay visible in your zone list. The full record set is available through the trigger history API.
- Vehicle name & ID
- Identifies which vehicle crossed the boundary
- Event type
- Entry or exit
- Timestamp
- Exact time of crossing
- GPS coordinate
- Exact position at the moment of crossing
- Rolling record
- Last 50 entry/exit events per geofence
Driver Map Visibility
Drivers see the zones that matter to them as overlays on their navigation map, with a lightweight payload so they know what they're approaching and the rules inside.
- Zone name
- Displayed on driver navigation map
- Boundary
- Polygon outline rendered as overlay
- Color
- Zone-specific color coding
- Alert config
- Entry/exit alert settings visible to driver
- Speed limit
- Zone-specific speed limit shown on approach
- Visible to drivers
- Toggle to hide the boundary from drivers while still alerting on crossing
- Inactive status
- Alerts suppressed, zone remains visible on map
- Archived status
- Zone hidden entirely from all views
Geofence & Dispatch Integration
The two systems are connected. Create a route and geofencing handles stop arrival detection for you, so dispatch analytics come from GPS, not driver button-presses.
- 01Secondary geofences are generated around every stop
- 02Each stop's geofence ID is saved in the route record
- 03When the route goes active, stop locations are cached in Redis for fast proximity checks
- 04Arrival is detected automatically, so the driver never has to confirm it manually
So your dispatch numbers, on-time arrivals, stop dwell, and departure times, all come from GPS, not driver button-presses.
Zone Lifecycle Management
Use inactive when a zone is temporarily paused. Use archived when a location is permanently closed or relocated.
Bulk Operations
Manage many zones at once with bulk status changes, delete, and export. Handy for seasonal moves or reworking a batch of sites.
Your zones should work as hard as your fleet does.
Set up your first geofence in minutes.