Before You Approve That Swap: A Manager's Checklist
Approving a shift swap takes ten seconds, but the wrong approval causes a no-show, an overtime bill, or a compliance problem days later. Here's what to actually check first.

A shift swap request shows up in your inbox and the easy thing to do is tap approve and move on. That's fine most of the time — but the swaps that go wrong usually go wrong because the manager approved on autopilot instead of checking the two or three things that actually matter. A bad approval doesn't cause a problem immediately; it causes one three days later when the replacement person doesn't show up, or six weeks later when payroll flags unexplained overtime.
The Checks That Actually Matter
Before you approve, run through this in your head — it takes less time than it sounds:
- Skills and certificates. If the original shift required a certification (food handler, forklift license, a specific clinical credential), does the person picking it up actually have it? Swaps bypass the normal assignment process, so this is the easiest check to skip by accident.
- Hours and rest rules. Will the swap push the picking-up employee into overtime, or put them under the minimum rest period before their next shift? Someone trading a Tuesday close for a Friday close might look harmless until you notice they already worked Thursday close and are now opening Saturday.
- Overlapping time off. Has this person already got approved time off that overlaps, or requested it and you just haven't actioned it yet? Approved time-off should already block the shift, but double-check if your system doesn't enforce that automatically.
- Staffing mix, not just headcount. A swap can keep the number of people on shift the same while quietly removing the only keyholder, the only trained cashier, or the only bilingual staff member on the floor. Check who's left, not just how many are left.
- Pattern, not just the one request. Is this the same two people swapping back and forth every week in a way that's really just an informal schedule change? That's not necessarily bad, but it's worth knowing so your published schedule reflects reality.
Named Swaps vs. Open Offers
A named swap — one employee offering their shift to a specific coworker — is usually lower risk because both people have already agreed to it and you're just confirming it's workable. An open offer to the whole team or department needs an extra beat of attention, because whoever claims it first might not be the person you'd have picked. If the shift needs a specific skill or certificate, make sure the system (or you, manually) is actually filtering who can even claim it — otherwise you're approving blind.
When to Say No
Saying no to a swap feels awkward, especially when both employees have already agreed between themselves and are just waiting on a rubber stamp. But a few situations are worth pushing back on:
- The incoming person doesn't meet a hard requirement — a certificate, a minimum age for a task, a legal rest-hour rule.
- The swap creates an overtime cost you weren't planning for and can't justify.
- It leaves a shift without anyone who can actually run it — no keyholder, no one trained on the register, no one who speaks the language your customers need.
- It's part of a pattern that's eroding the schedule you actually built, rather than a genuine one-off.
In all other cases, approve quickly — the whole point of letting employees arrange swaps themselves is to take coverage problems off your plate, not to recreate the same bottleneck at the approval stage. A system that checks skills, hours, and time-off conflicts automatically — the way helloswap's approvals inbox does — removes most of the guesswork, but even with no software at all, these five checks are the difference between a swap that solves a problem and one that creates a new one.