RevPASH: Formula, Benchmarks & 5 Levers

Occupancy rate is the KPI almost every restaurant owner watches. And yet it is one of the most misleading metrics in hospitality. A full dining room does not guarantee strong revenue — and a half-empty room can be surprisingly profitable. The KPI that exposes this difference is called RevPASH: Revenue Per Available Seat Hour.

RevPASH was popularised in the 1990s by hospitality researcher Sheryl Kimes at Cornell University, partly inspired by the RevPAR concept from the hotel industry. Today it has become the central performance metric for many leading restaurant groups worldwide. In this article you will learn the fundamentals, master the formula and benchmarks, and then work through 5 concrete levers to lift your revenue per seat — from raising average spend to cutting the empty time between guests, with specific attention to the UK gastronomic context.

View transcript

What is RevPASH?

RevPASH stands for Revenue Per Available Seat Hour. It measures how much revenue each seat in your restaurant generates on average per hour that you are open.

The basic formula is straightforward:

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

There is also an alternative calculation that provides intuitive insight:

RevPASH = Occupancy Rate × Average Check per Guest

This second formula immediately reveals the two levers that determine RevPASH: how many seats are occupied and what guests spend on average. You can increase RevPASH by raising occupancy, by raising the average spend, or — the most powerful scenario — by improving both simultaneously.

A worked example

Suppose your restaurant has 40 seats. On a Friday evening you are open from 6 pm to 11 pm — that is 5 hours. Total revenue that evening is £2,400.

RevPASH = £2,400 ÷ (40 × 5) = £2,400 ÷ 200 = £12 per seat-hour

Using the alternative formula: suppose you have an average of 28 of the 40 seats occupied (70% occupancy) and the average spend per guest is £60.

However, if guests stay for an average of 2.5 hours, you need to convert the spend into a per-hour figure: £60 ÷ 2.5 hrs = £24 per seat-hour. Then: RevPASH = 0.70 × £24 = £16.80. This is closer to the direct calculation, though small differences arise because occupancy fluctuates across the service.

This immediately reveals a core insight: average table duration is a critical variable that occupancy rate alone never captures.

Why RevPASH beats occupancy rate

Occupancy rate tells you how many seats are occupied at any given moment. That is useful, but fundamentally incomplete. The biggest problem: occupancy rate ignores how long guests stay and what they spend.

Here is a concrete example that illustrates the difference:

Scenario 1: Restaurant X has 50 seats and is always full (100% occupancy). Guests stay an average of 3 hours and spend £45 per person. RevPASH = 1.0 × (£45 ÷ 3) = £15 per seat-hour.

Scenario 2: Restaurant Y also has 50 seats but is only half full (50% occupancy). However, guests spend £80 per person and stay an average of 1.5 hours. RevPASH = 0.5 × (£80 ÷ 1.5) = £26.67 per seat-hour.

Restaurant Y earns nearly 80% more per seat-hour than Restaurant X, even though the dining room looks half empty. As the owner of Restaurant X, you might feel satisfied — full house, after all? But you are leaving significant revenue on the table.

This is precisely the trap of occupancy rate: a packed dining room with long table turns at low average checks can dramatically underperform a half-empty room with quick turns and high spending.

Occupancy rate also tells you nothing about the value of time. A table occupied from 7 pm to 10 pm by four guests who collectively spend £120 generates far less than a table used twice — first from 7 pm to 8:30 pm and then from 8:45 pm to 10:15 pm — with £120 per party each time.

Read our comprehensive guide to restaurant analytics and data-driven decision making for a broader framework.

RevPASH benchmarks by restaurant type

RevPASH varies considerably by restaurant concept. A fast-food outlet has a fundamentally different revenue model to a fine dining establishment. The benchmarks below give you orientation points:

Restaurant type	Typical RevPASH	Characteristics
Quick service / Fast casual	£3 – £6 / seat-hr	High turnover, low average spend, short dwell time (20–40 min)
Casual dining / Brasserie	£7 – £12 / seat-hr	Average turnover, average spend £25–55, dwell time 60–90 min
Gastronomic / Fine dining	£15 – £30+ / seat-hr	Low turnover, high spend £75–200+, longer dwell time 2–3.5 hrs
Gastronomic (UK top tier)	£20 – £40+ / seat-hr	Set menus, wine pairing, average spend £100–250+

Important: always compare your RevPASH with restaurants of the same type and in a comparable market. Comparing a Manchester bistro with a London fine dining restaurant makes little sense. The trend in your own figures over time is at least as important as the absolute value.

Occupancy Rate ≠ RevPASH: a visualisation

The visualisation above illustrates the core principle: RevPASH combines who is sitting with how long they sit and what they spend. Occupancy rate only captures the first element.

The 5 levers to lift your revenue per seat

Now that the insight is clear, the practical question arises: what do you do with it? Below are the five concrete levers that move RevPASH — work through them in order, from raising spend to cutting the empty time between guests.

1. Raise the average spend (menu engineering & upselling)

Every additional pound in average spend directly improves RevPASH. If your average spend increases by 10% — from £60 to £66 — your RevPASH also increases by 10%, without needing a single extra seat.

Menu engineering is the systematic approach to achieving this. You analyse which dishes are both popular and high-margin (the "stars") and position them prominently. Dishes with low popularity but high margins ("puzzles") get better presentation. Read our comprehensive guide to menu engineering for concrete techniques.

Particularly effective: beverage pairings and wine flights. A fine dining restaurant offering wine pairing can increase average spend by £40–70 per person. This has a disproportionately large effect on RevPASH because the food cost of drinks is typically lower than that of food.

For your most sought-after slots — Friday at 8 pm, Saturday at 7:30 pm — a minimum spend per person works in the same direction. Many fine dining restaurants in London, Manchester and Edinburgh already operate minimum spends of £65–£95 per person, or mandatory set menus for weekend evenings. This raises the average spend and, as a bonus, reduces no-shows: guests who have made a financial commitment are more likely to turn up.

2. Speed up table turnover without rushing guests

Faster, smoother turns convert the same seat-hours into more covers. The trick is to compress the service flow — order, fire, pay — not the guest experience.

A strategy that works successfully at some UK restaurants: offer two clear sittings — an early sitting at 6:30 pm with the table offered until 8:30 pm, and a late sitting at 8:45 pm. This increases effective table occupancy from once per evening to roughly one and a half times.

Concrete calculation for a fine dining restaurant (50 seats, 5-hour dinner service):

• Without sittings: 40 seats occupied, avg. spend £90, dwell time 3 hrs. RevPASH = (40/50) × (£90 ÷ 3) = 0.8 × £30 = £24
• With two sittings: Early sitting 30 guests × £75, late sitting 25 guests × £90. Total: £2,250 + £2,250 = £4,500 over 5 hours. RevPASH = £4,500 ÷ (50 × 5) = £18 — but with higher absolute revenue.

This reveals an interesting tension: more turnover increases absolute revenue but can sometimes lower RevPASH if per-sitting spends are lower. The right strategy depends on your concept and market positioning.

3. Fill your quiet hours and spread demand

Most restaurants measure RevPASH as a single daily average. This conceals enormous variation. Lunch and dinner are fundamentally different services in terms of dwell time, average spend and occupancy rate, and they call for different strategies.

A typical UK brasserie might have a lunch RevPASH of £8 (lower spend, faster turnover) and a dinner RevPASH of £18 (higher spend, longer dwell time). If you combine both, you get a figure of around £13 that lets you optimally manage neither lunch nor dinner. Measure RevPASH at minimum by daypart: lunch, early dinner (5:30–7:30 pm) and late dinner (7:30–10:30 pm).

Once you can see the quiet slots, you can deliberately move demand into them — early-bird menus, midweek offers, and an active waitlist that re-fills cancelled peak slots. See also our analysis of managing peak hours for additional context.

4. Optimise your table mix and capacity

One of the most overlooked RevPASH killers is inefficient table assignment. When you seat two guests at a four-person table, you lose two seat-hours of capacity. At a RevPASH of £20 per seat-hour and a service duration of 2 hours, this represents a loss of £80 per table turn.

How large is this effect in practice? Suppose you have 10 four-person tables and consistently seat two-person parties at them. You lose two seats per booking. Over a busy evening with eight such tables occupied: 8 × 2 seats × 2 hours × £20/hour = £640 in missed revenue.

The floor plan itself matters just as much. A restaurant with 60 seats that can never simultaneously serve more than 45 guests due to an illogical layout has a structural RevPASH ceiling. Analyse your floor plan on real booking data: which tables are least popular, which combinations are requested most often, where are the dead spots? A rearrangement based on analytics data can sometimes unlock 10–15% more effective capacity without expanding the premises. Smart table management then assigns the smallest available table that fits each party automatically.

5. Cut the empty time between guests (table reset & management)

Every minute a table sits empty between two parties is a seat-hour you never bill. The decisions your host makes when re-seating have a direct, measurable impact on RevPASH.

The three critical table management decisions that affect RevPASH:

1. Table assignment: Small parties at small tables, never at larger tables unless absolutely necessary. This requires knowing at all times which tables are available when.
2. Combining vs. separating: Splitting large parties across multiple small tables can sometimes yield higher RevPASH than one large table. But always communicate this transparently with guests.
3. Buffer and turn management: How much time do you allow between two occupancies of the same table? Too little buffer leads to overlapping guests; too much wastes seat-hours. Ten to fifteen minutes is generally realistic in a gastronomic setting.

With HappyChef's visual table plan, you see in real time which tables are occupied, reserved and free, including the expected availability time based on reservation duration. This enables proactive table reset and management rather than reactive.

Tracking RevPASH: a practical approach

The best data is data you collect consistently. Here is a practical framework for tracking RevPASH without drowning in spreadsheets.

Step 1: Define your measurement periods

Measure RevPASH at minimum per service (lunch / dinner), per day of the week and per month. Always compare with the same period last year to eliminate seasonal effects.

Step 2: Collect the base data

You need three inputs: total revenue per service (from your point-of-sale system), number of occupied seats per hour (from your reservation system), and total available seat-hours. The latter is simple: seats × operating hours per service.

Step 3: Calculate weekly averages, watch trends

An individual service with low RevPASH may be coincidental. The trend over four to six weeks is informative. Is your Friday evening RevPASH consistently declining? Action is needed. Is your lunch RevPASH rising after a menu change? Proof that the intervention is working.

Step 4: Use RevPASH as an action threshold, not a target

Set a minimum RevPASH per service. Services that consistently fall below that threshold demand specific action: adjusted pricing, promotions, or reconsidering whether that service is profitable at all. Some restaurants discover through RevPASH analysis that their Sunday lunch is systematically unprofitable after labour costs.

The HappyChef Analytics dashboard calculates and visualises occupancy patterns by daypart, enabling RevPASH analysis without manual spreadsheets.

RevPASH for fine dining restaurants: specific challenges

Fine dining restaurants in the UK — from the London fine dining scene to the country-house restaurant — face a specific RevPASH challenge. Their concept is inherently built on slow services, high spends and hospitality that takes its time.

A typical fine dining restaurant with:

• 50 seats
• 5-hour dinner service (6:30 pm–11:30 pm)
• Average spend £85 per guest
• 75% occupancy rate

Has a RevPASH: Total revenue = 50 × 0.75 × £85 = £3,187.50. RevPASH = £3,187.50 ÷ (50 × 5) = £3,187.50 ÷ 250 = £12.75.

That seems far from the benchmark of £20–30+. But raise the average spend to £115 (e.g. through wine pairing) and occupancy to 90%:

Total revenue = 50 × 0.90 × £115 = £5,175. RevPASH = £5,175 ÷ 250 = £20.70. That is a 62% increase purely by optimising two variables.

For fine dining restaurants the route to higher RevPASH rarely runs through faster service — that undermines the concept. Here it is almost exclusively via higher average spend (better wine list, culinary experiences, personalised recommendations) and higher occupancy (smarter reservation policy, better no-show prevention, active waitlists).

Also see how 2026 hospitality trends are shaping the way fine dining restaurants optimise their RevPASH — from experience-led concepts to personalised menus.

Conclusion: RevPASH as a compass for your restaurant business

RevPASH is not a magic number that answers every question. It is a compass: an instrument that indicates whether you are moving in the right direction. A rising RevPASH over six weeks means your adjustments are working. A falling RevPASH despite full dining rooms is a warning signal you cannot see if you only look at occupancy rate.

The five levers — raising average spend, speeding up turnover, filling quiet hours, optimising table mix and capacity, and cutting the empty time between guests — are all implementable without major investment. They do require good data and the discipline to follow that data.

That is precisely where HappyChef helps you. The Analytics dashboard gives you insight into occupancy patterns by daypart, and the visual table plan enables you to maximise every seat, every hour. Together they give you the data you need to turn RevPASH from a theoretical KPI into an active management tool.

Want to see how HappyChef can concretely help improve your RevPASH? Start free — 2 min and we will show you how other UK restaurants approach this.