RevPASH
RevPASH (Revenue Per Available Seat Hour) is a restaurant performance metric that measures revenue efficiency by dividing total revenue by the product of available seats and operating hours, revealing how effectively a restaurant converts seating capacity into sales.
RevPASH (Revenue Per Available Seat Hour) is a performance metric that measures how much revenue each seat in a restaurant generates per hour of operation. Introduced in 1998 by Professor Sherri Kimes at Cornell University, RevPASH calculates efficiency by dividing total revenue by the product of available seats and opening hours. For example, a restaurant generating $6,000 in revenue with 100 seats open for 8 hours produces a RevPASH of $7.50 ($6,000 ÷ 800 seat-hours).
How RevPASH Works
RevPASH uses one of two formulas depending on available data. The direct method divides total revenue by available seats multiplied by operating hours. The alternative method multiplies average check size by seat occupancy percentage. Both approaches measure the same fundamental metric: how effectively a restaurant converts seating capacity into revenue over time.
The metric tracks both time and capacity simultaneously, making it more comprehensive than daily sales totals or average check size alone. In a theoretical perfect scenario, RevPASH would equal the average spend per cover, indicating 100% seat occupancy for the entire measurement period. The gap between actual RevPASH and average check reveals unrealized revenue from empty seats, slow table turns, or mismatched table assignments.
Origins and Industry Context
Professor Kimes adapted RevPASH from airline revenue management practices, where similar metrics optimize flight schedules, aircraft selection, and dynamic pricing. The hospitality industry already used RevPAR (Revenue Per Available Room) for hotel operations, and RevPASH applies the same capacity-efficiency thinking to food and beverage outlets. Boston University School of Hospitality later developed a calculator application to help operators analyze and optimize their RevPASH performance.
Practical Applications
Operators calculate RevPASH hourly, daily, weekly, or monthly, with hourly breakdowns providing the most actionable insights. Hour-by-hour tracking identifies peak demand periods, reveals slow times that need promotional support, and highlights service bottlenecks that reduce turnover. A lunch service might show strong RevPASH from 12-1pm but significant drops at 11am and 2pm, signaling opportunities for early-bird specials or extended lunch promotions.
RevPASH data informs menu design decisions—complex dishes that slow table turns during peak hours reduce the metric even if check averages stay high. The measurement guides table configuration choices, showing whether four-tops or two-tops better match actual party sizes. It drives staffing schedules by correlating labor deployment with revenue-per-seat-hour targets. Operators also use RevPASH to evaluate menu engineering changes, pricing adjustments, and marketing campaign effectiveness.
Limitations and Complementary Metrics
RevPASH measures revenue efficiency but doesn’t account for profitability. A high RevPASH from expensive menu items might pair with elevated food costs that reduce net margins. Operators should analyze RevPASH alongside prime cost (food plus labor) to understand true operational performance. The metric also doesn’t capture bar revenue separately from dining room performance, potentially masking underperforming areas in mixed-use spaces.
There’s no universal “good” RevPASH benchmark—the metric varies by concept, location, and price point. A fast-casual restaurant with $12 average checks and high turnover might target $8-10 RevPASH, while a fine dining establishment with $75 average checks and longer dwell times might aim for $25-30 RevPASH. The value lies in tracking your own performance over time and comparing periods to identify trends and opportunities.
Improving RevPASH Performance
Restaurants boost RevPASH by reducing bottlenecks that slow table turns—streamlining ordering processes, pre-bussing during meals, and presenting checks promptly without rushing guests. Menu complexity adjustments during peak periods help kitchen throughput without sacrificing quality. Dynamic pricing strategies increase check averages during high-demand periods. Reservation management systems optimize table allocation by matching party sizes to appropriate tables and managing arrival times to smooth demand spikes.
Filling low-RevPASH periods requires targeted promotions: happy hours, early dinner specials, or prix fixe menus that attract customers during typically slow hours. POS system reporting provides the transaction-level data needed to calculate RevPASH accurately and track the impact of operational changes over time.
Common Uses
Restaurant operators use RevPASH to diagnose operational efficiency, comparing performance across different dayparts, days of week, and seasonal periods. General managers track hourly RevPASH to identify peak demand times requiring additional staffing and slow periods needing promotional support. Corporate restaurant groups compare RevPASH across locations to identify high-performing units and troubleshoot underperforming ones. The metric appears in management dashboards alongside traditional measures like daily sales and covers, providing context about capacity utilization that raw sales numbers miss. Operators reference RevPASH when making decisions about table configuration changes, menu revisions, pricing adjustments, and marketing campaign timing.
