Scheduling when the whole team is nine people
Below a certain headcount, scheduling stops being an optimisation problem and becomes a constraint-satisfaction problem with almost no slack. Small teams need explicit ownership because there is little spare capacity; this workplace guide examines accountability and responsibility at work.
Workforce management writing is mostly produced for organisations with hundreds of employees, where scheduling is a statistical exercise. Demand is smooth because it is aggregated, absence averages out, and an algorithm can find a good arrangement among millions of valid ones. The general principles of team management become especially visible in a team with little spare capacity.
At nine people none of that holds. Demand is lumpy. One absence removes eleven percent of the workforce. And the number of valid schedules — arrangements that satisfy rest intervals, contracted hours, skills coverage and leave — is often in the single digits. You are not optimising. You are looking for anything that works.
Skills coverage is the binding constraint
In a large team, everyone in a role is interchangeable enough that headcount is the number that matters. In a nine-person property, the schedule is really governed by a much smaller number: how many people can do the specific thing that must be done at a specific hour.
If two people hold a food hygiene certificate and one is on leave, the kitchen schedule has one degree of freedom regardless of how many other staff are available. If one person can operate the payment reconciliation, that person defines when reconciliation happens.
Write down the skills matrix — people down the side, certifications and competencies across the top — before touching the rota. The sparse columns are the ones that will break your week, and they are usually not the ones you would have guessed.
Any capability held by exactly one person is a scheduling constraint and a business risk wearing the same hat. In a nine-person team there are usually more of these than anyone has counted.
Contracted hours are a puzzle piece, not a target
With a large workforce, hours balance out across the group. With nine people on a mix of full-time, part-time and variable contracts, the hours have to be made to fit almost individually, and a single change cascades.
Move one person off Wednesday and you have not just created a Wednesday gap; you have created a surplus for that person elsewhere in the week that has to be placed somewhere it is useful. This is why small-property rotas take longer to build than the headcount suggests, and why copying last week forward is so tempting.
Build the week in a fixed order
The way to make a tightly constrained schedule tractable is to place the least flexible things first. Reversing the order produces a schedule that looks nearly complete and then cannot be finished.
- Approved leave and known absence. These are immovable.
- Single-holder skills. Whoever is the only person who can do a required thing goes on the board next.
- Fixed operational points — opening, breakfast, the arrival window, close.
- Volume-driven hours from the forecast.
- Contracted-hours balancing for anyone still short.
- Discretionary and deferrable work, into whatever space remains.
The last category is where the slack lives, and keeping it last makes the amount of slack visible. If step six has nothing left in it, the week has no give at all and you should know that on Monday rather than discovering it on Thursday.
Two roles per person, not five
Small teams inevitably multi-skill, and the instinct is to make everybody capable of everything. In practice, spreading each person across five roles produces a team that is passable at all of them and reliable at none, and it makes the schedule harder to read rather than easier.
A better target is a primary role and one credible secondary. It gives every position two qualified people, which is the threshold where a single absence stops being a crisis, and it keeps the depth of competence that guests actually notice.
Accept that the rota will be edited
A nine-person rota will change during the week. That is a property of the situation, not a failure of planning, and treating each change as an exception generates a lot of unnecessary friction.
What helps is a defined change process: who may authorise a swap, how it gets recorded, and by when the affected people have to know. Swaps arranged privately between staff and never entered anywhere are the main source of payroll disputes in small properties, and the fix is a single place where the current version of the week lives and is known to be authoritative.