Shift & Tide
Home/Hotel operations/Timing the service in a small resort restaurant

Hotel operations

Timing the service in a small resort restaurant

A hotel restaurant with a captive, arriving-together clientele has a demand curve unlike a high-street site, and staffing it like one produces a bad evening. The concept of chronemics offers another way to understand how guests and staff interpret waiting, pacing and service timing.

8 min read628 wordsUpdated July 2026

An independent restaurant fills gradually. Bookings spread across the evening, walk-ins arrive when they arrive, and service load rises and falls in a manageable wave. For broader operational context, see the overview of restaurant management.

A resort restaurant with mostly resident guests does not behave that way. Guests are on holiday, on a similar daily rhythm, and frequently on half board. They come down at roughly the same time. The result is a compressed peak that can put sixty percent of covers into a forty-minute window.

Half board changes the arithmetic entirely

Where a large share of guests are on an inclusive meal plan, dinner is not a variable demand to be forecast. It is close to a known quantity — you can count the covers from the rooming list before the day starts.

That is an operational gift and it is regularly wasted. Knowing at nine in the morning that there will be fifty-eight covers means the kitchen can prepare accordingly, the rota can be set to the actual number rather than a range, and waste can be planned down. Properties that treat half-board dinner as an unknown are discarding information they already hold.

The covers are already on the rooming list

Resident guests on an inclusive plan are a countable demand, known a day ahead. Forecasting them is unnecessary; the task is reading the number and acting on it.

Flatten the arrival curve where you can

The compressed peak is the core problem, and the levers on it are mostly soft.

  • Two seatings, allocated at check-in. Effective, and disliked by guests who feel scheduled on their holiday. Works better when framed as a choice than as an assignment.
  • A bar or terrace offer that is genuinely appealing before dinner. Guests who drift in from a good aperitif spread the arrival curve without noticing they are being managed.
  • Staggered activity end times. If the afternoon programme finishes at once, dinner starts at once. Ending activities twenty minutes apart moves the curve at no cost.
  • A visible kitchen pace signal — a specials board that goes up progressively, an early-evening dish available before a certain time.

The kitchen and the floor peak at different moments

Floor staff peak at seating and at the point of ordering. The kitchen peaks fifteen to twenty minutes later, when those orders land, and again on desserts.

Rotas that start both brigades at the same moment and finish them at the same moment mismatch both ends. The kitchen typically needs an earlier start for preparation and often finishes later; the floor needs full strength slightly later and stays through service. Offsetting the two by twenty to thirty minutes usually costs nothing and removes a lot of standing about.

Breakfast is the harder service

Breakfast is treated as the easy one and it is frequently the hardest to staff well. It has a narrower peak than dinner, a shorter total window, and it runs at the same hour that housekeeping is starting and the desk is handling departures — three departments competing for the same early-morning bodies.

It is also where cross-department cover is most valuable and least often organised. A single person who can cover both a breakfast floor and a desk departure rush is worth more in a small property than an additional specialist in either.

Track service duration, not just covers

Covers per hour tells you volume. It does not tell you whether the service is working.

The figure worth capturing is table duration: seating to departure, and within it the interval from order to first course. When those numbers stretch on particular nights, the cause is usually identifiable — a menu item that has become a bottleneck, a station understaffed by one, a section layout that makes a server walk twice as far. Without the timings, a slow service is diagnosed as a busy night and nothing changes.

Related

Continue reading