Shift swaps between colleagues: the rule that stops the chaos
Echipa HR 365 · reviewed 2026-09-04 · 5 min read
Swapping happens in any shift team, with or without your permission. The only question that matters is whether a trace remains: who was scheduled, who is coming instead, and who answers if nobody comes. Without a trace, at month end nobody can reconstruct that day.
Why it is worth allowing rather than tolerating
Banning it does not work: people will swap anyway, only without saying so. What gets lost then is visibility — and the planner finds out at reconciliation that somebody was there who was not on the rota and somebody was not there who was.
Allowed and recorded, a swap becomes an advantage: the team solves part of its own problems and the planner is no longer involved in every arrangement. Their workload falls rather than rises.
The three-step procedure
Who does what, in order
- The person who cannot come — finds the stand-in and submits the request — with their name, not “somebody is covering me”
- The stand-in — confirms explicitly; without their confirmation, the request does not exist
- The manager — approves or refuses, checking the stand-in’s competence and accumulated hours
What the manager checks, concretely
| The check | What happens if you skip it | How long it takes |
|---|---|---|
| Competence for that post | The post is formally filled and the work cannot be done | Seconds, if you have the matrix |
| The stand-in’s accumulated hours | Somebody ends up on two consecutive shifts with no real rest | Visible from the rota |
| It does not create a gap elsewhere | You cover one shift and uncover another | Visible from the rota |
| Is it the first time or the fifth this month | A pattern of repeated swaps hides a planning problem | A glance at the history |
The last row brings the most valuable information. Two people swapping with each other five times a month do not have a personal problem — they have a rota that does not suit them. The signal is worth reading, not merely approving.
Who answers if nobody turns up
The rule has to be written before the first case, otherwise it gets decided on the day it happens, which means badly. The version that works and is also fair: after the manager approves, responsibility passes to the stand-in. Before approval, it stays with the person originally scheduled.
From which it follows why approval has to be quick: a request left pending for two days keeps responsibility with somebody who has already made other plans. A 24-hour approval deadline solves that.
The limits worth setting
- A maximum number of swaps per month, per person. Not as a sanction, but as a signal: above it, the conversation is about the rota, not the request.
- A minimum notice period — 48 hours, say, with exceptions for genuine situations.
- No swaps that produce two consecutive shifts for the same person.
- No swaps between posts requiring different qualifications, however willing both parties are.
What you read from the swap history
After two or three months of recording, the history becomes one of the most useful sources of information about the rota — more honest than any survey, because people are not answering a question, they are solving a problem.
| What you see | What it usually means | What you check |
|---|---|---|
| The same weekday, always given away | A rota incompatible with something fixed in their life | It can be solved permanently, not by a weekly swap |
| Two people always swapping with each other | Their schedules should actually be reversed | One permanent change removes dozens of requests |
| One person always taking on, never giving away | Either they need the hours, or they are pressured into accepting | Worth a conversation; both possibilities matter |
| A spike of requests in a particular period | Something predictable: start of the school year, a season | Anticipated in next year’s planning |
The second row produces the biggest gain for the smallest effort. Two people who swap with each other constantly are telling you, without asking for anything, that the original rota is wrong for both — and a single permanent change removes every future request.
Where to start
If swaps already happen over messages, do not ban them — just ask that both confirm in the same place, whatever that place is. The trace matters more than the tool, in the first month.
After two months of records, read the history against the four patterns above. You usually find at least one pair swapping constantly — and one permanent rota change removes dozens of future requests.
Set the responsibility rule before the first case where nobody turns up. Written afterwards, whatever it says, it will look like it was made against somebody in particular.
Can I refuse a swap between two people who agree?
Yes, and that is precisely the role of approval: if the stand-in lacks the qualification for the post, or would end up on two consecutive shifts, their agreement does not change the fact that the work cannot be done safely. Give the reason, so the refusal does not look arbitrary.
What if swaps happen anyway, without telling me?
First check why: usually the procedure is too heavy or approval takes too long. A flow requiring three days’ wait for a shift the day after tomorrow will be circumvented, whatever rules you write.
Swap requests with the stand-in’s confirmation and approval
A swap becomes a request with two signatories and one approver, and the rota updates itself — so at month end you no longer have unexplained deviations.
Free account, every module for 7 days, no card required.