Your IT technician carries the company phone all weekend, can't leave town, and has to answer within 15 minutes if a server goes down. No calls come in. Monday morning, do you owe them two days of wages — or nothing at all?
Under the Fair Labor Standards Act, the question is never "were they working?" It is "were they free?" If your on-call rules keep an employee from using the time for their own purposes, those standby hours are paid work time — and they count toward overtime. Get it wrong across a whole crew for a whole year, and the liability adds up fast.
This guide walks through how the Labor Department draws the line, the control factors that decide your case, the special rules for sleep time, the overtime math almost everyone flubs, the state laws that go further than federal rules, and how to build an on-call policy that keeps restriction-free standby genuinely unpaid.
The One Question: Engaged to Wait or Waiting to Be Engaged?
Federal regulations frame every on-call dispute the same way. An employee who is "engaged to wait" is working and must be paid. An employee who is "waiting to be engaged" is off duty and need not be paid. The entire inquiry collapses into a single test: can the employee use the time effectively for their own purposes, or does the employer's control make that impossible?
Two textbook examples set the poles. A paramedic who plays cards at the station between emergency calls is engaged to wait — paid, even while dealing the hand. An employee who goes home, leaves word where they can be reached, and lives their evening freely is waiting to be engaged — unpaid, until the phone actually rings. Time spent responding to a call is virtually always compensable, even when the standby time before it was not.
Notice what the test is not. It is not whether the employee was busy, where they waited, or what the handbook calls the arrangement — "standby," "on-call," and "callback" labels decide nothing. What decides is control.
The Control Factors That Decide Your Case
Investigators weigh these restrictions together — no single factor decides, but together they answer the freedom question:
Where must the employee stay? Requiring someone to remain on your premises — or so close that they cannot leave — points strongly toward paid time. Letting them stay home, run personal errands, and move around their community points the other way. Geographic restrictions are among the heaviest factors: the tighter the leash, the more likely the hours are compensable.
How fast must they respond? A 10- or 15-minute callback window effectively pins an employee in place; they cannot go to a movie, take their kids to the park, or do much of anything except wait by the phone. A one- or two-hour window leaves room for a real personal life. Short response times are one of the most common reasons at-home on-call arrangements get reclassified as paid.
How often does the phone actually ring? A rotation interrupted three times a night is not time anyone can use for themselves, whatever the policy says. Pull your actual call data before concluding the burden is light.
Can they trade shifts or decline? An employee who can freely swap on-call weeks, decline a rotation without penalty, or hand off the pager looks genuinely free. One locked into a mandatory rotation with discipline for missed calls looks controlled. Document that swaps are allowed and actually happen.
What happens if they miss a call? Discipline is the tell. If a missed page triggers a write-up, the standby time was a duty, not a convenience. Reserve discipline for employees who are actually on the clock, and keep voluntary callback lists separate from mandatory rotations.
Are they confined to a uniform, a vehicle, or monitoring equipment? Staying in uniform, remaining with a company vehicle, or actively monitoring screens during standby all signal control. A phone in the pocket while life goes on signals freedom.
If most factors point toward control, budget those hours as paid time rather than betting an investigator will see it differently.
At Home vs. On Site: Why Location Is Evidence, Not the Rule
Many small employers assume "at home equals unpaid." That is the most expensive misconception in this area. Location is just one piece of the control analysis.
An employee stuck at your facility overnight "just in case" is the easy case: on-premises standby where the employee cannot come and go is compensable hours worked. The harder and more common case is the at-home rotation with strings attached — stay within 20 minutes of the shop, answer within 10 minutes, no alcohol, remain sober and dressed, keep the company laptop open. Stack enough of those conditions and you have recreated the station house in the employee's living room. Investigators will treat it that way.
The genuinely unpaid at-home arrangement looks like this: the employee is wherever they choose, reachable by phone, with a reasonable response window, infrequent actual calls, and the freedom to eat, sleep, shop, and socialize. When a call comes, the response time is paid — including travel if you require them to report in. Write the policy to protect each freedom explicitly, and make sure supervisors do not layer on verbal extras ("stay close tonight, it's been busy") that contradict it.
Sleep Time and 24-Hour Shifts: The Rules Within the Rules
Overnight and live-in arrangements get their own federal rules, and they surprise a lot of employers.
Shifts of 24 hours or more. When an employee is on duty for 24 hours or longer, you and the employee may agree to exclude a bona fide sleep period of up to 8 hours — but only if you provide adequate sleeping facilities and the employee can actually get at least 5 hours of uninterrupted sleep. If the night brings interruptions that prevent 5 hours of unbroken sleep, the whole sleep period counts as paid time. The agreement to exclude sleep must be express; you cannot simply assume it.
Shifts under 24 hours. An employee required to be on duty for less than 24 hours is considered to be working the entire time, even if they are permitted to sleep during downtime. The overnight security guard on a 12-hour shift who dozes between rounds is on paid time all 12 hours. There is no sleep exclusion for sub-24-hour shifts, no matter how quiet the night.
Employees who reside on the premises. A live-in caretaker, apartment manager, or ranch hand who resides on your property for an extended period is not considered working all the time they are there. You and the employee may reasonably agree on which hours are work and which are free time for meals, sleep, and personal pursuits. Put that agreement in writing, revisit it when duties change, and keep records of the hours actually worked — "resides here" is not a timesheet.
Match your situation to the right rule, get the required agreement signed, and keep interruption logs that back you up.
The Overtime Math Almost Everyone Gets Wrong
Here is where compliant intentions still produce violations. Three payroll mechanics trip up small employers again and again:
Paid on-call hours count toward the 40. Compensable standby hours are hours worked. If a technician works 36 regular hours plus 8 paid on-call hours in one week, that is 44 hours worked — 4 of them at time-and-a-half. Employers who pay on-call hours at straight time and stop there owe the missing half-time premium.
Flat on-call stipends must be folded into the regular rate. Many businesses pay a flat amount per on-call shift — say $50 per night — that the regulations would not otherwise require. That stipend still counts as compensation for overtime purposes: it must be included when computing the employee's regular hourly rate for that week, which raises the overtime premium. The Labor Department's position is that the stipend is attributed to the specific workweek in which the on-call hours occurred, not smoothed across pay periods. If your payroll system books stipends as non-wage bonuses excluded from the regular rate, fix that mapping now.
Response time starts the clock. Even under a valid unpaid standby arrangement, every minute spent answering the call, diagnosing the problem, driving to the site, and performing the work is paid time. Remote logins count. The 20-minute "quick check" from the couch at 11 p.m. counts. Make sure employees have a frictionless way to log these fragments — a mobile time entry, a callback log, a simple form — because unrecorded fragments are the raw material of collective back-pay claims.
Self-audit one recent pay period: add paid standby hours into weekly totals, recompute the regular rate with stipends included, and confirm logged response fragments made it onto the timesheet.
State Laws That Go Further Than Federal Rules
The FLSA is the floor, not the ceiling. Several states add obligations that catch multi-state and relocating employers off guard:
California applies a control test of its own to standby time and layers on reporting-time pay: an employee who reports for work but is given less than half the scheduled shift (with minimums) is owed partial pay anyway. California courts have treated a required pre-shift check-in call — phoning in two hours early to learn whether an on-call shift is activated — as reporting to work that triggers that minimum. If you run California on-call rotations, the check-in procedure itself can create a wage obligation even when the employee never leaves home.
City predictive-scheduling ordinances in places like San Francisco, Emeryville, New York City (retail and fast food), Philadelphia, and Seattle require advance notice of schedules, extra pay for late changes, and in some cases pay for on-call shifts even when no work is performed. These ordinances typically cover retail, food service, and hospitality employers above a size threshold — exactly the businesses most likely to use on-call scheduling.
Massachusetts and several other states require minimum pay when a scheduled employee reports and finds little or no work — typically three hours at minimum wage in Massachusetts. A few states extend similar minimums to specific groups or situations.
New York considered sweeping call-in pay regulations that would have mandated minimum payments for on-call and last-minute scheduling changes, then dropped the effort — but New York City's Fair Workweek law still constrains covered retail and fast-food scheduling. The lesson travels: check the city, not just the state.
Before rolling out one national on-call policy, map every state and city where your employees work and overlay the local premiums, minimums, and notice rules.
Fresh 2026 Guidance Worth Knowing
The Labor Department has been active on hours-worked questions this year, and three opinion letters are directly useful context for on-call administration:
- Mandatory pre-shift time counts. Required roll calls and similar pre-shift duties are compensable hours worked, even under a union contract that says otherwise. Audit your own equipment checks, briefings, and logins with the same lens.
- Off-the-clock fragments face exacting scrutiny. The Department warns that de minimis defenses get hard looks when off-the-clock work happens regularly. A two-minute login here and a five-minute callback there, repeated nightly, is a pattern — not de minimis. Log it and pay it.
- Remote and mobile work boundaries are tightening. Recent guidance distinguishes passively receiving an automated page (likely not compensable alone) from the calls, scheduling, and coordination that follow (compensable). Real phone work counts regardless of where it happens.
The enforcement direction is toward counting more fragments, not fewer. Build timekeeping that captures small increments rather than defending their exclusion later.
How to Build a Restriction-Free On-Call Policy
If you want standby time to be genuinely unpaid, engineer the freedom deliberately. Use this checklist when drafting or revising your policy:
- Put response windows in writing — and make them livable. Specify a callback window (an hour is far safer than 15 minutes) and a separate on-site arrival window. Train supervisors never to demand faster responses verbally than the policy promises.
- Rotate and allow swaps. Spread on-call duty across the largest practical pool, publish rotations in advance, and let employees trade freely without managerial approval hurdles. Keep records showing swaps actually occur.
- Drop restrictions you do not need. Every rule — sobriety requirements beyond safety needs, geographic limits, uniform mandates, monitoring duties — is a control factor Exhibit A. Keep only what the work truly requires, and document the business reason for each.
- Separate mandatory rotations from voluntary lists. If missing a call carries discipline, that rotation is a duty assignment — budget it as paid or redesign it. Maintain any truly voluntary callback list under different rules with no penalties.
- Pay for every response minute. Provide a dead-simple logging method for callbacks, remote logins, and travel, and pay it at the applicable rate with overtime math done right. Review logs monthly for unlogged patterns (same employee, same 2 a.m. server restart, zero entries).
- Handle sleep and live-in situations with signed agreements. For 24-hour-plus shifts, execute the express sleep-time exclusion agreement, provide real sleeping quarters, and track interruptions against the 5-hour rule. For resident employees, agree in writing which hours are work.
- Overlay state and city rules before publishing. Add the California check-in safeguard, city predictability premiums, and local minimum-pay rules as addenda so one policy flexes per jurisdiction.
- Train the supervisors, not just the handbook. Most violations are created by a manager's text message, not the written policy. Annual wage-and-hour refreshers for anyone who assigns on-call duty cost far less than one investigation.
Review the policy yearly or whenever duties, technology, or staffing change — a rotation that was restriction-free with six techs and rare pages can become controlled standby with three techs and nightly alerts.
Keep Your On-Call Records Audit-Ready
None of the above works without records. Separate standby hours from regular hours in your timekeeping, track stipends as their own pay code so the regular-rate calculation can find them, log response fragments with dates and durations, and retain payroll records for at least three years. When standby hours, stipends, and response minutes each flow into distinct general-ledger accounts, the overtime math becomes a report instead of a forensic exercise — and if an investigator ever asks, the answer is already reconciled.
Simplify Your Financial Management
As you tighten up on-call scheduling, overtime math, and payroll recordkeeping, maintaining clear financial records is what turns compliance effort into lasting control. Beancount.io provides plain-text accounting that gives you complete transparency over your payroll accounts and labor costs — no black boxes, no vendor lock-in. Get started for free and see why developers and finance professionals are switching to plain-text accounting.