PunchDo You Have to Pay Employees for On-Call Time? (FLSA On-Call and Waiting Time Guide 2026)
Do You Have to Pay Employees for On-Call Time? (FLSA On-Call and Waiting Time Guide 2026)
The short answer: It depends on how restricted the employee is. Under the FLSA, on-call time is paid when the worker cannot use the waiting period for their own purposes, and unpaid when they are free to live their life and just leave word where they can be reached. The line is called "engaged to wait" versus "waiting to be engaged." Once an on-call worker is dispatched and starts a job, that time is always hours worked. A time-tracking app like Punch lets a tech punch in the moment a call comes in, records where and when, and rolls the hours into the overtime math automatically.
On-call rotations are standard for HVAC, plumbing, IT, property management, and emergency service teams. They are also one of the quietest sources of wage claims, because owners assume on-call means unpaid until proven otherwise. Sometimes that is right. Sometimes it is a back-pay problem waiting to happen. This guide explains the test the Department of Labor actually uses, then shows how to keep clean records when a call comes in at 2 a.m.
Waiting Time Is the Foundation
Before on-call, understand waiting time. The DOL treats an idle period one of two ways, and the whole question turns on which one applies.
Under 29 CFR 785.15, an employee is on duty when waiting is an integral part of the job. The regulation gives the classic examples: a receptionist reading a book between calls, a messenger doing a crossword while awaiting an assignment, a firefighter playing checkers while waiting for an alarm. All of them are working during the quiet stretches because they are engaged to wait. The employer controls the time, so the employer pays for it.
Under 29 CFR 785.16, an employee is off duty when they are completely relieved from duty for a period long enough to use effectively for their own purposes. That time is not hours worked. The employee owns it.
The general principle in 29 CFR 785.14 is that there is no mechanical rule. Whether waiting time is work depends on the agreement between the parties, how they actually behave, the nature of the service, and all the circumstances. Courts look at the real restriction on the worker, not the label on the schedule.
On-Call: Engaged to Wait vs. Waiting to Be Engaged
On-call time is the specific version of that question, and 29 CFR 785.17 draws the line.
An employee who is required to stay on the employer's premises, or so close to it that they cannot use the time for their own purposes, is working while on call. They are engaged to wait, and the hours are paid. An employee who is not required to stay on the premises and only has to leave word where they can be reached is generally not working while on call. They are waiting to be engaged, and the standby hours are unpaid until a call actually comes in.
The premises rule is the anchor, but courts weigh the practical burden of the restrictions, not just the physical location. Factors that push on-call time toward paid include:
- A required response time so short the worker cannot really leave home or must stay near the shop.
- A geographic limit that keeps them inside a tight radius.
- A call volume so high that the worker is interrupted constantly and can never settle into personal time.
- Rules against activities like drinking, traveling, or being unreachable for even a few minutes.
- A ban on trading or covering the shift with anyone else.
Factors that push on-call time toward unpaid include a generous response window, the freedom to be anywhere as long as they answer the phone, infrequent calls, and the ability to swap the rotation. A plumber who must reach any job in the metro within 30 minutes, cannot leave the county, and gets paged six times a night is closer to engaged to wait. A plumber who carries a phone, can be at dinner or a kid's game, and gets called maybe once a week is closer to waiting to be engaged.
The Moment a Call Comes In, the Clock Starts
Here is the part that is not ambiguous. Whatever you decide about standby hours, the work itself is always paid. The instant an on-call employee is dispatched and begins responding, they are on the clock.
That includes the phone diagnosis if it is substantial, the drive to the site under 29 CFR 785.38 because travel during the workday is hours worked, the repair, and the drive to the next call if there is one. Many employers who correctly treat standby as unpaid still get the callout wrong, either by rounding a 90-minute emergency down to an hour or by forgetting the drive time. Those are the errors that add up across a year of night calls.
If your on-call pay policy pays a flat standby stipend plus hourly for actual work, that stipend has its own consequence, covered next.
On-Call Pay and the Overtime Trap
On-call work does not live in a separate world from overtime. Every hour a dispatched tech works counts toward the 40-hour weekly overtime threshold under 29 CFR 778. A worker who logs 38 regular hours during the week and then answers two callouts totaling 5 hours has worked 43 hours, and 3 of them are overtime at 1.5 times the regular rate.
Flat on-call stipends complicate the regular rate. If you pay a set amount for carrying the pager, the DOL generally treats that money as part of the regular rate of pay, which raises the overtime rate for the week. A stipend you thought was a simple perk can quietly bump the multiplier on every overtime hour. This is exactly the kind of calculation that goes wrong on a paper timesheet, because the person doing payroll rarely reconstructs which hours were callouts, what the stipend was, and how the blended rate shifts.
Getting this right is not about paying more. It is about paying the correct amount and having the records to prove it if a claim ever lands.
How to Track On-Call Time the Right Way
The reason on-call pay causes disputes is that the work happens at the worst possible time for good record-keeping. It is late, the tech is tired, and the last thing on their mind is writing down a start time. Memory fills the gap at payroll, and memory is where back-wage exposure lives.
Punch removes the memory step. When a call comes in, the on-call tech opens the app and punches in. The start time is stamped the moment they tap, not reconstructed later. They punch out when the job is done. The record is exact, it carries a timestamp, and it is there whether the callout was at noon or 2 a.m.
A few product details that matter for on-call teams:
- Callout hours flow straight into overtime. Punch counts every dispatched hour toward the weekly threshold and calculates the overtime premium for you, using the 50-plus country overtime presets it ships. You see regular hours, callout hours, and overtime on one paid breakdown, with no side spreadsheet.
- Drive time can carry its own rate. If your callout policy pays a separate drive rate, Punch tracks travel as its own kind of time and runs the weighted-average overtime math the FLSA requires. Travel is movement, so it is never geofenced to a site.
- Punches survive dead zones. A tech driving to a rural emergency with no signal can still punch in. The record queues offline and syncs when service returns, so the 2 a.m. callout never goes missing.
- A manager approves the callout the next morning. On-call hours land in the approval queue with the rest of the week. An owner or manager can review the timestamp, approve or bulk-approve, and move on.
- A geofence verifies the job, never a camera verifies the tech. Punch confirms an on-site punch-in with GPS, not facial recognition or a photo at the punch. On-call workers are already stretched thin. They should not also have a camera in their face at midnight. Trust beats surveillance.
Punch does all of this on every plan. Pricing is flat per organization, owners are always free, and every feature is included on every tier, so an on-call rotation does not cost extra per seat the way it would on a per-user competitor.
The Bottom Line
On-call pay comes down to one honest question: how much freedom does the worker really have while waiting? If the restrictions are heavy enough that they cannot use the time for themselves, the standby hours are paid. If they can live their life and simply answer the phone, the standby is unpaid until a call arrives. But the callout itself, the drive, and the repair are always hours worked, and they always count toward overtime.
The safe posture is exact records. Punch captures the real start and stop of every callout, folds those hours into the overtime math, and gives a manager a clean record to approve, so a night of emergency work never turns into a payroll guess or a wage claim.
This article is general information, not legal advice. Some states set their own on-call, reporting-time, and call-in pay rules that are stricter than the FLSA. Confirm your obligations with an employment attorney or your state labor agency.
Sources: