Geofencing
Geofencing is a virtual boundary drawn around a real-world location, a yard, customer site, or service area, that a GPS tracking platform monitors continuously, automatically triggering an alert the moment a vehicle enters or exits it. Fleets use it for unauthorized-use alerts, automated arrival/departure timestamps, and proof of service without a driver logging anything manually.
Rajat Gupta runs FleetOpsClub and writes its software reviews, comparisons and pricing pages. Every tool on the site is assessed against the vendor's own published documentation and pricing, and each pricing figure carries the date it was last verified so readers can judge how current it is. Where a vendor does not publish a price, the page says so rather than estimating one.
Last reviewed Oct 15, 2026Compare gps fleet tracking platforms on verified pricing and deployment detail before you shortlist: every gps fleet tracking platform we have reviewed.
How a geofence behaves in practice
That is why a fence drawn tight to a building generates false exits. A vehicle parked near the edge reports a fix that scatters a few dozen feet either side of its true position, and each scatter across the line looks like a departure. Two settings fix it: a buffer wider than the expected position error, and a dwell threshold that requires the vehicle to stay inside or outside for a set period before the event counts.
| Setting | What it controls | Typical failure when it is wrong |
|---|---|---|
| Shape | Circle by radius, or polygon traced to the site | A circle over an irregular depot includes the road outside it |
| Buffer | How far beyond the true boundary still counts as inside | Tight buffers turn GPS scatter into phantom entries and exits |
| Dwell threshold | How long a vehicle must be inside before the event fires | No threshold means a pass-by on an adjacent road registers as an arrival |
| Reporting interval | How often the device sends a position | A long interval stamps arrival minutes after it happened |
Alert fatigue is the other common failure. A fleet that puts a fence on every customer site and alerts on every crossing generates thousands of notifications a week, and dispatchers stop reading them. The fences worth alerting on are the exceptions: movement outside working hours, entry to a restricted area, or a vehicle leaving a yard it was not scheduled to leave.
Where geofencing earns its keep
It is also the cheapest unauthorised-use control a fleet has. A fence around the yard with an out-of-hours schedule catches weekend use of a company vehicle without anyone watching a map. Before rolling that out, tell drivers it exists and what it does, because a tracking programme that drivers discover by accident is the one that fails.
- Draw polygons for irregular sites rather than forcing a radius over them
- Set the buffer wider than the position error you observe in the yard, not the vendor's accuracy claim
- Use a dwell threshold so traffic on adjacent roads does not register as arrivals
- Alert on exceptions only, and report on the rest
- Confirm the platform stores the crossing event with its own timestamp, so a billing dispute can be reconstructed months later
- Tell drivers which fences exist and what triggers an alert before the first one fires
Terms like this one decide what a vendor is really quoting for, so it is worth checking the fleet software profiles that document how each platform handles it, and modelling the cost with a fleet cost calculator before a vendor call.
Geofencing FAQ
Quick answers to the questions buyers usually ask once the category, software, or rollout details start getting more specific.
Four things, in rough order of how much fleets rely on them: automated arrival and departure timestamps for billing and proof of service, unauthorised-use alerts outside working hours, restricted-area warnings, and utilisation reporting based on time spent inside yards or customer sites.
Yes. A geofence only fires because the device reports position continuously. The FMCSA ELD specification sets the resolution: position must be accurate to within half a mile, which at the required reporting precision works out to roughly a one-mile radius during commercial operation. The one carve-out is personal conveyance, where reporting precision drops to a single decimal place, about a ten-mile radius (49 CFR Part 395 Appendix A section 4.3.1.6, and 395.26(c)(2)).
Three. GPS scatter around a tight boundary produces phantom entries and exits. Fences on every site produce more alerts than anyone reads. And the arrival timestamp is only as precise as the reporting interval, so a 60-second plan can stamp an arrival several hundred yards late.
Tracking company-owned vehicles during work is generally lawful in the United States, and the ELD rule already requires position reporting on most commercial vehicles. Notice and consent requirements vary by state, and tracking a personal vehicle used for work is a different question. Check the rules in the states you operate in before rolling out a programme.
On a commercial platform, yes. Drawing a fence, setting a buffer and choosing which events alert are normally self-service in the admin interface. What is not self-service is the reporting interval, which is usually tied to the plan you bought and sets the precision ceiling on every fence you draw.
The boundary itself is exact; the crossing event is not. Accuracy is set by the device's position error plus the gap between reports. A vehicle moving at 30 mph covers about 440 feet between 10-second fixes, so treat the event time as approximate unless the reporting interval is short.