Premium pay tied to commitment: the FTE attainment model

A core night-shift nurse on a med-surg floor works her three twelves a week, every week. She covers her commitment to the unit. She has done this for six years.

A per-diem nurse on the same unit works one shift a month, choosing the one with the highest incentive. Chronic Friday-night gaps mean there’s often a bonus available.

Under a flat-bonus structure, both nurses get the same dollar amount for that Friday shift. The core nurse who anchored the schedule for the other fifty-one weeks of the year gets the same per-shift premium as the per-diem who showed up once for the highest-paying slot. Worse: a core nurse who is short of her FTE for the period can pick up a bonus shift and collect the premium, even though what the unit needed from her was the regular shift she didn’t work, not the bonus shift on top.

A flat shift bonus doesn’t account for whether someone has already met the hours they committed to work.

Not every bonus is equal

The same bonus can pay for extra coverage or for hours already included in a worker’s commitment.

To a clinician who has already hit her committed FTE, the bonus is what it’s supposed to be: a premium for extra hours on top of her commitment. It rewards going above and beyond. To a clinician who hasn’t hit her commitment yet, the same bonus is something else. It pays her premium rates for hours she was already expected to be working. She substitutes a base-rate core shift for a bonus-rate shift, collects the difference, and the unit ends up paying more for the same coverage it was always going to get.

When we audited customers’ incentive spending, we found workers substituting bonus hours for core hours. Some of that premium spending bought the coverage the unit already expected, rather than additional coverage.

The structure also gives the same premium to a core worker who has already met her commitment. It doesn’t distinguish those extra hours from hours that fill an existing commitment.

FTE attainment as the gate

We tied premium eligibility to the worker’s committed FTE for the pay period. Before reaching it, additional shifts pay at base rate. After reaching it, they pay the configured premium. The rate therefore depends on the worker’s progress as well as the shift.

In the example above, the per-diem nurse has no FTE commitment to a hospital-employed role, so his pickup goes through whatever rules govern his agreement. The core nurse who is below her commitment picks up the Friday shift at base rate, because the system counts that shift toward her commitment first. Once her cumulative scheduled hours cross her committed FTE, the next shift she picks up unlocks premium pay.

For a worker who meets her FTE on her regular schedule, additional pickups receive the premium. The incentive pays for hours beyond that commitment.

There’s a tradeoff worth naming. FTE attainment gating is harder for workers to mentally model than a flat bonus. A clinician glancing at the shift board no longer sees a single posted rate; she sees a rate that depends on where she is in her pay period. We chose to absorb that complexity in the UI---showing each worker her FTE progress and the rate she would actually be paid for each posted shift---rather than push it onto her to compute. The signal it produces is worth the friction.

The snapshot model

The mechanism underneath the gate is an FTE Attainment Snapshot. For every worker in a workforce group with attainment-based incentives enabled, the system maintains a running snapshot for the current pay period: committed FTE, scheduled hours, worked hours, and a derived attainment percentage.

Whenever a relevant event fires---a shift is picked up, dropped, traded, or worked---the snapshot updates. When the system needs to decide whether a given incentive applies to a given pickup, it consults the snapshot and asks: has this worker crossed her committed FTE line for this period yet, including this shift?

If she hasn’t, the shift counts toward her commitment and is paid at base. If she has, premium pay unlocks.

The snapshot is configurable at the Workforce Group level. Different units, facilities, and worker classes have different commitment structures, and the attainment configuration tab in the workforce group drawer is where each is set: the committed FTE definition, the pay period boundary, the shift types that count toward attainment, the incentive pay codes gated by attainment.

A snapshot comparison KPI overlay sits on top of the snapshot data and lets administrators see, at a glance, how attainment is distributed across a workforce group. Two unit managers running otherwise similar floors can see whether their workers are clustering above commitment, below it, or right on the line, and whether incentive spend correlates with attainment. That’s the analytics surface we use to tune the gate itself: deciding whether the committed FTE definition for a workforce group is set at the right level.

Bulk overrides for gap shifts

Some urgent coverage gaps need an exception.

For a holiday weekend, an unexpected unit reopening, or a chemo bay that must stay staffed, an operator may need to offer premium pay regardless of attainment. We built an explicit override for those cases.

The Bulk Shift Rate Overrides wizard is the operator’s knob. Admins filter the open-shift set by unit, role, date range, and shift attributes; preview the matched shifts; set a rate override; and apply the change across the set in a single action. The override carries through to the incentive engine, which treats the shift as having a different rate and a different attainment posture for the duration of the override window.

Because a bulk rate change can affect substantial spending, the wizard requires a preview and a reason. It records who made the change and when, so the team can review it later.

The plumbing: UKG sync, money pay codes, async jobs

None of the above matters if the right dollar amounts don’t make it onto payroll.

Many of our larger customers run UKG as their time-and-attendance and payroll system. When a worker picks up a shift and the incentive engine decides on a rate (base or premium, depending on attainment), the result has to land in UKG as a specific pay code with a specific dollar amount attached, before the next payroll cutoff. If it doesn’t, the worker is paid the wrong amount, and the audit trail and the paycheck disagree.

The integration is shaped by three constraints.

Money pay codes. Earlier versions of our UKG sync supported hours-based pay codes (regular hours, overtime hours, a handful of differentials). FTE-attainment incentives required a money pay code: a flat dollar amount on a shift, independent of the hours worked. Adding money pay code support to the sync was the precondition for any of this to work end-to-end. The worker’s timecard now carries both her hours and the discrete dollar amount of the incentive, as a separate line item that UKG knows how to process.

Async, dedicated jobs. UKG’s API is rate-limited and occasionally slow. A worker picking up a shift cannot wait on a synchronous round-trip to UKG before the system confirms the pickup. The sync runs in dedicated async jobs that pick up pending changes, batch them sensibly, retry on transient failures, and surface persistent failures to the operations team rather than swallow them. The system stays responsive to the worker. UKG stays consistent with the system, eventually.

Auditability across the boundary. Every dollar of incentive pay has to be traceable from the worker’s pickup, through the attainment snapshot that gated it, to the rate the incentive engine returned, to the money pay code on the UKG timecard, to the paycheck. Payroll is a domain where “trust me, the math works out” isn’t an answer. The sync writes structured records at each handoff so any premium dollar can be reconstructed.