Hiring for a Seasonal Peak: Getting the Start Date Right

If your busiest weeks are the same every year, the hardest part of seasonal hiring is not finding people. It is the start date. Hire for a seasonal peak by counting backwards from the peak, through ramp up, through training, through notice periods, and you will usually find you needed to start weeks before it felt urgent.

Start too late and you are paying salaries for people who become genuinely useful in the week after the rush ends.

Count backwards, not forwards

Forwards planning asks when you can start hiring. Backwards planning asks when someone must be productive, then works out what that requires.

Work through four spans in this order:

1. The peak itself. The dates when demand is highest. Be honest about the shape: most seasons have a build up, a spike and a tail, and staffing needs differ across all three.

2. Ramp up. How long until a new person works at normal speed without supervision. Ask someone who joined last year rather than guessing.

3. Training and induction. Formal training, shadowing, systems access, safety briefings, whatever applies to your work.

4. Notice periods and hiring time. From posting a role to a signed offer, plus whatever notice a candidate owes. Notice terms vary by contract and by country, so check the range you are actually likely to face rather than assuming a standard.

Add those four together and count backwards from the first day of the build up. That is your posting date. For most seasonal roles it lands earlier than instinct suggests, and the gap between instinct and arithmetic is where every year's staffing panic comes from.

Your posting date is the start of the peak minus ramp up, minus training, minus hiring and notice time. Work out those four numbers once, write them down, and reuse them every year.

The peak is not a single day

This matters most in event work, where a season is a sequence rather than a moment. Planning delivery around Onam, Vishu and Thrissur Pooram starts from the same idea.

Kerala's festival calendar is a good example of the shape. Onam is a season, not a date. Thrissur Pooram builds for weeks around one enormous day. Temple festivals, Theyyam and Kathakali performances, backwater boat races and city carnivals all cluster in periods that organisers know well and outsiders do not. EventifyPlus exists because that information is scattered: people struggle to find what is on, and organisers who depend on word of mouth struggle to be found.

For staffing, the practical point is that the build up often needs different people from the peak. Setup, logistics and coordination load arrives early. Front of house and crowd handling load arrives on the day. If you hire one group for both, one of the two periods gets covered badly.

Split the plan:

• Build up staff. Fewer people, earlier start, more experience, longer contracts.
• Peak staff. More people, later start, shorter contracts, training that is short enough to actually deliver. Working out how many people a festival season needs is a separate sum worth doing first.
• Tail staff. The smallest group, and the one everyone forgets. Teardown, reconciliation, follow up with venues and vendors.

Ramp up is the number people get wrong

Training length is easy to measure because it is scheduled. Ramp up is not scheduled, so it gets estimated at zero.

Two ways to get a better number:

• Ask the last three people who joined into that role how long before they stopped checking with someone before acting. Their answers will cluster.
• Look at when new starters stopped generating rework or escalations. That point is closer to real productivity than the end of training.

If ramp up is long and your season is short, the hire may not be worth it at all. Sometimes the better answer is fewer, earlier hires with more experience, or bringing back people who worked last season and already know the job. Returning staff are the cheapest ramp up available, and the same holds for volunteer crews who worked last year.

What happens after the peak

Decide this before you hire, not during the tail.

• Are these fixed term roles, and does everyone know the end date in writing?
• Is there a path for the best of them into permanent work, and who decides?
• Who handles the teardown weeks, and are they on contracts that extend that far?
• What do you want recorded about each person, so next year's hiring starts from a list rather than from scratch?

That last one compounds. A team that keeps notes on who was good, who would return and what each person was suited to spends far less effort the following year. Fixed term contracts, hours and end of engagement obligations differ by jurisdiction, so confirm the rules that apply to you before you commit to a shape.

One calendar, made once

Draw the season on a single page: peak dates, build up, tail, then the four spans counted backwards from each. Keep it and adjust it every year with what actually happened.

The calendar takes an afternoon to build and it removes the same argument every season, which is the one about whether it is too early to start hiring. It usually is not.