Allergy Requests Need a Clear Route Through Service
Make room for the request before promising a dish
Handling an allergy request efficiently begins with giving it enough attention the first time. We pause the order-taking conversation and establish which guest the request concerns. We record the food or ingredient to be avoided in the guest's own terms, then clarify anything ambiguous without challenging the request. A broad word such as nuts needs clarification about the specific foods involved. We never turn a stated allergy into a preference because the room is busy or the preparation looks straightforward.
A food allergy can cause a serious reaction, so a guest's previous experience is not permission for us to improvise. We follow the food-safety and allergen rules that apply where we operate, together with the operation's established procedures. Other dietary requests also deserve accurate recording, including restrictions connected to intolerance or personal practice. We clarify what must be avoided and keep the guest's description intact. We do not diagnose the reason or rank how deserving the request sounds.
Read the information back before leaving the table
We confirm the request with the guest and connect it to a clear seat position in the order. This matters when several people choose similar dishes or change seats later. We record each relevant restriction explicitly, using the operation's approved notation rather than an abbreviation invented during service. If information came from the host, we confirm it directly with the guest before proceeding. That check completes the handoff begun during the welcome at the door.
We explain that the kitchen must check the proposed food and its preparation before we can confirm suitability. We do not promise that removing a visible ingredient will solve the request. A garnish can be only one part of the issue, and a menu description is not a complete ingredient record. When a guest asks for a recommendation, we identify possibilities for checking rather than naming a dish as safe from memory. The distinction should remain clear in our wording.
Send a marked order and obtain an acknowledgment
The request travels through the designated ordering process with the relevant dish and guest clearly identified. Where the procedure requires direct communication with the kitchen, we make that handoff as well as marking the order. We seek acknowledgment from the person responsible for checking the request; sending a note does not establish that it has been understood. One server keeps ownership of the response, even if a manager helps resolve the question. Otherwise several people may each assume someone else has answered.
The kitchen's assessment needs current ingredient information and consideration of the actual preparation, including possible cross-contact. Shared equipment and utensils can matter even when the named ingredient is absent from the recipe. We relay the kitchen's answer accurately, including any limitation or inability to accommodate the request. If the answer remains uncertain, we do not serve the proposed item as suitable. Any alternative goes through the same checking process; a simpler-looking dish does not earn an automatic exemption.
Keep the rest of service organized while checks happen
We tell the guest that a check is underway and return with an update rather than disappearing into the kitchen conversation. If the assessment takes time, we discuss what that means for the table's meal without framing the guest as the cause of a disruption. Other service tasks can continue where appropriate, but food or drink for the affected guest still needs the relevant checks. Bread placed automatically on the table should not bypass the established procedure.
Once the kitchen confirms what it can prepare, we agree the meal's timing with the table and pass that decision back. A modified dish may have a different preparation time, which belongs in the course plan before other dishes are released. We preserve the allergy marking through any order change. If an item is canceled and entered again, the replacement order needs the full information rather than relying on a conversation attached to a ticket nobody is now using.
Verify the plate at the pass and at the table
Before food leaves the pass, the designated check confirms the dish against the marked order and the approved preparation. The runner needs to know which plate belongs to which guest, including the relevant request. We do not rely on a vague gesture toward a tray or the appearance of a missing garnish. If the plate cannot be identified confidently, it stays at the pass while the team resolves the uncertainty. A second of hesitation should never become a reason to guess.
At the table, we confirm the intended guest before placing the dish and identify the agreed preparation discreetly. If people have moved seats, we resolve that change directly. We make the usual check after service while remaining attentive to anything the guest reports. A suspected reaction requires the operation's emergency procedure and prompt emergency assistance where needed, never reassurance that the food was checked. A plate served incorrectly must return for assessment; removing the unwanted ingredient at the table is not a correction.
Carry the request through the whole meal
The request remains active for later courses and any additional order. Dessert does not become a fresh conversation in which the earlier information disappears. We pass the details explicitly if another server takes over and check any offered accompaniment through the same process. Shared dishes need particular care in the conversation, because a plate intended for the middle of the table may still be eaten by the affected guest. We establish the intended arrangement rather than assuming everyone will remember an earlier explanation.
After service, unclear handoffs belong in the team's review. We look for the specific break, such as an unreadable modifier or a runner who received no seat information, and revise the procedure that allowed it. Updated ingredient information belongs in the next service briefing before the same question arises again. Efficiency comes from avoiding repeated uncertainty. Necessary verification keeps its place in the sequence, even when that means explaining a longer wait or declining a dish.