Fleet Geofencing UK: How to Set Up Depot, Job-Site and Unauthorised-Use Alerts
geofencingfleet trackingfleet alertsdepotsjob sitesvehicle monitoring

Fleet Geofencing UK: How to Set Up Depot, Job-Site and Unauthorised-Use Alerts

MMobile Track Pro Editorial Team
2026-11-20
7 min read

Learn how to plan UK fleet geofences, reduce false alerts and review depot, job-site and unauthorised-use rules.

Well-designed geofences help a fleet team understand when vehicles arrive at depots, reach job sites or leave approved areas, without turning every GPS fluctuation into an urgent alert. This guide explains how to plan fleet geofencing in the UK, choose sensible boundaries and dwell times, assign notifications, test the setup and review it as your operation changes.

Overview

A geofence is a virtual boundary drawn around a real-world location in fleet tracking software. When a vehicle enters, leaves or remains within that boundary, the system can record the event or send an alert. Common uses include monitoring depot movements, confirming attendance at customer sites, identifying possible unauthorised use and supporting lone-worker procedures.

Geofencing is most useful when each alert has a clear operational purpose. An arrival alert might help a coordinator prepare for a delivery, while a departure alert could prompt a check that a vehicle has left a restricted area. By contrast, creating a notification for every movement across a large number of overlapping zones can quickly produce noise. The objective is not to track every possible event; it is to surface events that require a decision.

Features vary between fleet tracking software platforms. Some offer circular zones only, while others support custom polygons, schedules, vehicle groups, dwell-time rules, escalation chains or links to other telematics events. Before planning your zones, confirm what your chosen vehicle tracking system actually supports, how often it receives location updates and whether alerts depend on a mobile data connection.

What to track

Start with locations that have a defined business outcome. A short list of useful geofence types is easier to manage than a map covered with zones that nobody reviews.

Geofence typeRecommended boundaryUseful triggersDwell-time approachTypical recipientCommon failure point
Depot or officeDraw around the site and its vehicle entrance, allowing for GPS variation and nearby roads.Arrival, departure, out-of-hours movementUse a short confirmation period to avoid alerts when a vehicle passes the edge.Fleet coordinator or depot managerThe boundary catches a public road, neighbouring premises or a separate parking area.
Customer job siteUse the actual work area where possible rather than the whole postcode or street.Arrival and departureAllow enough time for a vehicle to enter, park and begin work before treating the event as meaningful.Operations team or assigned plannerAddresses cover large sites, shared estates or multiple entrances.
Restricted or unauthorised-use areaKeep the zone tightly linked to the rule being monitored.Entry, exit or movement during a defined scheduleKeep the delay short only where a rapid response is genuinely required.Duty manager or security contactAn alert is sent without checking driver authorisation, vehicle status or the operating schedule.
Operating territoryUse a broad polygon for a territory rather than many small overlapping zones.Entry or exit from the territoryUse a longer confirmation period where boundary crossings are routine.Regional manager or plannerGPS accuracy and roads near the edge create repeated false crossings.
Service, charging or fuel locationDraw around the relevant facility, not the entire retail park.Arrival, departure or extended dwellSet a period that distinguishes a visit from passing traffic.Fleet administrator or workshop teamNearby facilities share the same access road or car park.

For depots and job sites, arrival and departure are usually more useful than continuous location alerts. If a platform supports schedules, apply them carefully: an out-of-hours depot alert may be relevant for one vehicle group but not another. A company car used for agreed personal journeys should not automatically be treated in the same way as an operational van.

Geofencing can also support wider workflows. For example, a job-site arrival event may be compared with a work order, while an extended dwell at a depot may prompt a maintenance or loading check. These connections depend on the software and should be tested rather than assumed.

Privacy and proportionality

Vehicle tracking geofencing can involve information about drivers, particularly where a vehicle is assigned to an individual or used outside working hours. Explain the purpose of monitoring, limit access to people who need it and avoid collecting or retaining more information than the business purpose requires. Keep the fleet policy, privacy information and alert rules aligned. For a broader review, see Fleet Vehicle Tracking and GDPR in the UK.

Cadence and checkpoints

Use a repeatable workflow when creating every zone:

  1. Define the decision. Write down what someone should do when the alert arrives. If there is no action, consider recording the event without notifying anyone.
  2. Choose the smallest useful boundary. Include the entrance, parking or loading area needed for the process, but exclude neighbouring roads and premises where possible.
  3. Set the trigger. Decide whether entry, exit, dwell time or an out-of-hours event matters. Avoid enabling every available trigger by default.
  4. Assign ownership. Name a recipient, a backup and an escalation route. A shared operational inbox or dashboard may be more reliable than one person’s phone.
  5. Test in realistic conditions. Check the zone with a vehicle approaching from different directions, stopping near the boundary and leaving during the relevant schedule.
  6. Record the rule. Note the zone purpose, boundary owner, vehicle group, schedule, dwell time and review date.

A practical alert-policy template can use the following fields:

  • Zone name: use a consistent format such as “Depot – Leeds – Main Entrance”.
  • Purpose: state the decision the alert supports.
  • Vehicles or assets: list the relevant group rather than applying the rule to the entire fleet automatically.
  • Trigger and schedule: specify entry, exit, dwell or out-of-hours conditions.
  • Delay: record the chosen confirmation period and why it is appropriate.
  • Recipients: identify the primary owner and escalation contact.
  • Review date: set a quarterly review, or sooner for temporary sites.

During a monthly operational check, review alert volume, missed events, duplicate notifications and unresolved escalations. A fuller quarterly review should examine whether sites are still active, whether boundaries remain accurate and whether the alert is producing a useful action. Temporary construction or customer zones should have an expiry date rather than remaining indefinitely.

How to interpret changes

A rise in geofence alerts does not automatically mean a rise in unauthorised activity. First separate genuine operational changes from technical or configuration issues. Look for patterns by location, vehicle, time of day and trigger type.

  • Repeated edge crossings at one site: the boundary may be too close to a road, entrance or neighbouring car park. Enlarge or redraw it, then retest.
  • Many alerts from one vehicle: check its tracker installation, power supply, location-update behaviour and assigned vehicle group. An OBD, hardwired or battery-powered device may behave differently depending on its configuration.
  • Alerts arrive late: check mobile coverage, device connectivity, platform processing and notification settings before changing the boundary.
  • Arrival alerts are missing: confirm that the vehicle enters the zone, the tracker reports a location during the visit and the selected trigger applies to that vehicle.
  • Out-of-hours alerts increase after a rota change: review schedules and authorised-use rules before escalating individual events.
  • Alerts are ignored: reduce recipients, remove low-value triggers or route the event to a dashboard for review instead of an immediate notification.

Compare geofence data with operational records where appropriate, such as job sheets, delivery notes or planned routes. Treat the tracking event as an indication to investigate, not as a complete explanation of what happened. GPS accuracy, update intervals, blocked signals, map boundaries and mobile-network availability can all affect the timing or apparent location of an event.

Geofences should also be kept separate from driver behaviour monitoring unless there is a clear reason to combine them. Speeding, harsh braking and route deviations answer different operational questions. Combining unrelated alerts can make it harder to identify the event that genuinely needs attention. See Driver Behaviour Monitoring in the UK for guidance on choosing more focused telematics alerts.

When to revisit

Review fleet geofencing at least quarterly as part of the wider fleet tracking software review. A monthly check is sensible for high-use fleets, busy depot networks or operations with frequent temporary sites. Revisit the setup immediately when:

  • a depot, customer site, service area or operating territory opens, closes or changes access;
  • vehicle groups, shifts, driver responsibilities or authorised-use policies change;
  • alert recipients leave, change role or become unavailable;
  • the tracking platform changes its map, notification, scheduling or dwell-time controls;
  • the business changes tracker hardware, connectivity arrangements or installation method;
  • alert volume rises unexpectedly or important events are missed;
  • a privacy review, employee consultation or internal policy update changes the monitoring purpose.

At each review, export or record a list of active zones and check five points: purpose, boundary, trigger, recipient and retention or access settings. Delete obsolete zones, merge duplicates and add an expiry date to temporary locations. Ask the person receiving each alert whether it led to a useful action; this simple test often identifies unnecessary notifications faster than looking at settings alone.

For a structured next step, choose one depot and one job site this week. Document their purpose, redraw the boundaries, apply a realistic dwell time, test entry and exit events and confirm the escalation route. Then use the same template across the fleet. If you are selecting software, compare geofencing controls alongside connectivity, reporting, vehicle compatibility and support; the most useful system is the one your team can configure, understand and review consistently. Related guidance is available in Fleet Tracking Software UK: Features, Costs and Questions to Ask Before You Buy.

Related Topics

#geofencing#fleet tracking#fleet alerts#depots#job sites#vehicle monitoring
M

Mobile Track Pro Editorial Team

Fleet Tracking Editor

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.