The Rota Everyone Screenshots

The rota goes up. Everyone photographs it. Within an hour there are fourteen copies in fourteen camera rolls, and every one of them is now frozen.

Then something changes — and there is no mechanism by which fourteen photographs can be told about it.

The cost is not the no-show

A missed shift is the visible failure and the rarest one. The routine costs are quieter:

Someone arrives for a shift that moved. They are annoyed, correctly, and they were not wrong — their copy said so.

Someone does not arrive for a shift that was added. ⚠️ This is the expensive one, and it is not their fault either.

Every change costs a round of messages. The manager tells the affected person, who tells someone else, and whether that reached everyone is unknowable.

Nobody trusts the rota. ⚠️ The end state. People check with a person instead of checking the schedule, which means the schedule has stopped doing its job entirely and every query now costs a manager's attention.

Why people screenshot

Not carelessness — a rational response to two real problems:

It is somewhere inconvenient. A board in the office, a document that needs a login, a group chat that has scrolled.

They do not trust it to be there later. ⚠️ If the rota has ever been taken down, replaced, or buried in a chat, photographing it is the correct defensive move.

The behaviour is a symptom. Telling people to stop will not work, because it solves nothing for them.

The property that matters

Not a nicer layout. One thing: the version they look at has to be the current one, at the moment they look at it.

That is the entire requirement, and it is exactly what a screenshot cannot provide. Everything else — colours, printing, layout — is secondary to this single property.

⚠️ A beautiful rota that can be photographed is functionally the same as a scruffy one that can be photographed.

What changes when the rota is live

Changes propagate without messages. The change is the notification.

"I did not know" stops being available. ⚠️ Not as a disciplinary matter — as a factual one. If they looked, they saw the current version, and both sides know it.

Swaps become records. A swap agreed between two people is currently invisible until it fails. On a live rota it either happened or it did not.

The manager stops being the lookup service. The queries that consume a manager's evening are almost all "when am I on" — a question the person could answer themselves if they trusted the answer.

The transition

Do not run both. A live rota alongside a printed one is worse than either, because now there are two sources and staff will use whichever they saw first.

Pick a date, remove the old one, and answer "when am I on" by pointing at the new one every single time for two weeks. That last part is the whole transition — the moment someone gets a verbal answer instead, the old system is back.

Three to hold

Schedule queries reaching a manager per week. Should fall sharply. The number that shows whether people trust it.

Shifts changed after publication. ⚠️ High numbers are not a rota problem — they are a planning problem the rota was hiding.

Missed shifts attributable to a stale version. Should reach zero, and until it does the transition is not finished.

Where the record has to sit

A rota needs to be readable on a phone by someone who is not at work, and editable by a manager who is. Anything that fails either half gets photographed, and you are back where you started.

tasteck puts cast and driver shifts on the same record staff use to submit availability, so the published rota and the one people check are the same object.

People screenshot the rota because they cannot rely on finding it later. Fix that, and the screenshots stop on their own.