Overtime Rights a Tech Should Know

Why this matters

Most overtime that goes unpaid in a service shop is not stolen at the rate. It is lost at the clock: the shop meeting before the first call, the parts you loaded in your driveway, the lunch you ate in the truck between calls, the callback you finished on "your own time" because it was your mistake. Each one is a fraction of an hour, every one of those fractions lands after hour 40 in a busy week, and every overtime hour is worth one and a half times your regular rate. A tech who knows what the law counts as an hour can catch a weekly shortfall that adds up to a few weeks of pay a year.

This card explains the federal floor and the main state layers. It is not legal advice; where the article says to talk to someone, that is the point to stop reading and call.

The federal floor, in one paragraph

The Fair Labor Standards Act (29 U.S.C. 207) requires overtime at one and a half times your regular rate for every hour over 40 in a workweek, for any employee who is not exempt. Three details carry most of the weight:

• The workweek is fixed. It is any seven consecutive 24-hour periods the employer picks, and it stays put. Hours cannot be averaged across two weeks (29 CFR 778.104), so a 50-hour week followed by a 30-hour week is 10 hours of overtime, not zero, even though the biweekly stub shows 80.
• The rate is your regular rate, not your base rate. Spiffs, commissions and promised bonuses get folded in. The method lives in a sibling card; see related: Reading Your Pay Stub as a Technician.
• You cannot waive it. An agreement to work overtime for straight time, or for comp time later, is unenforceable for a private employer. Comp time in place of overtime pay is allowed only for public-sector employers.

Are you covered? Usually yes

Most techs are nonexempt, meaning the overtime rule applies. The white-collar exemptions (executive, administrative, professional) require both a salary paid at or above a minimum the Department of Labor sets and duties that fit the exemption, and the regulations say outright that workers who perform work with their hands are not exempt under them however much they earn (29 CFR 541.3). Being paid a salary does not, by itself, make a tech exempt. A 2024 rule raising the salary minimum was vacated by a federal court, so the earlier level applies as of 2026; check the DOL's overtime page for the current figure.

Flat-rate and commission techs are covered too, in most cases. Piece-rate pay still owes overtime over 40 clock hours; the math is in a sibling card (see related: How Flat-Rate Pay Works From the Tech's Side). The narrow exception is FLSA section 7(i), which can exempt commissioned employees of a retail or service establishment when more than half their pay over a representative period comes from commissions and their regular rate exceeds one and a half times the minimum wage. If your shop says 7(i) applies to you, ask them to show you how both conditions are met.

The exemption most techs have never heard of is the Motor Carrier Act exemption (FLSA section 13(b)(1)). It can remove federal overtime for drivers, loaders and mechanics whose work affects the safety of vehicles over 10,000 pounds gross vehicle weight rating in interstate commerce. A 2008 amendment restored overtime for employees who work, even part of the time, on vehicles at or under 10,000 pounds, which covers most service vans and pickups. If you drive a heavy box truck or a large service body across state lines, this exemption may reach you, and state law may still require overtime.

What counts as an hour worked

This is where the money actually leaks, and it is set out in 29 CFR Part 785.

Rounding clock times is allowed only if it is neutral over time, so it does not consistently favor the employer (785.48(b)). A system that always rounds your 6:52 punch to 7:00 and your 4:38 punch to 4:30 is not neutral.

A worked week

A tech at a shop with a Monday-to-Sunday workweek and an hourly base rate. Write the rate as R. The tech keeps their own log; here is part of it.

TUE  06:40  loaded 2 condensers dropped at house
     06:55  left house, drove to 1st call
     07:30  arrived 1st call (shop clock starts)
     11:50  lunch in truck, driving to 3rd call
     16:00  done, clocked out
THU  07:30  clocked in
     16:30  dispatch closed, clocked out
     16:35  back to my callback from Mon, leak
     18:15  leak fixed, left site

The shop's records and the law's count, day by day, with a 30-minute lunch deducted every day by the payroll system:

• Monday. A mandatory 7:00 meeting, then calls 7:30 to 4:30, lunch taken and fully relieved. Hours worked: 7:00 to 4:30 is 9.5 hours, minus 0.5 lunch, is 9.0. Shop paid from 7:30: 8.5. Gap 0.5.
• Tuesday. Loading at home is a principal activity, so the day starts at 6:40. Lunch was eaten driving, so it was not relieved and is not deductible. Hours worked: 6:40 to 4:00 is 9 hours 20 minutes, 9.33. Shop paid 7:30 to 4:00 minus 0.5: 8.0. Gap 1.33 (50 minutes of morning plus the 30-minute lunch).
• Wednesday. 90 minutes waiting at the supply house, on the clock. 7:30 to 4:30 minus a relieved lunch: 8.5 worked, 8.5 paid. No gap: engaged-to-wait time was handled right.
• Thursday. The callback ran 4:35 to 6:15 after clock-out. The shop knew, because it was their callback ticket. 7:30 to 6:15 is 10 hours 45 minutes, minus 0.5 lunch, is 10.25 worked. Shop paid 8.5. Gap 1.75. (The five minutes between leaving dispatch and starting the callback stays in: once the workday began, it runs continuously.)
• Friday. 7.5 worked and paid.
• Saturday. One on-call emergency, 2.0 hours including the drive from home. 2.0 worked and paid.

Totals: worked 9.0 plus 9.33 plus 8.5 plus 10.25 plus 7.5 plus 2.0 is 46.58 hours. Paid 8.5 plus 8.0 plus 8.5 plus 8.5 plus 7.5 plus 2.0 is 43.0 hours. The gap is 0.5 plus 1.33 plus 1.75, which is 3.58 hours, and it matches 46.58 minus 43.0.

Pay: the shop paid 40 straight hours plus 3.0 overtime hours at 1.5 R, which is 40 R plus 4.5 R, or 44.5 R. Owed: 40 R plus 6.58 overtime hours at 1.5 R, which is 40 R plus 9.87 R, or 49.87 R. The shortfall is 49.87 R minus 44.5 R, which is 5.37 R, a little over five hours of base pay, and every missing hour is an overtime hour because the week was already past 40. If that pattern held 40 weeks a year, it would come to about 215 hours of base pay, which is more than five full 40-hour weeks.

Notice what did NOT leak: the supply-house wait and the night emergency, both of which shops sometimes miss. The losses were the three things that feel like they are not "real" work: a meeting, home loading, and finishing your own callback.

The state layer, and where it changes this week

States can add to the federal floor and many do. California owes daily overtime: time and a half after 8 hours in a workday and double time after 12, plus special rules for the seventh consecutive day in a workweek. Run this tech's week under California law and the daily overtime is 1.0 plus 1.33 plus 0.5 plus 2.25, or 5.08 hours. The remaining 41.5 hours trigger 1.5 hours of weekly overtime, for 6.58 overtime hours total. That matches the federal total for this particular week, but the reason is coincidental. California also owes an extra hour of pay when a required meal period is not provided (Labor Code 226.7), so Tuesday's lunch-in-the-truck costs the shop a premium hour on top of the overtime.

Where the state layer flips the answer outright is the four-day, ten-hour schedule. Federally, 4 days of 10 hours is 40 hours and zero overtime. In California, the same week is 8 hours of daily overtime unless the shop has adopted an alternative workweek schedule through the secret-ballot employee election the state requires. Alaska also has daily overtime for most employers above a small size, Colorado counts overtime past 12 hours in a workday, and Nevada has a daily rule limited to lower-paid workers. Most other states follow the federal weekly rule. Check your own state labor department's overtime page; do not assume your state is either California or federal.

When the hours are wrong

Keep your own log of start, stop, lunch and anything after clock-out, made the same day. A record written at the time carries weight, and under the FLSA, where the employer's records are inaccurate, a worker can prove hours by reasonable estimate. For a method, see related: Tracking Your Own Hours and Pay.

Raise it in writing with payroll first. Most gaps are system defaults (an auto-deducted lunch, a clock that starts at first dispatch) rather than intent. See related: Raising a Paycheck Error.

Know the clock on recovery. A federal claim reaches back two years, or three for a willful violation (29 U.S.C. 255), and the FLSA allows liquidated damages equal to the unpaid amount (29 U.S.C. 216(b)). State limits are often longer: New York reaches back six years, and California generally three. Retaliating against you for complaining is itself a violation (29 U.S.C. 215(a)(3)).

The fork where you stop acting alone: if payroll will not fix a documented gap, or you are told you are exempt and the reasons above do not fit, take your log and your stubs to your state labor department, the federal Wage and Hour Division, or an employment attorney. Many wage-and-hour attorneys take these cases on contingency.

One tax note: federal law passed in 2025 created a temporary deduction for the FLSA-required overtime premium, current as of 2026; see related: Deductions a W-2 Tech Can and Cannot Take.

References

• 29 U.S.C. 207, 215, 216 and 255 (Fair Labor Standards Act overtime, retaliation, remedies, limitations)
• 29 CFR Part 785 (hours worked) and 29 CFR 778.104 (each workweek stands alone); 29 CFR 541.3 (manual workers not exempt)
• U.S. Department of Labor, Wage and Hour Division, Fact Sheet 22 (hours worked) and Fact Sheet 19 (Motor Carrier Act exemption)
• California Labor Code sections 510 and 226.7 (daily overtime, meal period premium)
• See related: Reading Your Pay Stub as a Technician, How Flat-Rate Pay Works From the Tech's Side, Tracking Your Own Hours and Pay, Raising a Paycheck Error