Introduction to Total Revenue Management

Early July, the half-year review. Adam arrives at Daniel’s desk with two monthly reports and lays them side by side.

“Daniel, look at these two months. April and June. RevPAR is 75.6 EUR in both — identical to the cent. At the monthly meeting we said the same thing both times: stable, on plan. Then the accountants closed the half-year and I looked at total hotel revenue. April: 244 thousand euros. June: 214 thousand. Thirty thousand euros of difference between two months that our own report shows as identical. Where is that money?”

Daniel looks at the two columns of numbers and knows the answer exactly. “The money is where RevPAR cannot see: in the restaurant, the meeting rooms, the spa. April had two conference groups and strong corporate weeks — full meeting rooms, guests eating lunch and dinner in-house. In June we posted our highest June occupancy ever, with OTA leisure guests who left after breakfast and came back at ten at night. At room level the two months really are identical. At hotel level they are not.”

This scene is the blind spot of room-focused revenue management — and the subject of this lesson. In the previous 44 lessons we almost always optimised room revenue: rate, mix, channel, group decisions. Total Revenue Management says it out loud: room revenue is a sub-goal — and whoever optimises for a sub-goal will sometimes decide against the whole. This lesson is an introduction: we lay down the mindset and the decision logic; the deeper outlet-level methodology (spa, F&B and MICE yield) comes at expert level, in lesson 58.

TRevPAR as the target KPI

We introduced TRevPAR (Total Revenue per Available Room) in lesson 4 and broke it down by segment in lesson 30. The base formula, as a reminder:

TRevPAR = total hotel revenue / available room nights

What is new at this level is not the formula but the role. So far TRevPAR was a reporting metric: it showed, after the fact, how much the guest was worth beyond the room rate. In Total Revenue Management, TRevPAR steps up to a target KPI: the decisions — which group to accept, which segment to grow, how to price a package — are made on total revenue from the start, not on room revenue.

Let’s put Adam’s two months into numbers. Hotel Peaqplus City, 80 rooms, both months 30 days long, so 2,400 available room nights:

Room revenue matches to the cent: 1,728 × 105 = 181,440, and 2,016 × 90 = 181,440. That is why the RevPAR report cannot tell the two months apart. TRevPAR, however, shows a 12.6 EUR gap — 30,200 EUR at monthly level.

And there is a second, more telling number: non-room revenue per sold night. April: 63,000 / 1,728 = ~36 EUR/night. June: 32,800 / 2,016 = ~16 EUR/night. The June guest spent less than half as much in-house as the April guest — while there were more of them. June is not a bad month. But while celebrating the occupancy record, the hotel filled its rooms with a low-spend mix, and the ground-floor capacity — restaurant, spa, meeting rooms — largely perished unsold. This is the same perishable-good logic we learned for rooms in lesson 2: a restaurant seat or a spa slot unsold tonight is revenue lost forever, exactly like an empty room.

When the ranking flips — two group offers

The TRevPAR mindset cuts sharpest in choice situations: when two pieces of business compete for the same capacity. In lesson 40 (Group displacement analysis) the number one trap was exactly this: comparing on gross room ADR alone and losing the ancillary value. Now let’s look at a pair where the ADR ranking and the total-value ranking flip.

Hotel Peaqplus City, Sep 22–25 (3 nights). Two inquiries arrive for the same 30-room block — because of the group ceiling (lesson 41) the two together do not fit; we can accept only one:

• Offer “A” — a German tour operator’s premium city-break series group: 30 rooms, 3 nights, 98 EUR/room/night. Room-only: the guests eat in the city, their programme package is set, at the hotel they practically only sleep. Expected in-house spend: ~10 EUR/room/night (breakfast upsell, bar).
• Offer “B” — the annual internal training of a regional bank (MICE — Meetings, Incentives, Conferences, Exhibitions): 30 rooms, 3 nights, 88 EUR/room/night, but the training runs in the hotel’s meeting rooms for two full days, with coffee breaks, lunches and a closing dinner. Expected F&B spend: ~58 EUR/room/night — the MICE average we saw in lesson 30, on single occupancy — plus the room hire.

The first reflex is the ADR ranking: “A” wins, 98 > 88. A room rate ten euros higher, the same number of nights — what is there to discuss?

Let’s work it through on total revenue, step by step. Both blocks are 30 × 3 = 90 room nights.

Offer “A”:

1. Room revenue: 90 × 98 = 8,820 EUR
2. Ancillary (supplementary spend): 90 × 10 = 900 EUR
3. Meeting revenue: 0 EUR
4. Total: 9,720 EUR — that is, 108 EUR / room night

Offer “B”:

1. Room revenue: 90 × 88 = 7,920 EUR
2. F&B (coffee breaks, lunches, closing dinner, bar): 90 × 58 = 5,220 EUR
3. Meeting room hire + technology: 2 days × 1,800 EUR = 3,600 EUR
4. Total: 7,920 + 5,220 + 3,600 = 16,740 EUR — that is, 186 EUR / room night

The ranking flipped. Behind the 10 EUR ADR advantage, offer “B” brings 7,020 EUR — 72% — more revenue into the house. A room-focused RM would have chosen “A”, and the decision would even have looked good in their own report: higher group ADR, same occupancy. The 7,020 EUR difference would never have shown up as an error — only as missing money, somewhere on the F&B and meeting lines, where nobody would have looked for it.

Two important nuances before we move on. One: the calculation above is revenue, not profit — the F&B margin (~30%) is far lower than the room margin (~70%), as we saw in lesson 30. The 9,720 vs. 16,740 gap narrows at profit level (roughly ~6,400 vs. ~8,900 EUR), but in this example “B” clearly wins there too — profit-side metrics (GOPPAR) and margin-weighted decision methodology are the subject of lesson 58 at expert level. Two: in a live decision this calculation plugs into the inside of the displacement analysis (lesson 40) — the question is not only “which group is worth more” but “which is worth more against the displaced transient business”. Total Revenue Management does not replace the displacement logic; it completes it: every side is measured on total spend, not on room rate.

Valuing segments on total spend

The same ranking flip lives not only in individual offers but in the whole segment strategy. In lesson 30 we built Hotel Peaqplus City’s segment-level guest-value table — now let’s put the two rankings side by side:

The biggest move is MICE: it jumps from the middle of the ADR ranking (5th) to 2nd place on total value — thanks to meeting and F&B spend. OTA leisure slides two places down: behind the respectable 95 EUR room rate sits ~21 EUR of in-house spend, because this guest lives in the city, not in the hotel. The three volume-carrying transient segments (business, direct and OTA leisure) bring ~30 EUR/guest/night of in-house spend on average, a tour operator guest ~12 EUR — a two-and-a-half-fold difference that is invisible in the room-rate table. (The ~25 EUR transient average used in lesson 40 is this same spend, volume-weighted and per room night.)

What does this mean in practice? In lesson 5 (The optimal mix) we optimised the mix for room revenue. In Total Revenue Management we re-weight the mix targets on total guest value:

• MICE weeks become an asset to protect. A 92 EUR MICE group is not “a cheap group dragging down the ADR” — it is the house’s second most valuable segment. When sizing the group ceiling (lesson 41), this segment deserves a different cap than the tour operator.
• The price of OTA volume becomes visible. In lesson 43 we already cut the OTA gross ADR from the channel-cost (commission) side — TRevPAR cuts it from the other side too: lower in-house spend. The two effects add up.
• Sales targets get repriced. If the sales team’s bonus runs on room revenue, they will bring the 98 EUR city-break series. If it runs on total group revenue, the 88 EUR MICE. Same team, same market — different incentive, different hotel result.

Unified optimisation — and the “separate kingdoms” trap

So far we have used TRevPAR for measurement and choice. The third layer of Total Revenue Management is the hardest: active demand management of the non-room capacities. Because the restaurant, the spa and the meeting room are just as perishable, capacity-constrained products as the room — it is just that nobody yields them.

Think through Hotel Peaqplus City’s ground floor:

• The restaurant seats 60. On Saturday at 7:30pm there is a waiting list; on Tuesday evening it runs at 30%. With rooms we would treat this pattern immediately with pricing and restrictions (lessons 35–36 and 42) — in the restaurant, the same menu prices typically apply on Tuesday as on Saturday.
• The spa’s two treatment rooms are overbooked on Saturday afternoon and empty on weekday mornings. The hotel guest who cannot get a Saturday slot is lost revenue — while Tuesday’s capacity perishes unsold.
• The two meeting rooms are a key resource in the spring and autumn peak weeks — giving a “free room hire with your room block” type of concession then is exactly the same mistake as discounting the room on a peak date. In dead periods, though, the room is better at any price than empty.

The unified optimisation toolkit will feel familiar — because it is the same RM principles on smaller capacities: peak/valley pricing and packaging in the spa, restaurant capacity and promotion planned off the house forecast, meeting-room yield by the demand calendar. One simple, immediately implementable metric is the capture rate: what percentage of the guests sleeping in the house have dinner in-house? If at June’s 84% occupancy the restaurant capture is 18%, then it is not a restaurant marketing problem — it is an RM problem: the mix and the package structure are not steering the guest inside.

And here comes the real obstacle, which is not mathematical but organisational: in most hotels, every outlet is a separate kingdom. The F&B manager is measured on food cost and their own P&L, the spa lead on treatment counts, the RM on room RevPAR — and nobody owns the guest’s total value. In this structure, the “B” MICE group’s room rate hurts the RM’s report, its F&B revenue improves the F&B manager’s report, and the decision depends on who sits closer to the GM. In lesson 30 we already stated the minimum: the F&B manager sits at the weekly revenue meeting (lesson 28), and the forecast is built at outlet level too. Total Revenue Management takes this further: one demand calendar for the whole house, a shared definition of peak weeks, and the big decisions — group acceptance, package pricing, promo timing — measured on total revenue, at one table. No new org chart is needed; a well-run revenue meeting and a jointly agreed target KPI are enough to start with.

Back to Adam’s two months

At the end of the half-year review, Daniel proposes three decisions, and Adam accepts all three.

One: TRevPAR goes into the monthly owner report, as a target KPI. RevPAR stays — it is the language of bank communication and compset comparison (lessons 4 and 44) — but from now on the “good month / bad month” verdict is spoken by TRevPAR. An April at 72% occupancy with a 101.9 EUR TRevPAR is a better month than a June at 84% with 89.3 — and that sentence has to be said by the report, not by the accountants after the fact.

Two: next spring’s MICE weeks get protection. Meeting-heavy groups in the conference season take precedence in group decisions — and the displacement analysis (lesson 40) counts every inquiry on total spend, not on room rate.

Three: the June profile becomes a packaging task. If the summer guest is OTA leisure and lives in the city, then next summer needs an offer that brings part of that spend into the house — dinner and spa packages, pre-arrival upsell. That is the territory of the promotional toolkit — which is exactly the next lesson, 46.

This lesson is deliberately an introduction: we laid down the mindset shift and the decision logic. At expert level, in lesson 58 (Total Revenue Management in depth — spa, F&B, MICE), comes the next layer of the methodology — spa and restaurant yield in detail, MICE pricing, outlet-level forecasting and profit-based, margin-weighted decisions.

Manually vs. Peaqplus

Manually, the data work of Total Revenue Management is the monthly outlet scorecard: the room and segment breakdown comes from the PMS (Sabeeapp, Previo, Hostware, Opera), F&B from the restaurant POS, the other outlets from the spa and meeting calendars — pulling all this together in Excel is typically 2-3 hours a month, and segment-level spend attribution (which guest group spends how much) exists only as an estimate in most hotels.

In Peaqplus, the room side of the picture is continuously alive: the Dashboard is the daily overview of how revenue is developing, and the segment breakdown shows what mix is producing the room revenue — precisely the mix shift that sat behind Adam’s April–June mystery, seen mid-flight rather than at the half-year close. Outlet revenues (F&B, spa, meetings) come from the hotel’s own systems; the TRevPAR scorecard is best assembled by adding those to Peaqplus’s room and segment data — and the weekly revenue meeting is the natural forum where the two sides land on one table.

Key takeaways

• Room-focused RM optimises for a sub-goal — between two months with identical RevPAR, a total-revenue gap in the order of tens of thousands of euros a month can hide on the F&B, spa and meeting lines.
• In Total Revenue Management, TRevPAR is a target KPI, not a reporting metric: group, mix and package decisions are made on total revenue from the start.
• The ADR ranking and the total-value ranking can flip: the 88 EUR MICE group brought 72% more revenue than the 98 EUR low-spend series group. In the segment table, MICE jumps from 5th place on ADR to 2nd on total value.
• Outlets are perishable capacities just like rooms — the spa slot, the restaurant seat and the meeting room can be yielded too. The capture rate is the first measurable step.
• The biggest obstacle is organisational: when every outlet is a separate kingdom with its own KPI, nobody owns the guest’s total value. A shared demand calendar + a shared target KPI is the entry ticket — the deep methodology comes in lesson 58.