Peaks and Seasons

Retail and hospitality run on peaks, and how a peak is staffed determines the three months either side of it.

Planning backwards from the peak

Work out the peak requirement first, from last year's actuals rather than from the sales target.

Then the recruitment lead time: advertising, hiring, right-to-work checks, induction, training to a usable standard.

In practice that is two to three months for anything beyond the simplest role.

Which means the December rota decision is made in September, and operations that decide in November are recruiting from whoever is left.

Offering hours internally first

Existing part-time staff who want more hours come before new hires.

Operationally: they are trained and they know the site.

And in several jurisdictions it is a legal requirement, with a record needed of what was offered and to whom.

Do this before advertising, not alongside it.

The seasonal cohort

Hire for a stated period with a stated end, so nobody is surprised.

Train them for a narrow set of tasks, because a fortnight is not enough for the full role.

And keep the good ones: a list of people who worked well, contacted directly next year, is worth more than any recruitment campaign.

Say so at the end of the season, which costs nothing and works.

Protecting the core team

The peak is when the permanent staff are most needed and most likely to leave.

Protect their leave — booked before the peak rota is built, not refused because of it.

Rotate the worst shifts rather than giving Christmas Eve to the same people annually.

And state the rule in advance, because a peak-period refusal that was not signalled is what people remember.

The trough

The months after a peak are where hours get cut and the good seasonal people are lost.

Plan the reduction rather than letting it happen through shortened shifts, which is where predictability pay accrues.

Be honest about the hours available in January when hiring in October.

The measure

Peak coverage achieved against planned.

Predictability pay during the peak, by site, which spikes where planning was late.

Permanent staff turnover in the quarter after the peak, which is the number that reveals how the peak was actually handled.

Decide in September

Working backwards from the peak.

Peak requirement from last year's actuals, then recruitment lead time, then training time.

Two to three months for anything beyond the simplest role.

Which puts the December decision in September, and operations deciding in November are recruiting from whoever is left and training during the peak, which does not happen.

Reproduce the workflow

For another way to make this requirement testable, review freelancer time tracking software. Treat it as a starting point, then reproduce the case with real roles, sites and exceptions.