Skip to content
Manager guide

Build an on-call rotation your crew can live with

Reported standby and call-out pay ranges, how to size a rotation to the staff you have, and the argument that gets a board to pay for the phone.

July 2026
Business & Governance
All
6
The short answer

On-call pay splits into two pieces: standby pay for holding the phone and call-out pay for responding. Reported ranges run from $0 to roughly $1,000 a week for standby, with a 2-hour overtime minimum typical for call-outs. Confirm every number against your own contract and FLSA rules before using it in a negotiation. A defensible rotation is deep enough to share the burden, ties its response window to where staff can actually live, and gets its terms written into the union contract or MOU, not left as a verbal understanding.

What you will be able to do

You just inherited the on-call schedule, and the first thing you notice is that nobody agrees on what's fair. One operator remembers a flat stipend from a past job. Another has never been paid a dime for holding the phone, only for driving in. A third has quietly stopped planning anything for the end of the pay period, because that's when the calls cluster.

The reason it feels uneven is that it is uneven. On-call pay varies by utility, by state, by whether the crew is union, and by whatever the last manager negotiated years ago and never revisited.

Some systems pay for the phone itself. Some pay only once it rings. Some hand one operator a rotation built for three people, because the third position never got filled, and call it fine.

None of that is a reason to guess your way through it. Below is what other systems report paying, how to size a rotation to the staff you actually have, and the argument that tends to land with a board that has never once been tethered to a phone at 2 a.m.

Newly promoted: that's rung 1.

The two things a rotation has to pay for

On-call comp almost always splits into two separate pieces, and a policy that only covers one is exactly where crews get burned. Standby pay covers holding the phone, whether it rings or not. Call-out pay covers the actual response once it does.

A rotation that only pays for call-outs is telling your crew that being tied to the phone all week, unable to leave town or have a drink, is worth nothing until something breaks. That's the specific gap operators describe fighting over: pay for the response, but nothing for the restriction.

What other systems report paying for standby

Standby pay for holding the phone ranges from nothing at all to roughly $1,000 a week at the high end, and every number below is a reported range, not a rate. Confirm your own union contract, local policy, and FLSA treatment of standby time before you rely on any of it in a negotiation.

  • A flat per-day stipend, commonly reported around $22 to $25 a day.
  • A tiered rate, roughly $50 for a weekday and $75 for a weekend day.
  • An hourly equivalent, about one hour of overtime pay for each day held, sometimes at
  • A flat weekly rate, up to around $1,000 a week at the reported high end.
  • Nothing. A fair number of operators get zero for holding the phone, and that's the gap most

time-and-a-half on holidays and weekends. on-call disputes are actually about.

Before you propose a number, check what other departments in your own organization already get for standby duty. If public works or the electric side of a combined utility already carries a stipend and operations doesn't, that internal comparison will carry more weight with your board than any regional survey.

What happens once the phone actually rings

Most systems pay call-outs on a minimum, not on the actual minutes worked, because a callout that takes fifteen minutes still costs the operator the whole evening. The standard reported most often is a 2-hour overtime minimum per call-out, no matter how short the fix.

  • A 2-hour overtime minimum is the common standard, sometimes ranging 2 to 4 hours by contract.
  • Some contracts allow a shorter minimum, around 30 minutes at time-and-a-half, for something
  • Time beyond the minimum runs at the normal overtime rate.
  • A small mileage or gas stipend, often around $10, shows up in some contracts to cover the

resolved remotely without a drive to the site. drive.

These minimums exist because a call-out costs more than the minutes on the clock. Getting up, driving in the dark, and being alert enough to work safely on equipment is not a fifteen-minute favor, even when the fix itself is quick.

How deep the rotation needs to be

A rotation only holds up if it's deep enough that no one operator carries the phone more weeks than they're free of it. Two people sharing on-call means one week on, one week off, forever. Add a third and it drops to one week in three. The staffing decision behind that math is usually the real issue: a lot of utilities run a two-person rotation because a third position never got funded, and the crew absorbs that gap as burnout instead of the utility absorbing it as a budget line.

The response-time window belongs in writing, and it should be built around where your operators can actually afford to live, not a straight-line distance on a map. Thirty to sixty minutes is the commonly cited informal norm for water and collections work. If your operators live outside that range because that's the housing they can afford, a window set from a map instead of from their actual commute sets them up to fail before the phone even rings.

Handoff should run through a call log, not a hallway conversation. If a call-out happens and nobody records when the call came in and when the operator arrived on site, you have no record to point to when a resident, a regulator, or your own board asks how the system responded. That timestamp habit protects the operator as much as it protects you.

Every rotation also needs a second name: someone the on-call operator can hand a call to when they're genuinely unreachable, sick, or already mid-callout somewhere else. A rotation with no backup name is a rotation that fails completely the one week someone's phone battery dies.

Making the case to your board

A board that has never carried the phone will ask why holding it deserves pay at all, and the argument that tends to land is about restriction, not sympathy. Being on-call limits what an operator can do with their own time: no leaving town, no drinking, no plans that would delay a response. That restriction has value whether or not the phone ever rings, and a policy that pays only for call-outs pretends it doesn't.

Point to internal equity where you can. If any other department in your organization, public works, IT, the electric side, already gets a standby stipend and operations doesn't, that gap is your strongest argument, because it's a fairness question the board already knows how to answer.

Loop in HR or your utility's counsel before you finalize the terms, especially the response window. How on-call and standby time gets treated under wage law can hinge on how restrictive the policy actually is, and that's a legal read, not a policy one.

Put it in writing

None of this holds up if it lives only in a verbal understanding between you and your crew. Standby rate, call-out minimum, and response window belong in the union contract or MOU, not in an email or a shift-change conversation. A verbal arrangement changes with whoever runs the schedule next year, and it gives your crew nothing to point to when a future manager tries to negotiate it down.

Get it in writing once, and you only have to defend it once.

Next on the ladder: The backup call, and other conversations you now have.

Further reading

Your state Rural Water Association or municipal league, for regional on-call pay comparisons. The U.S. Department of Labor, for how the Fair Labor Standards Act treats on-call and standby time. Your union local or legal counsel, for how your existing contract already defines standby pay, call-out minimums, and response windows.

Looking for your state? Find your state for certification rules, renewal, and who to call, one page per state.
A free resource from Ziptility. We make software for small water systems.