Rotas are forecasts wearing a uniform

Nobody calls the rota a forecast, but that is exactly what it is: a prediction of demand, expressed in people. Get it high and you pay wages to watch an empty floor. Get it low and you pay differently — queues, walkouts, a rushed team making rushed mistakes, and your best staff quietly deciding the chaos is not worth it.

The two curves that should match and don't

Your till knows the shape of demand by hour and day with total precision. Your rota has a shape too. Lay one over the other and almost every business finds the same mismatches: the flat rota over a peaked day, the Saturday cover that starts an hour after Saturday does, the quiet Tuesday afternoon staffed like a rush because it always has been. We built the practical method in How many staff does Saturday actually need? — the one-line summary is: staff the curve, not the opening hours.

The number that makes it a discipline

Pick one metric and track it weekly: revenue per labour hour (or covers per labour hour in a kitchen). Not to maximise it — pushing it to the ceiling just means understaffing with extra steps — but to *watch* it. A drifting number is asking a question: demand moved and the rota didn't, or hours crept, or the mix of hours got expensive. Weekly, it is a conversation. Annually, it is an autopsy.

Fair warning about the ceiling

Staffing analytics has a boundary the spreadsheet cannot see: rotas are made of people. The mathematically optimal rota that shreds someone's childcare or hands every dead shift to the same person optimises itself straight into resignations, and the cost of replacing a good person dwarfs a quarter of rota efficiency. The data says where the demand is; judgement says what to do about the humans. Keep both in the room.

Kauzio reads your sales curve against your rota where rota data exists, and flags the specific mismatched hours — the analytics half of the job, delivered. The judgement half stays yours, which is exactly where it belongs.