How to Create an On-Call Schedule
What is an on-call schedule? The rotation types, the FLSA on-call pay rules, the scheduling laws, and how to build an on-call schedule for a small team.
On-Call Scheduling
The rotation types, the pay rules, the scheduling laws, and how to build one
The first time I set up an on-call rotation, I got the scheduling part right and the pay part completely wrong. I assumed that because my on-call person was at home, not doing anything, I did not owe them for that time. Mostly that was correct, but I had no idea the answer depended on how tightly I restricted them.
Getting the on-call pay question wrong can mean back pay. On-call scheduling is one of those areas where the calendar is the easy part and the compliance is where the real risk lives. This guide, written for a small business owner, covers the scheduling, the pay, and the law together.
On-call means employees are available during set periods, ready to respond if needed, without actively working the whole time. It is essential for businesses with unpredictable demand in healthcare, retail, hospitality, and field service. It also comes with two things most guides skip: pay rules that decide when on-call time must be compensated, and scheduling laws that in some places restrict on-call entirely.
Below you will find what on-call scheduling is, the rotation types, how to build a schedule, the federal pay rules, the scheduling laws, how to write a policy, and best practices. Your scheduling and time-tracking tools run the rotation; I built FirstHR to hold the on-call policy and signed acknowledgments behind it. This is general information, not legal advice, so confirm current rules with counsel.
What Is On-Call Scheduling?
On-call scheduling is the practice of assigning employees to be available to work during specified periods, ready to come in or respond if needed, even though they are not actively working the entire time. It provides coverage for unpredictable demand, ensuring someone is ready to handle issues, emergencies, or coverage gaps that fall outside normal staffing.
On-call scheduling is common in industries where problems do not keep business hours. A hospital needs a nurse or physician reachable overnight; a property-management company needs someone available for maintenance emergencies; a retailer may want backup staff ready for unexpected rushes or call-outs.
In all three examples, the business cannot justify having someone actively working at all times, but it needs someone ready to work on short notice, which is exactly what on-call provides.
One clarification up front: the term is ambiguous. On-call scheduling also refers to IT and software teams, where engineers are on call to respond to system outages and the rotation runs on specialized incident-response tools. That is a related but distinct world with its own software.
This guide is about the workforce and HR meaning: on-call for employees in healthcare, retail, hospitality, and field service, which is what most small businesses need. The scheduling principles are similar, but the context and tools differ. If you landed here looking for incident response, the rotation mechanics below still apply.
Types of On-Call Rotations
The heart of a good on-call schedule is the rotation: how you cycle the on-call responsibility across your team so coverage is reliable and the burden is shared fairly. Five common types are weekly, primary and secondary, weekday and weekend split, follow-the-sun, and ad-hoc. The right one depends on your coverage needs and team size.
| Rotation type | How it works | Best for |
|---|---|---|
| Weekly rotation | Each person takes on-call duty for a full week in turn | Steady coverage needs; simple and predictable |
| Primary and secondary | A first responder is backed by a second person | Ensuring coverage if the primary is unreachable |
| Weekday / weekend split | Separates the less desirable weekend duty | Sharing the burden of unpopular weekend coverage |
| Follow-the-sun | Coverage passes across time zones around the clock | Distributed teams avoiding overnight shifts |
| Ad-hoc / as-needed | On-call assigned only when specifically required | Occasional or seasonal coverage needs |
For most small businesses, weekly rotation with a primary-and-secondary structure is the practical default. Weekly rotation is simple to understand and administer, and pairing each on-call person with a backup means coverage does not fail if the primary is unreachable or already handling something. The backup layer matters more than people expect, because the whole point of on-call is reliability, and a single point of failure undermines it.
That structure fits on one page. Fill in three months at a time so people can see their turn coming, and keep the swap column, because an informal swap nobody wrote down is how a night ends up with no coverage.
| A | B | C | D | E | F | G | H | I | J | K | |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Week starting | Primary on call | Primary contact | Backup on call | Backup contact | Coverage window | Required response time | Holiday in this week | Swap agreed with | Swap approved by | Notes |
| 2 | Replace this row with your first week | [Name] | [Name] | Weeknights and weekend, outside staffed hours | As written in your on-call policy | Publish as far ahead as you can. Some places require advance notice | |||||
| 3 | |||||||||||
| 4 | |||||||||||
| 5 | |||||||||||
| 6 | |||||||||||
| 7 | |||||||||||
| 8 | |||||||||||
| 9 | |||||||||||
| 10 | |||||||||||
| 11 | |||||||||||
| 12 | |||||||||||
| 13 |
No law sets a minimum size for a rotation, so the practical test is how often each turn comes around. Count the weeks between one person's turns, and when that gap narrows to one or two, add people rather than letting the same names absorb every week. Sharing weekend and holiday on-call fairly matters just as much as rotation size.
How to Create an On-Call Schedule
Building an on-call schedule takes six steps, from defining your coverage needs to tracking the hours people actually work. Working through them in order, rather than ad hoc, is what makes the schedule fair and reliable.
The step small businesses most often underestimate is the last one: tracking. On-call scheduling creates two things to track: the availability itself and the hours actually worked when someone is called in, and both matter.
Time actually worked while on call is always paid and counts toward overtime, so it must be captured accurately. Getting the schedule right is only half the job; tracking what actually happens is the other half.
The log below is the half that gets skipped. One line every time somebody is contacted, filled in the same week rather than reconstructed from memory: who was reached, how long they took to answer, whether the call fell through to the backup, and how long the work ran.
The hours go onto the week's timesheet, where the standby-versus-call-time split and the overtime check happen. The second tab totals the same rows by week, which is how you find out that one person has been carrying the rotation without saying so.
| A | B | C | D | E | F | G | H | I | J | K | L | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Date | Rotation week | Who was contacted | Primary or backup | Time contacted | Time they responded | Response window met | Fell through to the backup | Handled remotely or on site | Hours worked, to the timesheet | What the call was | Reviewed by |
| 2 | Replace this row with your first call-out | [Name] | Primary | Yes / No | No | Remote | Short description of the issue | |||||
| 3 | ||||||||||||
| 4 | ||||||||||||
| 5 | ||||||||||||
| 6 | ||||||||||||
| 7 | ||||||||||||
| 8 | ||||||||||||
| 9 | ||||||||||||
| 10 | ||||||||||||
| 11 | ||||||||||||
| 12 | ||||||||||||
| 13 |
Where the On-Call Calendar Lives
The rotation only works if people can see it without having to ask. Put the on-call calendar in whichever shared calendar your team already opens every morning, one event per rotation week, with the primary and backup names in the event title and both phone numbers in the details. A group chat thread is not a calendar.
Publish a quarter at a time and keep one shared entry rather than sending individual invitations, so a swap is a single edit everybody sees. When somebody does swap, change the event and add the swap to the rotation sheet above: the calendar answers who is on call tonight, and the sheet records who agreed to it and when.
On-Call Pay Under the FLSA
Once the rotation is in place, the question that gets employers into real trouble is simple to ask: when do you owe on-call pay for time employees spend waiting rather than actively working? Under the Fair Labor Standards Act (FLSA), the answer turns on a single principle: how much the job restricts what the employee can do with that time.
The FLSA draws a line between being engaged to wait and waiting to be engaged. If an employee is engaged to wait, they are effectively working while waiting, because they cannot use the time for their own purposes, and that time is paid.
An employee merely waiting to be engaged is free to use the time largely as they wish while staying reachable, and that time is generally not paid. The federal on-call regulation, 29 CFR 785.17, puts it plainly: the question is whether the employee can use the time effectively for their own purposes.
In practice, location and restriction decide which side of the line you are on. Between the two extremes, a very short required response time or a tight geographic radius can tip reachable-at-home on call into paid time, because they prevent the employee from using the time effectively.
Whatever the arrangement, time actually spent working once called is always paid, and it can trigger overtime if it pushes the week past 40 hours.
Two more points matter for getting this right. First, whether an employee is exempt or non-exempt changes the analysis, because the on-call pay rules apply only to non-exempt (overtime-eligible) employees. Classify before you build the rotation, so you know which part of your team the pay question covers.
Second, state law sits on top of the federal floor, and reporting-time pay is one example. Seven states and the District of Columbia require it when an employee reports for a scheduled shift and is sent home early. The seven states are California, Connecticut, Massachusetts, New Hampshire, New Jersey, New York, and Rhode Island, per SHRM.
Reporting-time pay rules vary in reach. Connecticut's rule applies only in certain industries, such as retail, and Oregon has a similar rule that covers only minors. A missed state rule can mean back pay, so confirm your own rules with counsel.
Scheduling Laws That Affect On-Call
Beyond pay, a second body of law affects on-call scheduling: predictive scheduling, or Fair Workweek, laws. These are relatively new and apply only in certain places, but where they apply, they can significantly restrict or even prohibit on-call scheduling, so covered employers must know about them.
Some jurisdictions go further and restrict on-call outright. Under the New York City Fair Workweek rules, covered retail employers cannot schedule workers for on-call shifts at all. Those workers can also turn down extra time offered less than 72 hours before a shift, and if they agree to work it, their consent must be in writing first.
The retail on-call ban is a prohibition, not just a pay requirement, and it shows how far some of these laws go. A covered employer that uses on-call retail coverage in New York City could be violating the law simply by continuing a common practice.
More broadly, predictive scheduling laws require covered employers to give advance notice of schedules and pay a premium for last-minute changes, which affects how on-call and short-notice coverage can work. Oregon's statewide law is the only state-level one, reaching retail, hospitality, and food-service employers with 500 or more employees worldwide.
New York City enforces these rules. Its Department of Consumer and Worker Protection announced a $38.9 million Fair Workweek settlement in December 2025, covering more than half a million violations at one national chain's city locations and returning $35.5 million to over 15,000 workers.
Whether any of this reaches you depends on your location, industry, and size. On-call scheduling is increasingly regulated, so if you might be covered, check your jurisdiction's rules before building a rotation that relies on short-notice coverage.
Writing an On-Call Policy
A written on-call policy is what turns an informal arrangement into a clear, fair, and defensible system. It prevents the disputes and compliance problems that on-call scheduling can otherwise create, and it does not need to be long. A good on-call policy covers a handful of essentials.
The policy should specify who is subject to on-call duty and how the rotation works, so expectations are clear and the burden is visibly shared. It should define the response time expected and how on-call staff are contacted, removing ambiguity about what being on call actually requires.
Compensation comes next: state how on-call time and time actually worked are paid, consistent with the pay rules above. The policy should also cover practical matters like how to swap on-call duty, what to do if the primary is unreachable, and any equipment provided.
Keep the on-call policy with your other written policies, alongside your employee handbook, so expectations stay consistent and you have something to point to if a question arises. Writing it down also forces you to make decisions you might otherwise leave vague.
The required response time is the clearest case. It determines both coverage reliability and whether on-call time is paid, so write it down once and the rotation stops depending on what people remember agreeing to.
Best Practices for On-Call Scheduling
The practices that matter most are a fair rotation, a backup for every slot, early notice, clear expectations, careful tracking, and regular review. They separate on-call scheduling that works from on-call scheduling that burns people out and creates problems. They matter most on a small team, where the on-call load falls on a handful of people.
Share the burden fairly and avoid overloading. On-call duty is demanding even when no calls come, because it constrains personal time, so rotating it evenly and having enough people in the rotation is essential to prevent burnout and resentment.
Always provide a backup, so coverage never depends on a single person being reachable. And give as much advance notice of on-call assignments as you can, so people can plan their lives around it.
Communicate expectations clearly, since most on-call friction comes from ambiguity about what being on call requires. Track everything, both the on-call assignments and the time actually worked, for pay, overtime, and compliance. And revisit the rotation regularly to keep it fair as the team and the workload change.
If you do only two things, name a backup for every rotation week and write the required response time and the pay rule into a short policy.
Frequently Asked Questions
What is on-call scheduling?
On-call scheduling is a way of naming which employees must stay available during set periods so that someone can respond or come in when a need arises, even though the person on call is not actively working for that whole stretch. Businesses with unpredictable demand rely on it, including healthcare, retail, hospitality, field service, and maintenance, because problems often show up outside normal coverage hours. The schedule itself is a simple record of who is available and when. It usually rotates, which spreads the responsibility across the team instead of leaving it with a few people.
How do you create an on-call schedule?
Begin with coverage: decide which hours need someone available and how fast that person must answer. Next, pick a rotation that spreads the load, such as weekly turns with a primary and a secondary, and staff it with enough people that nobody carries too much, giving every slot a named backup. Tell everyone what being reachable means and how you will contact them, then publish the schedule as early as you can. Keep a record of who was on call and any hours actually worked, since those hours affect pay and compliance. Review the rotation from time to time so it stays fair.
Do you get paid for being on call?
It depends on how tightly the job restricts the employee. If someone must wait on your premises, or stay close enough that the time is effectively not their own, federal law generally treats the wait as work and you pay for it. If they can be at home and only need to answer the phone within a reasonable window, that waiting time is generally unpaid. The deciding question is how much freedom the employee keeps while waiting. Either way, every hour they actually work once called is paid, and state law may add its own requirements.
What is the difference between engaged to wait and waiting to be engaged?
Together, the two phrases form the legal test for whether waiting time counts as paid work. Being engaged to wait means the wait itself is part of the job: the employee cannot spend the time on personal matters, so you pay for it as hours worked. Waiting to be engaged means the employee may spend the time largely as they please and only has to stay reachable, so the wait is generally unpaid. What separates the two is how far you restrict the person. Staying on your premises or under tight limits points to engaged to wait, while being reachable from home points to waiting to be engaged.
What are the types of on-call rotations?
Five types are in common use. A weekly rotation gives one person the duty for a full week, then passes it to the next. A primary and secondary setup puts a backup behind whoever is called first. A weekday and weekend split keeps the less popular weekend duty from landing on the same people every time. Follow-the-sun suits distributed teams, because coverage moves across time zones and nobody has to cover the night. Ad-hoc, or as-needed, on call fills occasional gaps. Choose by coverage needs, team size, and how demanding the on-call load is.
Can employers require employees to be on call?
Generally yes. Employers may make on-call duty part of a job, provided they meet the pay rules and any scheduling laws that apply where they operate. Some places go further and restrict it: New York City's Fair Workweek rules bar covered retail employers from scheduling on-call shifts altogether. Elsewhere the practice stays legal but comes with conditions. You still pay according to the on-call pay rules, and predictive scheduling laws, where they apply, add notice requirements and premiums when schedules change. In short, on-call is permitted in most settings but increasingly regulated, so the answer depends on your location and industry.
How many people should be on an on-call rotation?
No law sets a minimum number of people for a rotation. What matters is how often each person's turn comes around and whether every slot has a named backup. Measure the gap between one employee's turns: when it shrinks to a week or two, the rotation is too thin and the same few people absorb every disruption. Either add people or shorten the coverage window so fewer hours need a name against them. Watch the load rather than the headcount, because a quiet rotation can work at almost any size while a busy one wears people down fast. Revisit the arrangement as your team and workload change.
Is on-call scheduling the same as IT on-call?
Not quite. The two share the idea of a rotation but differ in setting. IT on-call, sometimes called DevOps on-call, means engineers stay ready to respond when a system goes down or an incident is raised, and the rotation typically runs on specialized incident-response and alerting software. Workforce on-call means employees such as nurses, retail staff, or field-service workers are available to cover shifts or deal with problems. Rotations, backups, and fairness matter in both, but the tools and details differ. This guide focuses on the workforce meaning, which suits most small businesses outside software operations.