The Shift Change Nobody Told Them About

Ask a security company owner about their worst rota moment and you will often hear about someone who didn't turn up. Dig a little and a lot of those stories change. The officer did turn up. Just not at the site, or the time, that the office thought.

The rota was right. The change was made. Nobody made sure the officer knew.

How it happens

It is almost never carelessness. A client rings at four in the afternoon and wants an extra body on Saturday night. The office moves someone, fixes the rota, and gets on with the next call. The officer gets a text, or a message in a group chat, or a voicemail. Maybe they see it. Maybe they are on another job, or asleep after a night shift, or the message sits under forty others.

Now the rota says one thing and the officer believes another. Neither side has any reason to doubt itself, so nobody checks until a shift is missed or somebody is standing at the wrong door.

The three versions of the truth

When changes travel by message, a company ends up with three versions of the rota:

• What the office thinks is happening.
• What the officer last remembers being told.
• What the client has been promised.

On a good week they match. On a busy week they drift apart, and you only discover it at the worst moment, usually first thing in the morning with a client on the phone.

Good managers burn their mornings on this. Ringing round to confirm things that were already agreed. Asking "did you get my message?" Writing the same change down in two places. It is wasted effort, and none of it is the fault of the people doing it. They are patching a gap that the process left open.

Why "I told them" isn't enough

There is a habit in this industry of treating a sent message as a delivered fact. "I told him on Thursday." Maybe you did. But if the only record is a text on one phone, then the question of whether it landed has no answer, and it is the officer who ends up carrying the blame for something the process failed to prove.

That is unfair on your staff. It is also expensive. A missed shift because of a change nobody confirmed costs you the cover, the client's patience, and sometimes a good officer who is fed up of being the one in the wrong.

What I'd want in place

You don't need anything clever. The test is simple: when a shift changes, can you tell, without ringing anyone, that the person affected has seen it?

A few things that help whatever you use:

One place where the current rota lives. If the answer to "what is Dave doing on Saturday?" depends on which chat you scroll, you have more than one rota.

Changes go through that place, not around it. The quick text is tempting. If it is not also reflected in the rota, it will be forgotten by Monday.

Officers look at their own shifts. If they can open their upcoming shifts themselves, they are not depending on a message surviving. Many of the questions the office gets asked simply stop.

Treat late changes as a different kind of change. A shift moved two weeks ahead is housekeeping. A shift moved the same afternoon needs a direct, confirmed conversation. Know which one you are doing.

Look at the pattern. If the same site, or the same time of week, keeps producing "I didn't know", that is a process problem to fix once, not a series of individual mistakes.

It matters more as you grow

With ten staff you can hold most of this in your head. With forty you can't, and the office starts spending a large part of the week acting as a human switchboard between the rota and the people on it. That is time you could be spending on clients and on tenders.

The goal is a rota that your staff can see for themselves, so a change made in the office reaches them without anyone having to remember to pass it on. In TacDesk your staff see their shifts in the app, which is the reason I care about this. But the principle holds whichever tool you use: the rota should reach the officer, not wait for them to ask.

If you want the longer version of how to build a rota that holds up, I wrote a guide to security guard scheduling software in the UK.

If you'd like to see how this works in practice, book a demo and I'll walk you through it.