Average service time measures how long, on average, the full experience of a table or guest lasts: from sitting down or the order being opened until they finish, pay and the table is ready to be sold again.
Average service time in hospitality is the indicator that measures the average duration of a visit or table cycle during a service. It can be measured from different starting points depending on the goal: from the guest's arrival to payment, from the order being opened to the ticket being closed, or from a table being occupied until it is clean and available again. What matters is always using the same criterion so the figure is comparable. This metric directly connects operations, guest experience and profitability.
An average time that is too long can reduce table turnover, worsen RevPASH and leave bookings waiting even when demand is good. But a time that is too short can also be risky if it feels rushed, lowers average spend or prevents you from selling desserts, coffees and extra drinks. So the aim is not to speed everything up indiscriminately, but to identify bottlenecks: long waits before orders are taken, a kitchen overloaded by second courses, dishes that block a station, too few front-of-house staff, slow payment or tables that take too long to be reset. The figure should be analysed by service, time slot, table type, channel, menu, server and type of order.
A restaurant serving a menú del día (Spain's set lunch menu) may aim for cycles of 40 to 60 minutes; a casual dining restaurant might work with 75 to 100 minutes; a fine dining restaurant will accept longer times if the spend and the experience justify it. Used well, average service time helps balance occupancy, demand forecasting, staffing, production and perceived quality.
Average service time = Total time of tables served / Number of tables served
To calculate it, add up the duration of every table in a period and divide by the number of tables served. If 42 tables are served during a dinner service and their combined duration is 3,360 minutes, the average service time is 3,360 / 42 = 80 minutes per table. It can also be calculated per guest, per ticket or per phase: wait until the first drink, time between ordering and the first course, time between courses, time to payment and table reset time. Breaking the figure down by phase helps you move from a general metric to concrete actions.
A 60-seat restaurant notices that it has strong demand on Fridays but only manages one and a half sittings. Measuring average service time, it discovers that the full visit lasts 118 minutes. The phase-by-phase analysis shows that guests are not slow to eat: the problem is an 18-minute initial wait before orders are taken and an average of 14 minutes between asking for the bill and paying. The team introduces pre-assigned sections, preps drinks mise en place before the rush, switches on handheld card payment at the table and simplifies two dishes that were blocking the kitchen.
A month later, average service time falls to 96 minutes without any drop in average spend. With the same dining room, the restaurant accepts more early bookings, improves table turnover and reduces waiting at the door.
Average service time matters because each table has a limited capacity to generate revenue per time slot. If the restaurant does not know how long each cycle really lasts, it plans bookings, shifts and production blind. Measuring it lets you adjust arrival times, booking promises, staffing levels, advance prep, menu design and payment processes. It also helps protect the guest experience: many complaints are not about the food, but about hidden waits the team has come to treat as normal.
Combined with occupancy, table turnover, average spend and RevPASH, this KPI shows whether the restaurant is making good use of its capacity without sacrificing quality or a sense of hospitality.
Zindra helps you measure average service time by combining bookings, tickets, orders, occupancy and reporting. That way you can spot slow time slots, compare services, see whether a menu or shift change improves operations, and make decisions on staffing, production and bookings with real data rather than end-of-shift impressions.
Tools and content to go deeper into this concept.
Average spend (the average ticket) is the average amount each customer (or table) spends in your restaurant. It is a key indicator of commercial performance and of how well your menu works.
RevPASH (Revenue per Available Seat Hour) measures the revenue generated by each available seat per hour. It is the most complete indicator of a restaurant's operational efficiency and real profitability.
Mise en place (French for 'put in place') is the principle of organising and preparing all the ingredients, tools and equipment in advance, before service or a recipe begins.
The occupancy rate measures the percentage of available seats actually filled during a service. It is a key indicator of a restaurant's efficiency and the basis for working out its revenue potential.
Table turnover measures how many times each table is occupied during a service. It is a key operational efficiency indicator which, combined with average spend, determines the restaurant's revenue potential.
Demand forecasting is the prediction of the sales, covers or usage a restaurant will have in a future period. It helps you buy better, plan staff and prepare production with less waste and fewer stockouts.
Every hospitality term with formulas, examples and benchmarks in a handy PDF.
Try Zindra free and keep food cost, staff, inventory and much more under control from a single platform.