Reservation, Waitlist & Overflow Management Plan

Purpose & Scope

Provide a repeatable, guest-centered process for handling reservations, waitlists and overflow during busy periods. The goal is to reduce perceived wait, maximize covers safely, and protect service and food quality while minimizing lost revenue and frustrated guests. This procedure applies to hosts, floor supervisors, managers-on-duty, and kitchen leads.

Roles & Responsibilities

• Host/Hostess: Greet guests, manage waitlist, collect accurate contact info, send status updates, seat according to rules.
• FOH Lead / Floor Supervisor: Oversee table flow, approve hold releases, manage incentives and overflow partners, handle complaints.
• Manager on Duty (MOD): Make real-time decisions about staffing add-ons, approve table time limits, coordinate kitchen staffing when needed.
• Kitchen Lead: Communicate throughput constraints, adjust express menu availability if necessary.

Pre-Peak Setup Checklist (30–60 minutes before expected rush)

• Confirm scheduled staffing; bring on pre-assigned add-on staff if forecasted covers exceed threshold.
• Print or display table map with current table sizes and ideal party sizes for each table.
• Set POS to block or accept reservations as policy requires (e.g., stop accepting reservations for peak slots).
• Prepare express menu / two-course options and pre-busser supplies (extra bussing buckets, pitchers, napkins).
• Designate overflow areas (bar seats, patio, partner restaurant) and ensure partner available contact info is handy.
• Confirm host device connectivity for SMS/text updates and charging cables ready.

Waitlist & Reservation Policy (Standard Rules)

Keep policies simple and visible to staff. Examples:

• Reservation types: Timed reservations (guaranteed table at time) vs. call-ahead / walk-ins on a waitlist.
• Hold times: Hold tables for arriving parties using a size-based policy (see table below).
• No-show policy: Consider a reminder text 24 hours and again 1 hour before; mark no-show after 10 minutes past reservation unless confirmed, or after policy threshold.

Real-Time Tactics

1. Greet & Capture: Immediate welcome, honest ETA, collect phone number for SMS updates. Example: “Welcome! We’re about 20 minutes for a table for two — can I get your phone number to text you when your table is ready?”
2. Text Updates: Send automated or manual texts at these triggers: seated, 10 minutes to ready, table ready, and if ETA changes by more than 10 minutes. Update cadence: every 10–15 minutes or on status change.
3. Seat Prioritization Rules: Seat by first-come-first-served within these constraints: avoid double seating a server who is overloaded; do not seat a just-left table until pre-bussing confirmed; reserve certain tables for reservations within X minutes of arrival.
4. Hold & Release: Use hold times table above. If held party not present within hold time, release table to next waiting party and notify the held party immediately.
5. Pre-busser & Turn Prep: Assign a pre-busser to clear priority tables as soon as the meal is visibly winding down (after dessert is served is too late). Buss and reset with mise-en-place to cut reset time by 30–60%.
6. Express Options: Offer an express menu or pre-set two-course option to guests willing to accept a timed table turn (communicate clearly: “Our 45-minute express menu is available if you'd like a quicker experience.”).

Table-Turn Incentives & Gentle Time Limits

• Offer a small incentive (discounted appetizer, comp non-alcoholic beverage coupon, or priority seating on next visit) for parties that accept express seating policies during peaks.
• When necessary, deploy polite, pre-approved time limits for peak seating: advertise when offering express seating — never spring a time limit on guests mid-meal.

Overflow Flows

Pre-arrange overflow partners and clear operational flows:

1. Bar seating: Host offers bar seating (short lead time, full service) and records guest details in the waitlist when bartender can accept more guests.
2. Partner venues: Maintain a rotating list of nearby cafés/bars that will accept overflow. Confirm terms (discounts, referral code, peak-time capacity) and a direct contact number.
3. Take a number and return: Give guests the option to receive a text when table ready and go elsewhere temporarily (clear expectations on how long the wait might be).

Guest Scripts (Short, Friendly)

• Joining the wait: “We’re running about 25 minutes; would you like a text when your table is ready?”
• When the table is ready: “Great news — your table is ready. We’ll hold it for 7 minutes — can I confirm you’re on your way?”
• If running late: “Thanks for letting us know. We’ll keep your spot for an additional 5 minutes.”
• Offering express option: “If you’d like a faster experience, our 45-minute express menu is available — same quality, a shorter table time.”

Metrics to Monitor (Simple, Actionable)

• Average Wait Time (AWT): Time from join waitlist to being seated. Target: <15 minutes for casual, <10 for fast-casual; adjust by concept.
• Turn Time by Party Size: Average duration table occupied. Use to schedule shifts and staffing.
• No-show / Cancellation Rate: Reservation no-shows ÷ total reservations. Target: <10% (use reminders to reduce).
• Contact Capture Rate: % of waiting parties who provided a phone number for updates. Target: >85%.
• Conversion Rate: % of waitlist entries who are ultimately seated (useful to see leakage).

Record metrics daily and review weekly. Simple formulas: AWT = sum(wait times)/#seated; Turn Time = sum(table durations)/#tables turned.

Post-Peak Review Prompts (Quick Debrief)

1. Was average wait within target? If not, why?
2. Were bottlenecks FOH (seating/reset) or kitchen (ticket backlog)?
3. How many parties left due to excessive wait? Capture reasons if possible.
4. Did incentive offers change behavior? Track uptake.
5. Which tables repeatedly caused delays? Consider re-mapping or redistributing server sections.
6. Create 1–3 action items for next similar peak and assign owners.

Quick Start Tips

• Run this procedure in a single busy service as a pilot and record the metrics above.
• Start with conservative hold times; shorten only after team confidence builds.
• Train the host team on the scripts until responses feel natural and consistent.
• Keep guest language positive and options-focused — guests respond better to clear choices than to pressure.

Appendix — Sample Text Templates

• Reservation reminder (24 hr): “Reminder: Your reservation at [Restaurant] for [Date] at [Time] is confirmed. Reply YES to confirm or CALL us at [Phone].”
• Table ready: “Hi [Name], your table for [#] is ready. Please come to the host stand within [HoldTime] minutes. Reply ARRIVING if you’re on your way.”
• Running late update: “Thanks for the update — we’ll hold your table for an additional [X] minutes. See you soon!”

Notes on Customization

Adapt hold times, incentive types, and targets to your concept, average check, and kitchen capacity. Preserve consistent guest messaging across staff. Test variants (different incentives, express menu prices, SMS cadence) over multiple peaks and compare the conversion and AWT impacts.