Shift Swap

A shift swap is two employees trading scheduled shifts, so one covers the other’s hours and vice versa. It’s the standard release valve in shift-based work — retail, hospitality, healthcare, logistics — and the usual alternative to taking leave for a single awkward date.

A swap is not leave. Nobody’s balance changes and no entitlement is used. But the hours move, and three things move with them.

What travels with the hours

Cost. The hours are now worked by a different person, with a different weekly total and possibly a different rate.

Compliance. Rest periods, maximum hours and scheduling rules attach to the individual, not the shift.

Capability. The shift may need a certification, a key, a language or a till code the covering employee doesn’t have.

That’s why swaps need approval, and it isn’t bureaucracy. A trade arranged in a group chat is invisible to all three checks until something goes wrong.

The overtime trap

This is the one employers reliably miss.

Under the FLSA, overtime is owed on hours actually worked over 40 in a workweek. It makes no difference that the swap was voluntary, that the employee asked for it, or that total hours across the two people are unchanged. If covering a colleague takes someone from 36 to 44 hours, the employer owes overtime on four of them.

The swap feels cost-neutral. It isn’t — it’s a redistribution that can push one person over a threshold the other was nowhere near.

The clinching evidence is the exception. 29 CFR 553.31 lets substituted hours be excluded from the overtime calculation — but only for two employees of the same public agency, where the trade is “made freely and without coercion” and the agency approves it in advance. Each is credited as though they’d worked their normal schedule.

That carve-out exists precisely because, without it, swapped hours count. Outside public agencies there’s no equivalent.

Where fair workweek laws bite

A growing set of US jurisdictions — Oregon statewide, plus Seattle, Chicago, Philadelphia, New York City, San Francisco, Berkeley, Emeryville, Evanston and the City and County of Los Angeles — require advance schedule notice and predictability pay when the employer changes them.

Who initiated the swap decides whether that premium is owed. Most of these laws exempt employee-initiated swaps: Berkeley, Emeryville, San Francisco, LA City, LA County, Chicago, Seattle and NYC fast food all carve them out. A change the employer imposes is a different matter. So the source of a swap isn’t a footnote — it’s the compliance fact worth recording.

The second trap is turnaround time. Many of the same laws set a minimum rest between shifts and penalise breaches — commonly 10 or 11 hours, 9 in Philadelphia — with premiums from time-and-a-half (Oregon, Seattle, LA, Emeryville) to 1.25× (Chicago) or flat payments ($100 per clopening shift in NYC fast food, $40 in Philadelphia).

Two employees trading in good faith can easily create a short turnaround that neither of them is thinking about. The system has to catch it, because they won’t.

Running swaps well

• Require approval, but make it fast. Slow approval pushes swaps into the group chat, where none of the checks happen
• Check the receiving employee’s weekly total before approving, not after payroll runs
• Check the turnaround either side of the swapped shift against your local minimum
• Gate by skill or certification, so only qualified colleagues appear as options
• Record who asked — employee-initiated versus employer-initiated is what predictability pay turns on
• Don’t deduct anything. A swap isn’t a leave type, and recording it as one corrupts both balances
• Watch the pattern. Someone swapping away the same shift repeatedly is telling you something about the schedule

This entry is general information, not legal advice. Overtime, scheduling, and rest-period rules vary by country, US state, and city.