Geofence alerts let your team know when an asset enters or leaves a defined area. They are useful for tracking unauthorized movement, confirming arrivals, and keeping equipment where it is supposed to be.
Geofence alerts are tied to the boundaries you create in CLUE. Once a geofence is set up, CLUE can watch for movement across that boundary and notify the right people when an asset comes in or goes out. If the geofence has not been created yet, start with Creating a New Geofence before setting up alerts.
CLUE supports entry and exit alerts. Each one is useful for a different kind of tracking, depending on whether you care more about arrivals or departures.
A Left Geofence alert is triggered when an asset exits the boundary.
Use it to:
An Entered Geofence alert is triggered when an asset enters the boundary.
Use it to:
When you set up a geofence alert, you can control which locations, assets, and people are included. This helps reduce noise and makes sure alerts only go to the teams that need them. If the geofence is linked to a project, that also fits well with Using Geofences in Dispatch, where geofences can be used as pickup and drop-off locations.
You can configure:
CLUE can send geofence alerts in a few different ways, depending on how your team works. This makes it easier for field users, supervisors, and managers to stay informed without all relying on the same channel.
Alerts can be delivered through:
Alert history helps you review what happened after the fact. This is useful when you need to confirm when an asset crossed a boundary or look into repeat movement at the same site. If you also monitor live location, this works naturally with Using Track Everything so you can compare alert history with current map activity.
In alert history, you can review:
A few simple setup choices can make geofence alerts much more useful. Start with the assets and locations that matter most, then expand the setup once your team is comfortable with the alert flow.