A restaurant host stand opening checklist verifies the guest route, one live waitlist, the floor’s capacity signal, the owner of exceptions and a staffed fallback before doors open. Run it in ten minutes, test one guest journey and escalate anything that would make the first promise unreliable. The purpose is not to forecast the whole shift; it is to make the first intake accurate, clear and ready for change.
This is a pre-service reset, not a policy for admitting every party or a playbook for a full rush. It gives the first host the information needed to welcome a guest without guessing. For the admission limit after doors open, use the restaurant waitlist capacity limit policy. The restaurant host training checklist covers observed skills, while the Friday-night host playbook coordinates a peak service after the room is already moving.
What must be ready before the host stand opens?
Open only when the guest-facing route and the team’s operating picture agree. The physical counter can look ready while a dead tablet, stale list or unknown floor lead makes the first promise unreliable.
| Opening check | Decide before the first guest | Quick proof |
|---|---|---|
| Arrival route | Where guests enter, read instructions or ask for help | Walk from the door to the stand without relying on staff memory |
| Floor signal | Who confirms what is actually available now | Name the lead and the next time they will refresh the status |
| One live list | Which queue is current and who may edit it | Remove stale drafts, paper notes or duplicate views |
| Guest path | QR code, link or assisted entry that guests can use | Complete one staff-only entry and remove it afterward |
| Devices and materials | Charged device, network, charger, menus and visible instructions | Open the same screen and materials the host will use |
| Guest updates | The approved channel and the person who handles an exception | Confirm the handoff if an update cannot be sent or answered |
| Accessible service | A clear route and an alternative when self-service does not work | Ask what assistance is available without asking a guest to explain a condition |
The test is deliberately small. A team does not need a perfect prediction of every table turn to know who can make the next capacity decision. It needs to avoid presenting an unconfirmed option as a promise.
Run a ten-minute opening sequence
Use the same order every service so the host can recognize what is missing quickly.
- Clear the guest route and put the current instructions where a guest can see them.
- Check the tablet, power, network and the public QR code or link.
- Confirm the floor lead, the section status and the next capacity review point.
- Open the one approved waitlist and remove any second list from the counter.
- Read the current wait language aloud with the person covering the stand.
- Confirm the channel for table-ready updates and the person who owns an exception.
- State the assisted alternative for a guest who cannot or does not want to use self-service.
The opening host should finish able to answer four questions: What can I offer now? What can I say now? What must I check? Who decides when the answer changes? If any answer is unclear, the stand is not ready yet.
Once doors open, use the restaurant waitlist check-in process to record a confirmed arrival without creating a second entry or guessing that a table is ready.
Test the guest path, not the staff shortcut
Employees often reach the list through a saved tab, a staff device or a familiar conversation. A guest does not. Test the exact sign, QR code or spoken instruction the guest receives, then make sure the next action is understandable without a private explanation.
The W3C Web Content Accessibility Guidelines 2.2 are a useful reference for clear digital instructions. In the United States, the Department of Justice’s ADA Title III overview is an official starting point to review alongside the local rules and physical conditions that apply to the restaurant. This checklist is operational guidance, not legal advice.
Do not treat an accessible route as a separate task that starts only after a guest asks. At opening, confirm the route is clear, the sign makes sense and a staffed alternative exists. The accessible restaurant waitlist guide goes deeper on keeping entry and updates usable during service.
Sort every opening issue into ready, wait or escalate
The host stand does not need to solve every issue itself. It needs a visible boundary so a small doubt does not get buried in a guest conversation.
| State | Example | Host action |
|---|---|---|
| Ready | The floor lead confirms the next capacity review and the guest path works | Welcome the party and use the approved wait language |
| Wait | A section may open soon, but the floor has not released it | Explain the current range and say when the team will update the guest |
| Escalate | A capacity change, accessible seating need or system issue changes the next promise | Give the facts to the named lead before offering an outcome |
This keeps the first interaction calm. A guest can hear a clear next step even when the final seating decision is not available yet.
Keep one list and a staffed fallback
Opening is the best moment to stop duplicate entry points from becoming duplicate queues. If guests can arrive at the counter, through a QR code, on the phone or through another approved channel, the team should know where each path converges. Use the multiple waitlist entry points guide to document that flow before a busy service.
The fallback also needs an owner. A charged device alone is not a fallback if nobody knows who will take an assisted entry, communicate a delay or put the information back into the live list. The waitlist shift handoff checklist can help the next host inherit that responsibility without copying private guest details.
Make the digital workflow support the opening routine
Once the opening routine is reliable, use a restaurant host stand staffing plan to assign who covers the door, the floor signal and guest updates through each service window. Opening confirms the stand is ready now; the staffing plan keeps those responsibilities covered after the room starts changing.
StoveOps lets guests join a live waitlist from their phone through a QR code or link, then receive a table-ready update by SMS, WhatsApp or email. It is designed to work beside the POS or checkout stack the restaurant already uses. A waitlist app for the iPad host stand and guest messaging software can support the live workflow, but they do not replace the named floor signal and staffed fallback in this checklist.
For a broader operational overview, review the restaurant waitlist software page as the team maps those guest paths to its opening routine.
Before the first party arrives, run the routine once with the people who will actually operate it. A clear start makes every later update easier to trust.