Do You Get Paid for Being On Call Overnight? A Q&A

The following is a constructed conversation, written to walk through a real area of federal wage law using a common real-world scenario. Neither participant is a real, named individual.

Worker: My manager wants me reachable by phone every night this week, in case a server goes down. I don’t get an hourly on-call rate, just my regular salary. Is that actually legal?

Advocate: It might be, and it might not be — the law doesn’t give you one clean rule to check it against. The relevant regulation is 29 CFR 785.17, and it splits on-call time into two categories with a name each: “waiting to be engaged,” which is usually unpaid, and “engaged to wait,” which usually has to be paid like any other work.

Worker: What’s the actual difference between those two?

Advocate: How much of your night you get back. The Supreme Court dealt with almost this exact question in 1944, in Skidmore v. Swift & Co. A group of employees at a meatpacking plant had to stay at the company’s facility overnight, ready to respond if a fire alarm went off, but they were otherwise free to sleep, play cards, and use the time as their own. The Court didn’t say that setup was automatically paid or automatically unpaid. It said no single rule could be drawn between “waiting to be engaged” and “engaged to wait,” and that the answer depends on the facts and circumstances of the particular arrangement, evaluated case by case.

Worker: So eighty years later, there’s still no simple test?

Advocate: There’s no bright line in the statute, but courts applying it since have converged on a consistent set of questions, even without a fixed formula. How far from home do you have to stay? Can you leave the house at all, or run errands, or is your entire radius the reach of your phone? How fast do you have to respond, minutes or hours? And realistically, how often do you actually get called, versus how often the phone just sits there? A geographic tether and a five-minute response window look a lot more like being engaged to wait. A phone that can ring while you’re at a movie, with an hour to respond, looks a lot more like waiting to be engaged. And however that gets classified, don’t be surprised if the employer wants proof you actually picked up and responded rather than just taking your word for it — the same instinct that’s pushed a lot of workplaces toward fingerprint and face-scan time clocks for regular shifts, with a comparable legal mess attached in states like Illinois.

Worker: My situation is the tight version. Fifteen-minute response window, and I can’t leave my apartment because the WiFi has to be reliable enough to remote in.

Advocate: That’s a real restriction on how you spend your own night, more than just a phone sitting on the nightstand. A fifteen-minute leash that also pins you to one location for reliable internet is closer to the “engaged to wait” side of the line than the “waiting to be engaged” side, and an unpaid arrangement built on facts like that is worth raising with your employer, or with your state labor department if that goes nowhere internally. States can and do set stricter standards than the federal floor, so check your own state’s rule too. It’s a different legal question from whether an employer can legally require proof you woke up at all, but the two come from the same instinct: an employer wanting certainty about hours it isn’t fully willing to pay for.

Worker: What actually happens the night I do get paged? Does that part get paid regardless?

Advocate: Yes, almost always, and that part isn’t really in dispute the way the standby time is. Once you’re actually working, whether that’s answering a call, remoting into a server, or driving somewhere, that time is compensable under ordinary wage rules, on-call classification aside. The live legal question is only about the hours you’re tethered but not actively doing anything.

Worker: Practically, what do I do with all this?

Advocate: Write down plainly what your actual restrictions are: the response window, the geographic limits, how often you’re called, whether you can sleep a normal night through it. That’s the fact pattern a court or a labor department asks about, and having it down before any dispute makes the conversation with an employer or an agency far more concrete than a general complaint that on-call “feels like work.” It usually does feel like work. Whether it legally is comes down to those facts, not the feeling. The same instinct shows up on the other side of a shift, too — some states require partial pay when you’re the one who showed up and the work wasn’t there.

---

This whole legal question is separate from what actually gets someone up at 2 a.m. when the page comes in, an older problem this site spends most of its time on; being startled awake reliably is a different question from whether the hour before the page counted as paid work. Knowing which category your on-call setup falls into takes five minutes with a notepad, before the next unpaid week of it goes by unquestioned.

FAQ

Is on-call time legally considered work? Sometimes. 29 CFR 785.17 splits it into “waiting to be engaged” (usually unpaid) and “engaged to wait” (usually paid), with no single bright line — courts weigh the actual restrictions case by case.

What factors decide whether on-call time must be paid? How far from home you must stay, how quickly you must respond, how often you’re actually called in, and whether the restrictions leave enough time for your own activities, like sleeping a full night.

What is the Skidmore v. Swift case? A 1944 Supreme Court case involving employees required to stay at a plant overnight in case of a fire alarm, free to sleep and use the time otherwise. The Court declined a fixed rule, holding that compensability depends on the facts of each arrangement.