A major airport authority automated its complex FLSA 28-day pay period calculation for firefighters and police using CloudApper WorkBridge — eliminating manual bi-period carryover math and delivering clean, auditable pay code entries to UKG Pro WFM every cycle.
Table of Contents
Most payroll runs on a familiar rhythm: two weeks, then pay. Biweekly cycles are so standard that WFM platforms build around them. But public safety organizations — specifically those with firefighters, police officers, and emergency responders — often operate under a different structure entirely. The FLSA permits a 28-day work period for law enforcement and fire protection employees, with a higher overtime threshold designed to accommodate the irregular shift patterns these roles require. In practice, running a 28-day cycle through a WFM platform built for biweekly payroll creates problems that no amount of native configuration resolves.
A major metropolitan airport authority in the US operates this way. Its firefighter and police workforce runs on a 28-day pay period split across two biweekly pay periods. Pay Period 1 covers 14 days, with a cap of 109 regular hours. Any hours worked beyond 109 in Pay Period 1 carry into Pay Period 2. Overtime is calculated on the full 28-day picture, not per period. Five distinct pay codes govern how hours are classified and posted. UKG Pro WFM — the platform this authority runs its workforce on — captures the time accurately. It cannot perform the cross-period math.
Every payroll cycle, someone at this organization had to do the carryover calculation manually. CloudApper WorkBridge was brought in to automate the entire bi-period calculation inside UKG Pro WFM — eliminating the manual step and ensuring firefighters and police officers are paid correctly on every 28-day cycle.
Free Datasheet
CloudApper Substitute Request & Management Solution for UKG Ready Datasheet
Why the 28-day pay period creates a structural problem for WFM platforms
The FLSA 7(k) exemption lets public safety employers set a work period of 7 to 28 days for overtime purposes. A 28-day period is common among municipal fire and police departments because it smooths out the uneven shift patterns these roles carry — 24-hour shifts, rotating schedules, mandatory coverage minimums. The practical effect is that overtime doesn’t trigger at 40 hours per week. For firefighters, the FLSA threshold is 212 hours in a 28-day period. For law enforcement, it’s 171 hours.
That’s the overtime threshold. The pay period structure is a separate matter. Most organizations still run payroll biweekly — HR systems, payroll vendors, and banks all operate on 14-day cycles. So you end up with two 14-day pay periods nested inside a single 28-day FLSA work period. Hours and overtime have to be tracked across both periods as a single unit, but pay has to post within each biweekly period in the amounts correct for that portion of the overall cycle.
For this airport authority, that meant: a cap of 109 regular hours in Pay Period 1. If a firefighter or officer works more than 109 regular hours in the first 14 days, the excess doesn’t simply become PP1 overtime — it carries into Pay Period 2, where it’s combined with PP2 hours to determine the full-period overtime picture. The final overtime determination and pay code assignments for both periods depend on what happened across the entire 28 days.
That is not a calculation UKG Pro WFM performs natively. As explored in the context of extending UKG without touching its core configuration, the platform is built to handle standard payroll logic reliably. Non-standard structures like cross-period carryover require an external engine that reads from UKG, applies the custom math, and writes back clean results.
“We were doing this manually every cycle. Pull the data, check who went over 109, figure out the carryover, make sure the right pay codes landed in the right period. It worked, but it was time-consuming, and one mistake in the carryover calculation means someone doesn’t get paid correctly. For firefighters and police, that’s not a small thing.”
— Payroll Director, Major Airport Authority
How CloudApper WorkBridge handles the bi-period calculation
The CloudApper WorkBridge automation runs as a calculation engine layered on top of UKG Pro WFM. At the close of Pay Period 1, it pulls schedule and timecard data for every firefighter and officer. It calculates total regular hours worked against the 109-hour cap. For any employee who exceeded the cap, it flags the excess hours and holds them for PP2 processing.
When Pay Period 2 closes, WorkBridge runs the full 28-day calculation: PP2 hours are combined with the PP1 carryover, overtime is determined based on the combined picture, and pay codes are assigned. The five pay codes this authority uses — covering regular time, carryover hours, overtime, and other classifications — are then posted back to UKG Pro WFM timecards at the correct period. Every transaction is logged and auditable.
Workbridge
UKG Personalization
Missed punches dropped from 30% to under 5% — without touching UKG's core.
The result is that payroll staff no longer run the carryover calculation manually. The system ingests the timecard data, applies the math, and delivers clean pay code entries to UKG. The 28-day cycle closes the same way every time — not the same way most of the time, which is what manual processes produce.
“The calculation was always correct when we were careful. But careful takes time, and time is a limited resource in a payroll department. Automating it didn’t change the math — it just means the math runs without anyone having to do it.”
— HR Operations Manager, Airport Authority
What this kind of error actually costs in a public safety context
Payroll errors in public safety organizations carry consequences beyond the immediate correction. Firefighters and police officers work under collective bargaining agreements that specify pay rates, overtime rules, and dispute resolution processes. An error in the carryover calculation — a firefighter paid regular time for hours that should have been overtime, or overtime posted to the wrong pay period — is a grievable event. The correction requires documentation. In some cases, it requires back pay. Repeated errors erode trust in a way that takes time to rebuild.
The FLSA 7(k) calculation is also auditable by the Department of Labor. An organization that can’t produce a clean, timestamped record of how hours were classified across each 28-day period is not in a good position if a wage and hour question arises. Manual processes don’t produce audit trails. They produce spreadsheets, which are modifiable.
Workbridge
UKG Personalization
Migrating UKG Ready to Pro? Your customizations come with you. No rebuilds.
Public safety automation more broadly follows this pattern — the audit trail is often as important as the operational outcome. Emergency services organizations building shift fill processes on top of UKG Pro WFM find the same thing: the log of who was offered what, when, and in what order is what resolves grievances. The same principle applies to pay. A timestamped, automated calculation record is defensible. A spreadsheet someone ran during a busy payroll week is not.
“When we transitioned to CloudApper, we gained an audit trail we didn’t have before. Every carryover calculation, every pay code assignment — it’s all logged and traceable back to the source timecard data. That changes how confident we feel about the next Department of Labor inquiry.”
— Director of Human Resources, Metropolitan Airport Authority
The broader pattern: public safety payroll complexity inside UKG Pro WFM
The 28-day pay period is one configuration. Public safety organizations running UKG Pro WFM encounter a range of payroll requirements that native UKG handles partially or not at all: shift-based incentive structures, step pay across multiple sworn and non-sworn categories, callback and on-call pay rules that vary by role, and cross-period overtime calculations. The common thread is that public safety compensation is governed by a combination of FLSA rules, state labor law, and collective bargaining agreements — a three-layer structure that produces requirements no standard WFM configuration can fully address.
CloudApper’s HCM automation approach for these organizations works the same way it does for the airport authority: read the time and schedule data from UKG, apply whatever rule logic the labor agreement requires, and write results back to UKG Pro WFM as clean, auditable pay code entries. The integration is standard. The logic is configurable to the specific policy — whether that’s a 28-day FLSA period, a step-based incentive structure, or a shift premium calculation that varies by assignment type.
Workbridge
UKG Personalization
50+ HR gaps UKG leaves open. WorkBridge closes them in days, not months.
For this airport authority, CloudApper WorkBridge automated a bi-period payroll calculation that UKG Pro WFM couldn’t handle natively — a calculation that directly affects the pay of firefighters and police officers every 28 days. The math was already correct. Now it runs without anyone having to perform it.
If your government or public safety organization runs UKG Pro WFM and manages FLSA 7(k) pay periods, complex pay code structures, or cross-period payroll calculations that require custom automation, CloudApper can build the right solution. Contact the CloudApper team to start the conversation.
