Geofencing in BuildOps uses GPS location to verify that technicians or vehicles are where they’re supposed to be when work starts, pauses, resumes, or finishes. This helps you improve accountability, protect margins, and reduce disputes around time and location.
This article covers:
Technician Geofencing for Job Visits (mobile app)
Fleet+ Geofencing (optional add-on, vehicle-based)
Technician Geofencing for Job Visits
What technician geofencing does
When a technician updates a Job Visit status on mobile (for example, Work, Pause, Break, or Finish), BuildOps compares their phone’s GPS location to a geofence radius around the property. If they’re outside the allowed radius, they’ll see a clear in‑app message and may be required to retry before proceeding, depending on your settings.
Technician geofencing:
Verifies whether the tech is inside or outside the defined radius when they change visit status.
Prompts the tech if they’re outside the radius, with guidance to move closer and retry.
Logs each attempt (including latitude/longitude) so office teams can review later in the Location Log on the Job.
Does not apply to certain non‑work statuses like Travel and Arrived Home, so technicians aren’t blocked while they’re simply moving between locations.
Geofencing currently applies to Jobs and Job Visits, not Project Visits.
When to Use Geofencing
Geofencing is especially valuable when you want to:
Verify on‑site presence for strict SLAs or compliance requirements.
Reduce timecard and location disputes between supervisors and field staff.
Identify patterns like repeated late arrivals or early departures.
Support customer conversations with concrete GPS evidence of where and when work happened.
Prerequisites & Setup
To get reliable results from technician geofencing, make sure the following are in place.
Property latitude/longitude
Geofencing depends on accurate property coordinates:
Turn on the “Latitude/Longitude based locations” setting so properties can store coordinates and show them on the Visit card.
When creating or editing a property, always select a suggested address from the dropdown so BuildOps can store latitude/longitude automatically. If you type a free‑form address and don’t pick a suggestion, the property will not have coordinates and geofencing cannot run for that location.
If a property has no lat/long, BuildOps cannot verify proximity for that visit.
Geofence radius at the customer level
Geofence boundaries are defined at the Customer level as a radius in miles around each property’s latitude/longitude:
Set a geofence radius (miles) on the customer record.
That radius is applied to all properties under that customer, using each property’s stored coordinates.
Typical patterns:
Tighter radius (e.g., 0.25–0.5 miles) for dense urban or campus environments.
Larger radius for remote or large industrial sites.
Technician device requirements
Technician geofencing relies on the mobile device’s GPS and OS permissions:
The device must support GPS; geofencing is not supported when using BuildOps on a Mac or PC.
The tech must allow location access for the BuildOps mobile app.
If geofencing is turned on after they’ve already logged in, they may see a pop‑up asking to enable location; they must approve it.
If they decline, they’ll need to turn on location manually in the device settings before geofencing can validate.
For best results, confirm:
Location Services are On at the OS level.
BuildOps has permission “While using the app” (or equivalent).
Retry attempts (bypass behavior)
You can control how strictly geofencing is enforced by configuring the number of retry attempts in Company Settings → Mobile Settings → General Settings:
0 retries – Technicians will see geofence messages, but they are not forced to retry; they can proceed without mandatory extra attempts.
1 or more retries – Technicians must retry that many times before they are allowed to bypass the geofence and continue. This gives them multiple chances to move inside the boundary or fix connectivity/location issues before proceeding.
This setting is useful when you want geofencing to be a strong guardrail (for compliance and policy) but still allow technicians to complete work in edge cases.
ServiceChannel integration considerations
If your company uses ServiceChannel V2:
ServiceChannel already validates its own geofence radius for check‑in/check‑out.
Running BuildOps technician geofencing on top of ServiceChannel’s own validation can lead to conflicting radius values and unexpected behavior.
Before enabling technician geofencing in a ServiceChannel V2 workflow, coordinate with your CSM to confirm the recommended setup.
How Geofencing Works on Mobile
Technician experience on mobile
When a technician taps Work, Pause, Break, or Finish on a Job Visit:
BuildOps reads the Visit’s property and finds its latitude/longitude.
The app asks the device for the technician’s current GPS location.
BuildOps compares the technician’s location to the customer’s geofence radius around that property.
Based on that comparison:
Inside the geofence
The status change is allowed and recorded as normal.
A GPS “stamp” is saved and later appears in the Job’s Location Log on web.
Outside the geofence
The technician sees a Geofence Boundary Alert telling them they’re outside the boundary and should move closer and retry.
If your account requires retries (e.g., 1–3), they will continue to see geofence messages until the required number of attempts is met. After that, they can choose to proceed with a confirmation prompt.
Location disabled for BuildOps
The tech sees a prompt explaining that location access is required to update the Visit, and must enable location for the app before geofencing can verify position.
Online vs offline behavior
Geofencing is designed to keep technicians productive even when connectivity is spotty:
Online with GPS available
BuildOps verifies the geofence in real time and records the GPS coordinates.
Offline with GPS available
BuildOps still uses the device’s GPS signal locally to verify whether the tech is inside the radius and logs that location for later sync.
Offline and GPS not available or inconclusive
The app explains that the location cannot be verified because the device is offline and may require retries depending on your settings. In some cases, after retries are met, the tech can still proceed so work is not blocked, and actions are recorded for later sync.
How Geofencing Works on Web
When technician geofencing is in use, office users get additional visibility on the Job detail page:
A Location Log section shows:
Action Date
Visit ID
Visit Status
Technician
Location (latitude/longitude) for each recorded action.
This makes it easier to:
Validate that technicians were on site when they started/finished work.
Investigate disputes or questions about whether someone was truly at a property at a specific time.
Support internal audits and customer conversations with concrete GPS data.
Fleet+ Geofencing (Optional Add‑On)
If your company uses Fleet+ (BuildOps’ integration with Azuga), you also have access to vehicle‑based geofencing.
What Fleet+ geofencing does
Fleet+ uses GPS hardware in your vehicles to power:
Fleet+ GeoFence functionality – Define zones and get alerts when vehicles enter or exit specific locations (yards, customer sites, restricted areas).
Geofenced timesheets (web) – With Geofence Fleet+ Timesheets, timekeeping can be enhanced using vehicle location, so you can see when a truck arrived at or left a monitored area.
Mobile geofence alerts – Mobile notifications when a vehicle or device enters or exits a tracked location, if Fleet+ and geofence pushes are enabled.
Fleet+ geofencing is separate from technician geofencing:
Technician geofencing is phone‑based, tied to visit status changes in the mobile app.
Fleet+ geofencing is vehicle‑based, tied to GPS devices and Fleet+ zones.
Many customers choose to use both:
Technician geofencing for visit‑level accountability.
Fleet+ geofencing for vehicle movement, route verification, and equipment tracking.
Limitations & Best Practices
Current limitations
Job Visits only – Technician geofencing does not currently enforce geofencing on Project Visits; customers needing project‑level enforcement often pair Projects with Fleet+/Azuga geofences as a workaround.
Requires location sharing – If technicians deny location access or turn off device‑level location, geofencing cannot validate proximity and behavior falls back to your configured retry/bypass rules.
Requires property coordinates – Geofencing won’t run on properties without latitude/longitude. Always select a suggested address during property setup to populate coordinates.
Device type – Technician geofencing is not supported from web or desktop; it requires the mobile app on a GPS‑enabled device.
Recommended configuration tips
Start with a modest radius (e.g., 0.25–0.5 miles) and adjust based on how often technicians see “outside geofence” messages.
Set 1–3 retries so the feature encourages compliance but still lets techs work through edge cases.
Train office staff on the Location Log so they know where to find GPS history when questions come up.
For Fleet+, coordinate with your BuildOps team on:
Which geofences you want alerts for (yards, key customers, etc.).
Whether you want Fleet+ geofence alerts and geofenced timesheets enabled.