A dietary request may describe an allergy, an intolerance, a religious practice, a preference or another need. The team should clarify what the guest is asking for, protect the information and check the food operation before confirming an option.
Never treat a menu note as proof that a meal is safe for a person with an allergy. Explore Feathers Hospitality’s hotel management services, its operations platform and the team contact page to review request handoffs.
In brief
- Clarify the request without asking for a diagnosis.
- Check ingredients and kitchen controls with the responsible team.
- Confirm only what can be delivered safely and consistently.
Ask what the guest needs the team to do
Use neutral wording such as “What would be helpful for us to know about your meal?” If the guest mentions an allergy, clarify the ingredient or food they need to avoid and which meal or service they are asking about. Do not ask for a medical history or assume that an intolerance and an allergy are interchangeable.
Explain that the kitchen must verify the request before the hotel confirms a dish. A front desk employee should not infer ingredients from a dish name or last season’s menu. If the guest communicates a serious allergy, pass the information directly to the authorised food-safety contact using the approved channel.
Separate preferences from allergy controls
A preference can often be addressed by selecting another listed dish; an allergy requires reliable ingredient and handling information. Use separate fields or labels in the workflow so a note such as “no dairy preference” is not treated as equivalent to a confirmed allergy procedure.
The ASAE’s restaurant allergy manual and EU food-information rules are relevant sources for allergen information. They do not mean that every kitchen can guarantee the absence of cross-contact. Confirm how the specific venue prepares, stores and serves the food before describing an option as suitable.
Check the current recipe and supply chain
Ask the kitchen to verify the recipe, current product label and any substitutions. A supplier or seasonal change can alter ingredients without changing the menu name. Record which version or service period was checked and who confirmed it. If a label is missing or unclear, pause the promise and offer only an option that can be validated.
The EFSA explains that small amounts of an allergen can trigger a reaction in a sensitive person. Do not improvise a reassurance such as “there should not be any.” If the kitchen cannot verify the information or control cross-contact, state that limit clearly so the guest can make an informed decision.
Limit who can see the request
Dietary information may reveal sensitive personal information. Store only what the teams need to prepare and serve the agreed meal, and restrict access to staff involved in that service. Avoid placing detailed health information on a printed room list or repeating it in a public area.
The GDPR requires data to be relevant and limited to the purpose. Agree how the request is removed after the service or stay and how an update reaches the kitchen. The hotel’s data protection lead should confirm its legal basis, access and retention approach for the actual workflow.
Set realistic expectations before arrival
Acknowledge the request and say that the team will confirm availability by a named time or channel. Do not write “we can accommodate this” until the kitchen has checked. If a request cannot be met, explain what remains possible, whether another venue can assist and who can answer further questions.
Make sure a change in arrival time or dining service reaches the responsible team. A request in the booking platform is not complete if staff cannot see it during service. Use a confirmation step and a clear owner, especially when the guest has asked about more than one meal.
Review incidents without blaming the guest
If the promised dish is unavailable or a note is missed, prioritise the guest’s immediate safety and follow the venue’s incident procedure. Record the process failure factually and involve the food-safety lead. Do not ask the guest to prove a medical condition before responding to an allergy concern.
Afterward, review where the handoff failed: request capture, recipe verification, supplier update, service communication or staff training. Change the process and test it before making the same promise again. Record only what is needed for the follow-up and apply the organisation’s retention policy.
Frequently asked questions
Can reception confirm that a dish is allergy-safe?
Only an authorised person with current ingredient and preparation information should confirm what the kitchen can safely provide. Do not guess or promise that cross-contact is impossible.
Should we record a guest’s medical diagnosis?
Usually the service needs the dietary requirement, not a diagnosis. Collect and share only the minimum information needed under the hotel’s approved privacy and food-safety procedures.