Field notes › Rostering
Shift swaps: the arrangement your roster doesn't know about
Two workers sort it out between themselves. One has a wedding, the other wants the hours, they shake on it in the crib room and both turn up where they agreed. The office finds out when the timesheet looks wrong, or when the client mentions a name that is not on the roster, or never.
It is a small act of cooperation and it is also the single most common way a compliant roster becomes a non-compliant one.
Why the swap breaks things
The person who turns up is not the person the checks were run against. They might not hold the ticket this site requires. Their induction for this particular site might have lapsed, or never existed, because they normally work somewhere else. They might be at the end of a swing where the fatigue rules the site runs to would say no.
None of that is visible, because as far as every system you own is concerned, the original worker is on that shift. The roster is wrong, the compliance record is wrong, and the audit trail records a booking that did not happen.
Then there is the mundane damage. The wrong person gets paid, or the right person gets paid for a shift they did not work and has to be clawed back. The client is invoiced against a name that does not match their gate records. Someone spends a Friday afternoon untangling it.
The reason it happens is not defiance
It is worth being clear-eyed about the cause. Workers do this because the official path is slow. Ring the office, hope someone answers, explain the situation, wait for a call back, hope it gets actioned before Monday. The unofficial path takes thirty seconds in the crib room.
Any policy that just says do not do it loses to that gap. The only durable fix is to make the official path faster than the informal one, or close enough that the informal one stops being worth the risk.
What a good swap flow looks like
The shape most likely to actually get used: the worker who wants out raises it from their phone, the office sees it as a request rather than a done deal, and the replacement is chosen from people who genuinely can do it.
That last part is where the compliance work happens. The replacement has to pass the same checks as the original booking: the site's required competencies, verified and current, the site induction, no clash with another shift, and their own availability. If your system runs those checks on the server before the booking lands, the swap cannot introduce a non-compliant person, no matter how much of a hurry everyone is in.
Until a swap feature exists in whatever you run, the practical stand-in is the open shift. The worker who wants out tells the office, the office releases the shift back to the crew as open, and whoever puts their hand up gets checked on the way in. It is one extra step and it keeps the record straight.
Tell the people affected
A swap has a third party: the client. If a different person is coming, the site should hear it from the system rather than notice it at the gate. That is the same notification that fires for any change of allocated worker, and it is the difference between a swap being a non-event and a swap being a phone call.
The worker coming off should also get a clear confirmation that they are off. Half the informal swaps that go wrong go wrong because one of the two people was not certain it had been approved, and both turned up, or neither did.
Make the rule easy to say
The version of the rule that actually gets remembered on a night shift is short: sort it out with each other if you like, but it is not real until the office has changed the roster. Not a form. Not a policy number. One sentence that fits in an induction and in a text message.
Pair it with a genuinely quick path for making it real, and the crib room agreement becomes the start of the process rather than a replacement for it.
What to watch for
If you want to know how big this problem is in your own operation, compare gate records or timesheets against the roster for a month and count the mismatches. It is a dull afternoon and it is usually informative. A handful of mismatches means the official path is roughly working. A steady stream means your crew has quietly built a parallel rostering system, and it is worth asking them why theirs is faster than yours.
The compliance page covers the checks a replacement has to pass, and last-minute cover deals with the version of this that starts at 4am.