Skip to main content

CONFIGURATION - Geofencing

Geofencing auto-detects vehicle arrivals/departures via virtual boundaries, improving ETA accuracy, stop updates & reducing manual input.

Arynne Hargreaves avatar
Written by Arynne Hargreaves
Updated over a month ago

šŸŽ„ Click below to watch our video on Geofencing.

What is Geofencing?

Geofencing is a feature that automatically detects when vehicles enter or exit defined geographical areas around locations.⁠⁠ It creates virtual boundaries (typically circular areas with customisable radius) around stop locations to provide more accurate arrival and departure timestamps without relying solely on driver input.

Benefits of Geofencing

  • More reliable stop updates

  • Improve accuracy of stop arrival & departure by using autocomplete

  • Improved ETA calculations

  • Less manual updates

  • Fewer calls between driver / office to update on arrivals

How does Qargo use Geofencing?

  • Geofences trigger ā€œArrived at locationā€ and ā€œDeparted at locationā€.

  • Geofences are defined by a circle radius around the location

    • This is defined on the tenant and on the location.

  • The stop is completed when the geofence associated to the location is triggered.

  • Once the stop is completed (green) Qargo logs the events and the times are recorded

ā€¼ļø Autocompleting stops requires a telematics system

Configuration

On the tenant level the following values can be configured for geofencing

  • Enable geofencing for resources: this makes it possible to define which types of resources should have geofencing enabled or disabled.

  • Update stop times based on geofence: Automatic completion of the stop once the enabled resource 'triggers' the geofence radius.

  • Default geofence location radius (meter): this defines how large the geofencing area should be by default. It is possible to override this on location level as well.

  • Locations - a radius can be defined that will override the radius defined on tenant level.

  • Click 'Customise' button to enable column in the Stops view

View Geofence times in the STOPS VIEW

Autocompleting stops

  • Trip must be completely dispatched to Driver

  • Automatically complete arrival and departure stops based on geofenced areas

  • Mobile app is only supported when used along with a Telematics system

  • Previous stop must be completed prior to the autocomplete stop

    • If previous stop was not successfully completed, geofence times still captured, but stop is not completed.

  • If autocomplete geofencing is used to depart stop, stop is marked complete

    • In mobile app, question path will not be show to the driver automatically

    • Driver can still update the information for the completed stop

Arrival at stop

  • Driver enters geofence area arrival is automatically completed

    • If using mobile app, the 'Arrive' stop is completed

    • Date / Time stamp for arrival is logged

    • If no arrival detected from geofence, driver must manually arrive to complete task

Departure from stop

  • Depart from stop completed when leaving location and passing through geofence

    • If using mobile app, driver will typically already complete the 'Depart' stop, in which case geofence is retained as 'backup'.

Limitations

ā€¼ļø Geofence detection based on tracking data from mobile app ONLY is not supported.

  • The autocomplete will only work if the previous stops were successfully completed.

    • If the previous stop was not successfully completed, the geofencing times will still be captured but the the arrival/departure will not be autocompleted.

  • If the autocomplete geofencing is used for departing from a stop, the stop will be marked as completed.

    • If using the mobile app, question paths will not be shown to the driver

    • Driver can manually go back to the completed stop to fill in the question paths.

Did this answer your question?