The best tables to combine are usually adjacent tables that seat a larger party while leaving enough separate tables for the smaller parties you expect at the same time. Set only combinations that can physically work, then decide which ones should be offered first. A table cannot count toward two overlapping reservations, even if the reservations use different combinations.
Start with the floor, not the number of seats alone. A workable plan considers walkways, chair clearance, service access and the tables left for other guests. The goal is to accept a useful mix of party sizes without making hosts untangle conflicting bookings during service.
Map physical tables and permitted combinations
Label each physical table on the floor plan. Record its normal capacity, which neighboring tables it can join, and the actual capacity of each joined layout. Joined capacity may be lower than the sum of individual seats if a chair must be removed at the join or a walkway needs to stay clear.
Here is a hypothetical dining room with four two-tops, T1 through T4, and two four-tops, F1 and F2. All six physical tables are available at the start of the example. Assume the layouts below have enough clearance and that each listed capacity is the maximum number of guests for that layout.
| Layout | Maximum guests | Physical tables used | Tables still separate |
|---|---|---|---|
| T1 + T2 | 4 | Both two-tops | T3, T4, F1, F2 |
| F1 + T1 | 6 | One four-top and one two-top | T2, T3, T4, F2 |
| F1 + F2 | 8 | Both four-tops | T1, T2, T3, T4 |
Read each row as an alternative layout, not as a set of combinations that can all be used at once. For example, F1 + T1 and F1 + F2 both use F1, so they cannot serve overlapping parties. When F1 + T1 is occupied, neither F1 nor T1 is available separately. Its six seats are committed to one guest party, even if that party has fewer than six people.
Keep the list of permitted combinations short enough for the host team to understand. In this example, T1 can join T2 or F1, but not both at the same time. Do not assume T3 can join F2 just because their capacities add up to six; measure that layout and add it only if it works. Note any furniture that must move and who will move it.
Ask a reservation software vendor whether you can name individual physical tables, specify permitted combinations and set the capacity of each layout. Also ask how the system prevents the same table from being assigned twice. If a layout is not supported as configured, decide whether hosts can manage it reliably without creating false availability online.
Trace overlapping parties before setting rules
Use the same hypothetical floor plan to walk through a conflict. Suppose a party of six is booked from 6:00 to 7:30 p.m. Two parties of two then request the overlapping period from 6:15 to 7:15 p.m. These times are assumed occupancy windows for this exercise; they are not a prediction of how long any real party will stay.
Assign the six guests to F1 + T1. F1 and T1 are now unavailable for the entire assumed window. The first party of two can use T2, and the second can use T3. T4 and F2 remain separate. The plan seats all three guest parties using four physical tables: F1, T1, T2 and T3.
Now change the assumption: T2 is already occupied by another reservation that overlaps the same period. After placing the six at F1 + T1, T3 and T4 can still take the two new parties of two. If T2 and T3 are both occupied instead, only T4 remains as a separate two-top. The second new party would need F2, another suitable table outside this example, or a different time. Seating two people at F2 is possible within its four-person capacity, but it uses a four-top that could otherwise serve a larger party.
That is the decision worth seeing in a booking screen: not just whether the six fit, but what remains after they are placed. A host should be able to identify physical table conflicts across the whole overlap, including a later booking that begins before the current party's window ends.
For a practice check, use a simulation or test environment with fictitious bookings. Confirm beforehand that it will not send guest messages, take payments or dispatch a courier. Trace the table assignments on paper if the software cannot isolate practice activity. A live service pilot is different: it uses real reservations, so agree on staff oversight and guest communication before starting one.
Choose precedence that protects the right tables
Combination precedence is the order in which a host or system considers suitable layouts. A simple rule such as “use the largest available configuration first” may fit a six-person party at F1 + F2, assuming the eight-seat layout is acceptable for six. That leaves all four two-tops separate, but commits both four-tops to one party.
Under the original assumptions, F1 + T1 is the more balanced first choice: it fits six exactly, leaves three separate two-tops for small parties and preserves F2 for a party of up to four. F1 + F2 preserves one more two-top, but leaves no separate four-top. Neither rule is universally best. If the next requests are mostly twos, protecting two-tops may matter more. If a four-person booking is likely or already pending, preserving F2 may matter more.
Write the preference in terms the host team can apply:
- Offer only a layout whose stated maximum capacity fits the party.
- Check every physical table in the layout for the full reservation window.
- Among workable layouts, prefer the one that leaves the tables needed for known overlapping bookings.
- When future demand is uncertain, use a house preference based on the party mix you expect, and let an authorized host revisit it.
Avoid holding the largest combination indefinitely just in case a large party calls. It can make several physical tables unavailable to smaller bookings. A practical alternative is to decide how long to protect a layout and who may release it, based on the restaurant's booking patterns. Review the rule after busy services and change it if hosts repeatedly have to work around it.
When comparing tools, ask whether combinations can have a preferred order, whether staff can see the remaining individual tables and whether an online booking can use a layout reserved for a different party size. If those controls do not fit your operation, ask what manual steps are needed and who will own them.
Control host overrides and check the next booking
Decide before service who may split or reassign a combination. For example, a lead host or manager might approve changes, while another host flags the need. Give the team one current floor plan and a consistent way to record the change so a colleague does not continue treating the old layout as available.
Before splitting F1 + T1, check the reservation assigned to it. If the party of six still needs those tables, splitting the layout would leave it without a valid six-person assignment. First find another permitted layout that fits the party and is free for its whole window. If none is available, keep the combination intact or discuss alternatives with the guest rather than silently releasing a table.
Once the current reservation has a valid assignment, check the next booking on each physical table. A table that looks free now may be committed 20 minutes later. Confirm that every affected party still has a layout within capacity and that no physical table appears in two overlapping assignments. Record who made the change and tell the service team which furniture needs moving.
Ask vendors what staff permissions, assignment history and conflict warnings are available. Also ask how a change made by a host affects availability shown to guests, including Google bookings where available. Do not rely on a warning alone: the operating rule should make someone responsible for checking the next reservation.
Take your labeled floor plan and three overlapping sample parties to a restaurant reservation system discussion. Ask the vendor to walk through the permitted layouts, availability and override steps. Compare that workflow with your requirements alongside your wider restaurant management software needs. For a separate look at missed bookings, see the guide to reservation no-show costs.
Frequently asked questions
Should every adjacent table be combinable?
No. Add a combination only after checking chair clearance, access and its actual guest capacity. Each extra option should be understandable and manageable by the host team.
Can a table be part of more than one combination?
Yes, as an alternative layout. In the example, T1 can join T2 or F1, but it cannot be assigned to both combinations during overlapping reservation windows.
What should a host check before splitting a combination?
Check that the current party still has a suitable assignment, then check the next overlapping booking on every affected physical table. Record the change and tell the team responsible for resetting the floor.
