Key takeaways
- Free-text notes fail at the shift change. A short list of standard tags, each with an owner, does not.
- Allergy notes need the most care: 23% of adults report a food hypersensitivity[1], and reported reactions have risen[1].
- Every tag answers one question: who does what, and when?
- Review the tag list monthly and delete tags nobody acts on.
Why most booking notes fail
Every booking system has a notes field, and most diaries are full of notes nobody reads. “Celebrating!!”, “regular, be nice”, “nut thing?”, “wants window”: each one was typed by someone who meant well and then went home. By the time the evening team arrives, the note is either missed, misunderstood or acted on twice.
The problem is not effort; it is format. Free text can say anything, so nobody knows which notes matter. A tag system fixes this by limiting notes to a short list of agreed codes, each with a clear owner and a clear action. Staff turnover makes this more pressing: young workers are a big part of evening hospitality, with 18.6% of night-time cultural and leisure workers aged 16 to 19 in 2022[2]. A system that a new starter can read on their first shift is worth more than one that relies on memory.
A tag dictionary you can copy
| Tag | Meaning | Owner | Action and timing |
|---|---|---|---|
| ALLERGY | Named guest has an allergy; detail in the note | Server and head chef | Chef sees it at 4pm briefing; server confirms at the table |
| DIET | Vegetarian, vegan, halal, coeliac or other preference | Server | Mention at order; kitchen notified on the ticket |
| OCCASION | Birthday, anniversary, engagement; what to do | Host | Card or candle ready before arrival |
| ACCESS | Step-free, quiet table, chair with arms | Host | Table locked when booked; checked at pre-shift |
| CHILD | Children in party, ages, high chair | Host | High chair set before arrival |
| SEAT | Specific table or area requested | Diary owner | Assigned if possible; guest told if not |
| REGULAR | Known guest; preferences in profile | Manager | Greeted by name; usual order noted |
| ISSUE | Past complaint or service recovery owed | Manager | Manager visits the table |
| PREPAID | Deposit or prepayment taken | Host | Checked against the bill at payment |
Keep the list short. Nine tags is plenty for most venues; twenty means people stop reading them. Each tag should be visible on the floor plan and the kitchen’s view of the diary, not hidden behind a click.
Allergy notes deserve their own rules
An allergy note is the one note where a mistake can hurt someone. In England, Wales and Northern Ireland, 23% of adults reported a food hypersensitivity in 2025[1]. Among people with a hypersensitivity, the share who had a bad or unpleasant food reaction in the past year rose from 42% in 2021 to 59% in 2025[1].
Source: Food Standards Agency, 2025[1]
Show the data
| Item | Value |
|---|---|
| 2021 | 42% |
| 2025 | 59% |
Food law requires businesses serving non-prepacked food to provide allergen information for every item containing any of the 14 regulated allergens[3]. The booking note does not replace that duty. It gives the kitchen a head start. Make the allergy note work by following four rules:
- Name the person and the allergen: “Guest in seat 3, sesame, carries an adrenaline pen” rather than “allergy on table”.
- Record severity only if the guest offers it, and never assume an intolerance is mild.
- Copy the allergy onto the order ticket, not just the booking. The kitchen cooks from tickets.
- Confirm it again at the table. Most people with a hypersensitivity, 71%, feel comfortable asking staff for more information[1], so make the conversation easy to have.
Written information carries more weight with guests too: 86% of diners were confident in allergen information given in writing, against 60% for verbal information[4]. A note that turns into a written check at the pass reassures guests and staff alike.
Making notes survive the shift change
Write notes at the point of booking
Whoever takes the booking adds the tags there and then, using the dictionary. No notes added later from memory.
Run a 4pm notes review
The diary owner reads every tagged booking for the evening, fixes vague notes and asks the guest if something is unclear.
Brief by table, not by name
At pre-shift, read out tags by table number and time so each section knows its own tables.
Print or display the kitchen view
Allergy and diet tags appear on the kitchen screen or a printed sheet with times, so the chef sees them before tickets arrive.
Close the note after service
Mark occasion and issue tags as done, and move lasting preferences to the guest profile.
Example: one birthday, three shifts
Example. A fictional 70-cover restaurant takes a booking on Monday for a Saturday birthday dinner for six, with one coeliac guest. The phone note says only “birthday + gluten”. On Saturday, the dessert arrives without a candle, and the coeliac guest is offered bread twice.
After switching to tags, the same booking reads: OCCASION (40th birthday, candle on dessert, name Ana), DIET (coeliac, guest in seat 2, confirmed no cross-contact options with chef), and a note that the cake is coming from the family. The head chef sees the DIET tag at the 4pm review and plans the dessert. The host has the candle ready. The server confirms the coeliac guest at the table before bread goes down.
Keeping the system clean
- Audit a sample of 20 bookings each month. Were the tags right, and did someone act on each one?
- Delete tags that nobody uses or acts on.
- Retrain new starters on the dictionary in their first week, with real examples from the diary.
- Keep notes factual and polite. Guests can ask to see the data you hold about them.
- Move health notes off the booking once the visit is over unless the guest agrees to keep them for next time.
A small, trusted set of notes beats a long, ignored one. If a tag has not changed what anyone did in a month, it is noise.
What the kitchen needs and what the floor needs
The kitchen and the floor read the same booking for different reasons, so show each team the tags it acts on. The kitchen needs allergies, diets, prepaid or set menus, large tables and their arrival times, and any birthday dessert. The floor needs everything else: occasions, access, children, seating requests, regulars and service recovery.
- Kitchen view: time, table, covers, ALLERGY and DIET tags with detail, PREPAID or set menu, and any dessert request.
- Floor view: time, table, covers, name, OCCASION, ACCESS, CHILD, SEAT, REGULAR and ISSUE tags.
- Both: the party size and arrival time, which drive pacing for the whole evening.
If your booking system cannot filter views, print a kitchen sheet at the 4pm review with only the kitchen tags on it. One page the chef reads beats a screen nobody checks.
Phone bookings: where notes go missing
Notes taken by phone are the weakest link, because the person answering is often serving at the same time. Give phone bookings a closing routine that mirrors the online form: ask about allergies and diets, occasions and access, then read back the tags you have added. “I’ve noted a sesame allergy for one guest and that it’s a birthday. Anything else we should know?” The guest hears exactly what the kitchen will see, and can correct it before it matters.
If calls are answered by several people, keep a laminated card of the tag dictionary by the phone. If messages are taken for a call back, the call-back slip should use the same tags, so nothing is translated twice.
Seating requests: promise carefully
Seating requests are the notes most likely to disappoint, because they are easy to type and hard to honour on a busy night. Treat them as requests, and be clear about which ones you can guarantee.
- Guarantee only what you can lock in the diary, such as an accessible table or a booth assigned at booking.
- For views, windows and quiet corners, say “we’ll do our best” and mean it.
- If a request cannot be met, tell the guest before they arrive rather than at the door.
- Never move a locked ACCESS table to satisfy a SEAT request.
Regulars and VIPs without the awkwardness
A REGULAR tag should help staff welcome someone warmly, not recite their history at them. Keep the profile to useful, friendly facts: their usual drink, preferred table, the name they like to be called and anything they have chosen to share. Leave out gossip and judgements, and write every note as if the guest might read it, because under data protection law they can ask to. A good test is whether a new member of staff could use the note to make the guest feel recognised in one sentence: “Welcome back, Mr Okafor. Your usual table by the window?”
Frequently asked questions
What should go in restaurant booking notes?
Only information someone will act on: allergies and diets, occasions, access needs, children and high chairs, seating requests, regulars and any service recovery owed. Use standard tags so every note looks the same.
How should allergy information be recorded on a booking?
Name the guest and the allergen, copy it onto the order ticket and confirm it again at the table. Allergen information must still be available for every dish containing a regulated allergen[3].
How do we stop notes getting lost between shifts?
Add tags at the point of booking, review every tagged booking before service, brief by table number and show allergy tags on the kitchen view.
How many booking tags is too many?
Most venues manage with eight to ten. If staff stop reading them, cut the list.
References
Food Standards Agency (2025). Food and You 2: wave 11 key findings (opens in a new tab) ↑
Office for National Statistics (2022). The night-time economy, UK: 2022 (opens in a new tab) ↑
Food Standards Agency (2026). Allergen guidance for food businesses (opens in a new tab) ↑
Food Standards Agency (2025). Food and You 2 Annual Report: Wave 11 (2025) (opens in a new tab) ↑