Maximise Your Hotel's Revenue Potential Through Strategic Revenue Management

Revenue management is often used as a synonym for pricing. Yet rate is only one of the discipline's tools. What is being managed is the balance between four variables: which room is sold, to which guest, through which channel and at which moment. Get one of them wrong and the other three stop producing the right answer.

A hotel room is a perishable product: the room not sold tonight cannot be sold tomorrow at twice the rate, and it does not go into stock. Inventory is fixed, demand moves, and the moment of sale never returns. Revenue management is the method for finding the highest total revenue under those three constraints — not for chasing occupancy with discounts.

Four misconceptions come up most often in practice:

• “Revenue management means lowering rates.” Raising the rate needs doing just as often; most lost revenue comes from the days nobody raised.
• “If occupancy rises, revenue rises.” A full, cheap hotel can leave less profit than a less full one priced correctly.
• “This is for big chains.” The scale changes, the logic does not; a thirty-room property still makes an inventory decision every night.
• “Buying a system will solve it.” A system applies rules, it does not write them. In a hotel without structure it simply makes the wrong decision faster.

Revenue management is not a piece of software or a report but an order of decision-making. Its test: the same questions answered the same way every morning, and an answer that does not change depending on who is asked.

I always start in the same place: finding where revenue is leaking. The loss rarely comes from one large mistake but from small structural gaps that feed one another — and none of them appears as its own line in the P&L.

Filling this table with the hotel's own data is the first output of the work. Which row is largest cannot be known in advance; the order comes out differently in every hotel, and that order sets the priority.

The rate decision rests on the forecast. With no view of where demand is heading, the rate decision becomes a guess too. The forecasting discipline I build is not a complex model but a handful of numbers read regularly.

The value of a forecast lies in its regularity rather than its precision. A forecast produced the same way every week and compared against actuals teaches the hotel its own demand behaviour within a few months. The direction of the variance — consistently high or consistently low — says more than the forecast itself.

1. 01Clean the history — unusual periods in last year's data (closures, refurbishment, one-off events) are flagged; comparisons made without flagging them mislead.
2. 02Build the demand calendar — events, holidays, school terms and changes in city supply are mapped onto dates.
3. 03Read OTB and pace — today's business on the books is compared against the same point last year.
4. 04Break it down by segment — instead of total occupancy, which segment is arriving and in what volume; the total can hold while the mix deteriorates.
5. 05Write the forecast — occupancy and ADR for the next 90 days are recorded date by date.
6. 06Tie it to rate and restriction decisions — a forecast that stays a report has done no work; every forecast should carry an action.
7. 07Compare against actuals — the variance is measured and the method corrected. This step is how the forecast learns.

A hotel's revenue is determined less by how many rooms it sells than by whom it sells them to. Transient guests, corporate accounts, agencies, groups and extended stays each bring a different rate, a different cost and a different level of ancillary spend. Managing the segment mix means allocating inventory to the demand that leaves the highest total value.

This decision takes its most concrete form in group and corporate quotes. If accepting a group means giving up transient sales on the same dates, the number the quote should be compared against is not the cost of an empty room:

Where a hotel has no occupancy problem, a group usually costs revenue; on dates that would otherwise sit empty, the same group earns everything above the floor rate. What decides between the two is not the group but the demand on those dates. Once this calculation is written down, the quote stops depending on who prepares it.

The test for a segment decision is not ADR but the total net value it leaves per room night: room revenue after commission, plus ancillary spend, minus the cost that segment brings with it.

The consultancy does not end with a report; the aim is to leave an order that runs inside the hotel. The sequence is usually this:

1. 01Current state analysis — 12 to 24 months of PMS data, segment and channel breakdown, rate history and competitive position are reviewed. The leak table above is filled in with the hotel's own numbers.
2. 02Settling the definitions — available rooms, gross versus net ADR and segment definitions are written down. Skip this and every later report is disputed.
3. 03Demand calendar and forecasting rhythm — an annual calendar is built and the 90-day forecast cycle begins.
4. 04Rate and restriction architecture — reference rate, floor and ceiling, room type differentials, rate fences and restriction rules are defined.
5. 05Channel and segment strategy — which rate appears in which channel, how much inventory each segment receives.
6. 06Building the decision routine — daily and weekly meeting structure, who looks at what, which threshold triggers which action.
7. 07Connecting the reporting — the measurement structure for tracking decisions is set up; the detail of that side belongs to the performance reporting work.
8. 08Handover — training for whoever will sustain the decisions. If the structure does not stay inside the hotel, the work is only half done.

Not every hotel needs all of these steps. Where the rate architecture is already settled, the weight shifts to segment and channel; in a newly opening property, calendar and forecast are built from nothing.

No; one sits inside the other. Dynamic pricing answers the question “what should the rate be for this date?” Revenue management places inventory, segment, channel and timing beside the rate: should I sell this room today at this rate, or hold it for demand of higher value?

In practice the two are built together. Revenue management cannot be applied without a rate architecture; and without inventory and segment decisions, dynamic pricing collapses into simply moving rates around. How the rate architecture is built is set out in detail on its own page, reachable from the service links further down.

• A revenue leak map — the loss points, filled in with your own data and put in priority order.
• A definition set — available rooms, ADR, segment and channel definitions written down.
• A demand calendar — a full-year view with events, seasons and day types.
• A forecasting rhythm — the 90-day template, the production cycle and variance tracking.
• Rate and restriction architecture — reference rate, limits, derived rates and restriction rules.
• Segment and channel strategy — how inventory is allocated, and the displacement calculation for group quotes.
• A decision routine — daily and weekly meeting structure, thresholds and responsibilities.
• Handover — training for whoever sustains the decisions, and the flow written down.

The outcome is not a document but a working order. The test is simple: if the same questions are still answered the same way every morning after the consultancy ends, the work was built properly.