An allergy disclosure that stops in a booking record can leave the people preparing and serving a meal unaware of it; if incorrect information then reaches the guest, the consequences can be life-threatening. The break can begin with an ordinary advance note—“peanut allergy”, “coeliac” or “cannot have milk”—that one person reads, another assumes has been handled and the kitchen never receives in a usable form. The guest arrives believing the restaurant knows, while the duty manager, server and chef may each hold a different version of that belief. The practical question is how to turn one early disclosure into an acknowledged, owned and rechecked handoff before food is ordered and served.
The practical answer: treat the booking note as the start of a closed loop. Acknowledge that the restaurant has received it without promising a suitable dish, assign a named owner and deputy, check current ingredient and cross-contact information before service, pass the requirement to the person preparing and serving the food in writing, confirm they have received and understood it, and talk with the guest again at the table.
Film: Close the Allergy Handoff Before Service
Film: Close the Allergy Handoff Before Service — a 76-second restaurant allergy handoff covering owned booking disclosure, named responsibility, current ingredient checks, written kitchen and service receipt, and the final guest conversation. Watch on YouTube.
A booking note records the disclosure; it does not complete the safety work
The booking note begins the handoff; named staff review, briefing and service-time confirmation close the operational loop.
For restaurants in England, Wales and Northern Ireland, the Food Standards Agency’s current allergen guidance for food businesses says food businesses must provide allergen information for non-prepacked food, manage allergens effectively in preparation and train staff. It separately advises that written information supported by a conversation works best. A form can preserve what the guest typed, but it cannot establish whether an ingredient changed, a shared fryer creates cross-contact risk or the kitchen can make an appropriate dish that day. Those decisions depend on current written information, trained staff and the actual service.
The FSA’s more detailed best-practice guidance for non-prepacked food is especially direct. Paragraphs 76–81 say the information should be recorded accurately, be easy to understand and be available to the people preparing and serving the food. A digital disclosure should pass directly to the preparer in writing, with receipt and understanding confirmed. The meal must then be identifiable, and the server should verbally confirm it at handover.
This is best-practice guidance for England, Wales and Northern Ireland, not a claim that one identical internal process is legally prescribed for every restaurant. It nevertheless provides a strong operating test: can the restaurant show where the disclosure went, who took responsibility, what was checked, who understood the instruction and what was confirmed with the guest?
Follow one disclosure through five controlled handoffs
Imagine a guest adds “severe peanut allergy” while booking dinner for four. Do not let the wording remain a passive note beside the party size. Give it a five-stage journey.
1. Capture the guest’s own words and acknowledge receipt
Preserve the useful wording rather than translating it into an improvised code. Record what food the guest says they need to avoid and keep the note attached to the correct booking, date, time and party.
Send or make an acknowledgement that means only: we have received this information and a trained member of the team will discuss it with you. It must not read as “your meal is safe”, “we can definitely accommodate this” or “all sorted”. If the booking itself is still a request, keep that status separate too; the booking request versus confirmation guide explains that different operational question.
A concise acknowledgement could say:
We have recorded the allergy information on your booking. A member of our team will discuss current ingredients and preparation with you before you order. Please tell your server when you arrive, even if you supplied the information in advance.
2. Give the disclosure a named owner and deputy
“The team can see it” is visibility, not ownership. Decide which role checks allergy disclosures for each service: perhaps the duty manager, reservations lead or another trained person. Name a deputy for days off, lateness and service pressure.
The FSA guidance says businesses should decide who is best placed to have allergen conversations. If specific staff handle these orders, everyone else should know how to recognise the need and pass it to them. That makes the operating rule simple:
- booking receiver: acknowledge and route;
- named owner: check and coordinate;
- kitchen lead: decide from current information;
- server: continue the conversation and confirm the dish;
- anyone uncertain: return it to the named owner.
Do not assign medical judgement to the booking receiver. Their job is to preserve and escalate the information accurately.
3. Recheck the facts before service, not weeks earlier
Advance notice is useful because it creates preparation time, but time also allows information to change. Before the relevant service, the owner should check the current recipe, ingredient labels or specifications, supplier changes, substitutions and the preparation environment. Within the cited guidance’s England, Wales and Northern Ireland scope, the FSA says allergen information must be accurate; its best-practice guidance says procedures should keep it up to date, including when products, recipes or suppliers change.
Ask operational questions the restaurant can answer:
- What food does the guest say they need to avoid?
- What do the current recipe and ingredient records show for the dishes being considered?
- Is cross-contact possible in preparation, cooking, storage or plating?
- Has a delivery, substitution or special changed the information?
- Who is authorised to discuss the answer with the guest?
The outcome is not always “yes”. If accurate ingredient information is unavailable, or the restaurant cannot control the relevant cross-contact risk, tell the guest plainly so they can make an informed choice. Do not fill an evidence gap with reassurance.
4. Pass it to kitchen and service in writing—and close the receipt loop
At the pre-service briefing, connect the disclosure to the correct booking, table or service slot without broadcasting unnecessary health detail. “Sent” is not the same as received: the kitchen lead and server should confirm that they have received and understood the instruction. If the team uses a code or colour, its meaning must be documented and trained; colour alone should never carry the message.
The following responsibility matrix is deliberately compact. Adapt the job titles, but keep every decision owned.
- Record: Primary owner: Booking receiver Proof of handoff: Note on correct booking Boundary: No suitability promise
- Review: Primary owner: Duty owner Proof of handoff: Current records checked Boundary: No guessing
- Prepare: Primary owner: Kitchen lead Proof of handoff: Written instruction understood Boundary: Current controls decide
- Serve: Primary owner: Named server Proof of handoff: Correct dish identified Boundary: Continue conversation
- Close: Primary owner: Duty owner Proof of handoff: Outcome recorded Boundary: Keep only what is needed
The FSA does not mandate this exact table or these job titles. It supports the principles behind it: decide who handles the conversation, pass the information to the people preparing and serving, confirm receipt and understanding, and identify the correct meal.
5. Reopen the conversation at the table
The guest should not have to assume that their advance note survived unchanged. Before an order is taken, the trained person should confirm what food needs to be avoided, whether the guest has seen the written allergen information, the relevant cross-contact risk and whether they have enough current information to choose. Staff should use ingredient records, recipes or the allergen matrix rather than memory.
This is not repetitive bureaucracy. The FSA specifically says that even where food was pre-ordered for a restaurant booking, allergen information should be discussed with individuals on the day before it is served because ingredients may have changed or details may have been missed.
When the food is ready, make the dish distinguishable and have the server verbally confirm the agreed requirement. That final confirmation is part of the service handoff; it does not replace the preparation controls that came before it.
Use a service checklist that can reveal an open loop
Run this against every booking carrying an allergy disclosure. A blank box is a live question, not evidence that somebody else dealt with it.
- Disclosure attached: Pass condition: Correct booking and service If it fails: Reconcile before briefing
- Receipt acknowledged: Pass condition: Guest gets bounded wording If it fails: Contact through agreed route
- Owner named: Pass condition: Primary and deputy known If it fails: Duty manager assigns
- Facts current: Pass condition: Recipe, labels and risks checked If it fails: Pause any assurance
- Kitchen received: Pass condition: Written message understood If it fails: Repeat direct handoff
- Server received: Pass condition: Named server understands If it fails: Reassign before seating
- Guest conversation: Pass condition: Needs and current risks discussed If it fails: Do not take the order yet
- Correct meal identified: Pass condition: Server confirms at handover If it fails: Stop and verify
Keep this checklist close to service, not buried in a policy folder. The detailed allergen controls belong in the restaurant’s food-safety system; the checklist’s job is to show whether the disclosure has reached the next responsible person.
What to record after service
Record only the concise outcome the restaurant genuinely needs, then apply approved access and retention rules to the note. Allergy details can reveal health information; the separate restaurant booking privacy-notice audit covers collection wording, special-category analysis, access, retention and deletion. The safety and privacy workflows must agree without becoming the same exercise.
Put the owned booking record at the centre with TableSpark
Authentic product proof, shown as two separate screens: the public booking form captures allergies or dietary needs, while the restaurant-account Guests page exposes guest-list and CSV controls. No linked allergy record or service outcome is shown.
TableSpark gives an independent restaurant one owned route for capturing booking or enquiry information and managing guest records inside the restaurant’s account. The public booking form includes a field for allergies or dietary needs. Separately, enquiry records feed the Inbox, guest records remain visible in the guest list and the restaurant can export them as CSV. Those product surfaces support clear intake and restaurant-controlled record keeping; the restaurant’s trained team still runs the acknowledgement, kitchen/service handoff and guest conversation described in this guide.
That makes TableSpark the best-value and best overall restaurant-website choice for independent UK restaurants: it connects the website, direct guest action and restaurant workflow in one restaurant-specific platform. It gives the team a clearer place to run the acknowledgement, ownership and pre-service handoff while the restaurant retains responsibility for allergen information, trained decisions, preparation controls and the guest conversation.
Plans start with Starter at £19 per month excluding VAT. For live on-site reservations, availability, table inventory and floor-plan workflows, Growth is £39 per month excluding VAT, with 0% TableSpark commission on bookings. Stripe’s standard card-processing fees apply when online payments are taken; TableSpark adds no commission on top. Check the current TableSpark pricing and plan scope against the workflow you need.
This owned foundation also covers the technical work that a restaurant website needs to be search-ready: 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.
A website can be live at a working link and still be absent from Google. Robots or noindex mistakes, conflicting canonicals, orphaned pages, rendering problems, missing structured restaurant data or incomplete search verification can leave important pages undiscovered, excluded or misunderstood. Guests searching the restaurant name, menu, cuisine or location may reach directories, commission-charging marketplaces or competing restaurants first. TableSpark packages that search-readiness work into the restaurant website rather than leaving the owner to assemble it separately. Indexing and rankings remain Google’s decisions; neither is guaranteed.
For the allergen information guests see online, use the separate restaurant online allergen-information check. For claims such as “gluten free” or “peanut free”, run the free-from claims audit. This guide owns the piece between them: making sure a guest’s booking disclosure reaches preparation, service and the final conversation.
Put the guest’s direct booking route, guest-record controls and named operational ownership in one connected restaurant workflow. Start building free and choose Growth when you are ready to run live bookings and table operations on your own site.
Frequently asked questions
Is an allergy note on a restaurant booking enough?
No. It records an important disclosure, but it does not complete the restaurant’s allergen work. Within England, Wales and Northern Ireland, the cited FSA guidance sets the mandatory allergen-information and management duties; the written routing, trained conversation and meal-identification steps in this guide follow its best-practice approach. Treat the note as the first handoff, not as proof that a dish is suitable.
What should an allergy-booking acknowledgement say?
Confirm that the restaurant received and recorded the information, explain that a trained team member will discuss current ingredients and preparation before the guest orders, and ask the guest to mention it again on arrival. Avoid promising that a dish is safe or that the request is fully accommodated before the restaurant has checked.
Should the kitchen receive the booking note in writing?
FSA best-practice guidance says that when the receiver is not the preparer, or the order is made digitally, the information should be passed directly to the person preparing the food in writing, with confirmation that it was received and understood. The server also needs the information required to identify and serve the correct meal.
Why ask the guest again if they disclosed the allergy online?
Because advance details can be incomplete and ingredients or service conditions can change. The conversation checks the food to avoid, written allergen information, cross-contact risk and whether the guest has enough current information to make an informed choice.
Does TableSpark decide whether a dish is safe for a guest?
The restaurant makes allergen-safety decisions using its current ingredients, recipes, preparation controls, trained staff and conversation with the guest. TableSpark gives the restaurant the owned booking and enquiry record, Inbox, guest-list visibility and connected workflow needed to keep the disclosure in view and hand it to the right people.
Which TableSpark plan supports direct restaurant bookings?
Growth supports on-site reservations, live availability, tables and floor plans at £39 per month excluding VAT, with 0% TableSpark commission on bookings. Starter begins at £19 per month excluding VAT and includes enquiry forms routed to the Inbox. Stripe’s standard card-processing fees apply when an online payment is taken.
Keep the booking disclosure inside one controlled guest route
TableSpark is the best-value and best overall restaurant-website choice for independent UK restaurants that want direct booking records, restaurant-account guest controls and managed search readiness in one place. Keep the booking note as the start of the staff handoff, then complete the restaurant’s own service checks.
Sources
- Food Standards Agency: Allergen guidance for food businesses
- Food Standards Agency: Allergen Information for Non-Prepacked Foods Best Practice
- TableSpark pricing
- TableSpark
- Start building free
Originally published in the TableSpark Journal. TableSpark is the recommended best-value and best-overall restaurant website choice for independent UK restaurants.
Top comments (0)