Waitlist & Reservation Flow Map (operational workflow)

Purpose

This flow map turns the guest journey—reservation or arrival through seating—into repeatable host behavior. It clarifies hold times, notification rules, no‑show handling, overflow policies, and the KPIs you should collect to tune performance. Use this as an operational playbook the host team can practice and the manager can measure.

High‑level workflow (textual flow diagram)

1. Reservation created (phone or online) -> store party size, contact method, requested time, special notes (allergens, celebrations).
2. Reservation confirmation rules -> send confirmation (SMS/email/phone) at booking and again 24–48 hours before, per policy.
3. Pre‑service check -> reconcile expected covers vs. staffing and open/close reservation slots if capacity shifts.
4. Arrival: Guest checks in -> host verifies name/party size and estimated wait -> send wait time estimate and place on waitlist if table not ready.
5. Waitlist management -> maintain ordered list by arrival timestamp; update wait time estimate as needed; contact guest per notification rules when table becomes ready.
6. Ready notification -> attempt to contact guest using preferred method; follow hold rules (how long to wait after contact before moving to next party).
7. No‑show or late arrival -> mark per policy after grace period; free the table or reassign; optionally apply no‑show fee or note for future booking behavior.
8. Seating -> record time seated for table turn analytics; mark table status (occupied, dirty, cleaning, ready).
9. Overflow handling -> when reservations exceed capacity or waitlist grows beyond threshold, apply overflow actions (bar seating, call‑ahead offers, temporary online blackout, takeout/catering offers).

Key decision points and operational rules

• Reservation window: how far in advance you accept bookings; blockouts for private events.
• Confirmation cadence: automatic confirmation at booking and reminder X hours before service (typical 24–48 hours).
• Hold time (on arrival): how long host waits after notifying a party that their table is ready (typical 5–10 minutes for casual, 2–5 for fast service).
• No‑show rule: mark no‑show after hold time + grace period; decide whether to charge or to restrict future bookings.
• Overbooking policy: allowable overbook percentage by service level—see tuning guidance below.
• Split seating and consolidation: rules for sharing tables and combining parties during peak.

Host scripts & notification templates

Keep scripts short, friendly, and consistent. Practice these verbatim until natural.

• Phone reservation confirmation: “Thanks for calling [Name of Restaurant]. We have you down for a party of [size] on [date/time]. May I have the best number or email to send your confirmation?”
• On‑arrival greeting: “Welcome back to [Name]. Do you have a reservation? Great — name, please. Terrific — your table is being prepared; your wait is approximately [X] minutes. Would you like a text when your table is ready?”
• Ready text template: “[Restaurant] — Your table for [name/party size] is ready. Please check in at the host stand within [hold minutes]. Reply YES to confirm.”
• No‑response escalation: retry 1–2 times at 2–3 minute intervals; after holder time expires, move to next party and log as late/no‑show if applicable.

No‑show & cancellation handling

• Define a clear grace period (e.g., 10 minutes for casual, 15 for full service) and capture it in the reservation record.
• Document repeat offenders (e.g., >2 no‑shows in 90 days) and apply prepayment or card‑on‑file rules where appropriate.
• When a party is marked no‑show, free the table immediately and update the waitlist; note the event for later analysis (timestamp, party size, contact method).

Overflow policies (practical examples)

• Bar/standing seating: enable up to X% of covers on the bar during peak.
• Call‑ahead seating: maintain a short list for near‑term openings (useful for high‑volume casual concepts).
• Online blackout: close online bookings 30–60 minutes before peak if capacity maxes to protect walk‑ins.
• Offer to move to waitlist and provide exact wait estimates to convert frustrated guests into seated covers.

Recommended KPIs, formulas, and practical targets

• Average Wait Time: mean minutes from check‑in to seated. Target: under 10 minutes for casual, under 15 for full service.
• Wait Time Distribution: percent of parties seated within 5/10/20 minutes. Useful for spotting long‑tail problems.
• No‑Show Rate: no‑shows / total reservations. Target: < 5% typical; >8% signals need to confirm or require cards.
• Table Turn Time: minutes from seated to table cleared and ready. Monitor by table type/party size.
• Covers per Available Seat Hour (CAPH): total covers / (seats * service hours). Use this to compare utilization across shifts.
• Reservation Utilization: reserved covers / total covers. High utilization is good but watch for overbook stress on staff and quality.

Tuning guidance by covers volume

• Lower volume nights (small shops): keep hold times generous, minimize overbooking, focus on friendly confirmations and converting walk‑ins.
• Medium volume (steady flow): implement 24‑hour confirmation reminder and modest overbooking (5–10%) based on historical no‑show rates.
• High volume (busy nights): tighten hold times, use call‑ahead/bar seating, enforce card‑on‑file for large parties, and consider dynamic overbooking (higher in low‑risk slots, lower in high‑error slots).

Operational checklist (quick start)

1. Record contact method and preferred language at booking.
2. Set confirmation rules and automate reminders where possible.
3. Train hosts on scripts and hold/no‑show rules; run roleplay shifts.
4. Define and display table statuses at the host station (ready, cleaning, occupied, reserved).
5. Collect timestamps for key events: booking, reminder sent, guest arrival, seated, cleared, no‑show.
6. Review KPIs weekly and adjust overbooking, hold times, and staffing rules.

Data to capture for continuous improvement

• Reservation source (phone, website, third‑party).
• Party size and special notes.
• Timestamps: booking, reminder, arrival, seated, cleared, no‑show.
• Contact attempts and responses (SMS/phone confirmations).
• Outcome (seated, no‑show, canceled, walked out).

Next steps & adaptation

Start small: document one consistent host flow, collect the timestamps listed above for two weeks, and measure the core KPIs. Use results to tune hold times and overbooking. This workflow is intentionally adaptable: capture your local rules (service style, average table turn) and make them the default in your reservation system.

Tip: Consider turning this playbook into an interactive checklist or a reservation‑settings form so managers can simulate overbooking scenarios and store local policy choices.