Dietary labels guests can trust on a menu

A small green V beside a dish tells a vegetarian guest they can order it without asking. A GF mark tells a guest with coeliac disease they can relax. Dietary labels save guests questions, save servers trips to the kitchen and make a menu easier to use for the growing number of people who eat with a restriction.

They only work if they are true. A vegetarian dish made with a meat stock, a vegan dish brushed with butter at the pass, a gluten free dish cooked in the same oil as battered fish: each one breaks a promise the guest relied on, and some of them can make a guest ill. Once a guest finds one label they cannot trust, they stop trusting the others.

This guide covers how to mark dishes honestly, from the recipe rather than the name, what each common label really requires, the kitchen caveat that has to be written down, and how to show dietary labels so guests can use them. Every figure in it is an example, and it is general guidance rather than legal advice.

More guests than ever eat with some kind of restriction. Some are vegetarian or vegan by choice. Some avoid gluten, dairy or nuts for medical reasons. Some follow religious rules about what they eat. Many tables now include at least one guest who reads the menu looking for a mark.

Dietary labels help all of them find what they can eat quickly. A guest who can see at a glance which dishes suit them orders with confidence, rather than interrogating the server or choosing the one dish they are sure about. Labels also help the team: a server who can point to a mark answers questions faster and more consistently.

But a label is a statement the venue makes, in writing, about every plate of that dish it serves. That is why it has to be right every time, not most of the time.

It helps to be clear about the difference between a dietary label and allergen information, because they work in opposite directions.

Allergen information is a warning: this dish contains milk, or gluten, or sesame. It tells guests what to avoid. A dietary label is a claim: this dish is suitable for someone who is vegan, or who cannot eat gluten. It tells guests they can relax.

A claim is a stronger statement than a warning. It says not only that no animal products or no gluten were added as ingredients, but that the dish is prepared in a way that keeps it suitable. That is why "nut free" is not simply the opposite of "contains nuts": a dish with no nuts in the recipe, made in a kitchen full of nuts, is not nut free. Our guide to building an allergen matrix that stays correct covers the warning side; this guide is about the claims.

Vegetarian looks like the simplest label: no meat or fish. But vegetarian dishes go wrong in the parts nobody thinks of.

Stocks are the most common problem. A risotto or a soup made with chicken stock is not vegetarian, however vegetable-led it looks. Some cheeses are made with animal rennet, which many vegetarians avoid; a classic Parmesan-style hard cheese often is. Gelatine appears in desserts and some sweets. Worcestershire sauce usually contains anchovies, and so can some dressings and pastes.

So check every component, not just the main ingredient: the stock, the cheese, the sauce, the garnish, the dressing. A dish is only vegetarian if all of them are. Where a component is doubtful, such as a cheese whose rennet you do not know, either confirm it with the supplier or leave the label off.

Vegan means no animal products at all: no meat, fish, dairy, eggs or honey, and none of the less obvious ones, such as gelatine or some wine-fining agents. Vegan dishes fail most often at the edges of the recipe.

Butter added to finish a sauce or glaze vegetables at the pass is a classic error. So is an egg wash on pastry, honey in a dressing, a dairy-based mayonnaise or a sauce thickened with cream. Shared equipment matters too: a vegan dish fried in oil used for fish, or toasted on a grill brushed with butter, may no longer suit a strict vegan guest.

There is no single legal definition of vegan in many places, including the UK, which makes it more important that your own definition is clear and applied consistently. Write down what vegan means in your kitchen, check every component of every dish you label, and tell guests honestly about any shared equipment.

Gluten free is the label with the clearest rules and the most serious consequences. For guests with coeliac disease, even small amounts of gluten cause harm. In the UK and the EU, a claim of gluten free on food is allowed only when the food contains no more than 20 milligrams of gluten per kilogram, which is a tiny amount.

That threshold is easy to break in a kitchen. Flour in the air, a shared toaster, a shared fryer, a spoon used in two sauces, a chopping board used for bread: each can add enough gluten to make a dish unsafe. A dish with no gluten-containing ingredients is not automatically gluten free; it is gluten free only if it is prepared in a way that keeps it so.

Many venues therefore use a more careful wording, such as "made without gluten-containing ingredients", when they cannot control cross-contact fully, and reserve "gluten free" for dishes where they can. Whatever you choose, the wording must match what the kitchen really does. Official allergen guidance for food businesses from the UK government is a useful starting point.

Beyond vegetarian, vegan and gluten free, guests look for other marks, and each needs the same honesty.

Only use a label you can stand behind. A menu with six labels, four of which the kitchen is unsure about, is worse than a menu with two labels that are always right. If guests ask about a label you do not use, the server can always check with the kitchen.

Almost every kitchen that handles allergens and animal products shares some equipment and space. That reality needs to be stated honestly, in writing, wherever dietary labels appear.

A short statement at the foot of the menu does it:

The exact wording should match your kitchen. If your fryer is shared, say so. If you have a separate gluten free preparation area, say that instead. The caveat does not replace the labels; it tells guests how much weight to put on them, so they can make their own decision.

The only reliable source for a dietary label is the recipe, every component of it. The name of the dish, the way it looks and the chef's memory are not enough.

For each dish you label, list every component: the base, the sauce, the stock, the garnish, the dressing, the oil it is cooked in. For each bought-in component, check the supplier's specification for animal products and gluten. Only when every component passes does the dish carry the label.

Keep that record. When a dish's label is questioned, by a guest or an inspector, you should be able to show why it carries it. When a component changes, the record tells you which labels to check again.

Dietary labels and allergen information should come from the same record. If the allergen matrix says a dish contains milk, it cannot carry a vegan label; if it says a dish contains wheat, it cannot be gluten free. Keeping the two in separate places is how they end up contradicting each other.

Build the labels from the matrix and the recipes together. When a recipe changes, update the matrix and check the labels at the same time. Our guide to allergen rules and the conversation at the table covers how the written information and the server's conversation work together.

Dietary requirements also overlap with allergies. A guest who asks for dairy free may have a milk allergy, a lactose intolerance or simply a preference. The label serves all three, but the guest with an allergy needs the server's conversation as well as the label.

The most common way a correct label becomes wrong is a supplier change. A different brand of stock, a new bread, a substitute sauce on a day the usual one is out of stock: any of them can bring in gluten, dairy or an animal product the original did not have.

Make supplier changes part of the labelling routine. When a bought-in component changes, check its specification before it goes into a labelled dish. If the substitute does not meet the label, either remove the label for as long as the substitute is in use or take the dish off for the day. Tell the team, so servers do not promise what the plate no longer delivers.

Substitutions on busy days are the hardest to catch, because they happen in a hurry. A simple rule helps: no unplanned substitute goes into a labelled dish without the head chef's say-so.

The best labels are clear, consistent and explained once. Use the same marks everywhere, such as V for vegetarian, VG for vegan and GF for gluten free, and explain them in a short key at the foot of the menu. Place each mark in the same position beside every dish, so guests know where to look.

Keep the set small. A menu covered in eight different symbols is hard to read, and guests stop noticing them. Use the labels your guests ask for most and that your kitchen can guarantee.

Make sure the marks are readable. Do not rely on colour alone, because some guests cannot tell colours apart; a letter or a clear symbol works for everyone. Our guide to menu design for reading, not for framing covers the wider principles of a readable menu.

Good menu design treats labels as part of the information, not decoration. They should sit close to the dish name, in a size that can be read in the evening light, and they should never crowd out the dish's description or price.

Avoid making the labelled dishes feel like an afterthought. A separate vegan section at the bottom of the menu can feel like a corner for difficult guests. Labelled dishes woven through the menu, with a clear mark on each, tell guests with restrictions that they are as welcome as anyone else.

When a dish can be made suitable with a change, say so carefully. "Can be made vegan, ask your server" is helpful, but only if the change really makes the dish suitable and the server knows exactly what to ask the kitchen for.

Digital menus can do more with dietary labels. Guests can filter the menu to show only dishes that suit them, which saves them scanning every section. That is genuinely useful, and it also raises the stakes, because a guest who filters for vegan dishes may trust the results without reading further.

So the data behind the filter has to be as accurate as the printed marks. Every dish needs the right labels in the system, updated whenever the recipe or a supplier changes. A note near the filter reminding guests to tell their server about allergies keeps the conversation going.

Our guide to menu allergens, and what to put on the page itself covers how much detail belongs on the menu, printed or digital, and how much belongs in the conversation.

Servers are where labels meet guests. They need to know what each label means, which dishes carry it and why, and what the kitchen caveat says. They also need to know the limits: a label is not a guarantee against traces, and a guest with a serious allergy needs a proper conversation, not just a pointed finger.

Give servers simple answers to common questions. "Is the risotto vegetarian?" "Yes, it's made with vegetable stock and a vegetarian hard cheese." "Is the fried chicken gluten free?" "No, it's coated in flour, and our fryer is shared." Consistent answers build trust; vague ones undo it.

When a server is unsure, the answer should always be to check with the kitchen. Guessing is how labels lose their meaning.

Some guests need more than a label can give. A guest with a severe allergy, a guest with coeliac disease who reacts to traces, a guest with several restrictions at once: each needs a conversation and, sometimes, a dish prepared with extra care.

The label is the start of that conversation, not the end. A good process takes the guest's need, records it properly, tells the kitchen in a way the kitchen cannot miss, and checks the plate before it goes out. Our guide to modifiers, and letting guests change a dish safely covers how changes to a dish reach the kitchen.

If the kitchen cannot safely meet a guest's needs, say so honestly. A guest told "we can't guarantee that tonight" is disappointed; a guest made ill is harmed.

Labels depend on kitchen habits as much as recipes. Train the kitchen on what each label requires, which components break it, and how to keep labelled dishes suitable during service.

Practical habits help: labelled containers for vegan and gluten free components, separate utensils and boards where possible, clean surfaces before preparing a gluten free dish, no butter finish on a vegan plate. Make the habits part of the station set-up, not something remembered in a rush.

Check from time to time. Watch how a labelled dish is prepared during a busy service and see whether the habits hold. Most label failures happen not because the kitchen does not know, but because a shortcut is taken when it is busy.

Review every label whenever the menu changes, and check the whole menu every few months even if it has not. Go dish by dish: does the recipe still match the label, have any suppliers changed, does the caveat still describe the kitchen accurately?

Look at guest feedback too. Questions servers keep being asked, or complaints about a labelled dish, point to labels that are unclear or wrong. A label guests keep asking about may need a clearer key; a label that has caused a complaint needs checking immediately.

Record each review. A simple note of when each dish's labels were last checked, and by whom, makes the routine visible and shows it is being done.

An invented café marks a dozen dishes as vegetarian, vegan or gluten free. A guest who is vegan finds egg in the vegan mayonnaise on her sandwich, because a supplier sent a different product the week before. Another guest asks whether the gluten free toast is made in a separate toaster, and nobody knows.

The café rebuilds its labels from the recipes. It lists every component of every labelled dish, checks each supplier's specification, and finds three labels that no longer hold. It changes "gluten free" to "made without gluten-containing ingredients" where the toaster and fryer are shared, and adds a short kitchen statement at the foot of the menu. Supplier substitutions now need the head chef's approval before going into a labelled dish.

The menu ends up with slightly fewer labels, but every one is right. Servers answer questions consistently, guests with restrictions start coming back, and the café's reviews begin to mention that it is a safe place to eat.

In servearound, each dish carries dietary tags and allergen tags separately, chosen from a catalogue: dietary tags such as vegan, vegetarian, pescatarian, halal, kosher, gluten free, dairy free and nut free, and allergens from the statutory list and beyond, each allergen by family or by specific source. On the menu guests open from a table's QR code, a dish's dietary and allergen tags show in their own sections, guests can filter to show only dishes that suit them or to avoid an allergen, with a note to tell their server about allergies, and before an order is sent they confirm they have reviewed the allergen and dietary information.

The kitchen ticket shows each dish's allergens and the guest's own allergies at the head of the ticket. servearound does not hold recipes or supplier specifications today, so the labels are set by the venue on each dish and checked against your own recipe records; inventory tracking, for the stock behind the menu, is coming. See the menus module.

An allergen is a warning that a dish contains something. A dietary label is a claim that the dish suits someone avoiding something, which is a stronger promise.

Check every component, including stock, cheese, sauces, dressings and garnishes. Watch for chicken stock, animal rennet, gelatine and anchovies.

Butter added at the pass, egg washes, honey, dairy-based sauces and shared equipment such as fryers and grills.

In the UK and the EU, food may be called gluten free only if it contains no more than 20 milligrams of gluten per kilogram.

Not fried ones. Many venues use "made without gluten-containing ingredients" where they cannot control cross-contact, with a clear kitchen statement.

That the kitchen handles allergens and shares some equipment, what the labels do and do not promise, and that guests should tell their server about allergies.

Only those your guests need and your kitchen can guarantee every time. Fewer, accurate labels beat many doubtful ones.

Check the new product's specification before it goes into a labelled dish, and remove the label or the dish if it no longer qualifies.

They make labels more useful and raise the stakes, because guests may trust a filter without reading further. The data must be as accurate as the printed marks.

Dietary labels are claims, not warnings, and guests rely on them. Mark a dish only from its full recipe, checking every component and every supplier: stocks, cheeses, sauces, finishing butter, egg washes and shared equipment are where vegetarian and vegan labels fail, and cross-contact is where gluten free fails. Use only the labels your kitchen can guarantee, and write down the kitchen caveat about shared equipment.

Show labels clearly and consistently with a key, keep them in the same record as your allergen matrix, and make supplier substitutions part of the routine. Train servers to answer simply and check when unsure, train the kitchen to keep labelled dishes suitable during service, and review every label whenever the menu changes.