Shift swapping: how to let people trade shifts without breaking the week

Two people agree to trade. Sam takes Dana's Saturday, Dana takes Sam's Tuesday. Nobody is short-staffed, both are happy, and the manager says yes in three seconds because it looks free.

Usually it is. The times it is not are predictable, and they all come from the same place: a swap does not move hours between shifts, it moves hours between people. Almost every rule that governs a schedule counts per person.

What a shift swap is, and what it is not

A shift swap, or shift trade, is two employees exchanging assigned shifts with each other, with the employer's agreement. Three neighbouring things get called the same name, and the difference decides which rule applies:

• Giving away a shift. One person drops it, another picks it up. One loses hours, the other gains them. Nothing comes back the other way.
• Picking up an open shift. An unassigned shift someone claims. Adds hours to one person and takes them from nobody.
• Covering a call-out. An absence filled at short notice. In almost every ordinance that regulates scheduling, this is an employer-initiated change, not an employee request.

Only the first of these is a true swap, and only a true swap is roughly neutral for the store. It is rarely neutral for the two people involved.

The four rules a swap can break

1. Overtime, counted per person, per workweek

Under the FLSA, overtime is owed to an individual for hours over 40 in a single workweek. A trade that looks even across two people is often not even for either of them.

Sam gives up a five hour Tuesday and takes an eight hour Saturday. Sam is up three hours, Dana is down three. If Sam was already sitting at 38, Sam finishes the week at 41, and the store owes premium pay it never planned for. Dana, meanwhile, drops to 35 and may be unhappy about it for entirely different reasons.

The check is one number per person: where does this trade leave each of them for the week. Not the store total, not the department total. Overtime pay and the 40-hour rule covers how the workweek is defined, and why two weeks cannot be averaged to make the arithmetic come out.

2. Minors, where the limits are hours and clock times

An adult swap is a question of totals. A swap involving anyone under 18 is a question of totals and of when the shift starts and ends, both of which change during the school year. A late Friday close that is fine for one employee can be prohibited for the other. Scheduling minors sets out the federal limits and where states go further.

3. Predictable scheduling, where the question is who asked

Where a fair workweek or predictive scheduling rule applies, what matters is not that the schedule changed but who caused the change.

Oregon's law is the clearest written example. It covers retail, hospitality and food service employers with 500 or more employees worldwide, and requires the written schedule at least 14 calendar days ahead. On employee requests it says: "Changes to the written work schedule resulting from your written requests are not subject to the advance notice requirements of this law" (Oregon BOLI).

One word in that sentence does the work: written. A swap the two employees asked for in writing sits on the employee-request side of the line. The same swap agreed verbally in the stockroom and then typed in by the manager is much harder to show as anything other than an employer change. City ordinances word this differently and set their own thresholds, so read your own before relying on it. Fair workweek laws lists which cities have one.

4. The close followed by the open

The trade most likely to cause trouble is the one that puts somebody on a closing shift and then the next morning's opening shift. American retail has a word for it, a clopening, and New York City regulates it by name. Some ordinances address the gap between two shifts directly, so check whether yours does. Even where nothing legal applies, this is the swap that produces the late arrival, the missed break and the call-out two days later. It is worth flagging in your policy on its own merits. Break and meal rules covers the rest side of the same problem.

A swap policy that fits on one page

Nothing here is required by law. All of it exists to keep the four rules above from surprising you:

1. Both people ask, in writing. A message thread is enough. It records who wanted the change, which is the fact that matters later.
2. A manager approves before it is final. Two employees can agree. Only the manager can see both weekly totals.
3. Approval is checked against one number. Each person's hours for the week after the trade. If either crosses 40, the swap is a cost decision, not a favour.
4. Same role by default. A trade that leaves nobody able to open the till is a staffing problem wearing a swap costume.
5. A deadline. Pick one, for example 24 hours before the earlier of the two shifts, and hold it. This is a choice, not a rule.
6. Republish the schedule. The posted version has to become the true version, immediately.

The mistake behind almost every argument

The schedule everyone looks at stops matching the schedule payroll reads.

A swap gets agreed in a group chat. The manager nods. The posted schedule still shows the old version, so a third employee plans around a shift that is no longer Sam's. Two weeks later, timesheets show hours nobody can account for, and the disagreement is no longer about the swap, it is about who said what.

When it goes further and nobody turns up at all, the policy question follows: no call, no show covers what to write down before you need it, and the pay deduction that can cost far more than the missed shift.

The fix is unglamorous: one schedule, updated at the moment of approval, visible to everyone without anyone having to ask.

How this works in Squadra

A swap is a manager edit. You change the two shifts, and the shared schedule link the team already has shows the new version straight away. There is no new link to send and nothing for anyone to refresh. For a small team, where the conversation happens face to face anyway, the written trail is the request message and the schedule itself.

In practice

Let people trade. It is one of the few things that costs a manager nothing and buys real goodwill. Just keep three habits: get the request in writing, check each person's weekly total before saying yes, and republish the schedule the moment you approve. The swap is not the risk. The unposted swap is.