The three core KPIs: occupancy, ADR, RevPAR

One Monday morning Adam, the general manager (GM) of Hotel Peaqplus City, walks into Daniel’s office with a coffee and a question: “How did last week go?”

Daniel pulls out a sheet and reads: “75% occupancy, EUR 92 average rate, EUR 69 RevPAR.”

Adam nods, takes a sip, and asks on: “And is that good?”

This moment — where a GM wants to put the numbers into an interpreted, business context — is where the three KPIs actually start working. A number on its own says nothing. Only when you compare it with something (last year, the plan, the compset, the previous week, the same segment for another period) does it become decision material.

In lesson 1 you already learned the formula and basic calculation of the three metrics. This lesson goes after how a revenue manager uses these numbers day to day: what the traps are, when you look at which one, and what their movement means.

Occupancy — the most misread metric

Occupancy has the simplest formula and, ironically, is the easiest of the three to mislead with. For two reasons:

1. Occupancy ≠ actual usage. A “booked room” doesn’t mean the guest actually sleeps in it. Occupancy includes:

• A non-refundable booking that is already paid but the guest cancels (the paid amount stays, the room counts as booked — but it’s physically empty).
• A double-booking, where Booking and your own site both sold the same room and the system noticed too late.
• A day-use (a daytime booking, 8 a.m.–6 p.m.) that can count in a daily occupancy figure but is empty in the overnight sense.

Occupancy measures contractual commitment — not necessarily “real usage.” That’s why a mature RM organization separately watches occupancy on the books (booked room-nights in the system) and arrived occupancy (guests who actually checked in), and tracks the gap between the two.

2. The occupancy average hides its “shape.” If Hotel Peaqplus City ran at 75% in a given week, that could be:

Version	Mon	Tue	Wed	Thu	Fri	Sat	Sun	Avg
”Even”	76%	78%	74%	73%	75%	74%	75%	75%
“Weekend peak”	55%	58%	60%	62%	92%	98%	100%	75%

Both rows average to 75%, but they demand radically different revenue management:

• The “Even” is a stable demand pattern — a deliberate segment mix, probably corporate-heavy. No urgent action here, just fine-tuning.
• The “Weekend peak” means Monday–Thursday is weak and the weekend is oversubscribed. Here the early-week days are worth advertising with a lower rate or a length-of-stay-friendly package so demand evens out — otherwise you sell every Saturday at 100% but lose the lower-ADR opportunity on the other days.

A report that shows only the average blinds you to these patterns. That’s why we look at occupancy at least daily — the weekly / monthly average is only an after-the-fact summary.

ADR — the trap of the mix effect

The average rate is the second metric that can mislead on its own. Its main problem is a piece of jargon: the mix effect.

Take Hotel Peaqplus City’s August and September figures:

Metric	August	September	Change
Average rate	EUR 105	EUR 111	+EUR 6 (+5.7%)

A surface read: “Great, we sold the rooms for more.” That’s how Adam would read it. But Daniel digs deeper — he looks at the segment breakdown:

Segment	Aug ADR	Aug share	Sep ADR	Sep share
Transient (individual)	EUR 120	60%	EUR 120	75%
Corporate	EUR 85	30%	EUR 85	20%
Group	EUR 75	10%	EUR 75	5%

Now you see it: not a single segment’s price changed. The EUR 105 → 111 rise comes purely from the higher-ADR transient segment growing its share and the lower-ADR group and corporate shrinking. We call this the mix effect: the average rate changes while the components don’t.

Why does this matter? Because if Adam shows up at the next bonus review saying “Daniel, great work, September ran +5.7% higher ADR,” that isn’t necessarily Daniel’s doing — perhaps the corporate season simply ended and fewer business travellers came. The real pricing decisions must be watched within a segment: how did the transient ADR move on its own? How did the corporate ADR move?

A mature revenue management organization watches this at rate-code level too: not only by segment but by specific rate code (BAR, NR, member, AAA, etc.). Because even behind “transient ADR EUR 120” there can be a mix shift between BAR and non-refundable.

The “shoulder ADR” trap

Another common problem: sold-out days and empty days average each other out.

Suppose Hotel Peaqplus City’s week looks like this:

Day	Occupancy	Rooms sold	Avg rate (sold rooms only)	Room revenue
Monday	40%	32	EUR 85	EUR 2,720
Tuesday	45%	36	EUR 85	EUR 3,060
Wednesday	50%	40	EUR 88	EUR 3,520
Thursday	55%	44	EUR 90	EUR 3,960
Friday	100%	80	EUR 140	EUR 11,200
Saturday	100%	80	EUR 145	EUR 11,600
Sunday	75%	60	EUR 105	EUR 6,300
Weekly	66%	372	~EUR 114	EUR 42,360

The weekly average ADR is 42,360 / 372 = EUR 113.87. A surface read: “EUR 114 average rate, that’s quite strong.” But it masks the question you actually need to ask:

• On the weekend we were full, and could have sold even higher — here the price may have been underset.
• Early in the week we were far from full, and the price was probably too high for demand to fill it.

If you read only the EUR 113.87 average, both pieces of important information are lost. That’s why a revenue manager always watches the daily level too — the weekly average is only an after-the-fact report, not a basis for decisions.

RevPAR — the investors’ eye

RevPAR (Revenue per Available Room) is the metric hotel owners, investors and bank financiers look at first. For two reasons:

1. A single number shows the whole performance: you don’t need to understand what 80% vs. 60% occupancy means, because RevPAR already views it combined.
2. It standardizes — an 80-room and a 400-room hotel’s RevPAR can be placed side by side and directly compared, regardless of size.

That’s why every hotel-industry market report, investment memo and composite analysis speaks in RevPAR. We cover this in detail in lesson 44 (Compset and market positioning).

The two components of RevPAR

RevPAR’s components — occupancy × average rate — can produce the same number through different strategies. In lesson 1 we already saw the A vs. B scenario. Now let’s go further: which is the “better strategy”?

A rule of thumb the profession accepts most of the time:

If there is little free capacity in the market, high ADR + lower occupancy is the winner. If there is a lot of free capacity in the market, high occupancy + lower ADR is the winner.

Intuitively this is simple supply-and-demand logic: if everyone in the market is packed out, you can push your price up too — even if a few rooms stay empty. If the market is empty, a low price helps pull in demand that could go elsewhere.

But this logic has one important addition that’s rarely mentioned at beginner level: TRevPAR (Total Revenue per Available Room) — which also brings in F&B, spa, parking and other spend. A lower-ADR guest who spends a lot in the restaurant can be more valuable overall than a higher-ADR guest who “just wants a bed.” TRevPAR is the main topic of lesson 4.

When do you look at which?

The three KPIs are for different decisions. Here’s a quick guide Daniel keeps in his head:

Situation	Primary metric	Why
Checking in the morning “how was yesterday”	RevPAR	One number, a quick read. Details later.
Deciding a rate increase / cut for a specific date	Occupancy + booking pace	Current state vs. the time window
Evaluating a segment’s strategy	Segment-level ADR	This measures the rate-structure choice
Writing a quarterly composite report	RevPAR + ARI (Average Rate Index)	Standardized market comparison
Evaluating a promo’s impact	Occupancy + within-segment ADR	Measuring volume vs. price cut
Evaluating an F&B-heavy segment	TRevPAR (lesson 4)	Only this shows the full guest value

The three KPIs live together. You don’t swap any of them for a single “master metric” — all three work at once in a revenue manager’s head, and the question is always which is most relevant to the decision at hand.

Back to Adam’s question

Remember: Adam asked on Monday morning, “75% occupancy, EUR 92 average rate, EUR 69 RevPAR — is that good?”

Daniel’s answer can now be far richer:

• “The EUR 69 RevPAR is +EUR 4 versus the previous week — we improved.”
• “But the occupancy shape was strongly weekend-peaked — Friday–Saturday at 100%, Monday at 38%. The four early-week days were underset; we lost pickup opportunity there.”
• “The ADR is stable in the transient segment, but the corporate share dropped to 22% (from 30%) — that’s one reason for the early-week weakness.”
• “From an investor angle: the EUR 69 RevPAR is +4% versus the comparable week last year and +2% versus budget — good by the numbers.”
• “But in business terms I’d say we could have gone higher on the weekend, and the start of the week needs a promo strategy for the coming weeks.”

This is what we call data-driven evaluation — not a simple “good” or “bad” verdict, but a story contextualized across several dimensions that leads to concrete actions. This is exactly revenue management.

Key takeaways

• Occupancy can mislead for two reasons: (1) there’s a difference between occupancy and real usage (cancellation, no-show, day-use), (2) the weekly / monthly average hides its “shape” — the daily pattern.
• The trap of the average rate is the mix effect: a shift in segment proportions can raise or lower the overall ADR without anything changing within a segment. Always evaluate at segment / rate-code level.
• The weekly average ADR fuses sold-out and empty days — this blinds you to daily pricing mistakes. Watch the daily level.
• RevPAR is the investor number: standardized, size-independent, a single figure. But it’s too coarse for operational decisions — for the detail you need occupancy and ADR.
• There is no single “master metric.” The three KPIs are for different decisions. A revenue manager constantly switches between them depending on the question at hand.