Geofencing

Geofencing creates events when vehicles enter or leave virtual zones. Learn the workflow, transport use cases and limitations.

Editorial and specialist review: Max Valjan · Last updated: August 18, 2026

TMS & dispatch

Geofencing places a virtual zone around a physical location such as a depot, collection address or delivery site. When a vehicle enters or leaves, a system can update a status, save a timestamp or send a notification.

How a geofence works

The location is defined as a circle or polygon. A telematics source sends current positions, which are compared with the boundary. A crossing creates an event that the TMS assigns to the right vehicle, order and stop.

Example: automatic arrival

A 250-metre zone surrounds a factory. Vehicle 12 enters at 08:53, so the stop changes to “arrived” and dispatch receives an update. It leaves at 09:17, giving a 24-minute dwell time. A signature or photo is still needed if the physical handover must be proved.

Useful applications

  • automatic arrival and departure statuses
  • updating an ETA after a stop
  • alerts on depot or restricted-area entry
  • analysis of recurring dwell time
  • a customer notification shortly before delivery

Zones that are too small may flicker because of GPS variation; zones that are too large report arrival too early. Closely spaced docks, radio gaps and multi-storey sites also make matching harder. Operators should test zone sizes with real trips.

Geofencing automates status events but does not replace review by dispatch or a proper proof of delivery. Maxmove links events with the relevant route so their operational meaning remains visible.

WorkflowEvent template

Entry, dwell and exit

A 250-metre example shows what a zone can actually establish.

  1. Entry

    08:53

    Status “arrived”

  2. Dwell

    24 minutes

    Time inside the zone

  3. Exit

    09:17

    not proof of handover

Original Maxmove example data; radius and event rules must be adapted to the real site.

Frequently asked questions