Double Booked Is a Rota Problem, Not a People Problem

Every owner has had the morning where the numbers don't add up. Two people are standing at one site, each sure it's their shift. Across town, a site that should have someone on it has nobody.

The first reaction is to ask who got it wrong. I think that is the wrong question, and I'd rather explain why.

It is rarely one person's mistake

When a double booking happens, there is usually a trail behind it. The rota went out on Thursday. On Friday someone swapped with a colleague on the phone. On Saturday the supervisor moved a shift to cover a sickness and told one person but not the other. Sunday night, the version on the spreadsheet still says what it said on Thursday.

Every one of those steps was a reasonable thing to do. Nobody was careless. The problem is that you now have several versions of the truth: the spreadsheet, the group chat, a text message, and whatever the supervisor is holding in their head. They agree most of the time. Double booking is what it looks like when they don't.

If your rota lives in more than one place, you will get double bookings. It's a matter of when, not whether.

The two failures look the same from the client's side

An owner tends to think of a double booking as the lesser problem. Too many people on site is waste, but at least the site is covered. A gap is the one that hurts.

They come from the same cause, though. A shift was moved or swapped, and the change reached some people and not others. Which way it falls depends on luck. One week you pay for two people. The next week the client rings to ask where the cover is.

The client does not see the difference between those two. They see a company that doesn't quite know who is where. That is a hard impression to shift once it forms, and it is the sort of thing that comes up when a contract is up for renewal.

What it does to your own people

The cost is not only financial. Turning up to a shift that someone else is already working is a bad start to a night. Being told you were never needed, after you rearranged your evening, is worse. Do it to someone more than once and they stop trusting the rota. Once that happens they start checking with colleagues before they commit, or they simply stop answering when you ring.

The reverse is just as bad. Someone who was told to cover a shift on Saturday, hears nothing more, and wonders on Sunday whether it's still on. People who aren't sure whether they are working are not people who feel looked after.

No good operator wants their staff to feel like that. It happens because the system lets it.

The fix is boring, and it is one rota

The answer is not more phone calls or a stricter rule about telling the supervisor. Those help for a few weeks and then drift, because they rely on everyone remembering every time.

The answer is a single rota that everyone works from. When a shift moves, it moves in one place, and the people affected see it where they already look. Nobody has to be told twice, and nobody has to remember to tell anyone.

A few things follow from that, whatever tool you use:

• A change is only real once it's on the rota. A swap agreed on the phone is not a swap until someone has put it in.
• Open shifts are visible as open. A gap should look like a gap, not like a blank space someone hopes was already handled.
• You can look at it two ways. By site, to ask whether each client is covered. By person, to ask whether anyone is being asked to do too much or has been put in two places at once.

TacDesk's rota has those two views, by site and by staff, for exactly that reason. Checking by site tells you whether the client is covered. Checking by staff tells you whether someone has been put in two places or is carrying more than they should. You are asking different questions, and one view can't answer both.

Where I would start

If you suspect your rota lives in too many places, count them. Spreadsheet, messaging group, notes on a phone, a whiteboard in the office. If it's more than one, that is your starting point, not your people.

I would also look back at the last three or four times it went wrong and ask where the change was made, rather than who missed it. My bet is that the answer will often be that the change was made somewhere the other person wasn't looking.

If you want the wider picture on scheduling, I've written up what to look for in security guard scheduling software.

If you'd like to see how TacDesk handles rotas for a company your size, book a demo and we'll walk through it together.