The Staffing Curve: 7 Mistakes Between Your Slow Season and Your Rush (2026 Numbers) | HappyChef
Staff

The Staffing Curve: 7 Mistakes Between Your Slow Season and Your Rush

You know your January headcount and your August headcount. What happens in the eight weeks between them, you improvise every single year.

In this article
  1. Why the curve stays invisible
  2. The 7 mistakes in the curve
  3. Run your own curve
  4. What to do with this this week, this quarter, and next year
  5. The season doesn't happen to you — you build it

Your business doesn't have a slow season and a rush. It has a curve between the two — and you plan that curve from memory, every single year, instead of from a spreadsheet.

On the coast, in a ski town, around a festival weekend, or just on a city-centre terrace in May: if your business lives off a season, you know two numbers by heart. How many people you need on a quiet Tuesday in February. How many people you need on a Saturday in August. You know those two numbers because you live through them every year.

The problem isn't those two numbers. It's the weeks in between. Somewhere between February and August you have to go from four people to eleven. Not in one jump — in stages, over weeks you never actually mapped out in advance. And those same weeks have to be counted back down again in September, without letting go of someone in mid-August you still needed for the last busy week.

Most owners handle that with a shrug and a group chat message: "we'll see how busy it gets." That works until it doesn't — and on a coast, on a mountain, or around a festival weekend, it doesn't work somewhere every single year. Either you're halfway through July with a kitchen that can't keep up. Or you're already paying in May for a headcount you won't actually need until July.

This article gives that curve a shape. Seven mistakes almost every seasonal business makes, each with the number behind it — and, at the end, a calculator that runs your own curve: what staying flat at peak headcount all year costs you, what staying flat at your quiet-season headcount leaves uncovered during the rush, and what the curve in between actually saves.

Why the curve stays invisible

A P&L shows you revenue by month, not by week. A staff list shows you who's employed, not when their shift started ramping up or down. No standard report in hospitality shows you the shape of your season — headcount, week by week, from the quietest to the busiest. Without that shape, you plan on two points instead of a line, and the line is exactly where it goes wrong.

That's not carelessness. It's a blind spot the whole trade shares: Eurostat, the EU's statistics office, does track seasonal swings in tourism employment — by quarter, by country — but that figure never shows up in any report an owner actually sees. You only see your own curve once you draw it yourself.

And drawing it is exactly what most businesses never do. They remember a peak number and a low number, and leave the weeks in between to whoever happened to be around last year.

Free guide Everything about your staff, in one guide From rota to turnover — the full guide to the numbers behind your team. Read the guide

The 7 mistakes in the curve

Each of these mistakes costs money in a different part of the year — the first four during the ramp-up, the last three during the peak itself and the ramp-down after. Together, they're why almost no seasonal business builds the same curve two years running.

1. You measure the peak, not the curve

Ask an owner how many staff they need and you get one number: the peak. Push further and you get a second: the quiet-season number. Ask about the weeks in between and the answer is usually a shrug — "we build up to it, as we go."

That "as we go" is the problem. Two points don't describe a line. Whether you go from four to eleven people over four weeks or eight, whether you spread that build evenly or dump it into one weekend — none of that is captured by the two numbers you remember. And that difference is exactly what decides whether you're ready for the first genuinely busy Saturday, or two weeks behind it.

2. Your hiring lead time is longer than your ramp-up

Posting a job takes an evening. Finding a suitable candidate, scheduling an interview, rostering their first trial shift, and getting them to a point where they can run a shift unsupervised — that takes weeks, not days. A flexi-job or student hire moves faster than a permanent contract, but even then you're usually looking at four to six weeks between the first search and a staff member who actually carries their weight.

Most owners start hiring the moment the rush becomes noticeable. That's exactly the moment it's already too late: the hiring lead time then runs alongside — or behind — the weeks you actually needed to build up in. The result is a team that only reaches full strength once the peak is already half over.

Four numbers that make the curve tangible

Not guesswork — the scale of the seasonal pattern every tourism-facing business in Europe shares.

9.9 million people worked in accommodation and food services across the EU in 2021 — 6.3% of the entire business economy Eurostat, tourism employment
higher employment in the busiest quarter versus the quietest, in Greece and Croatia's tourist-accommodation sector Eurostat, seasonality in accommodation
70–80% annual staff turnover in hospitality for hourly roles — among the highest of any industry US labour-market data (BLS), as an order of magnitude
56 uncovered staff-weeks during the peak if you stay flat at low-season headcount all year — in the worked example below the worked example, see the calculator

The first two figures come from Eurostat, the third from US labour-market statistics as a general order of magnitude — not an exact EU figure, but a real signal that the problem is bigger than any one business. The fourth figure isn't an estimate: it's exactly what the calculator below computes for the starting example.

3. You pay for high-season readiness at low-season demand

The opposite mistake is just as costly, and owners who've just been burned by mistake two often fall straight into it: afraid of being late again, you hire too early and too much. Four weeks before the first genuinely busy Saturday, you're already staffed at near-peak strength — and paying three weeks of wage cost for a terrace that's still half empty.

Both mistakes cost money on the same page: hiring too late costs you revenue you miss during the peak, hiring too early costs you wages for hours nobody needed. The calculator further down puts both side by side, so you don't have to choose between one kind of guesswork and the other.

4. Seventy to eighty percent of your team won't come back

Hospitality as a whole carries one of the highest staff-turnover rates of any industry — US labour-market data (the Bureau of Labor Statistics) commonly puts it at 70–80% annually for hourly roles, and that's before accounting for the extra effect of a season that simply ends. A seasonal role at a beach bar or a ski-town kitchen can turn over almost entirely from one year to the next: whoever leaves in September often lands somewhere else by next spring.

That means the ramp-up curve isn't only a scheduling problem — it's a repeated onboarding problem. You're not just building up numbers each year; you're rebuilding the same knowledge, largely with new people. Knowing that is exactly why mistake two's hiring lead time needs more room for first-timers, and why deliberately keeping a core of people who DO return matters so much — often the real reason decent seasonal-staff housing (see the related articles below) pays for itself: people who have somewhere good to live are far more likely to come back next year.

5. Employment doubles in Greece and Croatia — you're not alone

It's easy to think your own business happens to have an unusually difficult seasonal pattern. Eurostat tracks employment in the tourist-accommodation sector by quarter, and the extremes aren't subtle: in Greece and Croatia, employment in the busiest quarter is nearly double the quietest quarter. Campsites feel the peak hardest, hotels the least — which makes sense, since a campsite often shuts entirely over winter while a hotel stays open year-round.

The sector as a whole — accommodation and food services combined — employed roughly 9.9 million people across the EU in 2021, 6.3% of the entire business economy. Behind that one annual figure sits a curve that varies wildly from country to country, coast to inland. The point isn't that your season is unusually hard — it's that you're not the only one living with it, and that the shape of that curve is plannable everywhere else too, not just something to endure.

6. The rush costs you more than the quiet week saves

Keep your staffing flat at low-season level all year, and you save wage cost on every quiet week. But on the first genuinely busy Saturday you're short-staffed for too many guests — and that costs you not just overtime and an exhausted team, but the guest who waited half an hour for their order and picks somewhere else next year.

Put the three scenarios side by side — flat at peak all year, flat at low-season all year, and the curve in between — and the pattern is clear: flat at peak is punishingly expensive, flat at low-season is cheap but leaves you unstaffed during exactly the weeks that carry your year. The curve sits in between, and the gap between "flat at peak" and "the curve" is precisely what a well-planned ramp-up saves you.

Three scenarios, one year

Wage cost per scenario, over 52 weeks — calculated with the worked example above.

Flat at peak all year
€371,800
The curve
€189,800
Flat at low season all year
€135,200

The curve always lands between the two flat scenarios — that's not a coincidence, it follows directly from the maths. The gap with "flat at peak" is what a planned ramp-up saves you; the gap with "flat at low season" is the real price of actually staffing your peak.

7. You rebuild the curve from scratch every year

The seventh mistake is really the sum of the first six: without a written-down curve — how many people, which week, how many weeks of lead time before it — every season starts with the same questions you already answered last year. Last year's experience lives in the head of whoever was there, and if that person doesn't return (see mistake four), you start again from zero.

A curve you map out once — your own low- and peak-season headcount, your own ramp-up weeks, your own hiring lead time — only needs repeating and adjusting next year. That's the entire difference between a season that happens to you and a season you plan.

Run your own curve

Enter your own headcount — low season, peak season, how many weeks the peak lasts, how many weeks you need to ramp up, and how many weeks of hiring lead time that takes — and the tool puts three scenarios side by side: flat at peak all year, flat at low-season all year, and the curve in between.

The numbers below are a starting example: four people at low season, eleven at peak, eight weeks of full peak, four weeks of ramp-up (and four weeks of ramp-down), six weeks of hiring lead time, and €650 average wage cost per headcount-week. Replace them with your own figures.

The staffing curve calculator

Six fields, three scenarios, one answer: what the curve saves you over staying flat at peak.

Curve saves vs. flat at peak
per year, in wage cost
Uncovered staff-weeks if flat at low season
what you'd miss during the peak if you never ramped up
Start hiring, weeks before peak
ramp-up weeks + lead time

The ramp-up and ramp-down are assumed to take equally long and to run linearly — average headcount during each half of the curve is the midpoint between your low- and peak-season numbers.

This is a headcount-weeks × average wage-cost model, not accounting advice. Use it to compare the shape of your own curve, not as an exact payroll forecast.

The "saves" figure is never negative: by construction, the curve can never cost more than staying flat at peak all year, and never less than staying flat at low season all year. What shifts is how much of that saving you actually capture — and that depends entirely on whether you start hiring on time.

The "uncovered staff-weeks" figure deliberately isn't converted to euros. That would require assuming how much revenue each uncovered week costs you, and that assumption varies too much from business to business to be honest. The figure itself — how many staff-weeks you'd be short during the peak if you never ramped up — is exact, and that's where your own judgement takes over.

What to do with this this week, this quarter, and next year

The curve itself doesn't change much year to year. What changes is whether you write it down once — or reinvent it every spring.

This week

  • Write down your own low- and peak-season headcount, and estimate how many weeks your ramp-up and ramp-down take.
  • Run your own curve through the calculator above and note the "start hiring" number.
  • Put that hiring date straight into your calendar — as a hard deadline, not a vague reminder.

This quarter

  • Build a core of staff who return every season — housing and a fair offer weigh more here than a couple of extra euros an hour.
  • Decide per role who's allowed to sign off a trial shift, so hiring lead time doesn't stall on a calendar with no room in it.

Next season

  • Compare the curve you actually ran against the one you sketched in advance, and adjust your ramp-up and ramp-down weeks based on what you saw happen.
  • Keep the curve as a document, not a memory — so next year it's a repeat, not a new puzzle.

The season doesn't happen to you — you build it

Every seasonal business in Europe shares the same shape: a quiet base, a ramp-up, a peak, a ramp-down. What differs is whether that shape lives on paper, or only in the head of whoever happened to be there last year.

The calculator above gives that shape a concrete answer: how much the curve saves you compared to staying flat at peak, how many staff-weeks you'd miss if you never ramp up, and how many weeks before your peak you need to start hiring to get there.

That answer changes very little from year to year. The only thing that changes is whether you already know it when spring comes around again.

Frequently asked questions

How many weeks in advance should I start hiring for peak season?

Add your ramp-up weeks (how long it takes to go from low- to peak-season headcount) to your hiring lead time (how long it takes to find, hire and train someone to run a shift unsupervised). For a typical business with a four-week ramp-up and six weeks of lead time, that means starting ten weeks before your first genuinely busy week.

Is it cheaper to just stay staffed at peak level all year round?

No — that's almost always the most expensive scenario. You'd be paying full-year wage cost for staffing you only actually need for a handful of weeks. The calculator above puts that scenario next to a planned ramp-up curve, and the difference is usually significant.

What if I just stay flat at low-season staffing and run overtime during the peak?

That looks cheapest on paper, but it shifts the cost into overtime, an exhausted team, and guests experiencing slow service during exactly the weeks that carry your year. The calculator shows how many staff-weeks you'd be short during the peak that way.

How do I keep seasonal staff who actually come back next year?

Hospitality turnover is high to begin with, and a seasonal role makes it worse. A returning core of staff is built mainly through decent housing, fair terms, and reaching out well before the season starts — see the related article on seasonal-staff housing below.

Does the curve differ between a coastal business, a ski-town business and a city business?

The shape of the curve differs, but the principle doesn't. A coastal business usually has one broad summer peak, a ski-town business a sharp winter peak, and a city business often several smaller peaks around holidays and events. In all three cases, the same sum applies: ramp-up weeks plus hiring lead time decide when you need to start.

Do I need to keep the same headcount for every peak week?

Not necessarily — some businesses see peaks and dips within their own peak period (a festival weekend inside a summer season, for example). This model assumes one peak level across the whole peak length as a simple starting point; if your pattern is choppier, run the calculator again per sub-period.

What's the difference between this and ordinary staff scheduling or rostering?

Staff scheduling and rostering (see the related article) cover the day-to-day or week-to-week shift plan at a roughly stable headcount. The staffing curve is about something else: the multi-month ramp-up and ramp-down of your total headcount around a seasonal peak, and the hiring lead time that requires.