Most restaurant owners think their revenue ceiling is set by seating capacity. It is not. It is set by the speed at which they can turn those seats. A restaurant with 40 seats running 2.0 turns per night has a different revenue ceiling than one running 2.8 turns.
The five metrics from The Five Restaurant Metrics That Tell You Whether the Business Is Actually Healthy point toward table turns as a lever when covers are flat and revenue is not growing. This article covers what table turn analysis reveals and how to use it. The Turn-Rate Revenue Analysis is the tool.
Most operators have a seating capacity and a sense of how long tables tend to run. The Turn-Rate Revenue Analysis turns that sense into a number with a revenue impact attached.
This article is also the supporting analysis for The Monthly Restaurant Review That Changes How You Operate. A turn-rate analysis is one of the inputs a meaningful monthly review draws from.
Why Most Restaurants Leave Revenue on the Floor Without Knowing It
The obvious reason is that table turn time is not tracked. Most operators have a sense of whether tables turn quickly or slowly. Very few have a number. Without the number, there is no baseline to improve from.
The less visible reason is that the friction points are invisible. A table that takes twenty minutes longer than the revenue-optimal window because the server forgot to bring the check is a different problem from a table that takes twenty minutes longer because the kitchen backed up. Both problems lose the same revenue. Both require different fixes.
The deepest reason is that most operators think of table turns as a hospitality variable. They are also a financial one. A thirty-second improvement in average turn time across forty covers on a busy night can produce two to four additional covers. That difference, compounded across a Friday and Saturday, is meaningful revenue at no additional fixed cost.
The Turn-Rate Revenue Analysis
The first component establishes the current baseline turn time
Turn time is measured from when a table is seated to when it is cleared and ready for the next party. The baseline is the average turn time for each service type: dinner service, lunch service, weekend brunch.
Most POS systems record reservation and seating data. If the restaurant runs a reservation system, the data is already being captured. If it does not, a two-week manual log of seating and clear times produces a usable baseline.
The baseline reveals two things: the average turn time and the variance. Wide variance means some tables run much longer than others. Narrow variance means the floor is running consistently. Both patterns are useful.
The second component identifies where friction extends turn time
Friction is anything that extends a table’s time beyond the revenue-optimal window without producing additional revenue. The most common friction points are three: check presentation lag, payment processing delay, and table clearing time. Each is measurable in a single service with a phone timer.
Each of these can be timed separately over a service period to find where the extension is happening. A table that lingers at the check stage is a different problem from a table that lingers because the server is managing too many simultaneous closes.
The analysis reveals where the intervention goes, not how to deliver it. A kitchen backup requires a kitchen fix. A server timing issue requires a service fix. The data specifies the target.
The third component calculates the revenue impact of a modest improvement
Once the baseline and friction points are known, the revenue impact of a modest improvement is calculable. If the average turn time on Friday dinner is 72 minutes and the revenue-optimal window is 60 minutes, a ten-minute reduction produces one additional cover per table over a full service. The revenue-optimal window varies by service model but is typically a reasonable dining duration plus time to close.
Forty seats, ten tables, one additional cover per table: that is ten additional covers at the average check. Multiply by the number of Friday dinners in a year. The number is usually large enough to justify focused attention on turn-rate management.
How the Living Library Builds Your Turn-Rate Analysis
The Living Library is the active knowledge layer of the Kiluma platform. It reads the table timing data the restaurant saves from its POS and reservation system and builds the turn-rate analysis from that accumulated history. The analysis shows average turn time by service type, where variance is highest, and where friction is extending specific table durations.
The Conductor is Kiluma’s context-aware AI. It can answer specific questions from this analysis: which service periods have the most friction and what a turn-time improvement is worth in revenue. These questions feed directly into the monthly review.
Kiluma is the knowledge layer, not the reservation or floor management system. OpenTable or Resy manages the bookings; Kiluma reasons over the timing data that system generates. The analysis is built from what the restaurant has actually documented.
Time Five Tables on the Next Busy Service
On the next Friday or Saturday service, time five tables from seating to cleared. Write down the time for each and note where the longest extension was: kitchen, server, payment, clearing.
That data is the starting point for the turn-rate analysis.
When Turn Rate Is Measured, the Revenue Ceiling Becomes Visible
The restaurant that tracks table turn time knows its actual revenue ceiling rather than its theoretical one. The Turn-Rate Revenue Analysis makes that ceiling visible. The monthly review that this analysis feeds into is covered in The Monthly Restaurant Review That Changes How You Operate. Try Kiluma free for 14 days at kiluma.ai.