A shift swap is when two people who are already rostered exchange their allocated shifts between themselves — one takes the other's shift and vice versa — rather than either of them simply cancelling.

How it works

Shift swaps usually need three things to go smoothly:

• Mutual agreement — both people involved actively agree to the exchange, rather than one unilaterally handing off a shift.
• Eligibility checking — the business (or the system) confirms the receiving person is actually able to do the shift — holds the right skill, isn't already committed elsewhere, and isn't over any applicable hours limits.
• Approval and record-keeping — most businesses require a manager to sign off the swap so the roster of record stays accurate for pay, attendance, and any reporting obligations.

Informally, shift swaps often happen over text or group chat with a manager only finding out after the fact — which is exactly the pattern that causes rosters to drift out of sync with who's actually expected to show up.

Why it matters

Shift swaps give staff flexibility to handle personal conflicts without creating a gap in the roster, which is good for both sides — the business keeps the shift covered, and the worker isn't stuck choosing between the shift and something else. The risk is an unrecorded or unapproved swap: if the person who shows up isn't the person the roster says should be there, attendance, pay, and reliability records for both people become wrong.

In Chronomancer

Chronomancer's bid-based model reduces the need for informal swapping in the first place, since people bid directly for the shifts they want. Where a change is still needed after allocation, moves are made through the roster's Revise state or, on the night itself, through audited Live Ops moves — never an unrecorded, off-system swap — so every change is logged against who actually ends up on the seat.