A host can accept extra guests on an existing reservation when the larger party has a suitable physical table allocation for the full meal and turnaround, without displacing another booking or exceeding the restaurant's chosen seating capacity. The guest also needs to agree to any material change in time, seating or terms.
That decision is different from setting a party-size limit for new requests. A booking may have been valid when confirmed, but an edit changes the space it needs. Treat the increase as a new allocation check while keeping the original reservation intact until the guest agrees to a change.
Capture the original promise
Start with the reservation already on the books. Find the guest's name, local date and time, confirmed party size, booking status and contact method. Check the assigned physical table or tables, if your team uses assignments, as well as the expected dining period and the time needed to reset for the next party.
A party is a group of guests; a table is a physical piece of seating. One party might need two tables, and one table might be able to seat a range of party sizes. Count both. A room that can seat more people in total may still lack a suitable table at the requested time.
Read any notes that affect the arrangement. A high chair, wheelchair access, a quieter location or a request to sit together can change which tables are suitable. Ask the guest whether the request still applies to the larger group. Do not assume that adding two chairs to the original table is comfortable or workable.
Also find the terms the guest was given when booking. These might cover a deposit, a cancellation policy or a seating time. If the increase changes a term, do not improvise a new promise at the host stand. Check who can approve it and what the guest needs to accept.
Keep the existing booking identifiable throughout the conversation. If a change cannot be accommodated, the guest should know whether the original reservation for the original number remains available. Avoid creating a second booking as a shortcut unless your procedure clearly prevents both records from being counted as separate parties.
Check the revised allocation
Use the following hypothetical example to practice the decision. The restaurant has a four-seat table and a six-seat table. Each is one physical table; neither has spare capacity beyond its stated seat count. The host plans 90 minutes for a six-person meal plus 15 minutes to reset the table.
A party booked for four at 6:00 p.m. asks to bring six. Its original four-seat table has another party booked at 7:30 p.m. The six-seat table is occupied until 6:30 p.m. and has another reservation from 7:30 to 9:00 p.m. After a reset, it is available from 9:15 to 10:45 p.m.; there is no later booking that conflicts with its reset.
| Option | Physical allocation | Timing check | Decision |
|---|---|---|---|
| Six guests at 6:00 p.m. | Six-seat table | Needed until 7:45 p.m., including reset; occupied until 6:30 and booked again at 7:30 | Do not accept |
| Six guests at 6:00 p.m. | Original four-seat table | Seats only four; another party arrives at 7:30 | Do not accept |
| Six guests at 9:15 p.m. | Six-seat table | Available for the 90-minute meal through 10:45, with reset afterward | Offer if the guest agrees |
The table separates seating capacity from timing. The six-seat table has enough chairs, but it is not free for the requested period. The later option works under these hypothetical inputs; it is not a reason to move the booking without the guest's consent. The original four-person reservation can remain as booked if the guest prefers it.
In service, check the whole interval, not just the arrival time. Look at tables that could be combined, the time needed to rearrange them, and whether the resulting layout leaves practical routes for guests and staff. Check the next reservation at each affected table. A short gap on the screen is not necessarily enough time to finish a meal and prepare for the next party.
Use this acceptance checklist before saying yes:
- Can the revised number be seated at suitable physical tables without exceeding their capacities?
- Are those tables free for the expected meal and reset, including any time needed to combine or separate them?
- Will the change leave the next parties with the tables and times promised to them?
- Do access needs and other relevant requests still work for the larger group?
- Has an authorized person resolved any changed terms, and has the guest agreed to the arrangement?
A restaurant reservation system can support the reservation workflow. When evaluating one, ask how a host edits a confirmed party size, sees affected table assignments and identifies conflicts before saving. Also ask whether staff can record the reason for an override and who can make one.
Offer alternatives without changing the promise
If the requested increase does not fit, give the guest a clear choice rather than a vague assurance that the team will try. A later time may allow everyone to sit together. Before offering it, check the full dining and reset interval just as you would for the original time. Tell the guest the proposed time and wait for an explicit answer.
Split seating is another possibility, but only if the guest agrees and the restaurant has suitable physical tables for both groups. Explain whether the tables would be adjacent or in different parts of the room. Check each table's capacity and subsequent booking separately. Do not describe a split as one table, and do not assume the guest will accept it simply because the total number of seats is sufficient.
A waitlist can be useful when the guest wants the original time but a suitable allocation is not currently available. Ask whether they want to wait for a larger table, and explain what happens to the original reservation while they wait. Record a deadline for the decision if the restaurant needs one. A waitlist is not a confirmed six-person booking; keep that distinction clear in the record and in the guest's message.
The guest may choose to keep the original booking for four instead. Confirm that choice and avoid leaving a note that makes the rest of the team expect six. If the guest declines every option, follow the restaurant's normal process for deciding whether the original booking remains or is canceled. Do not cancel it merely because an increase was requested.
For software comparisons, ask how a waitlist or alternative offer would be recorded, whether the original booking stays visible and how staff distinguish an offer from an accepted change. If bookings arrive through the restaurant's website or, where available, Google, ask whether the same change workflow applies to each channel.
Document the outcome and hand it over
Once the guest decides, update one clear reservation record using the restaurant's approved process. Record the final party size, local date and time, table arrangement, relevant requests and status. Note whether the guest accepted a later time, agreed to split seating or kept the original booking. Include the name or role of the staff member who handled an exception so the next shift knows whom to ask.
Confirm the outcome through the guest's agreed contact method. Be specific: a confirmation for six at a new time should state six guests and that time. If the party is split, describe the arrangement rather than relying on an internal table code the guest may not understand. If the larger party is only waitlisted, say so and restate the status of the original reservation.
Escalate a change involving a deposit or other disclosed term to the person authorized to handle it. That person should check the original terms, determine what needs to change and communicate the outcome before the booking is treated as final. A deposit is not the same as a processing fee or a completed sale. Ask a qualified adviser about contract, legal or tax treatment when needed.
Use the same care for special requests. If the only available table cannot accommodate a relevant access need, do not mark the request as solved. Ask the guest about workable alternatives and involve a manager when the team cannot find one.
For handoffs, ask how your restaurant management software shows edits to the next shift and whether staff can see who made them. If reservation details need to be reflected in a restaurant POS system, ask how that information gets there rather than assuming the systems share every update.
Practice the checklist with a simulated booking before relying on it during a rush. Use fictional guest details and a practice environment that cannot send a guest message, take a payment or dispatch a courier. Walk through an accepted change, a conflict and an unaccepted offer. A live service pilot is separate: assign an owner to review actual changes and use normal guest-consent and communication procedures.
Next step: Take one upcoming shift's table plan and apply the checklist to a hypothetical increase. Then compare the workflow with your requirements when evaluating Fleksa's reservation system, including how staff would flag a conflict and record the guest's decision.
Frequently asked questions
Can a host add guests if the room has empty seats?
Not on that fact alone. The seats need to be at suitable physical tables available for the full meal and reset, without conflicting with other reservations. Check the guest's seating needs and any changed terms too.
Should the original booking be canceled while a larger table is offered?
Keep its status clear and tell the guest what happens to it. An alternative is only an offer until the guest accepts it; follow your restaurant's process if the guest chooses to cancel instead.
What should a host do when a deposit may change?
Check the terms already disclosed and refer the change to the person authorized to handle deposits. Confirm the resulting arrangement with the guest before treating the revised booking as final.
