Section · 7 guides
How rotas get built, why they break, and what to do when the schedule meets a real week.
A rota is a forecast written in people. It commits a business to a certain shape of week before that week has happened, and every assumption baked into it — occupancy, arrival times, how long a task takes, who is actually available — will be tested within days. Any employee attendance tracking software should support the rota rather than become a substitute for scheduling judgment.
This section covers the mechanics: pattern choice, the arithmetic of coverage, the handover points where work leaks between shifts, and the protocols that keep a last-minute gap from turning into a bad guest experience. The general overview of workplace scheduling provides additional terminology for rota design.
Fixed, rotating, split and on-call patterns each solve a different problem. Picking one before you know which problem you have is how rotas go wrong. The OSHA worker-fatigue guidance explains why schedule design is also a health and safety issue.
Read the guideThe rota should be a translation of expected demand into people and hours. Most are a translation of last week's rota.
Read the guideSplits move labour cost off the payroll line and onto the employee's day. Whether that trade works depends almost entirely on geography.
Read the guideMost operational failures in a hotel happen at a shift boundary. The fix is a structured handover, not a more conscientious team.
Read the guideEvery rota contains hours people would rather not work. How those hours are distributed does more for retention than most benefits.
Read the guideSomeone will call in sick two hours before a shift. Deciding what happens next in advance turns a crisis into a procedure.
Read the guideBelow a certain headcount, scheduling stops being an optimisation problem and becomes a constraint-satisfaction problem with almost no slack.
Read the guide