Technician travel time pay is the quietest line in a service business, and the one most likely to be reconstructed years later by someone holding a payroll register. The Fair Labor Standards Act does not treat every mile the same way. Some trips are hours worked for a nonexempt technician, some are ordinary commuting, and the dividing line is set by where the trip falls in the workday rather than by who paid for the fuel. Sorting the categories once is cheaper than arguing about them later.
What technician travel time pay covers under the FLSA
The operative rules sit in 29 CFR part 785. Section 785.35 states that “Normal travel from home to work is not worktime,” and it applies that principle whether an employee reports to a fixed location or to different job sites. Section 785.34 explains that section 4 of the Portal-to-Portal Act generally keeps that commute outside hours worked even where an employer has agreed to pay for it. Paying for a commute is a compensation choice, not an hours-worked conclusion.
The analysis changes once the workday is under way. Section 785.38 provides that “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.” The regulation works through its own example: an employee who finishes a job at 8 p.m. and returns to the employer’s premises at 9 p.m. has all of that time counted as working time. If the same employee drives home instead, the regulation treats the travel after 8 p.m. as home-to-work travel that is not hours worked.
That single distinction decides many route disputes. A technician who ends the day at a customer site and goes straight home is generally in commuting time. A technician who is required to return the van, the parts or the paperwork to the shop first is generally still on the clock for that leg.
Which legs generally count
The table below summarizes how the regulations and the Department of Labor’s guidance treat the trips a service route actually produces. It is a summary of published rules, not legal advice, and close calls on your own facts belong with your employment counsel.
| Trip | Generally hours worked for a nonexempt technician | Published source |
|---|---|---|
| Home to the first stop on an ordinary day | No | 29 CFR 785.35 |
| Between job sites during the workday | Yes | 29 CFR 785.38 |
| Last stop back to the shop or yard | Yes | 29 CFR 785.38 |
| Last stop straight home | No | 29 CFR 785.38 |
| Called out at night to an emergency job far from home | Yes, on the regulation’s own example | 29 CFR 785.36 |
| Special one-day assignment in another city | Yes, though the normal commute and the usual meal time may be deducted | 29 CFR 785.37 |
| Overnight trip, travel falling inside regular working hours | Yes | 29 CFR 785.39 |
| Driving the van on an overnight trip, outside regular hours | Yes, as work performed while traveling | 29 CFR 785.41 |
| Riding as a passenger outside regular hours, with no assistant or helper duties | Not counted, as a stated enforcement policy | 29 CFR 785.39; WHD Fact Sheet #22 |
Two rows deserve a second look. Section 785.36 addresses the emergency call-out and says there may be instances when travel from home to work is overtime, using the example of an employee who has gone home, is called out at night to an emergency job far away, and whose travel is working time.
Section 785.41 says that an employee who drives a vehicle, or is required to ride in it as an assistant or helper, is working while riding, except during bona fide meal periods or when permitted to sleep in adequate facilities the employer furnishes. For a two-technician crew on an overnight install, that means the helper in the passenger seat may be on the clock as well. Section 785.36 also expressly takes no position on an emergency call that brings a technician back to the employer’s own place of business rather than out to a customer, so treat that variant as a question for counsel.
Technician travel time pay and the on-call hours around it
Drive time rarely arrives alone. Section 785.17 draws the on-call line at control: an employee required to remain on call on the employer’s premises, or so close to them that the time cannot be used effectively for the employee’s own purposes, is working while on call. An employee who is “merely required to leave word at his home or with company officials where he may be reached” is generally not working. The Wage and Hour Division’s Fact Sheet #22 adds that “Additional constraints on the employee’s freedom could require this time to be compensated.”
Waiting time follows a related test. Fact Sheet #22 frames it as whether the employee “was engaged to wait (which is work time)” or “was waiting to be engaged (which is not work time).” A technician sitting in a parking lot because the gym opens at six is closer to the first than the second.
Breaks and meals carry their own rules, and both show up on route sheets. Fact Sheet #22 says rest periods of short duration, usually 20 minutes or less, “must be counted as hours worked,” while bona fide meal periods of typically 30 minutes or more “generally need not be compensated as work time.” The condition is real: the employee “must be completely relieved from duty for the purpose of eating regular meals,” and “is not relieved if he/she is required to perform any duties, whether active or inactive, while eating.” A technician eating in the van while monitoring dispatch is a weak candidate for an unpaid meal period.
A worked example, on stated assumptions
Every figure in this example is an assumption chosen to show the mechanics. None of it is industry data, and your own rates, routes and exemption status will differ. Recompute it with your payroll register before you rely on any of it.
Assume one nonexempt technician at $28.00 an hour, five scheduled days, 5.5 hours of wrench time a day, and 1.75 hours a day of driving between job sites. Assume one paid 15-minute break a day, which Fact Sheet #22 treats as hours worked, and a 30-minute lunch during which the technician is completely relieved, which is not counted. Assume a 35-minute drive from home to the first stop, which section 785.35 treats as ordinary commuting.
Those assumptions give 5.5 plus 1.75 plus 0.25, or 7.5 hours of recorded work a day, and 37.5 hours for the week. No overtime yet. Now assume two emergency night call-outs in the same week, each with 45 minutes of travel in each direction and 1.5 hours on site, which is 3.0 hours apiece on the section 785.36 example. The week becomes 43.5 hours.
Paid correctly, that week is 40 hours at $28.00, or $1,120.00, plus 3.5 overtime hours at $42.00, or $147.00, for $1,267.00. Code the 3.0 hours of call-out travel as unpaid commuting instead and the week records as 40.5 hours, which pays $1,120.00 plus $21.00, or $1,141.00. The gap is $126.00 for one technician in one week. On these assumptions, a six-technician crew over 52 weeks would carry a $39,312.00 difference, before any liquidated damages or back-pay interest a regulator or a court might add.
The point is not the dollar figure, which is invented. It is that a single coding habit, applied quietly across a route board, compounds into a number worth more than the dispatch software that produced it. Operations that already track technician route hours and where billable time leaks have much of the raw data this calculation needs.
A seven-step route pay review
- Write down, for each technician, where the compensable workday starts and where it ends, and whether the shop is part of it.
- Pull one recent week of dispatch records and separate the commute legs from the between-stop legs, leg by leg.
- Code every between-stop leg as hours worked, and reconcile that total against what payroll actually paid for the same week.
- Put the call-out rule in writing, including travel in both directions, and make sure dispatch and payroll are using the same rule.
- Test the on-call arrangement against section 785.17 by asking what the technician is actually free to do during the window.
- Confirm that unpaid meal periods are genuinely relieved of duty, including radio, phone and dispatch obligations.
- Recompute the corrected week end to end, then decide with counsel whether anything needs to be corrected going backward.
Records that decide the argument
Wage disputes are won on contemporaneous records, not recollection. The file that answers a technician travel time pay question usually holds dispatch timestamps for every leg, telematics or GPS traces, signed work-order arrival and departure times, the payroll register for the same weeks, the published on-call schedule, and the written travel and call-out policy the crew was given.
- Dispatch and work-order timestamps, matched leg by leg to payroll hours.
- The written travel policy, with the version history that shows when it changed.
- On-call rosters, including how often a technician in the window was actually called.
- Any flat allowance, stipend or per-trip payment, and the hours it was meant to cover.
- Time records for helpers and second technicians riding on the same calls.
Warning signs on a route board
- A flat daily truck or travel allowance standing in for recorded hours.
- Technicians clocking in at the first customer site as a matter of policy, including on nights they were called out.
- Windshield time between stops excluded by habit, with no written basis.
- Weeks that land on exactly 40.0 hours across a whole crew, month after month.
- Unpaid lunches logged while the technician is still answering dispatch.
- Overnight installs where only the driver is paid for travel.
Common questions
Does paying mileage satisfy technician travel time pay?
No. Mileage is a vehicle-expense question and hours worked is a separate one. Section 785.34 makes the direction of the error clear in the other direction too: ordinary home-to-work travel generally need not be counted as hours worked even where the employer agrees to pay for it.
Does a take-home van make the commute compensable?
Not by itself, on the published rules above, which treat ordinary home-to-work travel as outside hours worked whether the work site is fixed or changes daily. Whether a particular vehicle, tool-loading or start-of-day requirement changes that is fact-specific, and it is the kind of question to put to employment counsel rather than settle from a fact sheet.
Are service technicians exempt from overtime anyway?
Treat that as a separate question with its own test, and do not assume the answer. The classification analysis for whether a worker is an employee at all is a different inquiry again, covered in our note on the IRS common-law test behind 1099 technicians.
Technician travel time pay is not a problem that needs new software to fix. Pull one week, split the legs, price the difference, and write the rule down. Shops weighing whether to carry the route at all will find the same hours and costs sitting underneath the in-house versus contracted service decision, and the same records that support a pay review also support the documented downtime costs a customer will eventually ask you to prove. The Department of Labor publishes the governing text in Fact Sheet #22 on hours worked, the travel-time sections at 29 CFR 785.38, and the on-call rule in 29 CFR part 785.
