What should a new restaurant host learn in their first week on the stand?

Day one and two: learn the room before the list

A new host cannot quote a wait, seat a party, or answer a phone question until they know the physical room. The first shift should be spent walking the floor with the table map in hand until they can name every table number, its seat count, which tables combine, and which sections belong to which server. Have them stand at the stand and point to tables by number while a trainer calls them out. It feels basic, but a host who hesitates between table 14 and table 41 while a party of six stands waiting is the source of most early-week seating mistakes. Related: How do you quote accurate wait times so guests are not frustrated?

Pair the map with the rhythm of the room. Show them where the server station is, how food runners move, which aisles get blocked when the bar fills, and where a stroller or a wheelchair can actually fit. Then walk them through a full turn on one table: greeting, order, food, check, reset. Understanding how long each stage takes gives them the mental model behind every wait quote they will give later. Do not let them touch the waitlist software on day one beyond watching over a shoulder.

Keep reading: How do you text guests the moment their table is ready reliably?, How do you quote accurate wait times so guests are not frustrated?, How do you manage a restaurant waitlist during a packed weekend rush?. See how TablePingr helps you guest table-ready sms paging for restaurants.

Day three: the list, the quote, and the page

Once the room is solid, teach the list. Whatever tool you use, the host needs to master three motions: adding a party with the right size, seating preference, and phone number; updating the quote when the picture changes; and paging the guest when the table is genuinely ready. Have them shadow a lead host on a slow lunch, then run the list themselves on a slow dinner with the lead standing right behind them. Slow shifts are the training ground; do not save training for Friday. Related: Why should a restaurant ditch physical pager buzzers for guest text paging?

Spend real time on the quote. Show them how to look at the list, the tables that are on checks, and the tables that just sat, and turn that into a range they can say out loud with confidence. Teach them the habit of quoting a little long and delivering a little early. If you use SMS paging, show them the exact moment to send the table-ready text: when the table is bussed and reset, not when the check drops. A premature text trains guests to distrust every future message. Related: How do you text guests the moment their table is ready reliably?

Day four and five: the phone and the hard conversations

The phone is its own skill. A new host should learn a short, natural script for the common calls: current wait, reservation questions, hours, large parties, and the classic request to hold a table for a group that is ten minutes away. Role-play these with a trainer, including the caller who is annoyed. The goal is not a robotic script but a set of answers the host does not have to invent under pressure while three people stand in front of them.

Then move to the in-person hard conversations. The guest who says they have been waiting longer than quoted. The party of five who insists on a booth built for four. The regular who expects to skip the line. Give the host clear rules for what they can decide alone and when to wave over a manager. A new host who knows exactly where their authority ends is far more relaxed and far more consistent than one who is guessing.

What to check at the end of week one

By the end of the first week, a host should be able to run the stand for a full slow shift without help, quote a wait that lands within a few minutes, seat according to the rotation without double-seating a server, and handle a table-ready text and a no-response follow-up on their own. If any of those is shaky, extend the shadowing rather than throwing them into a Saturday. A weak host on a busy night costs you covers and reviews, and it also crushes the confidence of someone who might have been great with two more slow shifts.

Close the week with a short debrief. Ask what confused them, which guest interaction rattled them, and what part of the software they still fumble. Their answers usually reveal a gap in your process, not just in their training. Many restaurants discover during a new host's first week that the seating rotation was never written down, or that nobody agreed on when the table-ready page should go out. Fix that for everyone, not just the new hire. Related: How do you manage a restaurant waitlist during a packed weekend rush?