Skip to content

Resource · Travel time and privacy

Drive time, travel pay and location data

Travel between jobsites during the workday is hours worked under federal law, while the ordinary commute from home generally is not. A time system therefore needs to record location during site-to-site travel, because that is paid time, and should not record the commute at all. For a badge, that means on at the start of the paid day and off at the end.

Last updated By ZeroBadge

This is general information, not legal advice. Laws differ by state and change over time. Check the primary sources below and talk to an employment lawyer about your situation.

Why does drive time create a location-data problem?

Because the law pays for part of the drive and not the rest, a location system has to know which part it is looking at. Federal rules treat travel as part of the day's work as hours worked, and treat normal home-to-work travel as not worktime. The first is evidence you need. The second is movement you have no business reason to record and, in some states, no legal comfort recording.

This page is about that boundary. The legal rules and worked pay days are in travel time between job sites: pay rules, and the policy decisions are in drive time policy for contractors. Read them for what is paid. Read this for what data to keep.

Should location data cover the commute?

No. Normal travel from home to work is not worktime, whether the worker goes to a fixed location or to different job sites (29 CFR 785.35), and the Portal-to-Portal Act relieves employers of federal minimum wage and overtime liability for traveling to and from the actual place of performance of the principal activity (29 U.S.C. 254(a)). Nothing in wage law requires you to know where a worker drove from home, so collecting it has no wage-law purpose.

Collecting it also raises the privacy stakes. A route from a worker's front door reveals where they live, where they stop on the way and when they leave. California privacy law, for one, requires collection to be reasonably necessary and proportionate to the disclosed purpose (Civ. Code 1798.100(c)), and a commute trace is outside the purpose of verifying hours at a jobsite. The cleanest design is the one that never records it.

The commute can come up in one case: a worker who stops at the shop before heading to a jobsite, where the stop is disputed. That is solved with the record of arrival at the shop, not by tracing the drive.

Does California treat travel differently?

Yes, in places, and this is a point to take to an attorney. In Morillion v. Royal Packing Co., the California Supreme Court held that time farmworkers spent on employer-required, employer-provided buses was compensable hours worked under the applicable wage order, applying the control test rather than the federal Portal-to-Portal approach (22 Cal.4th 575 (2000)). Courts later read the holding as tied to travel the employer requires and controls, so an optional ride is a different question.

For location data the practical effect is a wider zone of compensable travel in California than the federal rule alone would give. If your crews in California ride in a company truck the employer requires them to use, or are directed to a distant site, the trip may be paid even though it starts at home. Where that is possible, the system needs to be able to start and stop on the facts of each trip, which a rigid rule about commute hours will not do.

How does verified travel data protect both sides?

It gives each side a time-stamped answer to the same question: when did the paid part of the day happen. Without it, travel gets estimated, and an estimate favors whoever is more confident.

Where travel disputes come from, and what a record settles
DisputeWithout a recordWith a time-stamped site record
"I drove 45 minutes between sites and wasn't paid for it"One person's memory against another'sLeave and arrive times at each site, and the gap between them
"He billed travel that didn't happen"A timesheet with a round numberWhether the worker was at the next site when the travel was claimed
"I went to the supply house for the job"A note on a ticketA stop recorded between two jobsites, with times
Job costing: which job carries the driveSplit by guessOrigin, destination and minutes, ready to allocate by your policy
Overtime: did the week cross 40 hoursJobsite hours onlyJobsite hours plus travel that is hours worked
A record shows when and where. Whether the time is paid depends on the law and your policy.

What dropping the travel does to a week

Jobsite time recorded
36 h 00 m
Travel between sites, 5 days at 45 minutes
3 h 45 m
Hours worked (jobsite plus travel)
39 h 45 m

A system that discards travel between jobsites understates the week by 3 h 45 m. Two more 15-minute drives would have crossed 40 hours and created overtime that the record never showed.

The same record protects the worker from being underpaid and the employer from a claim that travel was ignored. It is also what a manager looks at before approving a timesheet.

What should a travel-friendly, privacy-friendly system do?

  • Start recording when the paid day starts and stop when it ends, so the commute is never captured.
  • Keep the travel between jobsites inside the shift, as its own line, rather than dropping it or merging it into the next job.
  • Record at arrival and departure for each place of work, not a continuous trace of the route.
  • Let a worker pause at unpaid breaks and leave the device behind where privacy requires.
  • Keep the time record (leave, arrive, minutes) much longer than the raw position data behind it.
  • Let the worker see and dispute each recorded trip.
  • Say all of this in the written notice and the consent.

Retention for each layer is covered in worker location data retention.

Where ZeroBadge fits

ZeroBadge is a company-owned cellular badge worn at work, not an app on the worker's phone. The worker switches it on when the paid day starts and it switches itself off when the scheduled shift ends, so the commute home is not recorded, and workers can switch it off at any time. During the shift it uses GPS, Wi-Fi positioning and cellular positioning, taking a reading about every 5 minutes. GPS is strong outdoors and weak indoors, Wi-Fi and cellular fill gaps at lower precision, and cellular readings are marked low confidence. A move between jobsites stays inside one shift as its own transit line, so drive time between jobs does not disappear into the next job.

ZeroBadge records the travel. Your policy and the law decide what is paid. Before a badge stores a worker's location, the worker reviews a plain-English disclosure in the worker portal and signs it electronically, and that acknowledgment supplements the signed written consent ZeroBadge strongly recommends each employer obtain. Raw location is deleted after 30 days and time records are kept 4 years. Workers can pause at meal and rest breaks, see their data and dispute a time record. We verify work. We don't track people. ZeroBadge's tools support compliance. They don't make tracking legal by themselves.

Frequently asked questions

Do I need to track location during the drive to a jobsite from home?
No, and generally you should not. Ordinary home-to-work travel is not hours worked under federal law, so a record of it has no wage-law purpose. In California, travel an employer requires and controls may be paid, so check the facts with an attorney.
Is travel between two jobsites in the same day paid?
Under federal rules, yes. Travel from job site to job site during the workday is hours worked. See the guide on travel time pay rules for worked days.
Can a time system discard travel time between sites?
It should not. Travel that is hours worked affects pay and overtime, and discarding it leaves the record short. Keep it as its own line inside the shift.
Does a company truck change whether the commute is paid?
Federal law has a provision for employer-vehicle commuting within the normal commuting area under an agreement, and California can treat required, employer-controlled transport as paid. Where a truck is required, the answer depends on the facts and your state.
Why not keep the raw route for longer in case of a dispute?
A long-kept route reveals more about a worker's life than a dispute usually needs. The time record, with leave and arrive times at each site, settles most travel disputes. Keep raw positions on a short schedule and hold them only when a dispute or claim is pending.
What should the written consent say about travel?
That location is collected during paid time including travel between jobsites, that it is not collected on the commute or off shift, when the device is on and off, and how long raw location and time records are kept.

Sources

  1. 1.29 CFR 785.38, Travel that is all in the day's work · Electronic Code of Federal Regulations
  2. 2.29 CFR 785.35, Normal travel from home to work · Electronic Code of Federal Regulations
  3. 3.29 U.S.C. 254, Portal-to-Portal Act · Legal Information Institute, Cornell Law School
  4. 4.Morillion v. Royal Packing Co. (2000) 22 Cal.4th 575 · Supreme Court of California (via Justia)
  5. 5.California Civil Code 1798.100 (collection reasonably necessary and proportionate) · California Legislative Information

Get started

See ZeroBadge on your workforce.

Tell us how your crews work today. We will show you a badge-recorded week built from your own jobsites.

What we will walk through

  • 01How the badge records a shift
  • 02Your jobsites as geofences
  • 03The weekly timesheet and approval
  • 04Sending approved hours to payroll