A seasonal property does not have a rota: it has four, and most of the trouble comes from treating them as one rota that stretches and shrinks.
The four regimes are opening, ramp, peak and closing. They have different constraints, not just different numbers.
Four regimes, not one elastic plan
Opening. Few rooms occupied and a lot of work that has nothing to do with guests: setting up, checking, training new starters. It is the only point in the year when time to train genuinely exists, and almost everyone wastes it because the building looks empty.
The ramp. Occupancy climbing while half the team is on the second shift of their life. It is the most fragile regime and the one most often mis-sized, because people look at occupancy rather than at available competence.
Peak. Here the constraint stops being how many people you have and becomes hours: contracted hours, rest periods and weekly limits all bind at once. It is the point where a hand-built plan stops holding.
Closing. Occupancy falling and staff leaving in waves, often earlier than promised. The final weeks are when cover actually breaks, because nobody plans them with the care they gave the first ones.
What changes and what does not
The distinction that makes the transition manageable: the coverage changes, the rules do not.
Coverage per time slot is the seasonal part: how many on reception, how many in housekeeping, how many in the restaurant in each band. Rewriting it four times a year is normal and expected.
The rules are not. Rest periods, contracted hours, night work limits, the skills each shift requires: those are identical in July and in November. Anyone suspending them in high season "because it is high season" is not gaining cover, they are accruing a debt that gets paid in September in overtime and resignations.
The ramp mistake
The moment things go wrong most is the climb, and the mistake is nearly always the same: the headcount goes up and nobody looks at who those people are.
Thirty people of whom twelve are in their first season are not thirty people. They are twenty-four, plus twelve who need somebody beside them. If the plan does not say so explicitly, the shadowing gets absorbed by whoever is there, on top of their own work, and that is the fastest way to lose your experienced staff halfway through the season.
It is worth keeping a map of who covers what, updated weekly during the ramp. The general reasoning is in ramp-up after a new opening.
The hours count runs across the season
The last point, and the most underrated. In high season the hours balance grows fast and with the same sign for everybody. Ignore it until the season ends and you are left with a pile of hours to give back at the exact moment the property closes and there is no way to give them as time off.
The practical rule is simple: look at the balance weekly even at peak, and schedule the payback before the season ends. How to keep that count healthy is in hour banks.
In Sked Solve the coverage per slot changes season by season while the rules stay put, so moving from low to high does not mean rebuilding the plan. See how it works at Sked Solve.
