Peak-season capacity
Peak season is not more bookings
It is more of everything that follows one — arriving in the same working day, handled by the same people.
A full house is the goal. It is also the workload.
What one additional booking actually generates
Occupancy is the number everyone watches. The workload that arrives with it is the number that breaks the team.
- Before it is confirmed
- An enquiry thread, availability and pricing questions, and often a comparison against two other properties.
- After it is confirmed
- Confirmation, pre-arrival messaging, arrival timing, access details and special requests.
- While the guest is in-house
- Questions, requests, faults, and the occasional problem that will not wait until morning.
- Around the stay
- A turnover to coordinate, a vendor to chase, and a record to update.
- After departure
- Follow-up, a review to request and answer, and any issue still open.
The work multiplies. The hours do not.
The failure is response time before it is service quality
Nothing collapses at once. It degrades in a predictable order — and each stage has a question you can answer from your own records today.
| What slips | What it costs | Ask yourself |
|---|---|---|
| Reply times | Guests chase, then book elsewhere while waiting | What was our average first-response time at last peak, against a normal month? |
| After-hours cover | Problems compound overnight and arrive worse in the morning | Who answers a guest at 11pm on the busiest night of the year? |
| Changes and cancellations | Queued requests become manual errors and double-handling | How long does a date change take to process when volume doubles? |
| Reviews | A permanent public record of the week you were stretched | How many reviews from last peak never received a reply? |
| Administration | January is spent catching up instead of selling | What did we postpone last peak, and when did we actually finish it? |
| The team itself | Resignations land immediately after the season ends | Who left within sixty days of last peak? |
Capacity added during peak arrives too late to be trained
A team member who starts mid-season is learning your properties on your busiest week. The same person, added six weeks earlier, arrives already trained.
Week −6
Scope
Expected volume, coverage window, channels and escalation rules agreed.
Week −5
Recruit
Team members selected against your role specification.
Week −4
Train
Your properties, tools, tone and process — before the volume arrives.
Week −3
Live
Production work under supervision, with time to settle before the peak.
Standing up a team takes 5–7 business days from a signed agreement. The weeks above exist so the team is trained and settled rather than merely present. Seats are reduced when the season ends, per the notice period in your service agreement.
Request the peak-season capacity guide
Three pages on what a booking really generates, where teams overload, and how to work backwards from your own peak. We will send it over and follow up only if you want us to.
- What one additional booking generates across the stay
- The order things degrade in, with questions you can answer today
- A backwards plan from your peak, and how to scale down after it
Prefer to talk it through? Book a scoping call.