Problem guide
Overtime is a surprise at payroll
Overtime surprises payroll because federal law counts one person's week across every job, location and shift, while most operating and cost reports count hours one job, location or department at a time. Under 29 CFR 778.103 the employer must total every hour a person worked in the workweek, even on unrelated jobs, and pay time and a half past 40. Total each person's week by Wednesday, across everything they worked, and the overtime stops arriving as news on payday.

How it actually happens
The law and the reports count two different things. The Fair Labor Standards Act counts a person's week. The field system, the job-cost report, the location schedule and most managers count a job's or a department's hours. Overtime lives in the gap between them, and nobody owns the gap until payroll.
Take an ordinary week at a mid-sized mechanical contractor. Monday through Wednesday a pipefitter works a hospital retrofit. The project manager on that job sees 27 hours and a crew on budget. Thursday the service manager borrows him for a boiler changeover across town, and by Friday night he has 16 more hours there. That service manager sees a normal two-day job. On Friday afternoon the superintendent on the hospital job learns the inspector moved up, and asks the same fitter to come in Saturday for five hours. Nobody in that chain did anything wrong, and nobody added 27, 16 and 5.
The office clerk does, the following Tuesday, when the payroll export comes out of the field app. Forty-eight hours, eight of them at time and a half. Now someone has to decide which job eats the premium. If the job-cost report prices the fitter at one flat rate per hour, both jobs still look fine, and the premium sits in an overhead account where no project manager will ever see it.
The same week happens off the job site. A line cook works four shifts at one restaurant and picks up two at the sister location. A warehouse associate is held over three nights to clear the dock for a client. A clinic's medical assistant covers a call-out at the second office. Each manager approved one reasonable thing, and each schedule looks normal on its own.
Service work hides it differently. A tech runs five calls a day and drives between them. Federal rules count the drive between job sites as hours worked, along with the parts-house run and the morning meeting. ServiceTitan's own help center warns that custom timesheet activities count as regular hours in its overtime math, and that hours fixed in an outside payroll system but not in ServiceTitan make job costing show profit that is not there. The paycheck ends up right. The job report does not.
Then the schedule adds the late surprise. An electrician on Reddit described working twelve hours after being told only at quitting time that he had to stay, about twice a month, because inspections were booked before rough-in could be finished. Saturdays came the same way, announced at the end of Friday. That overtime was decided by whoever booked the inspection, and that person never saw an hours total.
Why the payroll number is right and still a surprise
Payroll did its job. The number is correct, and under 29 CFR 778.106 it is due on the regular payday for that week. The surprise is that it arrived four days after anyone could have changed it. Move the person-week total from Tuesday's payroll run to Wednesday's schedule meeting and the same number becomes a planning input instead of a correction.
Signs you have this problem
- Payroll finds the overtime after the week has already closed
- A person with 30 hours on one job or location and 15 on another shows no overtime on either report
- A job or department looks on budget until the overtime premium lands on it at month end
- Weekend shifts and extra days get booked late in the week without anyone checking who is already near 40
- Hours get fixed in the payroll file, and the cost reports keep the old ones
What usually causes it
- Nobody sees a running total of each person's week until payroll adds it upThe invisible queue
- The person who books the extra shift, the Saturday or the late appointment cannot see hours already workedThe handoff gap
- Hours reach the office only at the end of the week, after the schedule that created the overtime is historyThe field-to-office split
- Hours are corrected in the payroll export instead of the system where time is recorded, so cost reports and payroll keep two versions of the weekThe re-entry trap
Find your cause
Ask these in order. The first yes is usually where yours starts.
- Can anyone name, on Wednesday, who will pass 40 hours this week?If yes: the total exists. Check whether the person booking extra work sees it. If no, start with the Wednesday total by person.
- Do your cost reports price labor at one flat rate per person?If yes: the premium never reaches the job or department until the books close. Carry actual pay into costing or post the premium as its own line.
- Do people work on two jobs, at two locations, or at two pay rates in the same week?If yes: check that overtime is counted on the combined week and figured on the blended rate.
- Are hours edited in the payroll file after export?If yes: cost reports and payroll hold different weeks. Move every correction back into the system where time is recorded.
- Is weekend, evening or extra-shift work decided late on the day before?If yes: the overtime is a scheduling outcome. Put the hours list in front of whoever makes that call.
How it breaks in each industry
- HVAC, plumbing and electrical service
- A tech runs four or five calls a day, and the drive between them counts as hours worked. No single call looks long. The week does. Parts runs, shop meetings and the trip back to the yard sit on the timesheet as activities that never appear on any job report, so the overtime has no job to show up on.
- Commercial electrical and mechanical with prevailing wage work
- A journeyman splits a week between a federally funded job and a commercial job. Certified payroll for the public job asks for hours on that contract and in total, and federal overtime is owed on the combined week. Each project manager sees a normal week on his own job.
- Restaurants and hospitality
- A cook or server picks up a shift at a sister location, or swaps shifts with a coworker after the schedule is posted. Each location's schedule looks normal, and the combined week only appears when payroll adds the two time clocks together.
- Logistics and third-party warehousing
- Volume spikes are known late: a client's shipment lands a day early or a peak week runs long. Supervisors hold shifts over at the end of the day to clear the dock, and the hours pile onto the same people who already worked the week.
Where it breaks between systems
- ServiceTitan timesheet activities and overtime
- ServiceTitan treats every custom timesheet activity hour as a regular hour for its overtime calculation. Pay and earnings codes on those activities change only the Master Pay File and the payroll export, not the overtime math.[19]
- ServiceTitan job costing
- Hourly labor pay, including overtime, shows in the job costing tool only when the account is configured to include it. A technician's burden rate is a per-tech setting in the profile. Our reading: without the configuration, the job carries the typed rate, not the paycheck.[20]
- Viewpoint Vista payroll and job cost
- Daily overtime from a job's overtime schedule is calculated only on a single job or on jobs that share a schedule. Trimble's own example: six hours each on two jobs with different eight-hour schedules produces no overtime, because neither job passed eight. Craft templates are the documented way around it.[21]
- Jobber and Gusto
- Jobber offers weekly, daily, daily double and seventh-consecutive-day overtime settings for Gusto. Approved Jobber hours overwrite unprocessed Gusto payroll data, including manual edits made in Gusto.[22]
- Jobber job costing
- Jobber's job-costing article describes one labor cost rate per employee, multiplied by the time on the job, and does not mention overtime.[23]
- FieldEdge and QuickBooks
- FieldEdge posts time entries to QuickBooks as timesheets, but its time-based pay rules are not available to QuickBooks Online users, and a day cannot be posted until it is complete.[24]
- BuildOps and QuickBooks
- BuildOps says it handles basic overtime thresholds. For QuickBooks Online and Desktop customers, time goes out as a file for payroll import, and complex overtime rules may need manual adjustment on the QuickBooks side.[25]
- Housecall Pro Time Tracking
- With overtime rules on, Housecall Pro splits regular, overtime and double time, counting daily overtime before weekly when both are on. With the rules off, someone types the split by hand. Housecall Pro runs payroll itself on its Payroll Advanced and Advanced Plus plans.[26]
By the numbers
| Figure | What it measures |
|---|---|
| 44.3 and 44.9 hours[13] | Average weekly hours of all employees in heavy and civil engineering construction, September 2024 and September 2025, not seasonally adjusted (BLS Current Employment Statistics). Compare the same month across years only. |
| 40.0 hours[14] | Average weekly hours of production and nonsupervisory employees in construction, September 2026, seasonally adjusted, preliminary (BLS). These are paid hours, and the average crew member is already at the overtime line. |
| 3.1 hours, and no construction series[15] | BLS publishes average weekly overtime hours for manufacturing (3.1 in May 2026). It publishes no overtime series for construction, so there is no public benchmark for how much overtime a contractor should expect. |
| $30 to $40 billion[16] | Estimated loss to labor inefficiency in 2022 among labor-intensive contractors who put nearly $900 billion in place, from FMI's 2023 Labor Productivity Study (consultant). It measures labor waste in general, not overtime. |
| 62%[17] | Construction firms naming rising direct labor costs (pay, benefits, employer taxes) among their top three concerns for 2025, out of 1,109 responses to the AGC and Sage outlook survey. The survey did not ask about overtime. |
| 6.3%[18] | Net income before taxes as a share of revenue for construction companies in fiscal 2023, from 1,290 companies (CFMA 2024 Construction Financial Benchmarker). An unpriced overtime premium comes straight out of a margin this thin. |
Rules that apply
- 29 CFR 778.103, the workweek total[1]
- The employer must total all hours a person worked for it in the workweek, even across two or more unrelated job assignments, and pay overtime on every hour past the maximum. This is the person-week the job reports do not show.
- 29 CFR 778.104 and 778.105, each week stands alone[2]
- No averaging across weeks: 30 hours one week and 50 the next means 10 overtime hours in week two, whatever the pay frequency, and the rule covers pieceworkers too. The workweek is a fixed, recurring 168 hours that may start on any day and hour.
- 29 CFR 778.106, when overtime is due[3]
- Overtime is paid on the regular payday for the period in which the workweek ends. A delay is allowed only when the amount cannot be computed in time, and never past the next payday after it can be.
- 29 CFR 778.115, two rates in one week[4]
- A person who works at two or more rates in a week has a regular rate equal to the weighted average: total earnings divided by total hours. The premium is figured on that blended rate, not on the base rate.
- 29 CFR 785.11 and 785.13, work suffered or permitted[8]
- Work the employer did not request but knew about is work time, and a written rule against unapproved overtime is not enough by itself. Management has to enforce the rule. Hours already worked are owed either way.
- 29 CFR 541.3(a), trades are not exempt[9]
- Non-management carpenters, electricians, mechanics, plumbers, iron workers and laborers are entitled to overtime no matter how highly paid they are. A salary does not take a foreman who works with the tools out of overtime.
- 29 CFR 5.5(b)(1) and (b)(2), Contract Work Hours and Safety Standards Act[10]
- On covered federal contracts over $100,000, laborers and mechanics get time and a half past 40 in a workweek, and the contractor owes liquidated damages of $33 per affected worker for each calendar day of unpaid overtime, per the eCFR as of October 2026. DOL adjusts that figure for inflation each January.
- Nevada NRS 608.018, daily overtime with a pay condition[11]
- Nevada requires time and a half after 8 hours in a workday only for employees paid less than one and a half times the state minimum wage, unless they agree to four 10-hour days. Most journeymen earn above that line, so daily overtime often reaches apprentices and helpers only.
- DOL Fact Sheet 1, construction[12]
- The Labor Department lists paying overtime only after 80 hours in a two-week period as illegal, along with failing to combine hours worked in two job classifications in the same week and failing to pay for travel from the shop to the site.
Measure it in your own shop
From: Your payroll register for the last eight workweeks and the timesheet or time clock detail behind it, from your field system (ServiceTitan, Jobber, Housecall Pro, FieldEdge), Procore Timesheets or your scheduling system, plus your labor cost report by job, location or department for the same weeks.
- Export hours by person, by day, by job or location for the eight weeks, using your written workweek start.
- Total each person's hours per workweek across everything they worked and mark every week over 40.
- Add the overtime hours in the payroll register and compare them to the overtime hours, or premium dollars, that appear on the cost report for the same weeks.
- For each over-40 week, note the day the person crossed 40 and whether that day's work was booked in advance.
- For anyone paid two different rates in a week, recheck the premium on the weighted average rate.
Reading it: The gap between payroll overtime and cost-report overtime is the premium your reports never saw. The crossing days tell you whether overtime comes from late bookings, travel, covering shifts or a short staff, and the share booked in advance tells you how much of it was ever a choice.
What does not fix it
- A policy that all overtime needs approval
- Federal rules say a rule against unapproved work is not enough by itself, and hours that were worked are owed whether anyone approved them or not. The policy moves the argument to payday without moving the information to Wednesday.
- Paying overtime on the two-week total
- The Labor Department calls overtime only after 80 hours in a biweekly period illegal. Each workweek stands alone.
- A payroll integration that applies overtime rules
- It computes the premium correctly, after the week is worked. It does not tell the person booking Saturday that the only available person is at 38 hours.
- Telling people to keep it under 40
- The people doing the work rarely decide when the inspection was booked, when the shipment landed or when the extra Saturday was promised. One electrician on Reddit described being told at quitting time to stay because inspections were scheduled before rough-in could finish.
What to try this week
- Total by person on WednesdayPull hours to date for every hourly person across every job, location and shift, including travel between work sites, errands and meetings. Anyone at 32 hours or more on Wednesday goes on a short list.
- Write down when your week startsPick the day and hour your workweek begins and make the scheduling or time system, the payroll provider and the cost reports all use it. Federal records rules require you to keep it on file anyway.
- Make the scheduler check the list firstWhoever books Saturday work, an extra shift, an evening callout or a covering shift at another location looks at the Wednesday list before saying yes. If the only available person is on it, the overtime is now a decision instead of a discovery.
- Put the premium where the work happenedTurn on the setting that carries actual pay, including overtime, into job or department costing, or add the premium as its own line. A flat labor rate hides every overtime hour until the books close.
- Correct hours only at the sourceEdit a wrong punch in the system where time is recorded, then export again. A fix typed into the payroll file pays the person correctly and leaves the cost report wrong.
Where do-it-yourself stops
These steps make the week visible, but somebody still pulls hours out of the time system, adds them up by person and checks them against next week's schedule by hand. The lasting fix is a tool built around your scheduling and your payroll, so each person's week totals itself across jobs and locations as the hours come in, and the person booking the extra shift sees it before agreeing. That is what a Workflow Spec designs.
Questions people ask
Do we owe overtime if someone worked 30 hours on one job and 15 on another?
Yes, under federal law. 29 CFR 778.103 says to total all hours worked for you in the workweek, even on unrelated jobs, and pay time and a half on the 5 hours past 40. The same applies to shifts at two of your locations.
Can we pay overtime only when someone passes 80 hours in two weeks?
No. The Labor Department's construction fact sheet lists that practice as illegal. Each workweek of 168 hours is counted on its own, and averaging across weeks is not allowed.
Is a salaried foreman exempt from overtime?
Not if he works as a tradesman. 29 CFR 541.3(a) says non-management construction workers such as electricians, plumbers and carpenters are owed overtime however highly paid they are.
What if someone worked overtime nobody approved?
It is still owed. Under 29 CFR 785.11, work the employer knows about is work time. You can discipline for breaking an approval rule, but you pay the hours.
What does a missed overtime hour cost on a federal job?
On contracts covered by the Contract Work Hours and Safety Standards Act, the eCFR as of October 2026 sets liquidated damages at $33 per worker for each calendar day overtime went unpaid, on top of the wages.
Next step
How we fix this
This guide is how to find it and work around it. If it keeps coming back, it is rarely the only thing costing you. We come on site, find the issues costing you the most, and fix them, starting with the most pressing.
Fox & Santiago, Genesee, Idaho. We work nationwide, for clients across the United States, from our headquarters in Genesee, Idaho.
