How to separate useful guest notes from unnecessary personal information
A review of how restaurants can separate practical preferences from unnecessary personal information in guest notes - with a simple relevance test, concrete examples of notes that work and don't work, and a reminder that notes are read by several staff members over time.
When a useful note becomes something else
Most guest notes start out practical: an allergy, a preferred table, a highchair that needs to be ready. Over time, and with several people writing them, some notes drift toward something else - a comment about mood, appearance, or assumptions about the occasion. No one means any harm by it, but the note stops describing a task for staff.
The problem isn't that the information is alarming, but that it doesn't belong in an operational routine. A note stating the guest seemed stressed last time, or is presumed to be on a first date, gives the server no instruction whatsoever. It becomes a private judgment stored in a system that's actually built for logistics.
The test: does the note give staff a concrete task?
The simplest way to weed out unnecessary notes is to ask one question before anything is saved: does this give a concrete task to whoever meets the guest next time? A note about nut-free service or wheelchair seating clearly answers yes. A note saying the guest was hard to please answers no - it describes an impression, not an action.
A good test can be broken down further. Is the information still accurate on the next visit, or is it tied to a single evening? Is it relevant to seating, kitchen, or service, or merely interesting to know? If the answer is uncertain on both counts, the note was probably written to remember something personal, not to help operations.
Examples that illustrate the distinction
Practical notes that work are short and action-oriented: a vegetarian main pre-ordered, a request for a table without stairs, arriving with a stroller, celebrating something and wanting cake served without candles, drinking only still water. These give the server and kitchen something concrete to prepare for, regardless of who reads the note again three months later.
Notes that shouldn't be kept often involve guesswork or opinions: comments about appearance, relationship status, presumed finances, political views, or general impressions of personality. Even well-meaning phrases like "a bit demanding" or "always in a good mood" say more about staff's subjective experience than about anything staff actually need to know to do their job.
Internal use: who reads the note, and why it matters
A guest note is rarely read by just one person. It follows the booking across several shifts, different servers, and sometimes the kitchen. That's why it should be written for the broadest imaginable reader - someone who doesn't know the guest but needs to know what to do differently this particular evening. Everything else is information without a recipient.
In TableBookings' dashboard, staff see bookings, guests, and the table map together, and tables can have a reference photo that makes it easier to find the right spot during service. This structure works best when the notes field contains what actually guides preparation and service, not what's interesting to know about the guest as a person.
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