The standard shift swap at most businesses: an employee texts the manager, the manager scrambles to find a replacement or lets staff sort it out on WhatsApp, the original schedule stays unchanged, and payroll runs from that schedule. Nobody updates it.
The result is predictable. One employee thought the other confirmed the swap. The other assumed the manager would handle it. A coverage gap appears. Pay goes to the employee who didn't show up.
Three Problems in One Bad Process
Informal swap management creates three distinct issues, and they compound.
Payroll errors. The person who covered the shift doesn't get paid for those hours. The person who stayed home does. Correcting this requires a conversation, a paper trail that doesn't exist, and a manual payroll adjustment.
Coverage gaps. In a text-or group-chat process, the manager often doesn't know the swap happened until the shift starts short-staffed. By then, options are limited.
No audit trail. If an employee disputes their pay or attendance, the record shows the original schedule. Nothing else.
A Better System
The mechanics of a functional swap process are straightforward. An employee submits a swap request through a scheduling app. The proposed swap partner accepts or declines. The manager reviews and approves. The schedule updates. Both employees receive confirmation.
Every step is logged. Payroll reflects actual hours, not scheduled ones. The whole chain takes under five minutes and produces a complete record.
The Step Most Teams Skip
Manager approval before the swap happens - not after. Most informal systems work in reverse: employees swap, the manager finds out later or doesn't, and the schedule never updates. The documentation problem is structural.
Some managers skip approval to reduce friction. The tradeoff is liability. If both employees miss a shift because each assumed the other took it, the manager owns the coverage gap with no record of what happened.
The Payroll Connection
Schedule changes that don't flow through payroll create drift. A team running informal swaps accumulates discrepancies that need manual correction every month. The time those corrections consume exceeds the friction saved by skipping a system.
A scheduling tool that pushes actual worked hours to payroll removes that correction cycle. The original schedule becomes a baseline, not the source of truth.
Common Escalations
Disputes about shift swaps rarely surface immediately. They emerge weeks later, during pay disputes or disciplinary conversations, when the only record is the original rota and neither employee's account matches it. That gap between event and dispute is the window a logged system closes.
Three-step approval - request, peer acceptance, manager sign-off - creates a chain of custody for every schedule change. It's not bureaucracy; it's protection for the manager and both employees.
Rezano
Rezano handles swap requests with a three-step flow: employee request, peer acceptance, manager approval. The schedule updates on approval. Payroll pulls from the updated schedule. The full chain is logged for any future dispute.