Overview
Many companies track drive time using a dedicated "Drive Time" cost code. But if On-Site Verification is turned on for a project, employees can only clock into that project (and its cost codes) while they're physically on-site, which defeats the purpose of tracking time spent driving. There are two ways around this.
Steps
Option 1: Add a Drive Time subproject with no geofence
Under the main project, create a subproject named "Drive Time" (or similar).
Don't set a geofence on that subproject.
Employees select the Drive Time subproject and cost code while driving, without needing to be on-site.
Option 2: Create a separate Drive Time project
Create a new project called "Drive Time" with no geofence.
Have employees add a note stating which project they're driving to or from.
Employees use the app's Switch button to move between projects and cost codes as they travel between work sites.
Notes
Both options work because the geofence restriction only applies at the project or subproject level where it's turned on. A subproject or project with no geofence has no On-Site Verification restriction, even if its parent project does.
If your company doesn't count drive time toward overtime calculations, see Overtime Settings and Explanation — this typically requires a custom payroll macro built by a BusyBusy specialist.