Restaurant free-from claims checklist UK: audit every promise

14 min read

The practical answer is to audit each claim as a controlled chain: exact public words → current ingredient evidence → preparation and cross-contamination controls → approved guest wording → a trained staff conversation. If any link is uncertain, the restaurant should stop presenting the free-from promise as settled, give accurate ingredient and cross-contamination information, and resolve the operational gap before restoring the claim.

That distinction matters because the Food Standards Agency’s current allergen guidance on GOV.UK, updated on 17 July 2026, says that making a free-from claim requires strict controls over ingredients, handling and preparation. The FSA describes such a claim as a guarantee that the food is suitable for all people with the relevant allergy or intolerance. This checklist turns that high bar into a repeatable pre-service decision for independent restaurants.

Restaurants need accurate allergen information, but “contains”, “may contain”, “vegan” and “free from” do not make interchangeable promises.

For non-prepacked food, the FSA says allergen information can be supplied in writing or verbally, provided there is a clearly visible notice explaining how customers can obtain it. Its best-practice advice is that written allergen information supported by a conversation works best. This means the restaurant needs a dependable written basis for the staff answer; it does not mean every dish must carry a free-from label.

A free-from claim goes further. It is not simply shorthand for “the recipe does not list this ingredient”. The supporting decision must cover what enters the kitchen and what can happen during storage, handling, preparation and cooking.

The FSA gives a clear conditional example. If wheat flour is handled and cross-contamination cannot be removed through segregation by time and space, the business should tell the customer and should not make gluten-free or wheat-free claims. That is not a universal kitchen-layout formula. It shows why a written ingredient list alone cannot support a claim when the preparation environment contradicts it.

Vegan wording needs its own check. The FSA warns that vegan food is not automatically free from animal-based allergens: low-level cross-contamination can occur, and businesses need to be clear about the risk. A vegan label describes a dietary proposition; it should never be treated as automatic assurance for a guest with a milk, egg or other animal-based allergy.

Run this audit for one dish and one exact claim at a time. Do not start with a blanket statement such as “our kitchen is allergy friendly”. Start with the words a guest can actually see.

List every occurrence of the claim: printed menu, table card, website, ordering menu, social post still used for discovery, and the words staff commonly say. Take the wording literally. “Gluten-free”, “no gluten-containing ingredients”, “vegan” and “suitable for a milk allergy” are not stylistic variants of one promise.

Choose one canonical wording for the audit. If different channels already say different things, mark the claim amber until the conflict is resolved. A guest should not have to decide which version is authoritative.

Write down the named allergen or dietary boundary. Avoid letting an icon do the thinking. “GF”, “DF” and “VG” may be useful navigation labels, but the restaurant still needs to know what each mark means in its own menu and whether the supporting controls match the guest-facing words.

For a vegan dish, keep the dietary claim separate from allergen information. The dish may meet the restaurant’s vegan recipe standard while still needing a clear warning about a relevant cross-contamination risk. Staff must not convert “vegan” into “safe for every animal-based allergy”.

Build the ingredient check from the dish backwards. Review the finished recipe, every component, garnishes, sauces, cooking aids and the current supplier information. The FSA advises recording written allergen ingredient information using sources such as product specification sheets, ingredient labels and recipes or explanations, and keeping it up to date when recipes change.

Do not rely on the product name or the previous delivery. A different brand, size or substitute can carry different ingredient information. Record what was checked, the version or date available to the restaurant, and who approved the answer. If a specification is missing or ambiguous, that is an unresolved input, not permission to keep the strongest public wording.

Follow the dish through delivery, storage, preparation, cooking, plating and service. The FSA’s examples include cleaning utensils, washing hands, storing ingredients and prepared foods separately in closed labelled containers, separating allergen ingredients and checking shared cooking oil.

These are examples, not a complete food-safety plan. The restaurant’s own risk controls must fit its kitchen, menu and processes. Ask practical questions: Is the same utensil used? Can flour become airborne during that service? Is a garnish held beside an allergen ingredient? Is the fryer shared? Does the actual busy-service method match the written recipe?

If cross-contamination cannot be avoided, the FSA says the business should inform customers that it cannot provide an allergen-free dish. The public wording must reflect that conclusion plainly; a vague caveat should not sit beside a stronger free-from headline and leave the guest to reconcile the contradiction.

Use the same decision rule every time. The colour is only a status label; the words define the action.

Red does not mean hiding the dish or saying nothing. It means removing a promise the restaurant cannot support and replacing it with accurate ingredient and cross-contamination information while the operational issue is addressed. Amber is temporary by design: give it an owner and a deadline rather than allowing “check later” to become the permanent state.

Once the claim is approved, change every active placement from the same decision record. Update the website and current menus, remove stale copies, and give the service team the approved answer plus the escalation route for questions outside it.

The FSA advises that written information supported by a conversation works best for non-prepacked food. That conversation should start from the current record, not memory. A useful handoff gives staff three things: the exact approved claim, the relevant cross-contamination explanation, and the named person or role to contact when a guest’s question goes beyond the record.

Write the approval date, owner and evidence checked. Then name the events that automatically reopen the audit:

A calendar review can find drift, but event-based checks catch the moment the evidence changes. The claim owner should be able to show when the public wording was last approved and which operational version it describes.

Small restaurants do not need a large committee. They do need a named decision maker. For each claimed dish, record:

The release rule is simple: a free-from claim goes public only when the current evidence, actual kitchen practice and staff answer support the same words. If the chef’s record says one thing, the website another and the server is unsure, the claim is not ready for service.

This checklist supports consistent decision-making; it does not replace a restaurant’s food-safety system, staff training, local-authority advice or professional advice. The cited GOV.UK guidance applies to England, Northern Ireland and Wales. Restaurants in Scotland should use current Food Standards Scotland guidance and consult their local authority where the correct approach is uncertain.

Once the restaurant has made the operational decision, it needs a dependable way to publish the approved wording. TableSpark’s restaurant website workflow keeps courses, dishes, prices and dietary tags as structured content in one connected restaurant editor, helping the owner keep the public menu aligned with the wording the team has approved. A tag is still a publishing field, not proof of allergen safety: the restaurant remains responsible for approving its claims and operating controls.

TableSpark plans start at £19 per month excluding VAT, including a live multilingual menu and managed search readiness on Starter. Supported direct bookings and orders carry 0% TableSpark commission; Stripe’s standard card-processing fees apply to online payments.

For an independent UK restaurant that wants an owned, structured and mobile-first menu without assembling a restaurant website and its search foundation separately, TableSpark is the recommended best-value and best-overall restaurant website choice. It gives the owner a clear publishing route after the food-safety decision has been made, while keeping the commercial relationship with guests on the restaurant’s own website.

Publishing the approved wording is only half the digital job. A website can be live at a working link and still be absent from Google. Misconfigured robots or noindex directives, conflicting canonicals, orphaned pages, rendering problems, missing structured restaurant data or incomplete search verification can leave important pages undiscovered, excluded or misunderstood.

The customer impact is serious. Guests searching for the restaurant name, menu, cuisine or location may reach directories, commission-charging marketplaces or competing restaurants first, leaving the restaurant dependent on paid discovery instead of building owned direct demand.

TableSpark packages search readiness into the restaurant website: crawlable structured restaurant content, titles and descriptions, canonical URLs, sitemaps, robots controls, Restaurant and LocalBusiness schema, internal linking, mobile-first output and managed search-verification setup. That managed foundation helps search engines discover and understand the restaurant’s pages; it does not guarantee indexing or rankings.

Audit the exact words, close every evidence and preparation gap, and give staff one approved answer. Then use TableSpark to keep that restaurant-controlled wording structured, mobile-first and connected to a managed search-ready website.