After-hours service calls produce some of the highest-margin revenue a field service business can generate, and they produce some of the most disputed labor hours when the office gets the tracking wrong. The contractor who runs after-hours work on a clean tracking discipline collects every billable minute, pays the techs correctly under FLSA, and closes the books at month-end without the back-and-forth that consumes a Friday afternoon. The contractor who runs after-hours on guesswork loses minutes on every call, overpays or underpays the tech, and ends up arguing with both the customer and the crew on the same week. The five rules below cover what to track, how to track it, what to pay, what to bill, and what the audit trail needs. Each section opens with the rule, then walks through the mechanics.
What Counts as After-Hours
Quick rule: anything outside the contractor's posted business hours, plus weekends and federal holidays, plus the specific emergency-rotation hours the team carries on call.
The first place tracking goes sideways is the definition. After-hours is not a feeling; it is a defined window the business has to document in the employee handbook, post on the website, and apply consistently across every tech on payroll. A typical residential service business posts 7 a.m. to 5 p.m. Monday through Friday as standard hours; anything outside that window is after-hours. A commercial contractor with a 24/7 service contract has a different defined window per customer, and the after-hours definition applies per contract rather than across the board. The reason the definition has to be written down is that the FLSA overtime rules apply against the documented standard hours, not against what the office remembers each pay period. The tech who works 47 hours in a week (40 standard + 7 after-hours) is owed 7 hours at the overtime rate; the tech who works 47 hours in a week of disputed standard hours produces a wage claim the contractor will not enjoy responding to.
How to Track the Hours
Quick rule: tech opens the app at start, tech closes the app at end, dispatcher confirms the timestamps the next business day. No retroactive guessing.
The mechanics of after-hours time tracking matter more than the mechanics of standard-hours tracking because the after-hours billing rate is higher and the audit risk is correspondingly higher. The clean workflow is: the tech opens the mobile app at the moment they leave the house (or the truck if they were rolling toward another stop), the app captures the GPS timestamp, the tech adds the customer reference and the brief job description, the tech closes the app when the work is complete and they are back on the truck, and the dispatcher reviews the timestamps the next business day for any irregularities. Field-captured time tracking through the mobile app is the only practical way to get clean after-hours timestamps; retroactive logging at the office on Friday produces the same disputes the cleaner workflow prevents. The other piece is the tech-side discipline. The clock-in habit has to become automatic at the truck-door moment, the same way putting on a seatbelt is automatic at the driver's-door moment. The tech who treats the clock-in as an afterthought ends up reconstructing the hour at the office two days later, and the reconstruction is always slightly wrong in one direction or the other.
What Pay Rate Applies
Quick rule: standard structure is 1.5x base for after-hours weeknight, 2x base for holidays, plus a fixed call-out fee that compensates the tech for showing up at all.
The pay-rate structure for after-hours work splits along two axes: the multiplier on the labor rate and the flat call-out fee. The multiplier is the FLSA requirement (1.5x for overtime past 40 hours per week is the federal floor; many states require 1.5x for any hour past 8 in a single day, and a handful require 2x past 12 hours in a single day). The call-out fee is the contractor's policy, not a legal requirement; the typical structure is a 1-to-2-hour minimum at the after-hours rate even if the tech is on-site for 15 minutes. The call-out fee compensates the tech for leaving home at midnight; the multiplier compensates the tech for working past standard hours. Both apply on most after-hours calls; the office that only applies one or the other is either underpaying the tech (legal exposure) or overpaying (margin erosion). The math compounds across the year: a five-truck business running 200 after-hours calls per year at the right rate structure collects $20,000 to $40,000 more in after-hours revenue than the same operation running the wrong rate structure, and the techs are happier because the pay is correct on the stub. The pricing math also pairs with the broader cost-stack discipline the office runs at the install-quote level, because the burdened-labor rate that feeds the after-hours multiplier is the same rate that drives the install pricing math.
How to Bill the Customer
Quick rule: disclose the after-hours rate at dispatch, before the truck rolls, in writing if possible.
The single biggest source of after-hours customer disputes is rate surprise. The customer who called at 11 p.m. about a leaking water heater agreed to "send someone" without ever being told the after-hours rate is 1.5x standard plus a 2-hour call-out minimum. The customer who hears the rate at the kitchen table after the invoice is presented disputes the bill. The customer who hears the rate from the dispatcher at intake (and confirms with a "yes, please send the tech anyway") pays the invoice without complaint. Disclose the rate at the intake call, repeat it in the dispatch confirmation text or email, and document the customer's verbal authorization with a timestamp. The contractor who handles the rate conversation cleanly at dispatch never has the conversation at the invoice presentation; the contractor who skips the dispatch disclosure has the conversation at day 30 of the AR aging cycle instead, which is the worst possible time to have it. The disclosure also belongs in the dispatcher's intake script as a standing line item so it gets said the same way on every after-hours call rather than improvised by whichever dispatcher answers the phone.
What the Audit Trail Needs
Quick rule: five fields per call. Clock-in timestamp, clock-out timestamp, customer reference, work performed, pay tier applied (standard, overtime, holiday).
The audit trail is what protects the business across three scenarios: a tech wage claim, a customer billing dispute, and a Department of Labor audit. All three look at the same data and ask different questions of it. The wage claim asks "did the tech get paid correctly per FLSA?" The billing dispute asks "did the customer get charged the rate they were quoted?" The DOL audit asks "is the contractor classifying hours correctly across the workforce?" Capturing the five fields per call on a clean tracking system answers all three questions with the same data set. The contractor running on memory and paper tickets has to reconstruct each scenario from sparse data; the contractor running on a clean tracking system pulls the report in fifteen seconds. The audit trail also feeds the broader SOP discipline the office runs on every operational workflow, and the monthly financial review that catches the rate-tier errors before they compound across the quarter. After-hours time tracking is one of those operational habits that looks like overhead when the business is small and looks like the foundation of a scalable operation when the business grows past one truck.
The compound benefit of running the five rules consistently shows up in three places: the pay stub the tech reads on Friday (correct rate every time, no disputes), the invoice the customer reads (correct rate every time, no surprises), and the year-end labor expense the accountant reads (every after-hours hour classified correctly, no FLSA exposure). The contractor who treats after-hours tracking as a craft worth doing well stops thinking about it inside three months because the system runs on its own; the contractor who treats it as a Friday-afternoon reconciliation task is still thinking about it on Friday afternoon three years later. The same tracking layer also feeds the broader dispatch management discipline the office runs across both standard and after-hours rotations. The compound runs in one direction.
Smart Service for Field Service
If you are running a field service business and want a software stack that handles scheduling, dispatch, customer history, mobile invoicing, and the field-captured time tracking that anchors a clean after-hours workflow, Smart Service integrates with QuickBooks Desktop and QuickBooks Online and iFleet keeps techs in the field synced with the office. Try a free demo to see how it fits!
