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.
Which travel does the data have to capture?
The travel that is paid. Under 29 CFR 785.38, time an employee spends traveling as part of the principal activity, such as travel from job site to job site during the workday, is hours worked, and travel from a designated meeting place to the work site counts regardless of contract, custom or practice (29 CFR 785.38). The regulation's own example is a worker sent from one job to another who must return to the employer's premises: all of that time is working time.
Paid travel is also the travel most easily disputed afterward. A foreman remembers sending a journeyman to the supply house, the journeyman remembers it taking an hour, and the timesheet shows one job all afternoon. A record of when the worker left one site and arrived at the next settles it in minutes, for the worker and for you.
- Site to site. Leaving one jobsite and arriving at another is the clearest case.
- Shop or yard to site after a required report-in. The day starts where the worker must report.
- Supply house and delivery runs. Mid-day travel in the job's interest, between two points of work.
- Return to the shop with a truck or tools when the employer requires it.
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.
| Dispute | Without a record | With a time-stamped site record |
|---|---|---|
| "I drove 45 minutes between sites and wasn't paid for it" | One person's memory against another's | Leave and arrive times at each site, and the gap between them |
| "He billed travel that didn't happen" | A timesheet with a round number | Whether 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 ticket | A stop recorded between two jobsites, with times |
| Job costing: which job carries the drive | Split by guess | Origin, destination and minutes, ready to allocate by your policy |
| Overtime: did the week cross 40 hours | Jobsite hours only | Jobsite hours plus travel that is hours worked |
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?
Is travel between two jobsites in the same day paid?
Can a time system discard travel time between sites?
Does a company truck change whether the commute is paid?
Why not keep the raw route for longer in case of a dispute?
What should the written consent say about travel?
Sources
- 1.29 CFR 785.38, Travel that is all in the day's work · Electronic Code of Federal Regulations
- 2.29 CFR 785.35, Normal travel from home to work · Electronic Code of Federal Regulations
- 3.29 U.S.C. 254, Portal-to-Portal Act · Legal Information Institute, Cornell Law School
- 4.Morillion v. Royal Packing Co. (2000) 22 Cal.4th 575 · Supreme Court of California (via Justia)
- 5.California Civil Code 1798.100 (collection reasonably necessary and proportionate) · California Legislative Information
Keep reading
- ResourceWorker location tracking lawsThe pillar guide to the federal and state rules.
- ResourceWorker location data retentionHow long to keep raw and derived data, and when to delete.
- ResourceWorker consent by stateA state-by-state quick guide to consent and notice.
- GuideTravel time between job sites: pay rulesThe federal rules, worked days and the California position.
- GuideDrive time policy for contractorsThe decisions a company drive time policy has to make.
