RevPASH for Restaurants: Definition, Formula, and Best Practices

RevPASH—Revenue Per Available Seat Hour—measures how much money each seat in your restaurant generates per hour of operation. It’s the metric that tells you whether a full dining room is actually making you money, or just making you busy.

A packed house feels like success. But if those tables are turning slowly and guests are splitting appetizers, you’re leaving revenue on the table. RevPASH cuts through the noise by combining occupancy, average check, and time into a single number you can actually act on. Here’s how to calculate it, what the results mean, and how to improve yours.

What is RevPASH?

RevPASH stands for Revenue Per Available Seat Hour. It’s a metric that measures how much revenue your restaurant generates for every available seat during a specific period of time. Unlike simply counting covers or checking if tables are full, RevPASH factors in both time and capacity to show how effectively your seating is producing revenue.

Here’s what makes up the calculation:

• Revenue: Total sales during a defined time period, whether that’s a lunch shift, dinner service, or full day
• Available seats: Every seat in your dining room, occupied or not
• Hour: The time unit that lets you compare different shifts and dayparts against each other

“RevPASH is one number that takes the time variable into the mix,” says Steve Case, Financial & Insurance Consultant at Insurance Hero. “Only once you do that do you begin to ask some very different questions about how your floor actually performs.”

A full dining room can feel like success. But RevPASH tells you whether those seats are actually producing revenue, and how efficiently they’re doing it.

How to calculate RevPASH

The RevPASH formula

The formula is straightforward:

RevPASH = Total Revenue ÷ (Number of Seats × Hours Open)

There’s also a second way to calculate it:

RevPASH = Seat Occupancy × Average Check

Both formulas arrive at the same number. The first version is easier when you’re pulling data from your POS at the end of a shift. The second helps you understand what’s driving your RevPASH, whether it’s how full you are or how much guests are spending.

An example RevPASH calculation

Say your restaurant has 50 seats. You ran a four-hour dinner service and brought in $4,000 in revenue.

Here’s the math:

• 50 seats × 4 hours = 200 available seat hours
• $4,000 ÷ 200 = $20 RevPASH

That $20 means each seat generated an average of $20 per hour during that service. Now you have a number you can compare against other shifts, other days, or other locations in your group.

What is a good RevPASH for restaurants?

There’s no universal benchmark here. A fine dining restaurant with two-hour turns and $150 checks will have a different “good” RevPASH than a casual spot with 45-minute turns and $25 checks. What matters is tracking your own numbers over time and understanding what moves them up or down. RevPASH is one of several restaurant metrics that reveal operational performance beyond simple sales figures.

What a high RevPASH means

A high RevPASH indicates strong revenue generation from your available seating capacity. Your tables might be turning efficiently, your average check might be healthy, or both.

Context matters, though. A high RevPASH during a slow Tuesday is different from a high RevPASH on a packed Saturday. The Tuesday number might signal an opportunity: what if you could replicate those conditions more often?

What a low RevPASH means

A low RevPASH signals untapped revenue potential. It’s a diagnostic tool, not a judgment.

Common causes include:

• Tables sitting empty during service
• Slow turnover, with guests camping longer than expected
• Parties that don’t match table sizes (two guests at a four-top)
• Lower average checks than the menu supports

“Covers and average spend are typically tracked by most restaurants,” Case notes. “However, that is not a complete picture. RevPASH bridges that divide and takes the front of house action and relates it to the effectiveness of your physical space.”

Why RevPASH matters more than occupancy

A packed house feels like a win. But occupancy only tells you how many seats are filled, not how much revenue those seats are generating or how long they’re occupied.

Here’s the disconnect: a full dining room with slow turns and low checks can underperform a half-full dining room with quick turns and higher spending.

Scenario	Occupancy	RevPASH	The problem
Full dining room, slow turns	High	Low	Seats aren’t generating enough revenue per hour
Half-full, quick turns, high checks	Moderate	High	Fewer guests, but more revenue per seat-hour

RevPASH captures both space utilization and average check size. That’s why it’s a better indicator of how your floor is actually performing than a simple headcount.

RevPASH vs table turns

Table turns and RevPASH get confused a lot, but they measure different things.

Table turns measure how many times a table is used during a service period. If a four-top gets seated three times during dinner, that’s three turns.

RevPASH measures revenue generated per seat per hour. It factors in what guests are actually spending, not just how often they’re cycling through.

Both are useful. But RevPASH gives you a fuller picture because a fast table turn doesn’t help if guests are only ordering appetizers and water. You can turn a table four times in a night and still underperform a table that turned twice with guests who ordered wine and dessert.

How to improve your restaurant RevPASH

Once you know your RevPASH, here are practical ways to increase it without rushing guests or compromising the experience.

1. Train your host team to think about revenue

Your host stand controls table assignments. That’s a revenue decision, whether they realize it or not.

When a deuce takes a four-top during a busy Saturday, you’ve just cut your potential revenue for that table in half. Training hosts to seat parties at appropriately-sized tables, two guests at a two-top instead of a four-top, directly impacts revenue per available seat hour.

2. Match table sizes to actual party demand

Pull your reservation and walk-in data. What party sizes actually come through your doors?

If most parties are twos and threes but your floor plan is heavy on four-tops, you’re leaving money on the table. Literally. Adjusting your table mix to match real demand can lift RevPASH without changing anything else about your operation.

3. Use menu design to increase average check

Menu engineering can nudge guests toward higher-margin items or add-ons. Placing profitable dishes in high-visibility spots and using descriptions that sell can lift average check without changing your seating capacity or turn times.

Since RevPASH = Seat Occupancy × Average Check, a higher check directly improves your number even if nothing else changes.

4. Add premium seating or minimum spend options

Consider offering premium reservations for patio seats, chef’s tables, or window spots with a minimum spend or slight upcharge during peak times.

This increases revenue per available seat hour during your busiest periods, when demand already exceeds supply. You’re not adding capacity; you’re getting more from the capacity you have.

5. Schedule staff based on revenue potential

Align your staffing levels with your RevPASH patterns, not just expected cover counts. Similar to tracking revenue per labor hour, RevPASH helps connect staffing to actual revenue generation.

If Saturday dinner generates significantly more revenue per seat hour than Tuesday lunch, staff accordingly. This connects labor costs to revenue potential rather than just volume. A shift with high RevPASH can support more labor; a shift with low RevPASH probably can’t.

Tip: Track RevPASH by daypart for at least a month before making staffing changes. You’ll spot patterns that cover counts alone won’t reveal.

Turn RevPASH insights into smarter scheduling

When you understand which shifts and dayparts generate the most revenue per seat, you can make smarter decisions about staffing, table setup, and even when to accept large reservations.

“When RevPASH is monitored every month, restaurants realize that some promotions seem to be filling seats during weak times, but don’t actually improve the overall score,” Case explains. “This is the sort of pattern that makes a pricing assessment fluid.”

Tracking all this manually means spreadsheets, a calculator, and time you don’t have. Tools like 7shifts help you align your schedule with revenue patterns so you’re not overstaffed during low-RevPASH periods or understaffed when revenue potential is highest.

Start a free trial to see how scheduling software can connect your labor costs to the shifts that actually drive revenue.

FAQs about RevPASH

How often should restaurants calculate RevPASH?

Weekly or after each service period (lunch vs. dinner) works well for spotting patterns and measuring the impact of changes. Monthly tracking works for high-level trends, but weekly gives you actionable insights faster.

Does RevPASH vary by daypart or day of the week?

Yes, and often significantly. Your Friday dinner RevPASH and Tuesday lunch RevPASH are essentially measuring two different businesses. Track each separately to get useful insights.

What is the 30 30 30 rule for restaurants?

The 30 30 30 rule is a general guideline suggesting restaurants aim to keep food costs, labor costs, and all other operating costs each around 30% of revenue, leaving roughly 10% for profit margins. It’s a starting point, not a hard rule. Your actual targets depend on your concept, location, and service model.