"Can you cover Saturday? I'll owe you one." In a healthy team you hear that every week, and it is a good thing: flexibility between colleagues is one of the reasons shift work stays bearable. The swap is not the problem. The problem is that six months in, nobody remembers who gave up three Saturdays in a row, and from that point on feelings do the accounting instead of facts.
And feelings are ruthless about fairness. One half-whispered "they always say yes to you anyway" can undo years of good atmosphere.
The informal debt is the most expensive kind
Untracked swaps create a parallel bookkeeping of favours, of "I owe you one", of tallies kept in heads. The catch is that everyone keeps their own: people who cover a lot remember everything, people who ask a lot remember little. Nobody is acting in bad faith, but the two ledgers never match.
A written note for every swap (who, with whom, when) is not bureaucracy. It is how you make the ledgers match. When the next request comes, you start from a fact both people can see, not from whoever has the better memory.
Three rules are enough, if they are clear
You do not need a ten-page policy. You need answers to three questions:
- By when can a swap be proposed? A change requested two weeks ahead and one requested at 11pm the night before are not the same thing, and it is fair to treat them differently.
- Who approves it? If only to check that skills still line up: if the swap leaves the opening shift without anyone who can handle banking, that is a problem to catch beforehand, not to blame on the swappers.
- What if it falls through? If the person who took the cover calls in sick, does the shift revert to its original owner or stay with the taker? Deciding this calmly, in advance, avoids deciding it heatedly, live.
Written once and applied always, these three rules strip swaps of their conflict potential and keep the good part.
The group chat is not a ledger
The negotiation can start in the chat, that is natural. But if the outcome lives only there, buried under two hundred messages, the official plan and reality quietly drift apart. Whoever looks at the calendar must see the shift as it really is, not as it was before this week's three swaps.
There is an underrated side effect too: as long as swaps go through the group chat, asking for one means asking in front of everyone. A dedicated channel, where the request goes only to whoever approves it, lowers the bar for people who hate asking favours in public.
Glance at the totals now and then
One last habit: once a month, look at who covered most and who asked most. Not to grade anyone, but because chronic imbalances need to be seen before they turn into resentment. Sometimes the fix is disarmingly simple: the person who always covers Saturdays might just want to be asked, once in a while, whether it still works for them.
With Sked Solve, swaps go through the app: request, approval, and a calendar that updates for everyone, no mental bookkeeping required. If this hits close to home, the site walks through how it works.