Guest notes that actually help - and the ones that just describe private life
A look at how restaurants can separate guest notes with practical value from notes that merely describe the guest as a private person - with concrete examples of neutral language and fixed routines for removing notes that have gone out of date.
From practical preference to private detail - how notes drift over the line
The first notes in a booking system are often entirely practical: window table, wheelchair, food allergy. But over time, some notes drift into something else - a comment that the guest always seems stressed, or that she came with a new partner last time. Such lines say little about what should happen at the table, but a lot about the guest as a private person.
The problem isn't that one server jots this down in a rush. The problem is that the note stays in the system, read by the next shift, the next season, and by staff who have never met the guest. What was a loose observation one evening can wrongly be taken as a fixed trait. A booking system should describe service, not pass judgment on guests' private lives.
Test the note against tonight's operations, not the guest's history
A simple test is to ask: does this note change anything concrete about tonight's operations? A request for a table away from the kitchen, a nut allergy, or that the party is celebrating a birthday - all three affect how the table is set, which route the kitchen takes, or when the cake is brought out. These are notes with a clear operational function.
Notes without such a function should be written down less often. That a guest 'always orders wine before food' is interesting to know, but changes nothing staff do differently. Compare 'wants a window table due to mobility' with 'likes to sit alone' - the first guides a decision tonight, the second merely describes a habit.
Language that describes the situation, not the guest
Wording should describe the situation, not characterize the guest. 'Asked for a new drink twice and wanted shorter waits between courses' is useful and neutral. 'Difficult guest' or 'demanding couple' says nothing concrete, but sets an expectation for the next server before the guest has said a word. Describe what happened, not who the guest is.
The same principle applies to information about health, family, or finances. A note that the guest recently divorced, just had a baby, or seemed short on money has no place in a booking system - however well-intentioned it was when written. Ask whether the information is necessary for service tonight or on the next visit; if not, it doesn't belong there.
Routines that keep the notes list clean over time
Notes need an owner, not just a sender. Regularly remove what was tied to a single occasion - an old birthday, a delay that was resolved, a complaint that has already been followed up on. How often this should be done, whether at the change of season, monthly, or on some other rhythm, is up to each restaurant to decide.
In TableBooking, bookings, guests, and floor plans are gathered in the same dashboard, so notes can be kept in one place instead of scattered across shift logs and private messages. This makes it easier to see what's actually written there - and simpler to weed out what shouldn't have been written in the first place.
Want to see how it works in practice?
Start with a free restaurant account and build your tables, opening hours and booking link at your own pace.
Start free