What RevPASH Tells a Restaurant

Consider a Chennai dinner report showing ₹36,000 in sales. The team also needs the seat count and opening hours. A room with 40 seats open for three hours has a different capacity from the same room open all afternoon and evening.

Longer visits also have a commercial purpose. In an August 2026 ET HospitalityWorld opinion, Manvir Singh Anand argues for designing longer dining occasions. That is an operator’s argument, not evidence that every Indian restaurant should lengthen dinner.

Calculate one complete service first

Start with a service whose opening, last guests and table resets all fit within the measured window. Use the full window consistently; cutting it off while customers remain creates an allocation problem.

RevPASH = dine-in revenue ÷ available seat-hours

For a constant seat count, available seat-hours are seats multiplied by hours. The figures below are chosen illustrations, not Mikro customer results, recommended prices or industry targets.

Dinner B earns more total revenue than A. It also uses an extra hour, leaving revenue per available seat-hour unchanged. Whether that extra hour is worth opening depends on its costs and the business it brings.

Dinner C earns more from the same seat-hours. The sheet still cannot explain whether guests paid higher prices, ordered more, received fewer discounts or filled seats that had previously been empty. Keep covers and average spend beside the result so the team can investigate the change.

Nor does ₹350 establish a good target. A quick lunch, a family dinner and a long tasting menu have different prices, service promises and costs. Begin with matching services at the same restaurant, with festival dates and unusual closures noted alongside them.

Define the seats and sales you count

An empty seat remains in the denominator while it is available for service. Counting only occupied seats would hide the unused capacity the measure is supposed to reveal.

For the proposed working sheet, retain the normal floor plan and record any closure separately. If a section cannot open because there are too few staff, show the capacity lost as well as the capacity actually offered. Otherwise a smaller denominator can make a difficult shift appear to improve.

When availability changes during service, calculate each interval separately and add its seat-hours. For example, 40 seats for two hours plus 20 seats for one hour gives 100 available seat-hours. These are illustrative quantities; the floor log supplies the real ones.

Gary Thompson and Heeju Sohn’s 2009 paper excludes taxes, tips and service charges from RevPASH, and separates takeout from revenue earned using dining seats. For this sheet, also apply discounts and refunds consistently. Document the basis with the export.

Delivery can use the same kitchen while adding no dining-room covers. Including it in seat revenue could make a delivery promotion look like better use of the floor. Its cash reconciliation belongs in a separate view; the delivery payout guide explains why sales and bank receipts can differ.

Check where the bill lands in the hour

A bill can open in one hour and close in another. Assigning its full value to either timestamp concentrates revenue into a single block even though the party used the table across both.

Thompson and Sohn found check-open allocation less accurate than spreading revenue over check-open to check-close time. Their fuller service-cycle method runs from committing the table to a party until it has been cleared and reset. POS timestamps alone can miss both ends. This is historical measurement research, not a current Indian trading benchmark.

Consider an illustrative ₹2,400 bill occupying its full recorded service cycle from 7.30 pm to 9 pm. A time-proportional allocation puts ₹800 into the first 30 minutes and ₹1,600 into the following hour. Those amounts sum to the same ₹2,400. They describe capacity use, not when individual dishes were ordered or cash arrived.

If the POS cannot supply trustworthy timing, keep the whole-service figure and label hourly results as approximate. A short manual observation can check whether bills close promptly and whether payment is followed by a long wait before the table is ready. Fixing a timestamp habit may change the hourly report without changing a single sale.

Faster meals need a waiting customer

Shortening a meal creates an opportunity only when another party can use the time released. The kitchen must also be able to serve that party. A quieter room may finish dinner earlier without selling another cover.

Thompson’s separate 2009 simulation study tested the assumption that shorter dining duration produces a proportional revenue increase. The simulated gains were much smaller; demand intensity, peak-window length and willingness to wait affected the result. The study does not provide a savings forecast for a Chennai outlet.

Guest experience adds another limit. Noone, Kimes, Mattila and Wirtz’s 2009 study found satisfaction rose with perceived pace only up to a point, then fell. Respondents tolerated a faster pace more after the meal than during earlier stages. It gives a reason to examine payment delays separately from eating time, without prescribing a universal dinner duration.

A higher sales figure can also carry higher ingredient costs or discounts. The menu contribution guide helps test what the sold dishes leave after food cost. Keep that cost view beside seat revenue before changing the menu or adding a late service.

Keep a service sheet the team can repeat

The following is a proposed operating routine, rather than a tested promise of uplift. Start with a comparable lunch or dinner and explain any changed hours, sections, prices or promotions.

For a group reviewing several outlets, preserve those outlet-level notes. Same-store sales answers the separate question of whether the mature estate grew. A seat-hour calculation adds capacity context; neither measure replaces the other.

Frequently asked questions