When Only One Person Can Run Your Rota

Most security companies I know have one person who really understands the rota. Sometimes it's the owner. Sometimes it's an operations manager who has been there for years. Either way, there is one person who knows which sites need two people on a Friday, who can't be put with whom, and who will actually pick up the phone at 05:30.

That person is usually very good. The problem is the business has quietly made itself dependent on them.

You only find out when they're off

A rota that lives with one person works perfectly until that person is on holiday, ill, or leaves. Then someone else opens the spreadsheet and finds it doesn't explain itself. The colour coding made sense to one person. The notes in the margin were reminders for one person. The three people who "never work Sundays" were never written down anywhere.

Nobody did anything wrong. The rota was built to be used by the person who built it, and that is the whole point. It was never built to be handed on.

What the cost looks like

It rarely shows up as one big failure. It shows up as small ones, all in the same week:

• A site is left uncovered because the cover arrangement was a favour agreed by text, and the stand-in didn't know about it.
• Someone is rung four times about the same shift because nobody knew they had already said no.
• A client's standing instruction (this person only, this entrance, no changes without a call) gets missed because it was never on the rota.
• The person back from leave spends their first two days putting things right, and the rota is wrong again by Friday.

None of this is a staffing problem. It is knowledge that sits in one place, and that place is a person.

It's also hard on the person

I think owners underestimate this part. The person who holds the rota together rarely gets a clean day off. Their phone is the control room at weekends. They check the spreadsheet on holiday "just in case". When they finally do take a week, they come back to a mess and a feeling that it wasn't worth going.

If you value that person, and you should, the kindest thing you can do is make sure the rota doesn't depend on them being reachable. You keep good people by letting them switch off.

A fair test

Here is the test I'd use. Pick a week and imagine your rota person is unavailable from Monday morning. Then ask:

• Could someone else produce next week's rota without ringing them?
• Would they know which standing requests and exceptions apply to which site?
• Could they see, in one place, who is already booked and who has asked for time off?
• Could your staff see their own shifts without asking anyone?

If you're answering "no" to most of those, the business is carrying a risk it hasn't priced.

Getting it out of one head

You don't need to do all of this at once, and you don't need a particular tool to start. But a few habits help whatever you use:

Write the exceptions down where the rota is. The unwritten rules (who doesn't work with whom, which client has a standing instruction) belong next to the shifts they affect, not in someone's memory.

One rota, with changes made in one place. If the live version lives in a chat or a notebook, the next person has no way of knowing what's current.

Let a second person do it for real. Not a rehearsal. Have another person build and publish a week, with the first person on hand to answer questions. The gaps in what's written down will show up quickly.

Let staff see their own shifts. If every question about who is working when has to go through one person, that person becomes the bottleneck for the whole company. Staff who can look it up themselves ask less, and miss less.

TacDesk's rota is built around that last point: your staff see their shifts in the app, and there are two views of the same rota, by site and by staff, so a second person can pick it up and see what's covered and who's stretched. That's useful, but the real fix is the habit of getting the knowledge out of one head and onto the page, whichever tool you use.

Where I would start

Ask your rota person, kindly, to list the ten things that only they know. Don't turn it into a project. Just get the list. I expect it will be uncomfortable reading. Most of what's on it will be small and fixable once it's written down, and the rest are the things you'd most regret learning about on the day they're not there.

If you want the wider picture on choosing a system, I've written about 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.