revpash for private events: the metric that changes how you allocate your room

Revenue Per Available Seat Hour was introduced by Cornell University's School of Hotel Administration in 1998. It measures how much revenue each seat generates per hour, combining occupancy and spend into a single number. Hotels use RevPAR. Airlines use revenue per available seat mile. Restaurants use RevPASH.

The metric is well understood for regular dining. It's almost never applied to private events. That's a missed opportunity, because RevPASH is the single best metric for deciding whether a given time slot should be an event night or a regular service night. And the answer isn't always what operators expect.

the formula

For regular dining: divide the total revenue from a service period by the number of seats in the room times the number of hours the restaurant was open for that period.

For private events: divide the total event revenue by the number of seats used for the event times the number of hours the event ran.

The unit is dollars per seat per hour. A higher number means the room is earning more per unit of capacity per unit of time.

regular dining revpash

Take a 100-seat restaurant running a Thursday dinner service from 5pm to 10pm (5 hours). Revenue for the evening: $6,800.

RevPASH = $6,800 / (100 seats × 5 hours) = $13.60 per seat per hour.

That number includes occupied seats and empty ones. It captures both the spend per guest and the utilization of the room. If 70 of 100 seats are occupied and average check is $68, total revenue is $4,760 and RevPASH drops to $9.52. RevPASH rewards both high check and high occupancy, which is why it's a better management metric than average check or cover count alone.

Industry benchmarks for regular-service RevPASH vary widely by concept: fast casual runs $5 to $10, full-service casual $10 to $18, upscale $18 to $35. Most independent restaurants don't track it.

event revpash

Same 100-seat room, same Thursday evening. Instead of regular service, the room hosts a corporate dinner for 50 guests from 6pm to 10pm (4 hours). F&B minimum: $4,500. Actual spend: $5,200.

RevPASH = $5,200 / (50 seats × 4 hours) = $26.00 per seat per hour.

The event RevPASH is nearly double the regular dining RevPASH on the same night, with half the seats and a shorter window. Every seat the event used earned twice as much per hour as a seat during regular service.

This is the comparison that changes decisions. The GM looking at $5,200 in event revenue versus $6,800 in regular service revenue thinks regular service is the better night. The GM looking at RevPASH per seat per hour sees the event as the more efficient use of the room.

why the per-seat-per-hour comparison matters

Gross revenue comparisons between events and regular service are misleading because they don't account for two things: the number of seats used and the time window.

An event that uses 50 of your 100 seats for 4 hours leaves 50 seats for regular service (if the event is in a private room) and occupies the room for a shorter window than a full dinner service. The remaining capacity and the shorter time commitment both have value.

A full buyout uses all 100 seats and shuts down regular service entirely. In that case, RevPASH is the direct comparison: did the event earn more per seat per hour than regular service would have?

worked comparison by day of week

Here's where the framework gets practical. The decision to accept an event booking should be different on Tuesday than on Saturday.

The day-of-week RevPASH comparison tells you where events are unambiguously worth it (Tuesday through Thursday for most venues), where they're still positive but close (Friday and Saturday at busy venues), and where you should hold for regular service (Saturday at high-volume concepts during peak season).

the contribution margin layer

RevPASH measures revenue efficiency. Contribution margin measures profit efficiency. The complete comparison layers both.

Events carry lower food cost (22 to 28% versus 30 to 35% on regular service) and lower labor cost per revenue dollar (16 to 20% versus 30 to 35%). So an event with the same RevPASH as regular service produces a higher contribution margin per seat per hour.

To calculate contribution-margin-adjusted RevPASH: (Revenue − Food Cost − Labor Cost) / (Available Seats × Hours).

For the Thursday example above: Regular: ($5,600 − $1,792 food at 32% − $1,792 labor at 32%) / (100 × 5) = $4.03 per seat per hour. Event: ($5,200 − $1,300 food at 25% − $936 labor at 18%) / (50 × 4) = $14.82 per seat per hour.

On a contribution-margin basis, the event produces 3.7x more per seat per hour than regular service. This is the number that belongs in your monthly executive summary.

how to start tracking it

One: Calculate regular-service RevPASH by day of week. Pull revenue for each day of the week over the last 90 days. Divide by seats times hours for each. You'll have seven numbers. These are your baselines.

Two: Calculate event RevPASH for every confirmed event. Revenue / (seats used × hours). Track it alongside regular RevPASH in the same report.

Three: Set a minimum event RevPASH threshold per day. Any proposed event that falls below your regular-service RevPASH for that day of the week is a net loss in room efficiency. Quote higher, move the event to a lower-demand day, or pass. This threshold protects you from underpriced bookings that look like revenue but cost you capacity.

Use the event vs. regular dining calculator to run the RevPASH comparison for your venue with your numbers. The output shows RevPASH for both, the contribution-margin layer, and the day-of-week breakout.

RevPASH is not new. Applying it to private events is. The venues that track it make better decisions about which bookings to take, which to negotiate, and which to leave for regular service.