Key takeaways
- RevPASH is revenue divided by available seat-hours; it shows which dayparts use your dining room well and which leave it idle.
- Split it into seat occupancy and revenue per seat-hour used, because the fix for an empty room differs from the fix for a slow turn.
- Peak dayparts improve through pacing, table mix and reliable reservations; slow dayparts improve through demand.
- Roughly 8 in 10 off-premises customers say they would use discounts for ordering on less busy days or times[1].
What RevPASH measures
Revenue per available seat-hour divides the revenue earned in a period by the number of seats multiplied by the hours the room is open. A dining room with 80 seats open for a five-hour dinner has 400 seat-hours to sell. Hotels learned decades ago that an unsold room night is gone forever; an empty seat at 7:30 on a Friday is the restaurant version.
Average check and covers each tell half the story. A Friday with high covers and a modest check can earn more per seat-hour than a Tuesday with a high check and a half-empty room. RevPASH puts both on one scale and lets you compare dayparts, days of the week and seating layouts fairly.
How to calculate it
Fix the seat count
Count the seats you can actually sell, including bar seats if they take reservations or walk-ins for dinner. Leave out seats you never use.
Define dayparts
Split the week into periods that behave differently, such as weekday lunch, weekday dinner, Friday dinner, Saturday dinner and weekend brunch.
Calculate available seat-hours
Multiply seats by the open hours in each daypart, then by the number of days in the period.
Pull revenue by daypart
Use net sales from the POS for dine-in only. Takeout and delivery revenue does not use a seat, so report it separately.
Divide
RevPASH equals dine-in revenue divided by available seat-hours. Calculate it for four weeks and compare like with like.
Worked Example: one dining room, five dayparts
This fictional Example uses an 80-seat restaurant and one representative day in each daypart.
| Daypart | Hours | Seat-hours | Dine-in revenue | RevPASH |
|---|---|---|---|---|
| Weekday lunch, 11 to 2 | 3 | 240 | $1,450 | $6.04 |
| Weekday dinner, 5 to 10 | 5 | 400 | $4,100 | $10.25 |
| Friday dinner, 5 to 10 | 5 | 400 | $9,600 | $24.00 |
| Saturday dinner, 5 to 10 | 5 | 400 | $10,400 | $26.00 |
| Sunday brunch, 10 to 2 | 4 | 320 | $5,200 | $16.25 |
The spread is the point. In this Example a Saturday seat-hour earns more than four times a weekday lunch seat-hour. The weekend needs speed and precision; the weekday needs guests.
Break it into the parts you can manage
RevPASH can be rewritten as seat occupancy multiplied by revenue per seat-hour used. Occupancy is covers multiplied by average dining duration, divided by available seat-hours. Revenue per seat-hour used is average check divided by average duration.
In the Example, Friday dinner served 240 covers at a $40 average check with a 90-minute average duration. Those covers used 360 of 400 seat-hours, a 90% occupancy, and earned about $26.67 per seat-hour used; 90% of $26.67 is the $24.00 RevPASH. A weekday dinner served 100 covers at $32 with a 75-minute duration, so it used 125 seat-hours, about 31% occupancy. Its revenue per seat-hour used is a healthy $25.60; the problem is the empty room, not the check.
Where to get the data, and what to watch for
Most POS systems can export net sales and covers by hour. Your reservation system adds party size, booked time and actual seated and closed times, which is how you measure dining duration. Pull four weeks so a single rainy night does not drive the answer.
- Use closed checks, not opened checks, and decide how to treat checks that span two dayparts.
- Exclude private events from the regular dining room numbers, or report them separately; a buyout makes a slow Tuesday look like a Saturday.
- Count the bar separately if bar guests behave differently from dining guests, since their duration and check differ.
- If you change opening hours during the period, recalculate seat-hours for each day rather than using one average.
Example: from RevPASH to a pacing plan
Pacing is where RevPASH turns into action at peak. In this fictional Example, the kitchen can comfortably fire about 30 covers in any 15-minute window on a Friday. The current book lets guests choose any time, so 7:00 to 7:30 fills with 70 covers while 5:00 to 6:00 holds 40. Tickets back up, turns slow down, and the second seating starts late. The manager caps each 15-minute slot at 30 covers, opens 5:30 and 8:45 slots with a small dessert offer, and asks the host to quote realistic times to walk-ins. Over the next four Fridays the average duration falls by about ten minutes because tickets move, not because guests are rushed, and the room fits one more partial turn. The kitchen is calmer and the late slots that used to sit empty now carry covers.
Check your table mix
Seat-hours are lost when party sizes and table sizes do not match. Pull a month of party sizes from the reservation system and compare them with your floor plan. If most parties are twos and your room is mostly four-tops, every couple wastes two seats for the whole meal. Tables that can be split and pushed together, or a few more deuces along a banquette, often lift occupancy more than any marketing effort. Do the same check for large parties: if groups of eight arrive regularly, have a plan for joining tables that does not block the room for an hour.
Moves for peak dayparts
- Pace reservations by kitchen capacity in 15-minute slots so the line is not hit by twenty covers at once.
- Match table sizes to party sizes. A couple seated at a four-top wastes half the seat-hours of that table.
- Shorten idle time, not the guest's meal: faster greeting, check drop when asked, quick bussing and resetting.
- Protect the book from no-shows. Diners see holding a table for a stated period, typically 15 minutes, as fair[2], so state the hold time when you confirm.
- Answer the phone at peak. At top US restaurants surveyed by Cornell, 49% of reservations came by telephone[3]; an unanswered call at 6:45 is an unsold seat-hour.
Moves for slow dayparts
- Create a reason to come: a set lunch, a weekday tasting, a neighborhood night or a standing group booking.
- Use time-based offers carefully. Roughly 8 in 10 off-premises customers say they would take advantage of discounts for ordering at less busy times[1], and the same logic applies to dine-in early seatings.
- Reduce seat-hours when demand will not come: close a section, shorten hours or open the patio only on strong days.
- Make booking easy at any hour. Cornell found that 59% of restaurants using online reservations saw sales rise as a result[4].
Reputation moves the ceiling
Peak RevPASH has a ceiling set by demand. A UC Berkeley study of San Francisco restaurants found that moving from 3 to 3.5 Yelp stars raised the chance of selling out at prime times from 13% to 34%[5]. Pacing and table mix help you capture demand; reputation decides how much there is to capture.
Source: University of California, Berkeley, 2012[5]
Show the data
| Item | Value |
|---|---|
| 3 stars | 13% |
| 3.5 stars | 34% |
Price by daypart, with care
Once you can see the gap between peak and slow dayparts, pricing becomes a tool as well as pacing. A prix fixe that is only offered at early seatings, a weekday lunch set, or a bar menu that runs until the dinner rush gives value-minded guests a reason to fill seat-hours you would otherwise lose. Avoid surcharges on peak times, which guests tend to resent; a discount for a quieter slot feels like a reward, while a premium for a busy one feels like a penalty. Measure the result in RevPASH for the slow daypart and watch that the offer does not pull guests away from the peak slots they would have paid full price for.
Review it every month
Report RevPASH by daypart next to sales per labor hour so you can see whether a busy daypart is also a well-staffed one. If RevPASH rises because you raised prices, check that occupancy held; if it rises because occupancy grew, check that the kitchen kept up. Change one lever at a time so the cause stays clear.
Frequently asked questions
What is a good RevPASH for a restaurant?
There is no universal target because concept, check size and hours differ. Compare your own dayparts with each other and with the same daypart last year, and track the trend.
Should takeout revenue be included in RevPASH?
No. Takeout and delivery do not use a seat, so including them inflates the number. Track off-premises sales separately.
How do I increase RevPASH without rushing guests?
Cut idle time between seatings, match table size to party size, pace reservations to kitchen capacity and reduce no-shows. The meal itself should not feel shorter.
Does RevPASH work for counter-service restaurants?
It can, for seated areas, but for counter service the more useful measures are sales per labor hour and orders per hour at the counter and drive-thru.
References
National Restaurant Association (2025). Report: Takeout, drive-thru, delivery are more popular than ever (opens in a new tab) ↑
Cornell University Center for Hospitality Research (Sheryl E. Kimes) (2008). A Consumer's View of Restaurant Reservations Policies (Cornell Hospitality Report, 2008) (opens in a new tab) ↑
Cornell University Center for Hospitality Research (Kimes and Kies) (2012). The Role of Multi-Restaurant Reservation Sites in Restaurant Distribution Management (Cornell Hospitality Report, 2012) (opens in a new tab) ↑
Cornell University Center for Hospitality Research (Sheryl E. Kimes) (2009). How Restaurant Customers View Online Reservations (Cornell Hospitality Report Vol. 9, No. 5) (opens in a new tab) ↑
University of California, Berkeley (2012). Yelp reviews boost restaurant business (Anderson and Magruder, Economic Journal) (opens in a new tab) ↑