Your service team has started getting after-hours requests. A client issue pops up at 8:30 p.m. on a Friday. A system alert hits on Sunday morning. Someone needs to be available, so you create an on-call rotation.
Then payroll asks the question that causes a significant pause: how exactly are we supposed to pay this?
That’s where many growing employers get stuck. On call compensation sounds simple until you try to write a policy that works in real life. If the employee is carrying a phone but not actively working, is that paid time? If they have to respond quickly, does that change the answer? If they’re in one state this week and helping a client in another next week, which rules control?
Those aren’t edge cases. They’re ordinary operating questions for small businesses that have grown beyond a straight 9-to-5 model. And the risk of getting them wrong isn’t limited to an irritated employee or a messy payroll correction. On-call pay issues can turn into wage claims, overtime mistakes, inconsistent manager practices, and hard feelings with the very employees you rely on most.
The practical goal is straightforward. You need an on call compensation approach that is fair to employees, workable for managers, and defensible if anyone audits your timekeeping and pay practices. That means understanding the legal test first, then choosing a pay model that fits the level of control you place on employees.
A common scenario looks like this. A company adds emergency client support because its customers now expect help outside normal business hours. Leadership sets up a rotating schedule and assumes the easiest answer is to pay only when the phone rings.
That approach sometimes works. It also sometimes creates a wage-and-hour problem the company never saw coming.
The issue usually starts with good intentions. A manager wants fast response times, so they tell the assigned employee to keep their laptop nearby, avoid anything that would make them unavailable, and be ready to jump in quickly. The business still thinks the person is “off duty” unless they’re actively solving a problem.
In practice, that line can be much blurrier.
If the restrictions are light, paying only for actual time worked may be fine. If the restrictions are heavy, the employee may be owed pay for the standby time itself. The distinction matters because on call compensation isn’t just a recruiting or morale issue. It affects payroll, overtime, recordkeeping, and legal exposure.
The hardest on-call problems usually don’t come from bad intent. They come from informal expectations that were never translated into a compliant pay rule.
Small employers feel this pressure more than large enterprises with in-house HR and legal teams. A founder, operations leader, or office manager often ends up trying to balance customer coverage, budget control, and labor law at the same time. That’s a lot to ask from a simple spreadsheet and a loosely worded Slack message.
A sound policy starts with one practical question: how much control are you exercising over the employee’s time when they’re on call?
Under Fair Labor Standards Act rules, the starting point is the distinction between engaged to wait and waiting to be engaged. That test drives whether standby time itself is compensable.
When an employer requires the employee to remain at or near the workplace, or otherwise restricts the employee so much that personal time is no longer really personal time, the employee is generally engaged to wait. That time must be paid. When the employee has substantial freedom to go about personal activities and only needs to be reachable, the employee is generally waiting to be engaged, and the employer typically pays only for actual work performed. The source used here also notes that the U.S. Department of Labor considers a 30-minute or longer response window a reasonable restriction in this context, which can help employers avoid turning standby time into compensable time when employees retain meaningful freedom, according to Wilentz on on-call compensation under the FLSA.
A technician who must stay close to the facility, keep equipment ready, and return almost immediately looks much more like engaged to wait. The employer is controlling the employee’s location and limiting personal use of time.
A remote support employee who can go to dinner, attend a child’s game, or spend time at home, as long as they answer the phone and can log in within a reasonable time, looks more like waiting to be engaged. In that setup, the employer may owe pay for actual time spent handling calls or incidents, but not necessarily for the entire standby block.
That’s the broad principle. The hard part is that many real policies sit somewhere in the middle.
Employers should review the actual restrictions they impose, not the label they use in a handbook. Calling a schedule “informal” or “voluntary” won’t help if managers are tightly controlling the employee’s time.
Look closely at these factors:
Practical rule: If your on-call setup would make most people decline dinner plans, avoid a movie, or stay close to home all evening, you should stop and reassess whether that time is really off duty.
A related mistake is trying to solve a legal classification issue with a stipend alone. A flat payment can be a valid compensation method, but it doesn’t decide whether the time is compensable in the first place. The legal test comes first.
For a deeper look at waiting time, on-call rules, and related timekeeping issues, see this guide on FLSA rules for waiting, on-call, and sleeping time.
A common small-business mistake looks like this: a Utah service company puts a technician on call for the weekend, pays a flat stipend, and assumes overtime only applies if the technician goes out on a job. If the standby time is compensable under federal law, that assumption can create back-pay exposure fast.
Under the FLSA, compensable on-call time counts as hours worked. For a non-exempt employee, those hours go into the same weekly total as regular shift time and any time spent responding to calls. Once the employee crosses 40 hours in the workweek, overtime pay applies.
The payroll problem usually starts before payroll ever touches the timecard.
A manager labels the on-call block as unpaid, the system records only call-backs, and the weekly total looks compliant when it is not. I see this most often with growing employers that started with a simple rotation, then added tighter response expectations as they expanded into multiple locations.
Use this review process:
A quick example shows why this matters. An Idaho employer has a non-exempt field employee who works a full weekday schedule, then remains on call over the weekend under restrictions that significantly limit personal time. The employee also takes several service calls. If that standby time is compensable, the employer has to count the full set of compensable hours, not just the time spent driving or fixing the problem.
That is where stipend plans often go wrong. A flat on-call payment can still be a reasonable business choice, but it does not answer the wage-and-hour question. If the employee's time is controlled enough to count as hours worked, the company still has to track those hours and pay overtime correctly.
This gets more complicated for employers operating across Utah, Idaho, Arizona, and Wyoming. Federal law sets the baseline, but a single companywide on-call practice can still create risk if managers in different states impose different response times, travel limits, or documentation expectations. The policy may read the same on paper while the actual restrictions vary by location.
If you need a plain-language refresher before reviewing your timekeeping setup, Helpside's guide on whether employers have to pay employees who are waiting to work is a useful companion. It also helps to remember the employee-relations side of the issue. Candidates often screen for schedules that protect personal time, which is one reason some employers benchmark against job listings for work-life balance when they rethink how often on-call duty is really necessary.
A Utah HVAC company puts one technician on weekend call, pays a flat stipend, and assumes the issue is settled. Then the same model gets applied to an Arizona support employee who has to respond within 15 minutes, stay near a laptop, and keep checking alerts. The pay approach may look consistent on paper, but the burden on the employee is not.
That is why pay model selection is an operations decision and a wage-and-hour decision at the same time. Small employers in Utah, Idaho, Arizona, and Wyoming often want one simple rule for every location. In practice, the better approach is to choose a model that matches the actual restrictions, the frequency of interruptions, and your ability to track time correctly across states. Helpside’s multi-state employment compliance guide is a useful reference if your on-call coverage crosses state lines.
| Pay Model | How It Works | Pros | Cons |
|---|---|---|---|
| Flat daily stipend | Employee receives a fixed amount for each on-call day | Easy to budget, easy to explain, low admin burden | Can hide legal issues if restrictions make standby time compensable |
| Flat weekly stipend | Employee receives one amount for a full on-call week | Works well for small teams with rotating schedules | Can become inaccurate when weeks vary widely in burden |
| Reduced hourly standby rate | Employee is paid an hourly amount for standby availability | Better reflects time commitment, clearer payroll record | More timekeeping complexity |
| Pay for actual call-outs only | Employee is paid only when actively responding | Low standby cost when interruptions are rare | Risky if the employee’s freedom is meaningfully restricted |
| Call-out premium with minimum | Employee receives premium pay and a minimum paid block when called in | Seen as fair by employees, useful when incidents are disruptive | Requires strong tracking and payroll discipline |
Small businesses often start with a flat weekly stipend because payroll can run it easily and employees understand it quickly. That can work for a light-duty rotation where calls are infrequent and the employee is largely free to spend the time as they want.
It works poorly when managers create tight response expectations without changing payroll practices. I see that problem most often in growing service businesses. A branch manager says the employee can stay home, but also expects them to answer immediately, avoid hiking or travel, monitor messages constantly, and be ready to log in or drive out at any time. At that point, the stipend may still be part of the pay package, but it does not solve the compensation analysis.
Use the assignment itself as the starting point.
The best model is the one your managers can follow consistently at 9 p.m. on a Saturday, not the one that sounds cheapest in a budget meeting.
IT, healthcare, field service, utilities, and maintenance teams often use different on-call structures because the work is different. Technical roles may use hourly standby pay plus call-out premiums. Other employers rely on daily or weekly availability payments because actual call volume is low.
Market practice still has limits. A rate that feels normal in one industry can be too low for a role with tight restrictions, repeated interruptions, or heavy overtime exposure. That is especially true for small multi-state employers in the Intermountain West, where one location may have a calm rotation and another may have near-constant after-hours demands.
Hiring pressure plays into this too. Employees compare schedule quality, not just wages. If you are testing whether an on-call structure is hurting recruiting or retention, review adjacent market signals such as job listings for work-life balance.
“What's the normal stipend?” is a fair budgeting question. It is not the right compliance question.
The better question is whether your pay model matches the level of control you place on the employee and whether your payroll process captures all compensable time. If those two pieces are out of sync, the plan is exposed even if the stipend amount feels competitive.
Federal law gives you the baseline. Multi-state operations create considerable complexity.
That’s especially true for employers with employees or clients across the Intermountain West. A business may be headquartered in Utah, have a remote employee in Idaho, send a service lead into Wyoming, and add support coverage for Arizona customers. The temptation is to build one clean, companywide on-call policy and move on.
That’s where exposure starts.
The challenge is not that every state has a completely different rule in every circumstance. The challenge is that state-level variations are often underexplained in practical guidance, particularly for employers outside the coastal states that dominate employment law content. According to the verified data, employers operating across states like Utah, Idaho, Arizona, and Wyoming face a real blind spot because state-level variations are rarely addressed clearly, while some states outside the region have specific minimum call-out pay thresholds such as New York’s 4-hour requirement. The same verified data also notes that the Bureau of Labor Statistics reports about 15% of U.S. workers have on-call arrangements, while data on multi-state misclassification remains scarce, as discussed in OnPage’s overview of on-call law and actual pay practices.
A single policy usually breaks down in one of three ways.
The risk is magnified for small employers because they often don’t have a dedicated compliance function reviewing policy by work location. The office manager, controller, or founder is trying to keep the business moving, and on-call administration becomes a side task.
For employers in Utah, Idaho, Arizona, and Wyoming, the practical challenge isn’t just legal variation. It’s lack of clarity in everyday guidance. Many articles discuss federal law and then jump straight to California or New York. That leaves Western employers with incomplete information and too much confidence in a generic template.
If your workforce crosses state lines, “we use the same rule for everyone” is an administrative convenience, not a legal defense.
That doesn’t mean every multi-state employer needs a different policy for every single worker. It does mean the policy should be built from a state-review process, not from assumptions.
Use a structured review for each state where employees perform work:
Confirm whether the state takes a stricter view than federal law on restricted on-call time.
Some jurisdictions impose minimum pay requirements when employees are called in or required to report.
Check how state overtime rules interact with on-call hours and whether daily rules or other state-specific triggers apply.
A valid policy still fails if managers don’t capture the time consistently.
For a broader framework on managing employees across jurisdictions, this multi-state employment compliance guide is a useful operational reference.
A workable on-call policy does two jobs at once. It tells employees what’s expected, and it gives payroll enough structure to pay correctly every time.
Most employer problems come from missing one side of that equation. The policy may describe scheduling but say almost nothing about time reporting. Or payroll may have a pay code for on-call work, but managers were never trained on when to use it.
At minimum, put these items in writing:
Employees assigned to on-call duty must remain reachable during the scheduled on-call period and follow the response expectations for their role. Employees must accurately record all time spent performing work while on call, including time spent responding to calls, logging into systems, communicating with clients, and completing required follow-up tasks. If the company designates any portion of on-call standby time as compensable, that time must also be recorded using the assigned payroll code. No manager may change on-call compensation practices informally without HR or payroll approval.
That sample is intentionally plain. It avoids vague phrases like “be available as needed” without defining what that means operationally.
The payroll side needs as much discipline as the policy itself.
A short training can make a major difference. This video is a useful reminder that wage-and-hour compliance often turns on how rules work in day-to-day operations, not just how they appear in a handbook.
Some practices create problems almost every time:
Write the policy so that a new manager, a payroll specialist, and an auditor would all reach the same conclusion about how the employee should be paid.
That’s the standard worth aiming for. Clear expectations, reliable records, and consistent payroll treatment are what make on call compensation manageable.
On call compensation looks like a narrow payroll topic until you have to administer it. Then it touches scheduling, overtime, state law, manager training, employee relations, and recordkeeping all at once.
That’s why this issue deserves more attention than many employers give it. The legal test is fact-specific. The pay model has to match the actual burden placed on the employee. And once your workforce crosses state lines, the administrative margin for error gets smaller.
For small and midsize businesses, the biggest cost is often distraction. Leaders end up spending time chasing down time entries, untangling manager assumptions, and second-guessing whether a policy that worked for a five-person team still works for a company with multiple departments and a broader footprint. That’s time not spent on customers, hiring, service delivery, or growth.
Good on-call administration is not just about paying people. It’s about reducing preventable risk while keeping the business responsive.
The practical answer is not to avoid on-call coverage. Many businesses need it. The answer is to treat it like a compliance system instead of an informal scheduling habit. Review how restrictive the arrangement really is. Match the compensation model to those conditions. Build payroll controls that hold up under pressure. Recheck the policy whenever your geography or service model changes.
That’s the point where outside HR and payroll support becomes strategic, not administrative. When an employer has to manage multi-state rules, overtime interactions, policy drafting, and payroll execution together, expert help can remove a meaningful amount of risk from the business.
If your team is wrestling with on call compensation, multi-state payroll questions, or broader wage-and-hour compliance, Helpside can help you build practical policies, cleaner payroll processes, and a more defensible HR foundation so your leaders can get back to growing the business.