Server

Servers carry the guest relationship for the length of a meal, and they are the widest collection point a restaurant has for guest information. An occasion mentioned over the first drink, an allergy, a wine somebody loved, the fact that one of the four does not eat pork: all of it surfaces at the table, and almost none of it is written anywhere.

How does a restaurant keep what a server learns at the table?

By giving the detail somewhere to go before the shift ends, and by attaching it to the guest rather than to the check. Two things work against that. Servers are the highest-turnover position in the dining room, so knowledge held in a server’s head has a short shelf life. And the tool in a server’s hands during service is the point of sale, which is built to record what was ordered rather than who ordered it or why they came in.

The fix is a habit more than a system. One line, typed into the booking or the guest record at the end of the night, by the server or by the manager closing out. Restaurants that manage it usually have a manager who collects it, because a server with four tables left will not stop to write anything down.

What gets recorded should be the part that lasts. A stranger reading the note in eight months has to be able to act on it, so “anniversary” is worth little where “anniversary, April 14” is worth something, and “liked the wine” is worth little next to a producer and a vintage.

Should servers have access to guest profiles?

To the parts they can act on, yes. The useful set during service is short: visit count, preferences, allergies, the occasion, and anything that went wrong last time. That fits on a pre-shift sheet, and most of it reaches the table that way rather than through anybody logging in mid-shift.

Spend history and contact details are a different question. Phone numbers and email addresses are guest personal information the restaurant is accountable for, and lifetime spend displayed in a service station changes how a table gets treated in ways an operator may not want. Guest platforms generally handle this with roles, so a server sees tags and notes while spend and contact detail stay with managers.