Timekeeping and overtime rules for 24/7 public safety departments

Reference article · 5 min read

A citywide timekeeping or ERP replacement often moves cleanly through finance, public works, and parks, then stops at the fire station and the patrol division. The reason is rarely the user interface. It is that sworn and uniformed schedules fall under a different part of the Fair Labor Standards Act, sit beneath agreements bargained separately for each unit, and generate pay events a generic product never anticipated.

What follows describes what makes 24/7 public safety timekeeping distinct, so project teams, payroll staff, and procurement officers can evaluate scheduling and timekeeping together and write requirements that survive the first payroll after go-live. Thresholds and interpretations change and vary by jurisdiction, so confirm them with the U.S. Department of Labor, your state labor agency, and your own counsel before encoding any rule.

The 7(k) work period, not the workweek

Most employees earn overtime after 40 hours in a seven-day workweek. Section 7(k) of the FLSA allows public agencies to establish a longer work period for employees engaged in fire protection or law enforcement activities, with a maximum-hours standard that scales to the length of that period. The permitted period is a range of consecutive days rather than a fixed seven, and the standard differs between fire protection and law enforcement. The Department of Labor publishes the thresholds. Treat them as a table an administrator maintains, not as constants buried in code.

• Establish the period and apply it consistently. The cycle configured in the system should match what the agency adopted, including start date and length.
• Different units carry different rules at once. Fire suppression may sit on a long cycle while dispatchers, often not covered by 7(k), stay on a standard workweek. One payroll run has to handle both.
• People move between rules. A firefighter detailed to a non-suppression assignment, or an officer on extended light duty, may fall outside 7(k) treatment for that stretch.
• FLSA overtime and contract overtime are two calculations. Many MOUs pay overtime beyond the scheduled shift, or on hours in paid status, which includes leave. The FLSA counts hours worked. Compute both and keep the FLSA result independently auditable.

The regular rate is where disputes start

Overtime is paid at one and one-half times the regular rate, which is not the base hourly rate. It generally includes nondiscretionary compensation tied to the work: longevity, shift differentials, and specialty or certification pay such as EMT, paramedic, hazardous materials, K-9, field training officer, and bilingual pay. Courts have also considered whether cash paid in lieu of health benefits belongs in the regular rate, and the outcomes have not consistently favored employers. Some payments are excludable, but less often than agencies assume, so treat inclusion as the default and document each exception.

• Pay code governance. Every pay code needs a recorded decision on whether it enters the regular rate, who decided, and when. That list is a governance artifact, not a technical detail.
• Retroactive increases. A settled MOU with a retroactive raise forces recalculation of the regular rate for closed periods. The system must re-run overtime for those periods and produce a reviewable adjustment record.

Trades, callback, court time, and holdover

Under the FLSA, hours in a voluntary substitution between employees are generally credited to the scheduled employee rather than the one who appeared, when the trade is voluntary, approved by the agency, and for the same kind of work. That makes trades a sharp test of any product: the roster must show who actually worked while the pay engine credits someone else. Payback tracking, partial trades, and trades crossing a period boundary all need explicit handling.

• Callback. Contract minimums guarantee a set number of hours regardless of time actually spent. That is contract pay; FLSA hours worked may be fewer. Track both.
• Court and standby. Off-duty appearances, subpoena time, travel, and cancellations usually carry their own minimums and notice rules.
• Holdover and early relief. Small increments at shift boundaries accumulate across a year and are a common source of grievances. Rounding must be neutral in effect and documented.
• Same-day trades in and out. These produce a shift no single employee worked end to end, which breaks simple daily-overtime logic.

Minimum staffing, hiring order, and acting pay

Filling a vacancy against minimum staffing is where scheduling and payroll meet. Hiring order is usually bargained: seniority rotation, overtime lists tracking hours offered and worked, refusals that count, and mandatory holdover as a last resort. When one system decides who works and another decides what they are paid, the seam between them is where money and grievances are lost.

Acting or out-of-class pay adds another layer. Working a higher classification for part of a shift may trigger a step calculation, carry a minimum duration, and affect the regular rate. The assignment has to attach to the hours, not to the pay period.

What to ask vendors and require in the contract

1. Ask for a demonstration configured with your work periods and MOU language, over a pay period containing a trade, a callback, a court appearance, and a retroactive increase. Supply the scenarios in writing beforehand.
2. Ask which rules are configuration and which require vendor development, rule by rule and in writing.
3. Require the FLSA calculation to be inspectable: a per-employee, per-period record showing hours counted, rate components, and how the overtime figure was derived.
4. Require an interface specification between scheduling and timekeeping, including the reconciliation path when the two disagree.
5. Tie acceptance to a parallel payroll run covering at least two full work periods per affected unit, with a variance threshold agreed before go-live.
6. Involve labor relations from the start. Rules encoded in software become de facto interpretations of the agreement, and bargaining units read them that way.

HQT builds and integrates public safety software for state and local agencies, including work at the boundary between scheduling, timekeeping, and payroll systems.

Frequently asked questions