A full booking list is not the same as a full dining room
Ten reservations can mean ten small tables or several large groups. Some guests arrive early, others cancel and some do not appear. The number of bookings alone therefore cannot explain restaurant occupancy. Party size, status, timing and the available seating arrangement provide the context. Together they allow you to ask more useful operational questions.
Bonzumo's reservation overview includes booking records, guest counts and status information. It distinguishes active and cancelled reservations and connects them to table and area context. This provides a basis for understanding how an evening developed. The information still needs interpretation, but it helps identify the actual records behind the situation being reviewed.
Distinguish reservations, covers and capacity
Before reviewing figures, decide what you want to understand. Reservation counts describe booking records, party size describes guests and seating capacity describes a physical possibility. They measure different things. Combining them carelessly can make fewer bookings look like fewer guests, even if the change was simply towards larger groups.
Time also matters. A seat can serve several visits during a day, while only one occupancy arrangement is possible at a particular moment. A total for the evening is therefore not a statement about how busy the room was at seven o'clock. Bonzumo connects reservations and areas. Use suitable periods and individual records to explain unusual totals instead of assuming they all describe the same thing.
Keep cancellations separate from no-shows
A reservation cancelled in advance creates a different opportunity from a party that does not arrive and gives no notice. Both can leave empty seats, but the timing and causes differ. Keep the statuses distinct. A booking without a completed check-in is not automatically a confirmed no-show either; staff may simply have missed the arrival update.
Agree who reviews the status and when. The result should reflect what actually happened. Bonzumo includes relevant reservation statuses and cancellation processes. Your approach to contacting late guests or offering a table to somebody else is a separate operational decision. The system provides context, while the venue needs a clear and consistently explained guest policy.
Compare services with similar conditions
A Saturday with a special event is not directly comparable to an ordinary Tuesday. Terrace availability, opening hours and usable rooms may also differ. To understand change, begin with reasonably similar conditions. Note unusual events that could explain a figure instead of treating every result as a lasting trend.
Start with a specific question. Which arrival times create the most coordination at reception? Which party sizes leave seating unresolved until late? Which bookings changed shortly before service? Individual records may answer those questions better than one large total. A regular review should improve decisions, rather than simply produce another collection of reports.
Turn an observation into a testable improvement
When a difficulty recurs, make one deliberate change. Larger groups may need earlier seating review, booking amendments may require a clearer handover or outdoor reservations may need better weather arrangements. State which observation prompted the change and what you would expect to see during the next comparable service.
Bonzumo links reservations to guest and table context, allowing a review to start from actual events. A no-show figure by itself does not identify the right response or guarantee future occupancy. The practical benefit is preparation: the team can recognise which information is missing early, which promises need clarification and where reception may need support during the next shift.
Fewer bookings can mean more expected guests
One Thursday has twelve reservations covering 24 people. The following Thursday has only eight reservations but 32 people. Looking only at booking count could suggest a decline. In this example, expected guest numbers have actually increased because parties are larger. Reception and seating may face more coordination on the second evening because larger groups require suitable contiguous places.
Read reservation counts alongside party sizes and inspect the unusual bookings in Bonzumo’s table context. The appropriate response is not automatically to release more tables. A group may need its seating arrangement reviewed earlier, or an area request may still be unresolved. The booking records help identify the actual question behind the total.
When comparing, state whether the figures describe expected guests or confirmed arrivals. A forecast before service and a clarified review afterwards answer different questions. They should not silently acquire the same label. Keeping that distinction visible helps the team understand whether it is planning work ahead or explaining an evening that has already happened.
Count no-shows against an explicit denominator
Suppose a reviewed evening establishes that two of twenty reservations included in the comparison did not arrive. On a booking basis that is ten per cent. If each missing booking was for two people and the same set of reservations represented 60 expected guests, the affected party sizes total four out of 60, or about 6.7 per cent. Both calculations can be correct while describing different things.
Define which reservations belong in the comparison and how prior cancellations are treated. Name the denominator instead of using an unexplained absence rate. If staff change the inclusion rule from week to week, the numbers may move even when guest behaviour does not. A useful internal note can simply state that the comparison uses bookings still expected at a specified point before service.
Also establish whether status matches events. A group with a missed check-in update is not a confirmed no-show on that basis alone. These calculations are editorial examples for interpreting your data, not a claim that Bonzumo automatically produces this exact metric as a ready-made report.
Cancellation timing and replacement seating explain the impact
Two equally sized groups can cancel on the same day with different operational consequences. One cancels in the morning, giving the venue time to use the table for another visit. The other calls shortly before the expected arrival, leaving less opportunity to arrange a suitable replacement. A count of two cancellations does not reveal that difference.
Review the relevant bookings and the sequence the team can actually establish. Was a walk-in seated, was the table used differently or did it remain empty? If the reason was not recorded and staff cannot reliably establish it, leave it unresolved rather than fill the gap with an assumption.
Do not turn an empty table into a precise lost-revenue claim without supporting sales information. A replacement group might have ordered differently or used the table for another duration. The more immediate operational question is where the team had an opportunity to respond and what information it needed at that point. That question can lead to a clearer reception routine without inventing financial certainty.
Occupancy needs both a time and usable seating
A restaurant has 40 usable seats on a particular evening. At 7:30 pm, 30 guests occupy the area being examined. That corresponds to 75 per cent of the seat capacity in this simple point-in-time example. More than 40 guests can visit over the whole evening as parties leave and others arrive. This does not mean more seats were occupied simultaneously than the restaurant had.
Account for whether the seating was genuinely available. A terrace closed by weather should not automatically be included in the same way as on an evening when it was open. Likewise, six empty seats scattered across several tables may not provide a suitable place for a party that wants to sit together.
Bonzumo supplies table and area context. Use it to explain the number rather than converting a theoretical seat total directly into a promise to the next caller. For a larger party, shape and allocation of available tables can matter alongside the numerical count. The useful seating decision is about where this particular group can actually be accommodated.
Choose an action that fits the observation
If larger parties repeatedly receive suitable seating only shortly before arrival, reviewing their table arrangements earlier is a specific response. If the main difficulty is incomplete statuses after service, improve reception handover first. An additional booking restriction would not fix missing information about what already happened. Match the action to the cause the team has established.
Does one weak evening justify stricter reservation conditions? First review comparability, party sizes and confirmed events. Identify periods with many actual arrivals separately from periods that look busy because earlier guests remain seated. An occupancy limit is not automatically an arrival-rate limit, and the two should not be described as interchangeable.
For a Bonzumo demonstration, bring two manageable example services with different group sizes, one cancellation and an arrival whose check-in was missed. Follow how the individual records explain the headline figures. This gives you a practical basis for preparing the next shift and deciding which information needs better coordination.
Keep the first improvement small enough to assess. For example, discuss larger group seating before the next comparable service and then ask whether reception still had to improvise those same arrangements at arrival. That establishes a visible operational outcome without promising a certain occupancy increase or treating a short comparison as proof of a lasting trend.