GPS Time Tracking for Field Service Employees | Netchex

Netchex launches Mesh AI HR Teammates for the Deskless Workforce

Learn More Arrow

GPS Time Tracking for Field Service and Building Services Employees

GPS Time Tracking for Field Service and Building Services Employees
Blog

Share

It’s 9:40 p.m. and the facilities manager for a ten-story office building is on the phone, and she’s not happy. The night cleaning crew was due to start floor care in the lobby at 9:00. Nobody walked through the door until almost 9:35. Yet the time and attendance system shows the crew clocked in at 8:58, sitting in a parking lot two blocks from the building.

That gap between a clock-in and an actual arrival is exactly what GPS time tracking is built to close. If you run a commercial cleaning company, an HVAC service business, a landscaping crew, or a pest control route, you already know the headache. Your workforce doesn’t punch in at one front door. It’s spread across a dozen buildings, twenty stops, or a territory that covers three counties. A time clock on a break room wall does nothing for a team that’s never in the same building twice in a week.

GPS time tracking closes that gap by tying a clock-in to a real location, confirming a crew or a technician actually reached the job site, and giving payroll a defensible record instead of a guess. But strap location tracking onto a workforce and you’ve stepped into two legal issues at once: wage and hour rules on what counts as paid travel time, and a patchwork of state privacy laws on when you’re even allowed to track someone’s location. Get either one wrong, and a tool meant to save time turns into a wage claim or a monitoring complaint.

Last updated: August 2026

Why Building Services and Field Service Crews Are Nearly Impossible to Track the Old Way

A route-based workforce breaks almost every assumption a traditional time clock is built on. Building services crews serve multiple client sites in a single night. Field service technicians in HVAC, pest control, and landscaping run a daily route where the stop order changes constantly. No supervisor is standing at every door to confirm who showed up and when.

There’s a lot riding on getting this right. The Bureau of Labor Statistics counts more than 2.4 million janitors and building cleaners working in the U.S., and most of them work evening or overnight shifts across sites nobody in the corporate office ever visits. Multiply that by a dozen client contracts and the math gets messy fast.

Field service businesses run into the same problem in a different shape. A single HVAC technician might hit five job sites before lunch. If the only record of when work started is a paper log filled out at the end of the day, that log is a guess dressed up as data. Buddy punching, rounded arrival times, and a crew that says it was on-site by 9:00 when it actually rolled in at 9:35 all become invisible without something more objective than a written timesheet.

How GPS Time Tracking Actually Works for a Route-Based Team

Here’s the basic mechanic. GPS time tracking ties a mobile clock-in to the device’s location at the moment the punch happens, often using geofencing to confirm the punch occurred inside a set radius of the job site. Many time and attendance platforms, including Netchex’s, give managers mobile clock-in tools that capture location data alongside the timestamp, so a manager doesn’t have to take an employee’s word for where they were at 9:00 p.m. on a Tuesday.

For field service crews, the same location data can capture mileage and travel time between stops automatically instead of relying on a technician to remember and log it hours later. That matters more than it sounds like it should. A route that runs five stops a day generates five separate travel segments, and each one needs to be accounted for correctly on the timesheet.

None of that replaces judgment. A location ping doesn’t prove someone actually did the work, and it can’t settle every dispute between a client and an account manager. But it does turn “the crew says they were on-site by 9” into a fact that can be checked, and that alone eliminates a lot of back-and-forth. So does that mean you just switch tracking on and walk away? Not quite. The legal side is where most employers get tripped up.

What Counts as “Hours Worked”: FLSA Travel Time Rules for Field Crews

Location data creates a paper trail, and that paper trail has to line up with wage and hour law, specifically what the Fair Labor Standards Act treats as compensable hours worked. The baseline rule hasn’t changed in decades: an ordinary commute isn’t work time. The U.S. Department of Labor’s Fact Sheet #22 on hours worked puts it plainly: “An employee who travels from home before the regular workday and returns to his/her home at the end of the workday is engaged in ordinary home to work travel, which is not work time.”

That changes the moment the workday actually starts. Under 29 CFR 785.38, “time spent by an employee in travel as part of his principal activity, such as travel from job site to job site during the workday, must be counted as hours worked.” That distinction is exactly where field service and building services employers get into trouble. A technician driving from the shop to the first job of the day is commuting. The same technician driving from client A to client B at 11:00 a.m. is working, and that time belongs on the clock.

  • Generally not paid: the ordinary commute from home to the first job site, and from the last job site back home.
  • Generally paid: travel from one job site to the next during the shift.
  • Generally paid: travel to a special one-day assignment in another city, minus the time an employee would normally spend commuting.
  • Usually not paid (DOL enforcement policy): time spent as a passenger outside normal working hours during overnight travel away from home.

GPS data actually helps here, and not just as a way to police employees. It helps prove the company got the math right. If a technician’s location log shows a stop at client A ending at 11:04 and a stop at client B starting at 11:22, that’s compensable travel time whether or not anyone remembered to write it down manually. That’s the upside nobody talks about when this topic comes up.

GPS Tracking and Employee Privacy: What State Law Requires

Wage and hour law tells you what to pay for. It doesn’t tell you when you’re allowed to track someone’s location in the first place, and that part varies quite a bit by state.

In California, Penal Code Section 637.7 makes it a misdemeanor to use an electronic tracking device to determine a person’s location without consent, but it carves out an exception when “the registered owner, lessor, or lessee of a vehicle has consented” to the tracking. A building services or field service company that owns or leases its own fleet vehicles can generally consent to tracking those vehicles on its own authority. That exception doesn’t automatically extend to an employee’s personal car, and it says nothing about tracking a worker’s personal phone.

Connecticut takes a different approach. General Statutes Section 31-48d requires any employer using “electronic monitoring” to give employees prior written notice describing the types of monitoring that may occur. The statute’s list of covered systems doesn’t name GPS specifically, but the definition is broad enough that Connecticut employers should treat location tracking as monitoring that needs disclosure, not something to switch on quietly.

Texas handles it through criminal law rather than an employment statute. Penal Code Section 16.06 makes it an offense to install a tracking device on someone’s motor vehicle without the consent of the vehicle’s owner or lessee, with consent operating as a defense. For a company-owned service van, that consent question is simple to resolve. For a technician using a personal truck for company routes, it isn’t automatic just because the company issues the paycheck.

The throughline across all three approaches is the same: consent and notice do the legal work. A written policy that spells out what’s tracked, when tracking is active, and who sees the data protects the company just as much as it reassures the crew. Silence is the risky option here, not disclosure. Requirements can differ by state, so it’s worth checking with your state labor agency before rolling out a fleet-wide tracking program.

Building a GPS Time Tracking Policy That Holds Up

A GPS tracking rollout works best when it’s treated as an HR policy first and a technology rollout second. Put it in writing: what’s tracked (vehicle location, clock-in location, mileage), when it’s active (scheduled work hours, not nights and weekends off the clock), and who can see the data. Have employees sign an acknowledgment during onboarding and keep it in the personnel file alongside the rest of the documentation your HR team maintains.

Scope matters as much as disclosure. Limit tracking to company-owned vehicles and devices during working hours instead of a personal phone that happens to have the time clock app installed. That single decision resolves most of the consent questions raised above before they ever come up.

The payoff shows up at payroll. When a system captures travel-between-sites time automatically instead of relying on a technician to remember it at 6:00 p.m., that data can flow straight into payroll and tax processing without a manual re-entry step, which is exactly where rounding errors and missed travel time tend to creep in. Consistency is the real compliance tool here. A policy applied the same way to every crew, every route, and every pay period is far easier to defend than one written after a complaint already landed.

Frequently Asked Questions

This article is provided for general informational purposes and does not constitute legal advice. GPS tracking and electronic monitoring laws vary by state and change over time. Consult your state labor agency or an employment attorney before implementing a GPS time tracking or vehicle monitoring policy.

Disclaimer: Any product roadmap or future plans provided herein are for informational purposes only. They do not represent a commitment to deliver any material, code, feature, or functionality. Plans may change without notification. The development, release and timing of any features or functionality described remain at the sole discretion of Netchex, its affiliates, and partners. Netchex does not give legal, tax, or accounting advice. You are responsible for ensuring your use of Netchex product meets your individual business and compliance requirements.

Related events

How to Manage Split Shifts in Payroll Software
09/01/26

How to Manage Split Shifts in Payroll Software

View Event
Biometric Time Clocks: Pros, Cons, and Compliance Considerations
09/01/26

Biometric Time Clocks: Pros, Cons, and Compliance Considerations

View Event
How to Manage Employee Schedule Changes Without Payroll Errors
08/31/26

How to Manage Employee Schedule Changes Without Payroll Errors

View Event
How to Enforce Attendance Policies Fairly in High-Turnover Environments
08/31/26

How to Enforce Attendance Policies Fairly in High-Turnover Environments

View Event