How to use geofences to monitor areas, entries and exits
A geofence is a virtual boundary associated with a real zone such as a depot, jobsite or customer location. The platform compares a vehicle's position with that area and records entries, exits or dwell under configured rules, turning GPS coordinates into readable operational events.
- Published
- Updated
Five rules for creating useful geofences
An effective area answers one precise operational question and produces an event someone knows how to handle.
Key takeaways
- Name the area so its place and purpose are clear.
- Decide whether you need entry, exit, dwell or out-of-hours use.
- Draw the boundary around access points and nearby roads.
- Send a notification only to the person who must decide.
- Review early events and adjust the area or rule if it creates noise.
How does a geofence turn a position into an alert?
The system turns the relationship between a position and a geographic rule into an event with a vehicle, area and time.
1. Define the area
An authorised user draws a boundary on the map and gives it an operational meaning: depot, customer site, jobsite, service area or zone to monitor.
2. Choose the rule
The rule defines the events that matter: entry, exit, dwell, time window or combinations that match the process. Available options depend on the project configuration.
3. Compare the position
When the device sends an update, the platform evaluates the relationship between the vehicle and boundary. Frequency, connectivity and positioning quality affect timing.
4. Turn the event into an action
An entry or exit can appear in history, feed a report or trigger a notification. It is useful only if the recipient, priority and expected action have been defined.
Which events can a fleet geofence monitor?
The same area can answer different questions, but not every event needs an immediate notification.
Event, question and use
| Event | Question answered | Appropriate use |
|---|---|---|
| Entry | When did the vehicle arrive? | Arrival history or exception notification |
| Exit | When did it leave the area? | Departure control or unexpected exit |
| Dwell | How long did it remain? | Process analysis, not automatic measurement of human work |
| Out of hours | Does the event fit the expected time window? | Operational review under policy and configuration |
| Recurring pattern | Does the same pattern repeat? | Periodic reporting rather than continuous alerts |
How do geofences differ across depots, jobsites, customers and environmental services?
The technology is the same; the question, tolerance and action change by sector.
Trucks, buses and depots
Entry and exit records help reconstruct vehicle availability and dwell. The platform does not replace driver rostering or service planning.
Construction and jobsites
A jobsite area can reveal arrivals, transfers or exit outside an expected window. It does not physically prevent theft or certify a person's working hours.
Field service and customers
Vehicle dwell at a customer location can support reconstruction of a visit. It does not automatically equal technician working time or contractual acceptance of the service.
Waste collection and field services
Journey history and entry into operational areas can contribute to a service timeline. The record is operational evidence; its value to a customer depends on the contract and process.
How to avoid false alerts and notifications nobody reads
Geofence quality is measured by useful events, noise and completed actions.
Start with a question
“Always alert me” is not an operational rule. “Alert me if a vehicle assigned to the depot leaves during the window when it should be stationary” defines the vehicle, area, time and action.
Test the boundary
Adjacent roads, long entrances and overlapping areas can produce unwanted events. The first real journeys should be used to adjust geometry and tolerance.
Choose the recipient
A safety alert, arrival confirmation and monthly report do not have the same recipient. Sending all three to everyone reduces the chance of action.
Review the rule
If an event never leads to action, move it to a report, change it or remove it. Configuration should follow the process rather than remain unchanged through inertia.
What a geofence does not prove or prevent
A coordinate associated with an area is operational data, not an automatic conclusion about work, responsibility or security.
It is not a physical barrier
A geofence reports a geographic relationship when the system receives data. It does not prevent exit, immobilise the engine or replace physical safeguards and security procedures.
It does not automatically measure a person's work
Vehicle dwell in a location does not prove who was present, which task they performed or for how long. The record must be interpreted with the process and applicable rules.
It has no universal accuracy
Environment, device, connectivity and update frequency affect events. Area size and timing expectations should be tested in the real use case.
Questions to resolve before enabling a geofence
Definition, timing, security, dwell and area size.
What is a fleet geofence?
A geofence is a virtual area drawn on a map. When a monitored vehicle enters, leaves or remains in the area under a configured rule, the system records the event and can issue a notification or add it to an operational report.
Does an entry or exit alert always arrive in real time?
It should not be promised as an absolute. Timing depends on update frequency, device availability, connectivity and rule configuration. Those parameters should be verified for the project and vehicle type.
Does a geofence prevent vehicle theft?
No. It can report movement or an exit against a rule and provide location and context when the device communicates. It is not a physical barrier, does not automatically immobilise the vehicle and does not guarantee recovery.
Can a geofence show how long a vehicle stays at a depot or customer site?
Entry, exit and dwell records associated with the same area can help reconstruct elapsed time. The data must be interpreted in the real process: vehicle dwell does not automatically equal a person's working time or contractual evidence of service.
How large should a geofence be?
It should represent the real area without overlapping nearby roads or sites that would produce unwanted events. There is no universal size: the environment, access points, signal quality and update frequency should be tested on location.
Start with three areas that currently need manual checks
Depot, jobsite or customer: define the operational question and verify with Zenit which events and rules fit the process.
- Alerts with an ownerEvery event needs a recipient, priority and expected action.