Key takeaways
- Start with the room as it is today, measured and photographed, not an old seating chart.
- Record each table's real capacity, features and accessibility, and define every combination explicitly.
- Balance server sections by covers, not table count, and keep a version for each staffing level.
- Update the map whenever the room changes, including patios, pickup areas and private rooms.
Why the map decides what gets booked
Your reservation system books what its floor plan says exists. If the map shows a six-top that is really two fours that do not quite meet, the system will sell it to a party of six who then wait while staff shuffle chairs. If a booth that seats four comfortably is marked as a six, guests are squeezed. The digital room has to match the real one.
Hosts depend on it. Their job includes greeting and seating guests and managing reservations and waiting lists[1], usually from the floor view on a tablet at the stand. Many work part-time: employees in food services and drinking places averaged 25.1 hours a week in September 2026[2]. A host on their second shift of the week needs a map that is obvious at a glance.
Capture the real room first
Walk the room at set-up
With the manager and a senior server, look at the room as it is set for a normal dinner, not as it was designed.
Number every table the way staff say it
If the team calls it “the round by the window”, give it a number and a short label that matches.
Record real capacity
Minimum and maximum covers for each table, based on comfort, not the most chairs that fit.
Photograph and sketch
Take photos from the host stand and draw a rough plan with walkways, doors, the bar and the pass. Use it to place tables in the system.
Mark fixed features
Pillars, steps, heaters, speakers, drafts from the door: anything that changes which guests should sit where.
What to record for each table
| Attribute | Why it matters | Example entry |
|---|---|---|
| Minimum and maximum covers | Stops the system selling a four-top to a single diner on a busy night | Table 12: min 2, max 4 |
| Table type | Guests request booths, high-tops or counters | Booth, high-top, banquette, counter |
| Location | Window, patio, quiet corner and bar requests | Window; near kitchen door |
| Accessibility | Step-free route and space for a wheelchair | Accessible; step-free from entrance |
| Bookable online | Some tables are best held for walk-ins or regulars | Online: no; held for walk-ins |
| Section | Who serves it on each staffing pattern | Section B (four servers); Section A (three servers) |
Keep labels short and consistent. If one host types “booth” and another “banquette”, filters and guest requests break. Agree a list of features and use only those words.
Resist the urge to record everything. Every attribute you add is one more thing to keep accurate. Start with capacity, type, location, accessibility, online availability and section, and add others only when hosts keep asking for them.
Combinable tops
Combinations are where most floor plans go wrong. A system cannot guess that tables 21 and 22 push together but 22 and 23 do not because of a pillar. Define every combination you are willing to use, explicitly.
- List each combination as a group, such as 21+22, with the party size it seats.
- Note combinations that need extra time to set, so the system can leave a gap before the booking.
- Mark combinations that block a walkway or a server station, and avoid them on busy nights.
- Set which combinations can be booked online and which need a host or manager.
- Check what happens when one table in a combination is already booked; the system should not offer the combination.
Fewer, well-defined combinations work better than many possible ones. Pick the three or four your team actually uses for sixes, eights and tens.
Server sections
Sections tell the system, and the host, who serves each table. Balance them by expected covers, not by table count: a section with three fours and a six is busier than one with six twos. Build a section layout for each staffing level you run, such as three, four and five servers, so the host can switch with one tap when someone calls out.
- Keep each section in one physical area so servers are not crossing the room.
- Give the strongest server the section with the most large tables or the busiest booths.
- Rotate seating across sections so no server gets three new tables at once.
- Mark the bar and counter as their own sections if bartenders serve food there.
Accessible seating
Restaurants and bars are among the categories of public accommodations covered by Title III of the Americans with Disabilities Act[3]. In practice, your map should show which tables have a step-free route from the entrance and space for a wheelchair, so a host can offer them on the phone and online without guessing.
Spread accessible seating across the room rather than putting it all in one corner, if your layout allows, so guests have a real choice of location. Make sure the system does not hide accessible tables from online booking by default, and train hosts to ask about access needs when they take a booking.
Rooms that changed for takeout
Many dining rooms are not the shape they were a few years ago. In National Restaurant Association research, 30% of full-service and 40% of limited-service operators have changed interior spaces or parking lots to accommodate off-premises orders[4]. Pickup shelves, takeout counters and delivery driver waiting areas often replaced tables.
Source: National Restaurant Association, 2025[4]
Show the data
| Item | Value |
|---|---|
| Full-service | 30% |
| Limited-service | 40% |
If your room changed, your map should too. Remove tables that no longer exist, adjust capacities near a busy pickup area, and consider marking tables close to the pickup door as less desirable for long dinners.
Patios, private rooms and the bar
- Patio: map it as its own area with a switch to close it in bad weather, and decide what happens to patio bookings when it rains.
- Private room: map it as a bookable space with its own rules, minimum party size and lead time, often handled by a manager.
- Bar and counter: decide whether seats are bookable, held for walk-ins, or split.
- Seasonal layouts: save a winter and a summer layout rather than editing tables every spring.
Map for the requests guests actually make
Look at a month of booking notes before you finish the map. Guests ask for the same few things again and again: a booth, a quiet table, a window, somewhere away from the door in winter, room for a stroller or a high chair. If those requests are tagged on tables, the host can honor them in seconds instead of scanning the room.
Be honest in what you offer online. If only two tables are truly quiet, do not let the booking page promise a quiet table to everyone. Offer the request as a preference the team will try to meet, and save guaranteed tables for a host to confirm.
Keep the map current
- Assign one manager to own the floor plan and approve every change.
- Update it the same day a table is added, removed, moved or replaced.
- Check capacities after any refurbishment; new chairs or banquettes change real comfort.
- Review combinations each season, especially when the patio opens or closes.
- Ask hosts monthly which tables they keep moving guests away from, and find out why.
Test the map before you trust it
- Book every table and combination once in a test account and check the host can seat it as booked.
- Book a party of each size online and see which tables the system offers.
- Switch between section layouts and check every table has a server.
- Close the patio in the system and confirm patio bookings are flagged for moving.
- Ask a new host to find five tables by name on the tablet within a minute.
Example: a fictional 140-seat restaurant maps its room and tests it. The system keeps offering an eight-top made of three tables that block the kitchen door when combined. The manager removes that combination, adds a different one by the windows, and marks two tables near the pickup shelf as walk-in only. Turn times and pacing depend on an accurate map, so continue with table turn times by party size and daypart and how to run a restaurant waitlist.
Frequently asked questions
How do I set up table combinations in a reservation system?
Define each combination you are willing to use as an explicit group with its party size, mark any that need extra set-up time, and decide whether each can be booked online.
Should every table be bookable online?
Not necessarily. Many restaurants hold some tables, bar seats or counter seats for walk-ins and regulars. Mark them clearly so the system does not sell them.
How should server sections be balanced?
By expected covers rather than table count, with a separate layout for each staffing level so the host can switch when someone calls out.
How do we show accessible seating?
Mark tables with a step-free route and wheelchair space as accessible, spread them across the room where possible, and keep them visible to online bookers.
References
US Bureau of Labor Statistics (2025). Occupational Outlook Handbook: Food and Beverage Serving and Related Workers (opens in a new tab) ↑
US Bureau of Labor Statistics (2026). Current Employment Statistics: series CES7072200002 (opens in a new tab) ↑
US Department of Justice (ADA.gov) (2026). ADA Title III Regulations primer (opens in a new tab) ↑
National Restaurant Association (2025). Report: Takeout, drive-thru, delivery are more popular than ever (opens in a new tab) ↑