A floor plan should be a shared working reference
A digital restaurant floor plan is useful when it matches the actual room. Consistent table numbers, understandable area names and realistic seat counts matter more than an elaborate drawing. Reception should be able to assign a booking and a server should recognise the same table without an explanation. Otherwise staff may replace the shared plan with informal names and separate notes.
Bonzumo uses floor plans and areas in reservation and service contexts. Tables and their seat counts provide information for seating decisions, giving a booking a specific place in the venue. Careful setup is particularly valuable with several rooms or outdoor tables. A theoretically empty seat in an area that is not operating tonight is not necessarily a usable place for the current service.
Name areas according to how the venue works
Choose names that staff can relate to the real space. Dining room, bar area and terrace are often clearer than purely technical numbers. Also consider whether each area is available throughout opening hours. A private room may be reserved for an event, a terrace may depend on weather and an upper floor may have no service coverage during part of the day.
Separate physical capacity from operational availability. A room might contain twenty chairs while only certain tables should be accepted for the evening. Establish the appropriate rules and settings during Bonzumo setup. Staff agreements need to match them. A colleague should not promise guests an area that the current shift cannot actually operate.
Review table sizes and group arrangements
Set seating information according to actual use. A table for two and a large shared arrangement meet different needs. Empty seats scattered across several separate tables do not automatically provide a suitable place for one group. Restaurant table reservations depend on the arrangement as well as the total number of seats.
Walk through typical party sizes. Where can three people sit comfortably? Which tables suit a larger group? Where is enough space left for staff and guests to move? Bonzumo provides table and area information for allocation. The team should still check that a proposed combination works in the physical room. Guests need an appropriate seating arrangement rather than a mathematical total of unrelated chairs.
Distinguish occupancy from arrival rate
Capacity concerns the places usable in a particular context. Arrivals concern the guests newly entering the venue. These are often confused. Several groups can arrive within a short period and then stay for a long visit. A low number of new bookings therefore does not necessarily mean low occupancy.
Consider visit duration and overlapping reservations during setup. Bonzumo includes reservation times and capacity rules, whose practical effect should be checked with examples. A setting concerning occupancy should not be described without verification as a limit on new arrivals. Reception planning also needs a separate judgement about how many arriving parties the team can welcome comfortably within a short period. Make that operational choice explicit.
Prepare for weather-related seating changes
If outdoor tables become unavailable, affected bookings need a new seating context. Review which indoor places are genuinely available and what guests were promised. Treating the terrace as additional indoor capacity would misrepresent the situation. A weather alternative needs a specific table decision and clear communication.
Establish a route for those changes: identify affected reservations, assess alternatives, contact guests and keep the revised allocation understandable to the team. Bonzumo provides the table and booking context for that work. Your restaurant decides which alternative can be offered and when. A carefully configured floor plan helps reception, servers and supervisors work from the same account of the available space.
Keep table references clear when the furniture changes
Two small tables are joined for a birthday party and separated again the following day. Reception, kitchen and service staff still need to understand the seating arrangement being discussed. Agree how your team refers to temporary layouts. An improvised name such as “the big window table” may make sense at the time but becomes unreliable when different people work the next shift.
Walk through Bonzumo's tables and their assignments in the real room. After a layout change, check whether the description, seat count and reservation allocation still reflect actual use. This does not assume that the system automatically detects furniture being moved. What matters is that the plan communicates the agreed arrangement and staff know which booking uses which space.
Avoid unnecessarily renaming every table for each event. A stable underlying structure makes orientation easier. Explain temporary differences clearly enough for the next shift to restore the ordinary layout without accidentally attaching a reservation to the wrong place. The shared reference should remain useful both during the special arrangement and after it has been removed.
A private-room booking affects more than its chairs
A side room has twelve seats and is being used for a private party. Those places cannot also be treated as ordinary available restaurant seating during the same period. Check whether the event needs adjacent space for welcoming guests or additional equipment. A booking can occupy more than its chair count when the agreed experience requires part of the surrounding room.
Review affected reservations and areas in Bonzumo before making further promises. If the room will return to ordinary service later, allow time to reset it. A celebration does not physically finish merely because its originally estimated duration has elapsed. Confirm the actual situation before bringing the next party into the room. The decision should remain connected to the space guests will really use.
The service team also needs the arrangement. Who is looking after the private party, and which other tables remain within normal service? An organised floor plan becomes useful when the shift can operate the areas that have been promised. A room being physically present does not by itself establish that it is available for another group.
Test overlapping visits with actual numbers
Suppose an area has 16 usable seats for the evening. Eight guests arrive at 6 pm and are expected to stay for two hours. Another six are due at 7 pm. Between 7 and 8 pm, 14 places are occupied even though only six people arrive at 7 pm. This simple example demonstrates why considering arrival time alone can underestimate the number of people already in the room.
At 7.30 pm, a party of four asks to book. Two remaining places are insufficient even if few other guests are arriving in that particular interval. Also check whether the tables themselves provide suitable arrangements for the parties already accepted. A total seat calculation and the practical layout answer different questions; both need to make sense before another promise is given.
Use cases like this when configuring Bonzumo's booking rules. Ask which period a setting considers and what happens when the assumed duration changes. Staff can then understand what the capacity setting means before using it to make decisions for a full evening. The numerical example is a planning illustration, not a claim that all groups will leave precisely at their estimated end time.
Include movement routes in the seating decision
An extra chair may increase the nominal seat count while making access to the bar, a passage or another seat more difficult. Examine the layout from several perspectives. How does the guest reach their place, how does service carry food to the table and where will arriving people stand while waiting? These are questions about the real room, not just the number stored in a table record.
When a guest describes a particular space requirement, find a suitable arrangement and confirm only what the restaurant can provide. A factual description of the need is more useful than a personal assumption about the visitor. Keep the agreed detail understandable to the staff responsible. Bonzumo's table and area relationship supports allocation; it does not automatically establish that every possible room layout suits every situation.
Give particular attention to places used only occasionally. An extra table may look reasonable on a plan but occupy the point where meals are collected or guests are welcomed during busy service. Checking the physical setup helps preserve the usability of the plan. It also avoids discovering an awkward arrangement only after the guests have already sat down.
Refresh the plan after layout and seasonal changes
New furniture, a revised terrace or a different use for the bar changes the working reference. Review area names, table sizes and the spaces actually in operation. Then look at reservations already accepted: do their assignments still fit? A previously suitable booking may need a different place when the layout changes. Resolve that before arrival rather than expecting reception to improvise while the guests wait.
Temporary restrictions deserve the same attention. An event or operational work may make one area unavailable while the rest of the restaurant remains open. Agree who checks these changes against bookings and how the team recognises when ordinary use resumes. Automatic room release or calendar connections are not assumed; use the workflow demonstrated for your actual installation.
You do not need an elaborate architectural drawing for a Bonzumo demonstration. A simple sketch with real table numbers, seat counts and two common alternative arrangements is enough. Follow an ordinary booking, a larger party and an overlap between visits. This shows whether the digital floor plan gives your team the practical orientation it needs for the next busy shift, including the changes that happen between one service and another.