Restaurant Employee Menu Knowledge Quiz
True / False
True / False
True / False
Select all that apply
Select all that apply
Select all that apply
Put in order
Put in order
Put in order
Select all that apply
Select all that apply
Select all that apply
Put in order
True / False
Menu Knowledge Pitfalls That Cause Wrong Orders (and How to Prevent Them)
Stating ingredients from memory when the dish is customizable
A frequent miss is describing the “standard build” while the kitchen actually plates different defaults (cheese choice, sauce base, garnish). Fix: memorize the default build for each signature item and also the “most common mods” (no cheese, sauce on side, protein swap) so you can confirm quickly.
Mislabeling dietary status (gluten-free, vegan, dairy-free)
Guests hear labels as safety guarantees. The biggest risk is assuming a menu icon means “no risk,” or assuming a substitution is always available. Fix: treat labels as rules-based: identify the ingredient that breaks the label (e.g., croutons for gluten; butter/cream for dairy; egg in dressings for vegan) and state whether a specific substitution exists.
Forgetting “hidden” allergens in sauces, dressings, and broths
Caesar dressing can contain egg and anchovy; marinades and glazes can contain soy; soups can use dairy or wheat thickeners. Fix: build a short list of high-risk components (dressings, aiolis, roux-based soups, compound butters) and verify recipes during pre-shift.
Ignoring cross-contact realities
Even if a dish has no nuts or gluten in the recipe, shared fryers, grills, cutting boards, or garnish stations can introduce exposure. Fix: never promise “safe” until you’ve confirmed the prep path (dedicated fryer? clean pan? separate utensils?).
Using the wrong modifier language at the POS
“No dairy” is not the same as “no cheese,” and “gluten allergy” is not the same as “gluten preference.” Fix: translate guest intent into kitchen/POS terms: itemize removals (cheese, butter, cream sauce) and add the allergy flag when applicable.
Pre-Shift Menu Mastery Quick Reference (Ingredients • Allergens • Modifiers)
Print/save as PDF and keep this as a pre-shift or new-hire reference. Update it whenever recipes, vendors, or plating standards change.
Signature builds to know cold (default components)
- Classic Caesar salad: romaine, Parmigiano-Reggiano, croutons, Caesar dressing (often egg + anchovy), black pepper, lemon.
- Margherita pizza: tomato sauce, fresh mozzarella, basil, olive oil; sometimes finished with Parmigiano-Reggiano.
- Guacamole: avocado, lime, onion, cilantro, salt; optional tomato and jalapeño.
- New York strip: short-loin cut; typical finish includes salt/pepper; may be finished with butter depending on house standard.
Allergen “hot spots” by component
- Dairy: cheese, butter, cream sauces, ranch/blue cheese dressings, mashed potatoes, béchamel/alfredo.
- Egg: mayo/aioli, Caesar dressing, some pastas, custards, breading/batters.
- Gluten (wheat/barley/rye): buns, croutons, breading, flour tortillas, roux-thickened soups/sauces, standard soy sauce.
- Soy: soy sauce, teriyaki, many marinades, miso, some veggie proteins.
- Shellfish/fish: shrimp stock, fish sauce, Worcestershire/anchovy in dressings.
- Nuts/sesame: pesto (pine nuts), nut oils, tahini/sesame seeds, dessert garnishes.
Dietary label decision rules (say what’s true)
- Gluten-free: no gluten ingredients and a low cross-contact prep path (confirm fryer/grill protocol).
- Vegan: no meat, dairy, egg, honey, gelatin; confirm broths, dressings, and buns.
- Dairy-free: remove cheese/butter/cream and confirm the sauce base (many “tomato” sauces are finished with butter/cheese).
30-second allergy handling checklist
- Clarify: “Allergy or preference?” and “Any level of cross-contact concern?”
- Identify triggers: list the likely sources in the dish (including sauces/garnishes).
- Confirm with kitchen: ingredients + prep path (separate utensils/pan/fryer).
- Repeat back: summarize the final build and the allergy note before sending.
Worked Example: Turning a Guest’s Restrictions into a Correct, Safe Order
Scenario: A guest says: “I’m gluten-free (celiac), dairy-free, and I can’t have eggs. Can I get the Caesar salad? Also, are your fries safe?”
Step 1: Break the request into constraints
- Gluten: no croutons; verify any seasoning blends and cross-contact.
- Dairy: no Parmesan; confirm no butter/cream in any component.
- Egg: Caesar dressing often contains egg (and may contain anchovy/fish).
Step 2: Identify the “hard stop” ingredients
Caesar dressing is the critical failure point for egg (and possibly fish). Croutons are the critical failure point for gluten. Parmesan is the critical failure point for dairy.
Step 3: Offer a specific alternative that matches the menu
Propose a romaine-based salad without croutons/cheese, using an egg-free, dairy-free dressing option your restaurant already supports (e.g., olive oil + lemon, or a verified vinaigrette). If the kitchen can do a protein add-on (grilled chicken or salmon), confirm the seasoning and grill protocol.
Step 4: Escalate prep-path questions before promising safety
For fries, ask the kitchen: “Do fries go in a shared fryer with breaded items?” If yes, they are typically not acceptable for celiac-level gluten avoidance. Offer a non-fried side cooked on a clean pan if available.
Step 5: Translate into kitchen/POS language
Send an order that is explicit: “Romaine salad — no croutons, no cheese, no Caesar; add verified vinaigrette; ALLERGY: gluten, dairy, egg; clean utensils/pan.” Then repeat the final build to the guest before it hits the pass.
Restaurant Menu Knowledge FAQ: Allergens, Labels, and Confident Recommendations
When a guest asks “Is this gluten-free?”, what’s the safest way to answer?
Answer in two parts: ingredients and preparation. If the recipe contains no gluten but shares a fryer/grill with breaded items, say it’s gluten-free by ingredients but not guaranteed gluten-free due to cross-contact, then offer an alternative cooked on a clean pan.
What should I memorize versus what should I verify with the kitchen?
Memorize default builds for signature dishes (proteins, cheeses, sauces, standard sides) and the usual “hidden” ingredients (egg in Caesar, dairy in cream sauces). Verify anything that changes by batch or vendor: soups, daily sauces, dessert garnishes, fryer usage, and any item marked “seasonal” or “chef’s special.”
How do I handle “vegan” requests when the dish looks plant-based?
Confirm the supporting ingredients: cooking fat (butter vs oil), broth base (chicken vs vegetable), and finishing touches (Parmesan, honey, gelatin). If a dish can be made vegan, state the exact swaps/removals and confirm the kitchen’s standard for that modification.
How specific should I be when noting allergens on a ticket?
Be itemized, not vague. “No dairy” should become “no cheese, no butter finish, no cream sauce,” plus the allergy flag if applicable. Specific notes reduce kitchen guessing and prevent accidental garnishes (e.g., shredded cheese, brioche crumbs, aioli).
What if a guest starts showing signs of an allergic reaction during service?
Escalate immediately per your restaurant’s emergency procedure (manager on duty, call emergency services if warranted, keep the guest seated, avoid giving food/meds you’re not authorized to provide). If you want to refresh response steps and communication under pressure, review the Emergency Quiz.
How can I ask clarifying allergy questions without sounding distrustful or robotic?
Use a short, respectful script: “Thanks for telling me—are we working with an allergy or a preference?” and “Is shared-fryer/contact a concern?” Pair empathy with precision. For phrasing and tone that keeps trust while gathering details, see the Customer Service Soft Skills Quiz.