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.
Onboarding runs as a five-day setup process from a signed agreement. The weeks above exist so the team is trained and settled rather than merely present. Team size for the season is agreed with you and adjusted as your volume changes.
A season sits on top of an operating model
Seasonal capacity is added to something. What you add it to decides how quickly it can be trained and how far it can be scaled back afterwards.
A hotel or group
Front office, reservations admin and guest experience carried year-round, with the season added to a team that already knows the property.
Hotel support teamsRentals across channels
Guest messaging, changes and turnover coordination across every listing — the volume that multiplies fastest when occupancy climbs.
Short-term rental supportMessaging you would rather hand over
AI answers first from knowledge you approve and a trained specialist takes over when a conversation needs a person, within your plan's coverage window.
Managed SupportNot sure which shape fits yet? Start with how hospitality support is staffed and covered.
Plan your peak-season capacity
Tell us your season dates, expected volume and the hours you need covered. We come back with a capacity plan — and follow up only if you want us to.
- A team shape sized to your expected volume and channels
- A week-by-week lead time worked back from your season start
- How the capacity scales back down after the peak
Prefer to talk it through? Book a scoping call.