The Shift Swap You Only Hear About After It Has Happened

Somewhere on your rota this week, two officers have already swapped a shift. One of them had a family thing, the other wanted the extra hours, and they sorted it out between themselves on their phones. It took two minutes and everyone was happy.

You will find out when you ring the wrong person, or when the client rings you.

I am not against swaps. Officers are adults, and a team that helps each other out is a good team. The problem is not the swap. It is that the rota did not move when the swap did.

The rota says one thing, the site says another

A rota is only useful if it is true. The moment two people agree a swap in a text thread, you have two versions of the week: the one you published and the one that is actually happening.

Most of the time nothing goes wrong. Then it does. The officer on the rota is not the officer on site, and you ring the first one about a late arrival or a missed check call. They are at home, off shift, and confused. Meanwhile the person who is actually on site is not on your list as being there at all.

If something happens on that shift, an incident, an injury, a dispute with the client, the paper trail says someone else was working. That is an awkward conversation to have after the fact.

You lose track of who is covering what

Swaps do not just move a shift. They move who knows the site.

Swap a quiet commercial unit for a hospital door and nobody thinks twice. Swap a site that needs a specific brief, a gate code, a key, an awkward client contact, and the swap quietly puts someone on it cold. I wrote about that separately in the officer who covers a site they have never seen. Informal swaps are one of the main ways it happens, because nobody in the middle is checking.

Hours are the other thing. Two officers agreeing a swap rarely sit down and work out what it does to a week of long shifts and short turnarounds. You are the one carrying that, whether you knew about it or not.

Banning swaps does not work

The obvious fix is a rule: no swaps without my say so. I have seen owners try it. It lasts about a fortnight.

Officers still need to swap. Life does not fit around a published rota. All a ban does is push swaps further underground. They still happen, you just stop hearing about them at all, and the officers who used to mention it now keep quiet because they know the answer will be no.

What you want is the opposite. You want swaps to be easy to ask for and impossible to do without you seeing them.

What a sensible swap looks like

Keep it simple. A swap is only a swap when three things are true.

You know about it before it happens. Not a text the night before saying "Dave's covering me". A request, with both names and the shift, that reaches whoever runs the rota.

Someone checks it works. Is the person taking the shift able to work that site? Do they have the hours? Are they where they need to be at the start time? That check takes seconds if the information is in front of you and is guesswork if it is not.

The rota changes, and everyone sees it change. The published rota is the record. If it is not updated, the swap did not happen as far as the company is concerned, however many texts were sent.

None of that is heavy. It only feels heavy when it runs through your own phone, in between everything else, at seven in the morning.

Why it ends up on the owner

In a small company it ends up on you for the simple reason that you are the one who knows what the rota is supposed to look like. Somebody has to hold the real picture, and if the tools do not do it, you do.

That is a lot to ask of one person's memory. It also means every swap is a small interruption: a call, a message, a quick check against a rota you carry around in your head. Ten of those a week is not a crisis. It is just a steady drain, and it is the sort that makes owners say the rota takes over their life.

Where software helps and where it does not

I will be straight about this. Software does not stop two officers texting each other. What it can do is give them somewhere better to go than the text thread, and give you one place where the rota is the rota.

If you want the wider picture of what to look for, I have set it out in our guide to security guard scheduling software in the UK. The short version is that the test is not how many features it has. It is whether your officers actually use it for the thing they were going to text about anyway. If asking for a swap is easier in the app than in a message, they will use the app. If it is harder, they will not.

What I would do this week

You do not need to buy anything to start.

Ask your team, honestly, how many swaps happened last month. Do not make it a telling off. Just ask. Most owners are surprised by the answer.

Then pick one rule and stick to it: swaps are fine, but the rota gets updated before the shift starts, and you or whoever runs the rota sees it first. Tell people why. Officers respond well to "I need to know who is on site if something goes wrong". They respond badly to "because I said so".

If you want to see how we handle this in TacDesk, I am happy to show you. Book a demo at tacdesk.co.uk/demo.