Covers per Hour

A restaurant seats many guests during dinner but has quiet stretches before and after the peak, so covers per hour turns the service into a comparable rate that helps staff plan preparation and shifts, guiding service planning rather than an arbitrary race for more covers. Lightspeed defines covers as the number of customers on a check, so a table of five guests represents five covers, and its hourly sales report shows covers by hour.

A restaurant booking glossary describes covers per hour as guests served divided by hours of operation, and together these sources support a simple formula but not a universal ideal target. Choose the service period, since a dinner window from 6 to 10 is four hours even if the restaurant is open at other times, and count guests served during that period, defining whether to include takeaway, bar-only visits and complimentary diners.

For example, 120 covers across four dinner hours give an average of 30 covers per hour. That average can conceal a rush, because forty-five covers in one hour and fifteen in another require different staffing responses, so the whole-period average should be paired with a view of the busiest individual hours.

A cover is a person, not a reservation, so a booked table of six that arrives with four diners usually contributes four served covers, and a customer on one bill with five colleagues is one of six covers, not one sixth of a check. Keep walk-ins in the count if the service definition includes them, because reservation data alone may understate throughput.

Use POS data to verify actual served covers, since reservations cancelled before arrival should not count as served guests. Look at seat capacity, because a 40-seat cafe and a 200-seat hall should not be judged by the same raw hourly number, and covers per available seat-hour can provide a more comparable capacity view when seating differs.

Check the duration of visits, since faster service may free tables but pressure to rush guests can damage their experience. Staff productivity needs its own denominator, as covers per labour hour asks a different question from covers per clock hour, and for a multi-site view you should total all comparable covers and service hours, since a simple average of venue rates can over-weight a small outlet.

A high guest count can strain the kitchen if orders arrive together, so pacing reservations may matter more than the average, and menu mix changes workload because a tasting menu can take more preparation time per cover than a simple lunch special. Compare like shifts and seasons, as an event night should not automatically become the target for every weekday, and document exceptional closures and private events, since otherwise the same denominator may not represent available service time.

A venue should define when a cover belongs to an hour, whether arrival, order opening or payment, because each method can shift the hourly pattern, and it should keep that time-assignment rule stable when comparing periods. Revenue per cover adds the spending dimension, since thirty guests buying a small drink are different from thirty buying full meals, while cost per cover adds the resource dimension, since high hourly volume may still be unprofitable if staffing or waste rises sharply.

A minimum staffing level may be required even during quiet hours, so a low covers-per-hour figure alone does not justify unsafe cuts. Check queue times and errors during peaks, because a faster apparent pace may coincide with mistakes and complaints; if the venue has a long wait, extra seating or a shorter bottleneck in service may increase capacity once the constraint is identified, but if demand is weak, adding seats will not solve it and marketing or timing may be more relevant.