Automating the rota: what works, and what breaks

Rotas get automated more often than almost anything else, and abandoned more often too. It is worth being clear about why, because the failure is predictable.

Most rota software assumes the hard part is working out who goes where. In most businesses the hard part is what happens after that: somebody is ill, a site changes its access times, a customer moves a visit, and the version of the rota in six people's heads stops matching the one on the wall.

What actually goes wrong

The rota is right and nobody knows. It was updated on Tuesday and re-sent to the group, and two people were driving and never scrolled back.

The change arrives through the wrong door. Somebody texts the supervisor. Somebody else tells the customer, who tells nobody. The system was never the source of truth; the supervisor's phone was.

Nobody knows what changed. A new version of the whole rota is sent out, and every person has to find their own line in it and work out whether anything moved.

Constraints live in someone's head. This cleaner cannot do that site. That driver is not signed off for that vehicle. This customer will not accept a substitution without a call. None of it is written down anywhere a system could read.

Where an agent genuinely helps

Telling each person only what changed for them. Not the new rota — the difference. "Tuesday's Bedminster visit has moved to 7am." One line, to one person, on the channel they actually read.

Chasing the gap. A shift with nobody assigned, seventy-two hours out, is a problem with a deadline. An agent can notice, ask the people who could cover it, and tell a human when nobody says yes.

Holding the constraints. Once you have told an agent who cannot go where and why, it stops being tribal knowledge that leaves when the supervisor does.

Confirming the day before. A short message to each person with their next day, and a reply that gets logged. Cheap to run and it catches the misunderstanding while there is still time.

Noticing the pattern. The site that always overruns, the day that always needs a second person, the customer who moves every third visit. Nobody has time to spot these and they are worth real money.

What it should not do

Reassign people without a human deciding. Rota changes affect people's lives — childcare, second jobs, travel. An agent proposing a solution is useful. An agent imposing one is a grievance.

Talk to customers about scheduling unprompted. Moving a visit is a commercial conversation.

Optimise routes it does not understand. The shortest route on paper is often wrong for reasons — parking, access windows, the customer who is only in on Thursday mornings.

The honest prerequisite

An agent cannot help until the rota exists somewhere other than a spreadsheet that gets re-sent by message. It does not need to be a fancy system — a shared sheet is fine — but there has to be one version that everyone agrees is the real one.

If that does not exist yet, that is the first job, and it is a smaller one than people expect. Getting to a single source of truth is usually a fortnight, not a project.

Who this suits

Anywhere people go to places on a schedule. Cleaning companies and facilities management feel it hardest, because a missed visit is immediately visible to a customer. Logistics and haulage have the same problem with a fleet attached.

If your week involves rebuilding a rota after somebody calls in sick, tell us how it works now and we will be straight about whether this is worth automating or whether you need a different first job.