USA
AU
UK
ES
FR
BR
TH
INSeasonal Shift Scheduling: Planning for Peaks & Quiet Months
Seasonal scheduling plans rosters around predictable swings in demand — the holiday quarter, the summer season, harvest, tax time — scaling hours and headcount up for the peak and back down after, rather than staffing flat all year.
Why it matters
Seasonal operations live a double life: a core team carries the quiet months, then the peak multiplies demand — sometimes three- or five-fold — for a stretch everyone can see coming. The scheduling craft is in using that predictability instead of being ambushed by it annually.
The standard architecture has three layers. The core team works stable patterns year-round and anchors quality. A flex layer — part-timers and annualised-hours staff whose contracts average over the year — stretches into the peak first. Seasonal hires top up the peak itself, onboarded in waves timed to the ramp. Rostering tightens in step: quiet months might publish monthly; peak weeks need precise daily templates, surge open-shift pools and fast swap mechanics.
Two failure modes recur everywhere: burning the core team out by making peak overtime the plan rather than the buffer, and discovering in week one of the peak that seasonal hires were scheduled like veterans. Both are roster-design problems, not effort problems.
A worked example
A coastal restaurant runs winter on a core of 12 with simple 5-on-2-off rosters. From May it adds annualised-hours staff to evening peaks; by July, 25 seasonal hires arrive in three onboarding waves with buddy-paired shifts for their first week. Peak rosters publish fortnightly with open shifts for the spikes; by October the structure folds back to core. Same playbook, every year — and every year smoother.
✓ Do
- Build the peak roster template in the quiet season, from last year's actuals
- Stagger seasonal onboarding waves so trainers aren't swamped
- Use annualised-hours or averaging agreements where law allows — they absorb seasonality legally
- Pair every seasonal hire's early shifts with a named core teammate
- Schedule the core team's recovery (leave, lighter weeks) immediately after peak
✗ Don't
- Treat core-team overtime as the peak plan — it's the contingency, not the plan
- Hire the whole seasonal cohort for day one of the peak
- Roster seasonal staff onto unsupervised closing or solo shifts in week one
- Forget local rules on fixed-term contracts and minimum-hour guarantees
- Lose the season's data — next year's template is this year's actuals
Variations & alternatives
Build this schedule in Tommy
Set the rotation once and Tommy fills the weeks ahead — shift swaps, leave and coverage gaps handled in one place, with your team always seeing the latest version.
