Revenue management for a dining room

At eight o'clock on a Saturday, a table for four sits empty because it was held for a party of two who booked at seven and are lingering over coffee, while a group of four waits at the bar and eventually leaves. On Tuesday at the same hour, half the room is empty. Over a year, those two moments, the empty seat at the peak and the empty room in the trough, cost a restaurant more than almost anything else. Revenue management is the discipline of reducing both.

Hotels and airlines have practised revenue management for decades. They sell something that perishes: a room unsold tonight, or a seat unsold on today's flight, can never be sold again. A restaurant's seats perish the same way. An empty chair at eight on a Saturday is lost for good. The tools hotels use, matching price and availability to demand, translate to dining rooms, but only partly, and the parts that do not translate can damage a restaurant if they are forced.

This guide covers what revenue management means for a restaurant, the two levers it works with, what a dining room can and cannot yield, the measures that matter and where to start. Every venue and figure in it is an example.

Revenue management is the practice of selling a fixed, perishable capacity to the right customers at the right time and price, to earn the most from it. It began in airlines, spread to hotels and car hire, and is now used wherever capacity is limited and demand varies.

In a restaurant, the capacity is seats over time: each seat, for each hour of service. The aim is to fill as much of that capacity as possible, with guests who spend well, without making the experience worse for anyone.

Revenue management fits a dining room because the conditions are the same as in a hotel. Capacity is fixed: the room has so many seats. It is perishable: an hour of an empty seat cannot be stored. Demand varies: Saturday night is full, Tuesday afternoon is empty. And guests differ: some want a quick lunch, some a long celebration.

Those conditions mean that how the capacity is used, and when, matters as much as how much each guest spends. A venue that understands its own demand can arrange its capacity to serve more guests, better, at the times they want.

A restaurant sells food and drink, but it also sells time at a table. A party of four that spends two hours at a table on a Saturday uses eight seat-hours of the venue's most valuable capacity. The same party on a Tuesday uses eight seat-hours that would otherwise be empty.

Seeing it this way changes the questions. Not only "how much did they spend?" but "how much did they spend for the seat time they used, and when?" That is the heart of revenue management in a dining room.

Revenue management in a restaurant works with two main levers. Price: what guests pay, which can vary by time of day, by menu and by package. Duration: how long guests use the table, which is shaped by booking lengths, pacing and the flow of the meal.

Hotels lean heavily on price. Restaurants usually lean more on duration and on how the room is filled, because guests are far more sensitive to price changes on a menu than to the price of a hotel room on a given night. The best results usually come from managing duration and demand well, with price used carefully.

A dining room can manage several things without upsetting guests:

Each of these changes how the capacity is used, without asking any guest to pay more for the same thing at a busier moment.

Some hotel practices do not translate. Raising the price of the same dish on a busy night, the equivalent of a hotel's peak-night rate, is usually resented by restaurant guests, who expect a menu price to be a menu price. Charging regulars more because they will come anyway damages the relationship that keeps them coming. Rushing guests to free tables makes the experience worse and loses them.

Revenue management that guests feel as unfair is a short-term gain and a long-term loss. In a restaurant, the tools that work are the ones guests barely notice: better use of tables and times, menus suited to each part of the day and reasons to come when the room is quiet.

Revenue management starts with knowing demand: when the room fills, when it empties and how that pattern changes through the week and the year. Look at bookings and walk-ins by day and hour, and at which times are turned away and which sit empty.

Most venues know roughly when they are busy. Fewer know exactly. A clear picture of demand, hour by hour, shows where the peaks are tight enough to need careful management and where the troughs are deep enough to need filling.

Capacity utilisation measures how much of the room's capacity is used: the seat time used as a share of the seat time available. It shows how full the room really is, across the whole service, rather than how full it feels at the busiest moment.

Most rooms are far from full when measured across the whole service, even on nights that felt busy. Our guide to capacity utilisation: how full is full? covers how to measure it and what a realistic ceiling looks like.

RevPASH, revenue per available seat hour, combines price and duration in one number: the revenue earned, divided by the seat-hours available. It shows how much each hour of each seat earned, and it rises when either spend goes up or more of the room's capacity is used.

It is the closest restaurant equivalent of the measures hotels use. Our guide to RevPASH: revenue per available seat hour covers how to calculate it from data most venues already have.

Yield per table looks at each table's revenue for the time it was available: how much a table for two by the window earned compared with a table for six in the corner. Some tables earn far more than others, because of their size, their position or how often they turn.

Knowing which tables yield most helps decide how to offer them: the best tables for the bookings that use them well, flexible tables combined or split to fit the parties that come, and tables that earn little looked at again.

The table mix, how many twos, fours and sixes the room has, decides how well the room fits the parties that come. A room full of fours, serving mostly couples, wastes half its seats at the busiest times. A room with too few large tables turns away groups.

Matching the table mix to the party sizes that book is one of the most effective changes a dining room can make. Our guide to table mix: how many twos, fours and sixes covers how to work out the right mix.

Turn times, how long a party typically uses a table, drive how many seatings a table can host in a service. Knowing the usual turn time for each party size and service lets the venue set booking lengths that match reality, so tables are neither held empty too long nor double-booked.

Turn times also show where the meal could flow better without rushing anyone: a long wait for the bill, slow clearing, a gap before dessert. Our guide to turn times: the number every booking rule needs covers how to measure and use them.

Booking rules are among the most powerful revenue tools a restaurant has, and among the least used. Which times are offered, how long each booking lasts, which tables can be booked online and for which party sizes, and how far ahead: each decides how the room's capacity is sold.

A rule that offers every table at every quarter hour, for any party, may fill the diary in a way that leaves awkward gaps. Rules shaped to the venue's demand and turn times fill it in a way that leaves room for the next seating.

Booking capacity is how many covers the diary should accept for each time and service, leaving room for walk-ins, for the kitchen's pace and for the next seating. Too few and the room sits partly empty; too many and the kitchen is overwhelmed and guests wait.

Setting it well is a balance that depends on the venue's kitchen, its walk-ins and its turn times. Our guide to booking capacity: how full should the diary be? covers how to find it.

Pricing by daypart, different menus and prices for different parts of the day, is the most accepted form of price management in restaurants. A set lunch, an early-evening menu and a full dinner menu each suit different guests and different levels of demand, and guests readily accept that lunch costs less than dinner.

It works because each daypart has its own menu, rather than the same dish costing different amounts at different hours. Our guide to pricing by daypart: lunch is not dinner covers how to set it up without confusing anyone.

Set menus and packages are another accepted price tool. On busy nights, a set menu can make the kitchen's night easier, keep turn times predictable and hold spend steady. For groups, a set menu or package agreed in advance makes the booking more valuable and more predictable.

They also suit quiet nights in a different form: a midweek set menu at a fixed price gives guests a reason to come when the room would otherwise be empty, without lowering the price of the regular menu.

Quiet night trade is the other half of revenue management. Filling the troughs, the quiet weeknights and afternoons, adds revenue from capacity that would otherwise earn nothing. Every guest on a quiet Tuesday is almost pure contribution, because the room, the kitchen and much of the team were already paid for.

The tools are invitations to regulars, events, set menus and a reason to come midweek. Our guide to quiet night trade: filling Monday honestly covers what works without training guests to wait for discounts.

Some guests can be encouraged to move from the peak to the shoulders: from eight on Saturday to six or half past nine, from Friday to Thursday. A guest who is offered a good table at seven instead of a squeeze at eight may be happy to move, and the venue serves both them and the guest who takes the eight o'clock table.

Offer alternatives when the peak is full, rather than simply saying no. "We are full at eight, but we have a lovely table at half past six or a quarter past nine" often keeps the booking and spreads the room's demand.

The peak, the busiest hours of the busiest nights, is the most valuable capacity a venue has. Protect it. Avoid filling it with promotions that lower spend, hold larger tables for larger parties rather than couples where you can, and make sure the meal flows well so tables are ready for the next seating on time.

Do not discount the peak. Guests who would come anyway do not need a reason, and every discount at the peak is margin given away on capacity that would have sold at full price.

Large groups can be very valuable or very costly, depending on how they are managed. A group of twelve on a Saturday uses several tables at the peak; if it spends well and stays a sensible time, it is a good booking. If it lingers, orders little and blocks tables that could have seated two parties, it may earn less than the tables it displaced.

Set menus, agreed timings and, where the venue uses them, minimum spends for private areas help make large groups worthwhile. Agree the arrangements when the group books, so there are no surprises on the night.

No-shows waste peak capacity: a table held for a party that never arrives earns nothing. Reminders, confirmed contact details and an easy way to cancel reduce them, and a standby list can fill the tables that still come free.

Some venues overbook to allow for no-shows, as airlines do. It is risky in a restaurant, because a guest with a booking who cannot be seated is likely to be lost for good. Most venues do better reducing no-shows and keeping a standby list than gambling on overbooking.

Bookings through different channels earn different amounts. A booking made directly, through the venue's own page or by phone, carries no commission. One made through a platform that charges a fee per cover earns less for the same table. Over a year, the difference can be large.

Encouraging regulars and returning guests to book directly is a quiet form of revenue management: the same guests, at the same tables, earning more for the venue.

A second sitting, two planned seatings at each table on a busy night, is one of the most direct ways to use peak capacity better. Done well, it can add many covers to the busiest nights. Done badly, it rushes the first sitting and keeps the second waiting.

It depends on realistic turn times, firm booking times and a kitchen and floor that can keep the first sitting on time without hurrying guests. Our guide to two sittings on a Friday: worth the risk? covers when it works.

Revenue management is not rushing guests, charging more for the same dish at busy times, squeezing tables closer than is comfortable or treating guests as yield rather than people. Practices like these may raise revenue for a few weeks and then lose the guests who made the venue worth visiting.

Done well, it is invisible. Guests find a table at a time that suits them, a menu that suits the hour and a room that feels comfortable rather than crammed. The venue earns more because its capacity is used well, not because its guests feel squeezed.

Start with three steps. First, measure: look at when the room fills and when it empties, and work out utilisation and revenue per seat hour for each service. Second, fix the booking rules: set booking lengths and times that match your turn times, and match tables to party sizes. Third, fill the troughs: give guests a reason to come on the quietest nights.

These three usually produce the largest gains for the least risk. Price tools, such as daypart menus and set menus, come next, once the room's capacity is being used well.

Measure progress with a few numbers, service by service: utilisation, revenue per seat hour, covers, spend per cover and the number of guests turned away at the peak. Compare each month with the same month last year.

Watch guest measures too: feedback, complaints about waits or rushing and the share of guests who return. Revenue management that raises revenue while guests become less happy is borrowing from the future.

In a group of venues, revenue management can work across venues as well as within each one. A guest turned away at a full venue can be offered a table at a sister venue nearby. Demand that is too high at one venue on a Saturday may fill another's quieter evening.

Each venue still needs its own measures and its own booking rules, because each has its own room, guests and demand. But sharing what works, and pointing guests between venues, lets the group earn more from its total capacity.

An invented bistro is full at eight on Saturdays and half empty on Tuesdays. The owner measures utilisation and finds that, across the whole Saturday service, the room is only about two thirds used: tables are held too long, couples sit at fours and the early and late slots are rarely offered. Tuesday's utilisation is under a third.

She sets booking lengths from the bistro's actual turn times, offers fours to couples only when no twos are left and suggests half past six or a quarter past nine when eight is full. On Tuesdays, she starts a set menu supper for regulars. Over three months, Saturday serves more covers without anyone feeling rushed, Tuesday fills steadily and revenue per seat hour rises across the week.

servearound gives a dining room the inputs revenue management needs, though it does not set prices or limits for you. Table analytics show utilisation, the time each table had a party against the service time the venue's shifts make available, along with seatings, revenue per seated hour, revenue per seat and unsold service minutes by table, the gap between seatings, results by zone and a heatmap of when the room fills.

Booking rules set the times offered for each shift, a single booking duration in minutes, the largest party and the notice needed, and each table's rules set whether it can be booked online, for which party sizes, how far ahead and on which days and hours. There is no automatic limit on covers per time slot, so pacing is set by the times you offer. Menus can be scheduled by days and times, with only one menu running at a time, so a lunch menu and a dinner menu can carry different prices. See Analytics and the reservations module.

Using the room's seats and time as well as possible, matching availability and menus to demand to earn the most from fixed capacity.

No. In restaurants, it works mainly through booking rules, table use, daypart menus and filling quiet times.

Booking times and lengths, table allocation, daypart menus, set menus, demand spread and booking channels.

Raising the price of the same dish at busy times, charging regulars more and rushing guests.

Measure when the room fills, fix booking rules to match turn times and table sizes, and fill the quietest nights.

Revenue per available seat hour: revenue divided by the seat-hours the room had available.

Usually not. Reduce no-shows and keep a standby list instead.

Watch utilisation, revenue per seat hour and covers, alongside guest feedback and return rates.

Revenue management for a dining room borrows the hotel discipline of selling perishable capacity well: every empty seat at the peak and every empty room in the trough is revenue lost for good. In a restaurant, it works mainly through duration and demand, using booking rules, turn times, table mix and quiet night trade, with price used carefully through daypart menus and set menus rather than raising the price of the same dish at busy times.

Start by measuring capacity utilisation and revenue per seat hour, then match booking lengths and tables to how guests actually dine, offer other times when the peak is full, protect the peak from discounts and give guests reasons to come on quiet nights. Watch yield per table and guest feedback together, and remember that revenue management done well is invisible to guests.