Guest request · Evidence before reassurance

How Restaurants Should Handle Dietary Requests

“Can you make this without dairy?” sounds like a menu question. In practice, it crosses the server, current labels, recipes, substitutions, shared equipment, the line, and final pickup. The safest useful answer is a documented capability decision, not a confident guess.

Read the direct answer Lire en français

Direct answer

Ask what food or ingredient source the guest needs to avoid and what cross-contact precautions they are requesting. Check the current label and recipe, map every station and shared tool, and have the responsible kitchen person decide whether the restaurant can follow its approved process. Record the decision on the ticket, control preparation and pickup, and say clearly when the request cannot be met.

What this page covers

Allergy, intolerance, gluten-free, dairy-free, and other dietary requests
Dine-in, takeout, delivery, catering, and changed ingredients
Request intake, capability decision, ticket, preparation, and pickup

What it does not decide

Diagnosing a guest or deciding what they medically need to avoid
A promise of zero cross-contact risk
Permission to ignore the restaurant’s approved allergen or food-safety process

What the intake record must translate

A label such as “allergy” or “preference” is not enough to direct a kitchen. Record the operational facts without asking the guest to prove a diagnosis.

Guest wording

Exact food or source to avoid
Requested cross-contact precautions
Item, modifier, service type, and timing

Read the request back in plain language. Do not tell a guest to claim an allergy to receive more care.

Current evidence

Recipe version and approved substitute
Package label, ingredient list, and advisory statements
Fryer, grill, toaster, blender, utensils, storage, and garnish path

If the current evidence is missing or the station path cannot be controlled, escalate before accepting.

Service handoff

Named kitchen decision maker
Ticket wording and visual control
Preparation owner, plate or package identifier, and pickup verifier

The same decision must survive every handoff. A verbal promise at the table is not a kitchen control.

Translate the request across five handoffs

Step 1

Start with the food, not a diagnosis

The restaurant needs an exact operating request.

1Ask which food, ingredient, or source must be avoided and what precautions the guest is requesting.
2Confirm the exact menu item, size, modifiers, sides, sauces, garnish, beverage, and service method.
3Repeat the request back without deciding whether it is an allergy, intolerance, preference, or medical restriction.

Step 2

Build a current evidence packet

Yesterday’s recipe card cannot verify today’s substitute.

1Open the current recipe, supplier label, ingredient list, allergen information, and approved substitution record.
2Trace compound ingredients such as sauces, dressings, spice blends, breading, stocks, desserts, and garnishes.
3Stop and escalate when a label is unavailable, a formulation changed, or staff cannot identify the product in use.

Step 3

Map the physical path

A suitable ingredient can still enter an uncontrolled station.

1Check storage bins, scoops, prep surfaces, utensils, gloves, cloths, fryers, grills, toasters, blenders, steam wands, pans, pass, packaging, and delivery seals as relevant.
2Identify flour dust, splashes, shared oil or water, crumbs, buttered surfaces, reused brushes, and utensil swaps that the approved process must address.
3Decide whether the restaurant can create and maintain the required separation during the current service.

Step 4

Make one capability decision

The person with the evidence must own the answer.

1Have the trained manager or kitchen lead accept, modify, or decline the request under the restaurant’s approved process.
2Record limitations and the exact approved item. Do not use “should be fine,” “probably,” or “we have never had a problem.”
3If the restaurant cannot control the request, explain that boundary before the order is placed and offer only verified alternatives.

Step 5

Protect the ticket, preparation, and pickup

A correct answer can be lost at the next handoff.

1Mark the ticket using the restaurant’s approved signal and require an acknowledgement from the preparation owner.
2Keep the order, tools, ingredients, plate or package, and garnish path identifiable until completion.
3Verify the finished item against the ticket at pickup and include the request in any remake, delay, substitution, or delivery handoff.

Step 6

Close the learning loop

A request can reveal a weak control even when no incident occurs.

1Record missing labels, unclear recipes, uncontrolled equipment, ticket failures, unavailable trained staff, and declined orders.
2Correct the menu reference, substitution approval, station plan, training, or staffing owner before the next service.
3Treat a reported reaction or suspected exposure as an incident and follow the restaurant’s emergency and notification process.

Common shortcuts that fail at the line

“The guest said preference, so cross-contact does not matter.”

Ask what precautions the guest requests, then state what the restaurant can and cannot control. Do not infer the acceptable risk.

“The allergen chart was printed last month, so the item is verified.”

A changed brand, sauce, garnish, or substitute can change the answer. Use the current evidence.

“The server knows the menu.”

Knowledge helps with intake, but the kitchen decision still needs current labels, recipes, station controls, and a documented handoff.

“Removing the visible ingredient fixes the order.”

Compound ingredients and shared equipment can remain in the path. Audit the whole item.

Shift-ready files

Keep the question, evidence, and decision together

The PDF keeps a stable print layout. The UTF-8 CSV is editable for the restaurant’s approved process.

Download printable PDF Download UTF-8 CSV

Sources and limits

The official sources below support the visible claims. Always verify the scope with the authority responsible for the activity and jurisdiction.

Questions that prevent false reassurance

Should staff ask whether the request is an allergy?

Staff can ask what food must be avoided and what precautions the guest requests. They should not diagnose, challenge, or ask the guest to change their wording.

What if the current ingredient label is missing?

Do not guess from memory or a previous case. Escalate to the responsible person and decline or change the item if the approved process cannot verify it.

Can the restaurant guarantee zero cross-contact?

Do not promise what the kitchen cannot prove. Explain the controls used, disclose relevant limitations, and let the guest decide whether to order.

What does Maxuod Shift do here?

It can schedule trained coverage and retain a shift note. It does not diagnose guests, verify labels, approve recipes, or guarantee a meal.

Open the ingredient-specific path

Gluten-free order guide Dairy-free order guide Ingredient substitution approval