Guest with an allergy: how the order note survives from the order to the folio

A guest sits down in the hotel restaurant and tells the server they are allergic to peanuts. The server nods, writes “no peanuts” in the margin of the ticket and drops it in the kitchen. Two hours later, the same guest orders dessert to the room by phone, and the person taking the order knows nothing about the allergy. The note existed, but it lived twenty minutes on a piece of paper. Everything after that depended on luck.

Where the note gets lost today

The allergy note travels a five-step chain between the guest’s mouth and the plate on the table, and at every step it can disappear. First, the server hears it and decides whether to write it down. Second, they write it by hand on paper or in a free text field on the terminal. Third, the kitchen reads it, or does not, among ten other tickets. Fourth, the dish goes out and nobody confirms the note was honored. Fifth, the next order from the same guest, on another shift or at another revenue center, is born without the note.

The problem is not attitude. Every server understands an allergy is serious. The problem is that the process treats the allergy as an optional comment, written in small letters, that lives in a single document and dies with it. In a hotel, where the same guest eats three times a day for several days across several revenue centers, that design fails by construction.

• The server writes the allergy on the paper ticket and the paper gets wet, lost or misread.
• The kitchen sees “no peanuts” but does not see that the house sauce contains them ground.
• The room service order is taken by someone else who never heard the guest.
• The pool bar serves a dish from the daily menu without knowing that guest already warned the restaurant.
• The guest comes back next month and everything starts from zero.

The note is not a free comment: it is a required field

The first change is one of design, not discipline. The allergy stops being free text in the “remarks” field and becomes a field of its own on the order, with a short list of common allergens and an “other” option that requires a description. Marking the field is not optional once the guest has warned: the system asks the server, on every order, whether there is any allergy at the table, and the server answers yes or no before being able to send the order.

That mandatory question has an effect that looks small and is not: it turns the guest’s warning into structured data the system can move, display and store. Free text can only be read; a field can be highlighted in the kitchen, inherited by the next order and searched in a record months later.

The note is tied to the dish and to the diner, not only to the table. At a table of four, the allergy belongs to one person; if the note lives at table level, the kitchen does not know which of the four plates has to come out different. The tables page (Tables and floor) explains how each order identifies the diner within the table, which is what makes that precision possible.

In the kitchen: a visible alert, not small print

When the order reaches the kitchen display, the allergy cannot be one more line between “medium” and “no onion”. It has to look different: its own color, a fixed label at the top of the ticket and, where possible, a block that forces the cook to confirm they read the alert before marking the dish ready. The kitchen at two in the afternoon reads out of the corner of its eye; the alert must be designed for that glance.

In addition, the kitchen ticket for a dish with an allergy is printed or displayed apart from the rest of the table, with its own number, so the cook prepares it separately, on a clean surface and with different utensils, and so the server knows exactly which plate on the tray is the allergy plate. How the kitchen display organizes tickets by station is on the kitchen page (Kitchen display); what matters here is that the allergy alert has visual priority over everything else.

What the kitchen needs to see

• The allergen spelled out in full, not an abbreviation open to confusion.
• Exactly which dish is affected, with its number within the table.
• Whether the dish, as written in the recipe, contains the allergen and which ingredient must be replaced or removed.
• A mandatory confirmation step before the dish can be marked ready.

The tray and the table: who confirms

The note survived to the kitchen and the dish came out right. There is still the step where most errors happen: delivery. At a table of four, the server sets down the plates and leaves; nobody says “this is the one without peanuts”. In room service, the tray goes up with two dishes and the guest does not know which is which. Confirmation at delivery is part of the process, not a courtesy.

The allergy dish is physically marked, with a flag, a different plate or a cover of another color, and the server delivers it saying out loud to which person and with which note. On the terminal, the server marks the dish as delivered and confirmed, and that mark is recorded with time and name. It is one second of work and it is what closes the chain.

Guest in house: the allergy lives on the profile, not on each order

Here is the difference between a street restaurant and a hotel restaurant. The street diner eats once and leaves; the hotel guest has breakfast, lunch and dinner and orders to the room for three or four days. If the allergy is recorded on every order from scratch, the hotel forces the guest to repeat it twelve times, and on one of those twelve someone will not hear it.

The allergy must be tied to the guest folio. The moment the server records it for the first time, it stays on the stay profile, and every later order charged to that room, at any revenue center, is born with the alert already set. The pool bar, room service and the restaurant all see the same thing. And when the guest returns on their next trip, the profile remembers before they have to say it.

This requires that room charge be tied to a real folio and not to a typed number. A room number in a text field has no profile and no memory; a folio does. The room charge page (Room charge) details that difference.

The record that protects the hotel

If despite everything an incident occurs, the question any lawyer, insurer or authority will ask is the same: what did the hotel know, when did it know it and what did it do with that information. A hotel that answers with a stained paper ticket is in a very different position from one that answers with a record showing the time the guest warned, the server who recorded it, the cook who confirmed the alert and the moment of delivery.

That record is not assembled afterward; it assembles itself as a consequence of the previous steps. Every mandatory confirmation leaves a trace with time, user and order, and the trace is kept tied to the folio for as long as hotel policy and the law of your country establish. How long and in what format is a conversation with your legal advisor; that the record exists and cannot be edited afterward is a conversation with your system.

An illustrative example with numbers

The figures below are invented to show the reasoning; they do not describe any hotel. Suppose a 30-room hotel with a restaurant that issues 600 orders a week across dining room, bar and room service. Of those 600, 30 carry an allergy note, that is one in every 20.

With the paper process, every note passes through five steps and each one carries a chance of loss. If one in every 50 notes is lost at each step, out of 30 notes a week roughly 30 × 5 ÷ 50 = 3 are lost. Three orders a week where the allergy did not arrive complete where it should have. In a year that is about 150. Not all of them end in an incident, but each one is a chance for one to happen.

With the required field, the kitchen alert and inheritance to the folio, the steps where the note can be lost shrink to one: the moment the guest warns and the server records. If one in 50 is still lost there, out of 30 weekly notes fewer than one is lost, and that one is what the mandatory question on every order addresses. The arithmetic is illustrative; the point is that what you control is the number of failure points, not people’s attention.

Frequent mistakes

• Recording the allergy in the remarks field alongside “no ice” and “medium”.
• Placing it at table level instead of diner level, so the kitchen does not know which plate is affected.
• Trusting that the night server will tell the breakfast server.
• Not physically marking the allergy plate on the room service tray.
• Allowing the order to be sent to the kitchen without answering the allergy question.
• Keeping the record on paper, where it cannot be searched and the time cannot be proven.

What to do this week

1. Review the last 100 orders from the hotel restaurant and count how many allergy notes there are and where they are written.
2. Define the list of allergens the server can mark with one tap, and the “other” option with a required description.
3. Agree with the chef on a physical signal for the allergy plate: flag, different plate or colored cover.
4. Establish that no order is sent to the kitchen without answering whether there is an allergy at the table.
5. Verify that an allergy recorded in the restaurant appears on the same guest’s room service order that night.
6. Ask your legal advisor how long the record must be kept and in what format.

Inn Restaurant records the allergy as a required field on the order, ties it to the guest folio so the whole stay inherits it, shows it on the kitchen display as an alert with confirmation and keeps the trace of every step. If you want to see how an allergy note travels from the table to the folio, book the 15-minute demo at (contact).