Front of House

The Hospitality Experience Starts Before the Guest Arrives

Most guests decide how they feel about a restaurant in the first minute, and most of that minute was decided hours earlier. Whether the host greets a returning couple by name, whether the server already knows about a shellfish allergy, whether a birthday table gets a card or an awkward pause: in my experience those outcomes are set by what the team knew at 4 PM, not by how charming anyone is at 7. I think of the hospitality experience as something you prep, the way a kitchen preps a station.

I'm Richard Yu. I have more than 15 years of startup and go-to-market experience, much of it in customer success, and today I'm a co-founder and the Managing Partner for marketing and operations at the restaurant I co-founded in San Francisco. I built Regular inside it, one service at a time. Here is the pre-service routine I use for allergies, regulars, celebrations and large parties, and where I think technology helps and where it gets in the way.

The Experience Is Decided Before the Door Opens

When a service goes wrong at the front door, the cause is usually upstream. The host did not know the four-top at 7:30 was a regular. The server learned about the nut allergy when the guest mentioned it for the second time. The anniversary note sat in the reservation and nobody read it.

None of those are effort problems. They are information problems. The guest told us something, or we already knew it from a past visit, and it did not reach the person standing in front of them.

I learned this in software before I learned it in restaurants. In customer success, the worst meeting is the one where you discover the customer's problem during the meeting. The good ones start with homework: what they bought, what broke last quarter, who is new on their side. A dining room works the same way.

Picture a guest who booked for a birthday, noted a gluten allergy and asked for a quiet table. If the team knows all three before doors, that guest gets a relaxed evening. If the team finds out one at a time, the guest spends the night repeating themselves.

What the Host Should Know at 4 PM

The restaurant host stand is where the night's information should come together, and 4 PM is my deadline for it. By then the book is mostly set, the schedule is known, and there is still time to act on what you find.

Here is what I want the host to be able to answer without opening a screen during service:

  • How many covers are booked, and where the pinch points are by time slot.
  • Which guests have been in before, and which of them come often.
  • Every allergy and dietary note on tonight's book, by table and time.
  • Celebrations: birthdays, anniversaries, promotions, anything flagged.
  • Large parties, their arrival time and whether their menu is set.
  • Seating requests that affect the floor plan, such as booths, accessibility or a quiet corner.
  • Who is working tonight, and whether anyone is missing.

If the host cannot answer one of these at 4 PM, that is the gap to fix before doors, not during the first seating. A host who walks into service with this picture can make better seating calls, warn the kitchen early and greet people like they were expected, because they were.

Allergies, Notes and Seating Requests

Guest notes are only useful if they travel. A note that lives in the reservation system but never reaches the server is, from the guest's side, a note we ignored.

For allergies I keep three rules. First, the host reads every allergy on the book aloud at pre-shift, with table and time, so the kitchen and floor hear it together. Second, the server confirms the allergy at the table anyway, because notes can be incomplete and guests sometimes forget to mention a second one. Third, anything the guest tells us at the table gets added back to their notes after service so we do not ask from scratch next time. Allergen handling is regulated in many places, so check your local rules and train to them; what I describe here is an operating habit, not a substitute for that.

Seating requests deserve the same care. If someone asked for a booth or step-free access, the host should block that table in the plan before service starts, not hunt for one when the party walks in. Picture a guest with a stroller arriving to a table that needs a step up. The fix took thirty seconds at 4 PM and is awkward at 8.

Regulars, Celebrations and Large Parties

Regulars are the guests whose experience is easiest to get wrong, because they notice when we forget them. Before service I want the host to know which reservations belong to repeat guests, what they usually order or where they like to sit, and anything we learned last time. Greeting someone by name is the start; remembering that they prefer the bar seats is what makes it feel personal. I wrote more about that progression in how to turn first-time guests into restaurant regulars.

Celebrations need prep that cannot happen once the guests are seated. A card, a personalised menu or a candle on dessert has to be decided and ready before doors. In Regular, the Celebrations app detects birthdays and anniversaries from reservation flags and notes, and prints a personalised menu per diner and a postcard per celebrant before service. However you do it, do it before 5 PM. There are more ideas in restaurant birthdays and anniversaries guests remember.

Large parties are a pacing problem as much as a hospitality one. Confirm the count, the menu and the arrival time, and tell the kitchen when twelve covers will hit at once.

A Ten-Minute Pre-Shift That Covers It

A pre-shift meeting does not need to be long to be useful. Mine runs about ten minutes and follows the same order so the team knows what is coming and can tell when something is missing. Use this as a front of house checklist at your next service:

  1. The book (1 minute): total covers, the busiest time slot, and any tables being held or combined.
  2. Allergies (2 minutes): each one read aloud with table and time. The kitchen confirms they heard it.
  3. Regulars and VIPs (2 minutes): names, preferences and anything to follow up on from their last visit.
  4. Celebrations (1 minute): who, which table, and what is prepared.
  5. Large parties (1 minute): arrival time, menu, and who is leading the table.
  6. Staffing (1 minute): sections, who is missing, who covers.
  7. One focus (2 minutes): a single thing to do better tonight, ideally drawn from last night.

The last item is where the coaching happens. Keep it to one point. If you want the larger rhythm this sits inside, I covered it in the manager's week.

What Technology Should Do Here

Technology should do the gathering, so people can do the greeting. Pulling allergies, visit history, celebrations and seating notes out of the reservation system and the point of sale is clerical work. In my experience it is also where most of the misses come from, because a manager compiling it by hand at 4 PM is tired and in a hurry.

What technology should not do is stand between the host and the guest. If the host is scrolling a tablet while a regular waits to be greeted, the tool has failed. The briefing should be read before doors and then mostly carried in people's heads, with a printed sheet at the stand as backup.

This is why I built Regular to connect the reservations, point of sale and staff schedule a restaurant already uses. Its Today's Guests app shows each reservation tonight with visit history, VIPs, allergies and seating notes, which is the 4 PM picture without the hunting. You can see the other apps in Regular, or book a demo if you want to walk through it.

If you run a different version of this routine, I would like to hear it. You can find me on Instagram.

Frequently Asked Questions

What should be covered in a restaurant pre-shift meeting?

A useful pre-shift meeting covers tonight's cover count and busy slots, every allergy with its table and time, regulars and VIPs with their preferences, celebrations and what is prepared for them, large parties and their menus, staffing and sections, and one focus point for the night. Keeping the same order each day helps the team spot what is missing, and ten minutes is usually enough.

What should a restaurant host know before service starts?

Before doors, a host should know the number of covers by time slot, which guests are returning, all allergy and dietary notes, celebrations, large party details, seating requests such as booths or step-free access, and who is working. Having this ready by mid-afternoon gives time to block tables, brief the kitchen and prepare for celebrations instead of reacting during the first seating.

How do restaurants keep track of guest notes and allergies?

Most restaurants store guest notes in their reservation system, but the notes only help if they reach the floor. A reliable habit is to read allergies aloud at pre-shift, confirm them again at the table, and add anything new back into the guest's notes after service. Allergen rules vary by location, so check local requirements and train staff to them.

Why does the hospitality experience start before the guest arrives?

Much of what makes a guest feel welcome depends on what the team already knows: their name, their allergy, the occasion, where they like to sit. That information has to be gathered and shared before service. When it is, the greeting and the first minutes feel prepared. When it is not, guests often end up repeating themselves to several people.

Regular

Run the Night Your Regulars Remember

One suite of apps that connects your reservations, POS and schedule, from before the meal to the next visit.