When a reservation is canceled, put one person in charge of the released table and record its status in the place every host checks. Then choose either a timed offer to an eligible waitlist party or a first-come opening. Before confirming anyone, check that the table is still available for the entire reservation period.
The fair choice depends on the time left, the parties waiting, and whether your team can actually hold inventory while an offer is outstanding. A cancellation creates an opening after a booking; it is different from deliberately holding tables back before demand arrives.
Give one person control of the released table
Start by verifying that the original reservation is canceled, rather than merely changed or moved. Record the cancellation time, service date, original reservation time, party size, and the physical table or table combination released. Note any seating limits and the time by which the table must be available for its next booking.
A physical table and a guest party are not the same unit. A table for four can accommodate one party of four, two, or perhaps three, depending on your seating rules. It does not automatically accommodate two separate parties of two. If the opening depends on joining tables, check that each physical table is free for the full seating period.
Assign a host or shift lead as the owner of that opening. Other employees can take inquiries, but they should send claims to the owner until the record shows a confirmed booking or the opening returns to general availability. If the owner goes on break, explicitly hand the opening to someone else.
Use simple statuses that fit your tools: available, offered and held, confirmed, or released again. Record who changed the status and when. A shared record matters more than a particular label. A note on one host's pad is not enough if another host is also answering the phone.
If online bookings, phone calls, and the front desk all draw from the same dining room, ask how each channel updates availability. A restaurant reservation system should be evaluated against the way your staff actually assigns tables, including combined tables and changes during service. Do not assume that a note or a message to a guest creates a hold in every channel.
Choose a fair offer for the time available
A waitlist offer gives a particular party a chance to accept before someone else takes the opening. It is useful when you have a documented order and enough time to contact people in sequence. Define eligibility before service: party size, requested time window, seating needs, and how long the party is willing to wait. Among eligible parties, use a consistent rule, such as the time they joined the list.
First-come availability can be simpler when service is close and there is not enough time for a sequence of offers. Make the opening available through the channels you can manage, and give it to the first eligible party whose booking the owner can confirm. The announcement should not imply that every person who responds has a reservation.
Both approaches have tradeoffs. A timed waitlist offer respects the queue but can leave a table empty while a guest decides. First-come can fill an urgent opening quickly, but guests who have waited longest may lose out. Tell guests the rule when they join the list, including whether a missed response moves the offer to the next eligible party.
A hypothetical decision worksheet
Assume one physical table seats up to four guests and is free from 7:00 to 8:30 p.m. The next reservation needs it at 8:30, so a new party must fit within that window. Two eligible parties are waiting: party A has three guests and joined first; party B has four and joined second. The table cannot seat both parties. The worksheet shows how the decision changes with the time remaining, not two offers made for the same opening.
| Cancellation time | Operating choice | Action and limit |
|---|---|---|
| 5:30 p.m. | Timed waitlist offer | Offer party A the table until 5:40. If A declines or the offer expires, offer it to B with a new deadline. |
| 6:55 p.m. | First-come opening | Offer the opening to the first eligible party the owner can confirm. Do not hold it for multiple replies. |
At 5:30, there is time for a ten-minute response window and a fallback. At 6:55, even one ten-minute hold runs past the 7:00 seating time, so this restaurant's assumed priority is an immediate, workable seating. A different restaurant may choose a shorter waitlist window or a later seating time. The important point is to decide that rule in advance rather than improvise after guests respond.
For either route, check the party can use the actual opening. If a guest wants to stay beyond 8:30, the host must find another valid arrangement or decline that slot. Do not promise the table on the assumption that the next reservation can be moved.
Set an expiry and prevent competing claims
For a timed offer, tell the guest the date, seating time, party-size limit, response deadline, and how to accept. Say that the table is reserved for them only until the stated deadline and that the offer expires if they do not respond. Use the restaurant's local time for the deadline and make the wording clear enough that a guest does not mistake an offer for a confirmed reservation.
Before sending the offer, mark the table as held in the shared record and, where possible, prevent other booking channels from selling the same capacity. Ask your software provider whether a temporary hold blocks website, phone, and any available Google booking paths; how expiry works; and what happens if two staff members act at once. If the system cannot block the opening across channels, use a single owner to control it and recheck every channel before confirming. A manual procedure reduces confusion but is not the same as an automatic lock.
When the deadline passes without acceptance, the owner removes the hold, records the expiry, and either makes the next eligible offer or returns the table to general availability. Do not leave an old offer active while telling another guest they have the table. If a late response arrives, check the current status and explain that the original deadline has passed before offering any remaining option.
For first-come openings, avoid sending simultaneous messages that each sound like an exclusive hold. If several guests can respond at once, make clear that availability is subject to confirmation. The owner should process responses in a consistent order and confirm only after checking the current table record.
Ask what the software does when an offer is accepted at nearly the same moment as another booking. Can it stop both from being confirmed, or must staff resolve the conflict? Also ask whether staff can see an audit trail of changes and whether online availability updates immediately. If the answer depends on setup, include that setup in your operating procedure.
Confirm, reconcile, and brief the floor
An acceptance is not the end of the process. The owner should check the physical table and full time window one more time, enter the accepted party as a confirmed reservation, and remove any temporary hold or outstanding offer. Record the guest's name, party size, time, contact details, and relevant seating request according to your normal process.
Then reconcile the views staff rely on. Does the reservation appear on the host stand and floor plan? Has the original cancellation disappeared from active covers? Does the table remain available for its next reservation? If another channel still shows the opening, correct the conflict before telling additional guests it is available.
Notify the floor lead of the new party and any timing constraint. A short handoff could read: “Table 12, party of three at 7:00, next booking at 8:30.” Include only the guest information staff need to serve the reservation. If a conflict is discovered after confirmation, assign one person to contact the affected guests and arrange an alternative; do not quietly move a booking and hope no one notices.
Practice the workflow before a busy shift. In a simulation, use fictional guests and a test record or another method that cannot create a real payment, guest message, or courier dispatch. Have two staff members try to claim the same opening and check the resulting statuses. Separately, if you run a live service pilot, designate an owner, use the normal guest communication process, and monitor actual bookings closely. A simulation checks the procedure; a live pilot checks how it works during service.
Review canceled openings periodically: how many were offered, expired, confirmed, or left unused? Look for missed handoffs and unclear deadlines before changing the rule. Your broader restaurant management software workflow may also affect who sees the floor plan and who can make changes. For the separate question of what missed bookings cost, see the guide to measuring reservation no-show costs.
Next step: Map one cancellation from release through confirmation, including every channel and staff handoff. Then compare those requirements with Fleksa's reservations workflow, asking specifically how holds, expiry, and competing claims would work in your setup.
Frequently asked questions
Should a canceled table always go to the first person on the waitlist?
Not necessarily. Start with the first eligible party under your published rule. The party must fit the physical table, available time, and seating requirements. Close to service, a clearly communicated first-come rule may be more practical.
How long should a restaurant hold an offered table?
Choose a deadline that leaves enough time to seat the party or contact the next guest. State the exact deadline in local time, record the hold, and release it promptly if the guest does not respond.
What if two guests accept the same opening?
Do not confirm both. Have the designated owner check the current record and apply the stated offer rule. If both have already received confirmations, contact the affected guests promptly and work out an alternative.
