Scheduling software for 24/7 shift workforces: police, fire, and dispatch

Reference article · 5 min read

An office timekeeping system answers one question: how many hours did this person work. A schedule for a police department, fire department, 911 center, or utility control room answers a different one: will every post be covered, by someone qualified, every hour of every day, and when it is not, who gets called and in what order. That is why general purpose HR and timekeeping products fail in 24/7 operations, and why the real schedule ends up on a whiteboard and in a supervisor's phone list.

The gap shows up in two places: overtime nobody can explain at budget time, and a grievance over who was passed over for a callback. Both are recordkeeping problems before they are money problems.

The schedule model itself

Office products assume a Monday to Friday week and a person who works one job. Shift operations break both assumptions.

• Cycles, not weeks. Rotating platoon patterns such as 24/48, 48/96, and four on four off repeat over a cycle that does not align to a calendar week. It has to project the master schedule months forward and absorb a rotation change without corrupting history.
• Positions, not headcount. The unit of scheduling is a post: an engine seat, a dispatch console, a beat, a jail floor, a supervisor slot. The software should show which post is open, not that the shift is short by two.
• Work periods. The Fair Labor Standards Act includes a partial overtime exemption commonly used for law enforcement and fire protection personnel, allowing overtime to be computed over a work period longer than a week. Eligibility and thresholds change over time, so confirm the current rules with the U.S. Department of Labor and your counsel rather than trusting a vendor default.

Minimum staffing by unit, rank, and qualification

Minimum staffing is rarely a single number. It is a matrix: per station or apparatus, per console per shift, a supervisor on every watch, specific certifications present. Rules have to express rank and qualification together: two paramedics per ambulance, a certified telecommunicator on every dispatch shift, a field training officer whenever a trainee is scheduled. Certifications expire, so qualification records should carry expiration dates and drop a person from eligibility when a credential lapses. A system that projects shortfalls days ahead lets a supervisor fill a hole by adjusting the schedule instead of paying premium rates.

Overtime and callback in the right order

The order in which people are offered extra work comes from a bargaining agreement or department policy, and it varies: strict seniority, lowest accumulated hours first, a rotating list that advances with each offer, forced hire in reverse seniority, separate lists by rank and specialty. Good software treats this as configuration, not as a fixed opinion. For each opening it should track:

• Eligibility. Rank, certification, rest requirements, maximum consecutive hours, and restrictions tied to light duty or leave status.
• Every attempt. Who was offered the shift, when, by what method, and the response: accepted, declined, no answer, unavailable, or skipped for cause.
• List position afterward. Whether a decline advances the rotation or counts as hours charged, since agreements differ on this point.
• Cost before assignment. An estimate of straight time versus premium cost, so a supervisor can compare options.

Trades, leave slots, and blackout periods

A shift trade is a staffing transaction, not a favor. The system should test a proposed trade against minimum staffing, qualification, and rest rules before it reaches an approver, and track payback where the contract treats trades as owed time.

Agencies commonly limit how many people of each rank may be off on a given day, allocate those slots by bid or first come, and impose blackouts for academy classes, elections, and large events. Slot limits should be enforced at request time, and requested hours checked against accrual balances in payroll.

The audit trail that settles a grievance

When someone grieves being skipped, the answer is either in the record or it is not. Require that the system keep, for each filled opening, the ordered list as it stood at the moment of the offer, every contact attempt with a timestamp, the response, the assignment, and the identity and stated reason for any override. An override field that captures why a supervisor bypassed the list is better than one that leaves no trace. The record has to export in a form a person can read, and retention should match your records schedule and the grievance windows in your agreements.

What to ask vendors and what to require

Decide first which system is authoritative: HR owns rank and status, training owns certifications, the scheduler owns assignments. Then run the demonstrations.

1. Give the vendor a real month of your schedule and your overtime language, and ask them to configure it in front of you.
2. Watch one callback end to end, then read the audit report an arbitrator would see.
3. Ask how a mid year change to a rotation or a list rule is made, whether agency staff can do it, and what it costs.
4. Ask what happens when the network, the app, or a member's phone is unavailable.
5. Ask for accessibility conformance documentation. Where the scheduler exchanges data with dispatch or records systems, confirm with your state CJIS contact how criminal justice information security requirements apply.

Test the payroll export against a real pay period before go live, including premiums, differentials, and callback minimums. In the contract, secure data export rights in a non proprietary format at termination, transition assistance, defined uptime and support response, and breach notification terms. Write your rules down in plain language first, including the informal ones supervisors carry in their heads, because a system can only enforce rules someone has stated.

HQT builds and integrates public safety and operations software for state and local government agencies, including scheduling and workforce systems.

Frequently asked questions