A tray of salmon and a vegan hen party
At 09:30 the spa receptionist prints the day's spa bookings and walks them to the kitchen. The head chef counts the packages with lunch: thirty-four. By 12:30 there are forty-one guests in robes waiting in the spa restaurant, because group bookings added guests yesterday and a couple of voucher bookings were made by phone after the list was printed. Six of a hen party are vegan, which nobody mentioned until they sat down. Two guests have allergies they told the person who took the booking in March.
The kitchen copes, because kitchens do. But the fish runs out, the vegan dishes are improvised and service runs half an hour late, which pushes back the afternoon treatments of everyone still eating.
Lunch is booked as a line on a package
The spa booking system knows that a package includes lunch. It does not know when the guest will be free to eat, and it rarely has a proper place for dietary requirements. The restaurant's own table system, if there is one, never hears about spa guests at all.
- Lunch numbers are taken from a morning printout that is out of date by midday.
- Sitting times are not set, so guests eat whenever their treatments allow and the kitchen gets waves it cannot predict.
- Dietary requirements are typed into booking notes in free text, or not recorded.
- Group organisers pass on dietary needs late, by email, to the events coordinator rather than the kitchen.
- Upgrades, such as afternoon tea instead of lunch, are made at the desk and reach the kitchen by word of mouth.
Food waste, short dishes and late treatments
The kitchen over-prepares on quiet days and runs short on busy ones. Guests with dietary requirements get an improvised plate and feel like an afterthought, even when they told you months ago. A slow lunch service delays afternoon treatments, and therapists wait for guests who are still at the table. Chefs lose trust in the spa's numbers and start preparing on instinct.
How we build a live spa covers list
- Each package with food has a sitting rule: for example, lunch between treatments, at a time that leaves enough gap before and after. The booking engine picks a sitting when the itinerary is built.
- Dietary requirements are captured as structured choices at booking and in the pre-arrival message, with a free text box for anything else, rather than buried in notes.
- Group guests enter their own dietary needs through their personal booking link.
- A covers screen in the kitchen, or a list that refreshes on a tablet, shows guests by sitting with their requirements, updating as bookings change.
- Late changes after a cut-off time you set, such as a guest added at 11:00, are highlighted so the chef sees them.
- Where the restaurant has its own table system that accepts bookings, spa lunches are placed into it directly.
| Information | Before | With the covers list |
|---|---|---|
| Number of covers | Morning printout | Live, updated with bookings |
| Sitting time | Whenever guests arrive | Set from treatment times |
| Dietary needs | Free text notes, often missing | Structured, collected before arrival |
| Late changes | Word of mouth | Highlighted on the kitchen screen |
We record what guests tell you. How your kitchen handles allergens and what you tell guests about them follows your own food safety procedures.
Service that matches the spa diary
The chef starts prep with numbers that match reality and a clear list of dietary requirements by sitting. Guests arrive for lunch in manageable groups rather than all at once. The ones who told you about a requirement find it already known. Afternoon treatments start on time because lunch did not overrun, and the kitchen can order and prep to the week's spa bookings rather than to a hunch.
Recognise your spa lunches?
- The kitchen gets spa numbers on a morning printout.
- Dietary requirements are found out at the table.
- Lunch service arrives in unpredictable waves.
- Group dietary needs arrive by email to the wrong person.
- Afternoon treatments are delayed by lunch running late.