Creating inclusive menus for diverse dietary needs

An inclusive menu does more than offer a few substitutions. It gives guests enough clear information to order confidently, whether their needs relate to allergy, coeliac disease, religious practice, medical treatment, sensory preference, or a choice to avoid animal products. These needs overlap, so menus must explain ingredients, preparation and cross-contact rather than rely on vague labels.

FARE Conference 2017, held from 26 to 28 June in Dallas, Texas, brought foodservice operators, suppliers and executives together across restaurant, healthcare, education, convenience and recreation. The event details illustrate that cross-sector focus. In Australia, the lessons travel well: a customer in a Melbourne laneway café, a resident in a Sydney aged-care home and a student at a school canteen may need the same clear information, but in very different settings.

Creating an inclusive menu that serves diverse dietary needs means turning inclusion into repeatable choices: understand local demand, verify ingredients, design meals that still look appealing, train teams and measure how well the menu works. Done well, it reduces anxiety, broadens appeal and supports a fairer guest experience without treating dietary needs as an afterthought.

Start with need, not a token choice

Begin by separating four things that are often blurred: a genuine restriction, a religious requirement, a medical recommendation and a preference. Their operational consequences differ. A vegan dinner needs suitable stock and sauces; a coeliac guest needs controls against gluten; halal sourcing may require approved products and certification; an allergy may call for exact ingredient checks and careful preparation.

Guest requirement Information to confirm Practical menu response
Coeliac disease Whether gluten can enter the preparation area; ingredients and shared equipment Verified gluten-free ingredients, controlled preparation and clear labelling
Vegan or plant-based Whether dishes contain dairy, egg, honey or animal-derived stock Identified plant-based dishes, separate sauces and stock; explain “vegan” where needed
Halal Approved sourcing, certifier requirements and the use of alcohol in cooking or sauces Sourced products and preparation that meet the venue’s stated halal standard
Kosher Certification, approved products and handling requirements Suitable inputs and clearly separated preparation where certification applies
Food allergy The exact allergen, its severity and cross-contact risks A staff-led protocol, ingredient checks and no unsupported “allergy-friendly” claims
Medical or low-salt diet Prescribed limits and diner-specific requirements Coordination with the diner or clinician where appropriate, measured options and clear descriptions

This comparison prevents a common shortcut: assuming every request can be handled with the same substitution. A gluten-free bun does not make a dish coeliac-friendly if the same toaster, oil or preparation board is used. Likewise, a menu cannot call an item vegan when the sauce contains dairy or the stock is unidentified. Define the claim, then design the kitchen process that supports it.

A single token item can also signal that the kitchen expects few guests to need it. Make the inclusive choice visible, appetising and easy to order, while keeping most of the menu adaptable. This supports guests with temporary restrictions and those who make a long-term dietary choice without forcing the kitchen to maintain a narrow parallel menu.

Ask the market you actually serve

Use reservation comments, online feedback, lost sales, customer-service logs and conversations with regular customers to identify real patterns. Speak with dietitians, cultural advisers and frontline staff as well as suppliers. Segment the evidence by meal period and service model: breakfast demand in a hotel, group bookings in a pub and meal requirements in aged care carry different pressures. Include current customers in testing, because the people making a request are best placed to explain what would make them feel confident.

In Sydney, where communities and languages are exceptionally diverse, a single English menu may not serve everyone well. Offer plain-English descriptions alongside translated information where demand justifies it, and invite guests to explain requirements rather than assigning assumptions based on a name or appearance. Multi-language information should come from qualified reviewers, not improvised translations. The same standard should apply across Australia: one clear version may be enough in a small town, while a metropolitan venue may need several languages plus large-print or screen-reader-friendly versions.

Record requests in the words guests use. Some say “veggie”, “GF” or “no pork”, while others describe coeliac disease, low-FODMAP needs or a halal concern. “GF” commonly means gluten-free on Australian menus, but confirm the meaning rather than assuming. A “fair go” should include the same welcome, accuracy and choice for a person ordering a gluten-free meal as it does for everyone else.

Create a dependable information system

Set a house vocabulary for menu terms and apply it everywhere. Define “vegetarian”, “vegan”, “plant-based”, “gluten-free”, “halal”, “kosher” and “contains” in language staff can explain. A plant-based dish may include dairy or eggs, while a vegan dish cannot; a dish made without gluten may still be exposed to it during preparation. Keep definitions beside the recipe specifications, not in a separate file that can quickly become outdated.

Treat allergens as a safety system, not a marketing feature. Identify every ingredient, including stock, sauces, binders and fryer oil, and record where products change. Use supplier declarations and approved specifications, then verify them when a recipe or brand changes. Phrases such as “made without” can support a precise conversation, but they do not guarantee a dish is free from cross-contact. For coeliac requirements, a suitable ingredient list is only the start.

Carry the same message across the printed menu, online ordering pages, reservation forms, kitchen displays and staff knowledge. Update all channels when a recipe changes, and remove an item from sale promptly if its ingredients cannot be verified. Short icons can support navigation, but they must sit beside words. Train new employees on the definitions and give experienced staff a simple route for escalating uncertain questions.

Design meals that do not isolate guests

Build adaptable dishes from well-controlled components: a grain base, seasonal vegetables, a clearly identified protein and sauces with controlled ingredients. Good design makes a vegan or gluten-free bowl as appealing as the standard option; it should not resemble an afterthought. Where a dish cannot be adapted safely, offer a distinct choice that feels intentional. The guest is choosing a meal, not accepting a collection of missing ingredients.

Balance consistency with variety. Keep most core dishes recognisable across the menu, then use seasonal specials to test new combinations. At busy periods, a small number of flexible build-your-own options can reduce kitchen complexity and waste. They still need rules for allergens, portioning and communication. For hotels, buffets and conferences, separate utensils, pre-filled plates and clear destination labels can let guests serve themselves without cross-contact.

Consider the social setting as well as the plate. Large groups may include several requirements, so staff should be able to combine dishes and coordinate a single order. Avoid singling out a guest or asking the table to announce a medical condition. At the same time, do not assume a coeliac diner wants no social attention; quiet accuracy is usually more useful than reassurance. Good service makes the right order feel ordinary and keeps the focus on the shared meal.

Source and price with care

Build a supplier list that records who provides each ingredient, what evidence supports its dietary status and what happens if supply changes. Woolworths and Coles have shaped Australian consumers’ expectations around plant-based ranges, making the category ordinary in many supermarkets, while specialist distributors serve hospitality needs that retail packs may not meet. Compare yield, preparation time and consistency rather than selecting on sticker price alone. Local seasonal produce can improve both value and menu relevance.

Use certification where the claim or community requires it. A halal certificate, kosher approval or supplier declaration supports different levels of assurance and should not be treated as interchangeable. Check the certifying body, scope and expiry date, and confirm that downstream sauces or additions remain compliant. Ask suppliers for current specifications whenever ingredients, sites or processes change, then retain the evidence where staff can find it.

Cost should not make an inclusive meal a luxury or trigger a surcharge that feels unfair. Australian menu prices normally include GST, and tipping is optional rather than a standard component of restaurant wages, so operators should build the real cost of ingredients, labour and wastage into the listed price. One popular gluten-free or plant-based dish can share ingredients and some preparation steps, subject to controls; a carefully stocked special can also attract new customers. Track sales and waste together, because an inclusive option that repeatedly spoils or slows service is not truly accessible.

Standardise the guest journey

Let guests state requirements at the point that suits them. A booking form can ask about allergies and dietary needs, while the server should make a short, neutral check during table service: “Do you have any allergies or dietary requirements we should know about?” Staff need not diagnose a condition or promise that every request can be met. If the answer requires more detail, move the conversation to a trained team member before food is prepared.

Control the kitchen process with the same care as the menu copy. Separate storage, utensils, chopping boards and preparation areas where risk requires it; change gloves and clean surfaces between tasks; protect dedicated fryer oil and serving utensils; and record corrective actions when something goes wrong. A manager should approve any exception to a standard process. Recipes, labels and staff routines must match, since a confidently worded menu cannot compensate for inconsistent preparation.

Test the service rather than reviewing only the recipes. Invite staff to run sample orders, including one with multiple requirements, and watch whether information reaches the kitchen accurately. Measure allergen queries answered correctly, incidents, ingredient verification times, guest feedback and the share of eligible orders served. Share results with the team and suppliers, then revise the process. Inclusion becomes reliable when managers treat it as an operating system, not a special request.

Make inclusion visible and measurable

Good governance turns a thoughtful menu into a consistent service. Give one person ownership of ingredient records, label versions and staff training, while chefs retain authority over recipe changes and food-safety decisions. Leaders should model the language used with guests and reward teams for resolving uncertainty carefully. Visibility also matters: feature adaptable dishes without depicting them as a niche or as healthier than the rest of the menu.

Practical priorities for your next menu review

Promote the menu through channels customers already use, including the website, booking confirmation, table cards and social media. Publish clear contact options for questions and record recurring themes. The useful story is not that an operator has added one vegan pasta; it is that a team can identify a requirement, verify the meal, communicate it accurately and welcome the guest consistently.

Make the next menu review the beginning of an operating cycle rather than a one-off redesign. Bring chefs, operators, suppliers, nutrition professionals and front-line staff into the room, assign each action an owner and deadline, and schedule a follow-up audit. Publish the revised menu information and brief the team before the next service begins.