Use this model to make table requests clear before the rush. It is a recommended operating policy for the restaurant to adapt and approve, not a universal rule for how every dining room must seat guests.

The key question is: “Would you like the first suitable table, with a booth if possible, or would you rather wait only for a booth?” Those choices should not look identical in the waitlist. An accessibility-related need follows a separate approved service process; it is not an optional preference.

Start with the active party, not the preferred table

Find the party’s existing record before writing anything new. Confirm the current party size and whether the guest is already checked in. The waitlist check-in process explains how to update an active visit without restarting it at the host stand.

Record the choice precisely: “Booth preferred; other suitable tables accepted” or “Booth only; longer wait explained.” Include the original entry time, the current estimate if one is supported, the person reviewing the request, and the next update time. Keep the note in the authorized waitlist, not in a personal phone or group chat.

Preserving entry time does not guarantee that every party sits in arrival order. Table size, readiness, the options a party accepts, and the restaurant’s documented reservation and seating rules still matter. Explain that distinction before a guest decides to wait for one type of table.

Copyable table-request policy for the host stand

Have the manager adapt this template to the restaurant’s real seating, reservation, and accessibility processes before staff use it with guests.

Our table-request policy

  • We record your preference and ask whether you will accept another suitable table or want to wait only for the requested type. A preference does not reserve a specific table or create priority.
  • We retain your original waitlist entry time. If you choose to wait for one type, other eligible parties may sit first at tables you decline; your total wait may increase.
  • We update the estimate when the floor can support one. If we cannot give a reliable estimate, we say so and discuss the available alternatives.
  • Your host names the person reviewing the request and the next update time. That time is for an update, not a promise that a table will be ready.
  • A request outside this policy goes to the manager or floor lead. They record the decision and its operational reason. Accessibility needs follow our approved service process, without asking for unnecessary personal details.

Example: keeping entry time while another party sits first

This is a hypothetical example, not a report of a customer’s service. Both parties have two guests; Table 4 is a standard table and Table 6 is a booth.

  1. 7:00: Party A joins and chooses to wait only for a booth. The host records that choice and explains the possible additional wait.
  2. 7:05: Party B joins and will accept any suitable table.
  3. 7:10: The floor releases Table 4; Table 6 is still occupied. Party A confirms that it wants to keep waiting, so Party B can take Table 4 under the seating policy. Party A’s entry time remains 7:00.
  4. 7:20: At the promised update time, the booth is still occupied. The host explains the delay and reviews the estimate with the floor rather than repeating the original range as a guarantee.
  5. 7:25: The floor confirms that Table 6 is clean and ready. The host offers it to Party A under the documented rules for eligible parties.

Party A kept its original entry time and still waited longer by choosing a narrower set of tables. If it changes its mind, update the choice on the same record and reassess the next suitable option; do not create a fresh entry or promise immediate seating.

Give the floor a decision it can actually make

The host should not decide that a requested table is ready just because it looks empty. Ask for a live floor signal: is the table cleared, compatible with the party, available under the current section plan, and not committed elsewhere? The seating rotation guide separates a usable table from a merely vacant-looking one.

Use a small decision set when the answer comes back:

  1. The requested type is available. Confirm the table and move the party through the normal seating step.
  2. A different suitable table is available. Offer it and confirm the guest’s choice. Under this model, declining it preserves the entry time but may mean waiting longer while another eligible party takes that table.
  3. The preference is still unavailable. Keep the party active, review the estimate, and provide the next update time without promising a table then.
  4. The request needs an exception decision. Name the manager or floor lead who will decide it and record when they will respond.

A host can be warm and direct: “I have noted that you want to wait for a booth. Your original entry time stays recorded, but other groups may take standard tables sooner. I will check with the floor lead and update you at 7:20, even if the booth is not ready.”

Keep preference, capacity, and priority separate

Table requests often get confused with three different decisions. Keeping them separate makes the policy easier to teach and fairer to run.

Decision Question it answers What it must not become
Table preference Which suitable tables will this party accept? A hidden reservation or unexplained longer wait
Capacity limit Can the restaurant make another credible wait commitment? A reason to accept a party without a review point
Seating priority Which active party can be seated with a confirmed option? A personal judgment made outside the live list
Bar option Would the party voluntarily choose a different experience? A forced substitute for a table request

Use the waitlist capacity limit policy before accepting a commitment the room cannot support. If a bar seat is a genuine option, the bar-seat versus table guide helps the team present it as a choice, not an unannounced downgrade.

Offer a staffed route without collecting more than needed

Some requests require more care than a standard booth or patio preference. A guest may need an accessible route, a place with room for a mobility device, or a quieter way to receive an update. The host’s job is to make the next route clear, not to ask for a diagnosis or create a shadow record.

The accessible restaurant waitlist guide outlines how to keep an assisted route connected to the same live operation. W3C WCAG 2.2 is a practical reference for understandable digital instructions, while the NIST Privacy Framework is useful when deciding what operational information actually needs to be retained. Neither source prescribes a restaurant seating policy or replaces its approved accessibility process.

Record only what changes the next service decision. Keep that note in the authorized waitlist, visible to the person who will act on it. Do not copy names, contact details, or personal explanations into a notebook, personal device, or informal staff chat.

Review the request policy after the rush

At close, inspect a few table requests rather than relying on memory. Did hosts retain the entry time and apply the documented eligibility rules? Did guests get a real review point? Did a requested table get promised before the floor confirmed it? Did the team offer a clear alternative without pressuring the guest?

Those answers reveal whether the problem is policy, floor communication, or table availability. A short reason code such as “patio closed,” “booth occupied,” or “compatible table pending reset” can make the next shift’s review concrete without turning a guest’s explanation into permanent data.

If the team needs one shared record for requests, updates, and table-ready handoffs, StoveOps provides a restaurant-owned live waitlist. Guests can join by QR code or link and receive a table-ready update through configured SMS, WhatsApp, or email. Review the workflow on the restaurant waitlist software page and test it against the policy before service.