Understanding Geofence Alerts

Geofences
Reading Time:
4 min read

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.

Overview

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.

Types of Geofence 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.

Left Geofence

A Left Geofence alert is triggered when an asset exits the boundary.

Use it to:

  • detect unauthorized equipment removal
  • track when assets leave a job site
  • monitor after-hours movement.

Entered Geofence

An Entered Geofence alert is triggered when an asset enters the boundary.

Use it to:

  • confirm equipment arrivals
  • track delivery completion
  • monitor access into restricted areas.

Alert Configuration

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:

  • Which geofences - choose one or more boundaries
  • Which assets - apply the alert to all assets or only selected equipment
  • Time windows - limit alerts to certain days or after-hours periods
  • Recipients - choose who receives the notification.

Alert Delivery

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:

  • Push notifications in the mobile app
  • Email with more detail
  • In-app notifications in the dashboard.

Viewing Alert History

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:

  • which asset triggered the alert
  • when the boundary was crossed
  • whether the movement was into or out of the geofence.

Tips

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.

  • Set up alerts for high-value equipment first
  • Use time-based rules to cut down on noise during normal working hours
  • Review alert history to spot patterns over time
  • If a site boundary is not working well, update it in Editing Geofence Boundaries instead of creating duplicate geofences
  • If arrival and departure times matter for project tracking, link the geofence to the project so it can support dispatch and site reporting more cleanly.