How a shift swap works
Two employees agree to exchange specific shifts: A takes B's Tuesday night, B takes A's Thursday day. The request goes to the supervisor, who checks the rules and approves or rejects. Once approved, the roster is updated for both, the change is notified to both employees, and attendance for those days is judged against the new shifts.
The informal version, a WhatsApp message saying 'bhai, meri Tuesday ki duty kar dena', is the source of many no-shows and payroll errors. The supervisor does not know, the register still shows the original name, and when the swap partner forgets, the post is unmanned with no record of who was responsible.
Rules a swap must pass
The purpose of approval is to run a small set of checks that the employees themselves cannot see across the whole roster. Write them into policy and, if your system supports it, into the swap workflow so that a request failing a rule is rejected automatically.
- Same skill or licence: an armed post cannot be swapped to an unarmed guard; an ICU night cannot go to a ward trainee.
- No hours breach: neither person should exceed 9 hours in the day or 48 in the week after the swap, or lose their weekly off.
- No double booking: the person taking the shift must not already be rostered elsewhere at that time.
- Minimum rest: no back-to-back shifts with less than the policy rest gap (commonly 8–12 hours).
- Cut-off: requests must reach the supervisor before a stated deadline (for example 24 hours before the shift).
Swaps, pay and records
A swap should be pay-neutral where the shifts are equivalent. Where they are not (a day shift swapped for a night shift), the allowance follows the person who actually works the night, which is one more reason to pay night shift allowance on worked shifts rather than rostered ones. Overtime is judged for each person on their own actual hours after the swap.
Keep a record of every approved swap: who requested, who accepted, who approved, and when. In a client dispute or a labour inspection, the roster and the attendance register must reconcile, and the swap log is what explains why the name on the register differs from the originally published roster.
Guard Suresh is rostered on the 20:00–08:00 night at Site A on Friday but has a family function. Guard Anil, rostered on Saturday day at the same site, agrees to take Friday night if Suresh takes his Saturday day. The supervisor checks: both are unarmed guards, Anil's Friday night ends at 08:00 Saturday so he would not have been able to do Saturday day anyway, and neither exceeds 48 hours that week. He approves. The roster updates, both get a notification, and the Friday night allowance goes to Anil.
Attend Mitra's employee app lets a worker propose a swap with a specific colleague; the colleague accepts, the supervisor approves, and the published roster updates for both with a full audit trail. The system warns on double booking and on approved-leave conflicts, and attendance for the swapped days is then compared against the new assignments.