On-call rotations for small agency IT teams: schedules, pay, escalation

Reference article · 7 min read

The permit portal goes down at eleven at night. A dispatch interface stops writing records. A pump station alarm cannot reach the historian. In an agency with three to eight IT staff, the person who fixes it is often whoever happened to see the alert, and the arrangement holds together on goodwill until someone leaves, takes two weeks off, or asks why they are not being paid for carrying a phone every night.

An on-call rotation is two things at once. It is an operations design: who responds, how fast, and what happens when they cannot. It is also an employment arrangement governed by wage and hour law, and often by a bargaining agreement. Agencies that build only the first end up with a schedule nobody is compensated for. Agencies that build only the second end up with a pay code and no escalation path. The sections below cover both, for a team that has to make it work with the staff and budget already on hand.

Rotation shapes that work with a small team

With a small eligible pool, the shape of the rotation matters more than the tooling.

Weekly primary. The simplest form and the easiest to schedule, but on a four-person team it puts someone on call roughly every fourth week. That is sustainable only if after-hours volume is genuinely low.
Split week. Divide the week at midweek so the weekend burden rotates separately from weeknights. This is useful when weekends are quiet but weeknight batch jobs are not.
Narrow the scope instead of the schedule. Before adding people to a rotation, cut what pages. Many small teams find that most overnight alerts do not require a human until morning. Write severity definitions and page only on the top tier.
Schedule holidays a year out. Holidays are the shifts people resent most. Publishing them early lets staff trade and makes the burden visibly rotate.

Define the on-call window in writing: which hours, which days, whether it includes agency holidays, and what response time is expected. Ambiguity here becomes a grievance later.

Primary, secondary, and the manager tier

A single on-call person is a single point of failure. Build at least two tiers, and a third for decisions.

Primary acknowledges the page within the interval your policy sets and works the incident.
Secondary is paged automatically when the primary does not acknowledge, and is also the person the primary calls for a second set of hands. Secondary should be someone with different system knowledge where possible.
Manager or duty officer exists to make decisions, not to troubleshoot: approving an emergency change, authorizing extended downtime, opening a severity-one case with a vendor, notifying the public information officer, or deciding to fail over.

Confirm in advance who is authorized to open an after-hours case with each vendor and whether your support agreement actually covers nights and weekends. Discovering at two in the morning that your contract is business-hours only is a contracting problem, not an operations problem.

Hand-off notes and the system only one person knows

The reason small teams fear vacations is undocumented knowledge. Two practices address most of it.

A short runbook per critical system. Who owns it, how to reach the vendor, what normal looks like, how to restart it safely, what breaks most often, and what must not be touched without the owner.
A weekly hand-off note. Open issues, changes going in, anything fragile, planned absences, and anything the outgoing person had to work around. Keep it brief enough that it actually gets written.

Then test it. Pick the system that one person understands, put that person on leave on paper, and have someone else walk the runbook. Also verify that the on-call person can get in: break-glass credentials in the password vault, verified periodically, and access to any vendor portal that would otherwise require a business-hours account manager.

Standby pay, callback, and exempt status

This is where agencies most often get exposed, and where general guidance stops and counsel begins. The federal Fair Labor Standards Act and its regulations draw a broad distinction for non-exempt employees between on-call time that is so restricted the employee is effectively working, and on-call time the employee can use largely for personal purposes. Courts weigh factors such as required response time, geographic limits, how often calls actually come in, whether shifts can be traded, and whether the work can be done remotely. The more restricted the arrangement, the more likely the waiting time itself is compensable.

Several points follow from that, all of which should be confirmed with your HR office, labor relations staff, or counsel, because requirements change and state law is sometimes stricter than federal law:

Time actually worked is compensable for non-exempt staff, including remote logins from home. Give people a simple way to record it, and make recording it mandatory rather than optional.
Standby stipends are commonly paid per shift or per week. Where such pay is non-discretionary, it generally must be included in the regular rate used to compute overtime.
Callback minimums, meaning a guaranteed number of hours paid when someone is called back in, usually come from a bargaining agreement or local personnel rule rather than from federal law.
Compensatory time in place of cash overtime is available to public agencies under specific conditions, including prior agreement and statutory caps.
Exempt employees are generally paid on a salary basis, and additional compensation beyond the salary is generally permitted, but the structure matters. Ask before improvising a stipend.
Bargaining. Creating or changing a rotation, its scope, or its pay is frequently a mandatory subject of bargaining. Talk to labor relations before announcing anything.

Getting the rotation into the budget

A rotation funded out of overtime overruns is a rotation that gets cut. Build a line item instead. Estimate the annual cost as the number of standby shifts multiplied by the stipend, plus expected callback hours at the applicable rate, plus any comp time liability you expect to carry. Present it against the service level leadership is asking for: if the expectation is that the financial system is recovered before morning, that has a price; if best effort is acceptable, get that in writing too.

Compare alternatives honestly, since each shifts cost rather than removing it: vendor-hosted services with contracted after-hours support, a shared rotation with a neighboring jurisdiction or council of governments, or a managed provider handling overnight triage with your staff as escalation.

What to require from vendors, and how to start

When you procure or renew a system that will page someone at night, put the support model in the solicitation and the contract, not just the sales conversation.

Support hours stated in your local time zone, with the vendor's observed holidays listed.
Severity definitions, target response times, and who at your agency is authorized to open each severity.
Named escalation contacts and a documented path past first-tier support.
Advance notice of vendor-side maintenance windows, with a right to object.
Direct portal or phone access for on-call staff without an account manager intermediary.
Clarity on whether service level remedies are credits only, and what termination rights exist for chronic failures.

To start internally, pick a defined on-call window, write the severity tiers, publish a twelve-month schedule including holidays, get the pay treatment reviewed before the first shift, and hold a short review after the first quarter to adjust what pages.

HQT is a technology and software company working in enterprise IT and systems engineering for public sector organizations, including monitoring, operations, and incident response practices.

Frequently asked questions

Do we have to pay IT staff just for being on call?

For non-exempt employees, it depends on how restricted the on-call time is. Under the Fair Labor Standards Act, time spent waiting that the employee can largely use for personal purposes is generally not compensable, while time so restricted that the employee is effectively working generally is. Courts look at factors such as required response time, geographic restrictions, how frequently calls occur, and whether shifts can be traded. Time actually spent working, including remote logins from home, is compensable, and agencies should confirm specifics with counsel because state law can be stricter.

What is a callback minimum and where does it come from?

A callback minimum is a guaranteed number of hours paid when an employee is called back to work outside their scheduled shift, even if the task takes less time. It usually comes from a collective bargaining agreement, a memorandum of understanding, or a local personnel rule rather than from federal wage law. If your agency has represented employees, check the applicable agreement before setting any on-call policy, since changing the practice may be subject to bargaining.

Does standby pay affect overtime calculations?

It can. Non-discretionary pay such as a standby stipend generally must be included in the regular rate used to compute a non-exempt employee's overtime, which means the effective overtime rate rises above the base hourly rate. Payroll should be told about any new stipend before the first payment so the rate is calculated correctly. Confirm the treatment with your HR or finance office, since the rules turn on how the payment is structured.

How do we run an on-call rotation with only three or four people?

Reduce what pages before you spread the schedule thinner. Write severity definitions so that only genuine after-hours emergencies alert a person, and let everything else wait for the morning queue. Then use a two-tier structure with a primary and a secondary, publish holidays a year in advance so the burden visibly rotates, and consider sharing overnight triage with a neighboring jurisdiction or a managed provider if volume justifies it.

Can salaried exempt IT staff receive extra pay for on-call shifts?

Generally yes. Exempt employees must be paid on a salary basis, but additional compensation above that salary is usually permitted, and many public agencies offer a stipend, comp arrangement, or schedule flexibility for exempt staff who carry the phone. The structure matters more than the amount, particularly anything that resembles a deduction from salary. Have HR or counsel review the arrangement before it is implemented.