Two hotels report their month. One is proud of 90% occupancy. The other is proud of a ₹6,000 average rate. Neither number, on its own, tells you which of them had the better month — and both owners believe theirs does.
Quick answer (for the impatient)
Occupancy = rooms sold ÷ rooms available. How full you were.
ADR = room revenue ÷ rooms sold. What the rooms you sold went for.
RevPAR = room revenue ÷ rooms available, or equivalently occupancy × ADR. This is the one that actually settles arguments.
Why occupancy alone is a trap
Occupancy is the easiest metric to move and the easiest to move destructively. Any hotel can hit 95% tonight by pricing low enough. The rooms fill, the number looks excellent, and the revenue is worse than a half-empty night at a sensible rate — while your costs went up, because full hotels consume more housekeeping, more laundry, more breakfast and more wear.
ADR has the mirror problem. Push rate high enough and your ADR is magnificent across the eleven rooms you sold, while forty sat empty.
RevPAR resolves the argument
RevPAR divides revenue by rooms available rather than rooms sold, which means empty rooms are counted in the denominator. That's the whole trick: it refuses to let you ignore the inventory you failed to sell.
A worked comparison, same 50-room hotel, same night:
Hotel A: 45 rooms sold at ₹3,000 → revenue ₹135,000 → occupancy 90%, ADR ₹3,000, RevPAR ₹2,700.
Hotel B: 25 rooms sold at ₹6,000 → revenue ₹150,000 → occupancy 50%, ADR ₹6,000, RevPAR ₹3,000.
Hotel A wins on occupancy by a wide margin. Hotel B made more money, with 20 fewer rooms to clean. RevPAR says so and the other two metrics don't.
Where RevPAR stops being enough
RevPAR only sees room revenue. For a property with a serious restaurant, bar or banquet operation, that's a partial picture — which is why TRevPAR (total revenue per available room) exists, folding in F&B and other income.
And none of these are profit. A hotel can grow RevPAR while margin falls, if the growth came through channels that take a commission. Which is the real argument for direct booking: two bookings at the same rate are not worth the same to you, and no rooms metric will tell you that. Look at contribution after distribution cost, not just RevPAR.
How to actually use these
Compare against yourself, same period last year — hospitality is too seasonal for month-on-month to mean much.
Segment by day of week. A property that's strong midweek and empty at weekends is a different business from the reverse, and the blended number hides it.
Track RevPAR by channel. This is where the commission argument becomes concrete rather than theoretical.
Watch the trade-off deliberately. If occupancy rose and RevPAR didn't, you discounted your way to a busier hotel and no more money.
A realistic hotel example: what the team sees during a working shift
Picture Lakeview Residency, an independent property where the same manager may answer a booking query, approve a rate, settle a guest account and help a new employee before lunch. The question behind ADR, Occupancy and RevPAR: The Three Numbers, and Why Only One of Them Matters does not arrive as a neat software task. It arrives while somebody is waiting, another department needs an answer and the record must still make sense at the end of the day.
The first useful observation is this: Occupancy = rooms sold ÷ rooms available. How full you were. The manager should translate that statement into a visible hand-off. Who starts the action? Which record do they open? What information must already be present? Who checks the result? If any answer depends on one experienced employee remembering an exception, the process is not yet reliable.
The second observation is equally practical: ADR = room revenue ÷ rooms sold. What the rooms you sold went for. At Lakeview Residency, the team would test this with one ordinary case and one awkward case. The ordinary case confirms the expected path. The awkward case exposes missing permissions, incomplete data, unclear ownership or a decision that still happens in a private message. Both tests matter because hotel operations rarely fail on the clean example shown in a demonstration.
The third observation is about the downstream record: RevPAR = room revenue ÷ rooms available, or equivalently occupancy × ADR. This is the one that actually settles arguments. A completed action should leave enough context for the next person to understand what happened without reconstructing the story from calls and chat messages. That does not mean collecting every possible field. It means keeping the few facts that change the decision, the status, the responsible role and the next action together.
Rollout checklist: move from a good idea to a repeatable process
Use this checklist before the team treats the workflow as normal operating procedure. It deliberately separates product reachability from management discipline: software can make a record available, but the property still decides who owns it and how exceptions are handled.
Name the owner. Choose the role responsible for starting and completing the process. "The office" or "the front desk" is too vague when several people share a shift.
Confirm access. Test with the real role and tenant configuration, not an unrestricted demonstration account. Check enabled modules, feature permissions and the property or outlet context.
Define the minimum input. Agree which guest, room, date, amount, document or operational detail must be present before somebody can act.
Run the normal case. Complete one realistic example from beginning to end and ask the next team member to explain the result using only the saved record.
Run the exception. Try a correction, cancellation, missing value, late change or disputed instruction that genuinely occurs at the property. Record the fallback if the product path does not cover it.
Check the hand-off. Make sure the relevant people in front desk, reservations, housekeeping and accounts can see the status they need without receiving unnecessary access to unrelated records.
Write the fallback. If the system is unavailable or the case sits outside the verified path, state who records the temporary decision and who reconciles it later.
Review after live use. Ask staff where they paused, duplicated work or returned to a spreadsheet. Fix the process before adding more fields or automation.
Decision table: evidence to collect before you approve the workflow
A manager does not need a large transformation project to evaluate this topic. A short evidence review is enough to distinguish a reachable workflow from an attractive claim. Use the table during a property review and write the answer in plain language.
Review point What to verify Evidence to keep Decision if it fails
Reachability The responsible role can open and complete the path in the correct tenant and property context. A completed test record and the role used. Do not announce the workflow; check provisioning and permissions.
Data quality The minimum information needed for the decision is present, understandable and current. The input checklist and one reviewed example. Fix the collection step before adding automation.
Ownership One role owns the next action and another can review where separation is appropriate. The operating owner and escalation path. Assign responsibility before rollout.
Exception handling A correction, cancellation or disputed case has a documented path. The tested exception and fallback note. Keep the process in controlled trial use.
Downstream hand-off The next department sees the status it needs without manual re-entry or excessive access. A hand-off check by the receiving role. Use a documented interim hand-off and reconcile it.
The honest AXOIX limit and what to review after the first live cycle
The first review should focus on behaviour, not vanity metrics. Ask the people who performed the work where they hesitated, what they entered twice and which decision still escaped into a phone call or personal message. Compare the saved record with what actually happened. If they differ, find the earliest point where context was lost.
Then separate a training problem from a product boundary. A training problem means the verified path exists but the team did not understand the trigger, required input or next action. A configuration problem means the module, property context or permission is not available to that role. A product boundary means the audited path does not support the case. Those three diagnoses require different responses; calling all of them "user error" guarantees a repeat.
Keep the limitation visible while reviewing this article: Verify the workflow and its applicability before relying on it. That boundary is part of the buying and rollout decision, not a footnote to remove from the sales conversation. Where the workflow is usable, test it honestly. Where it is partial, keep the manual control explicit. Where applicability depends on law, policy or professional judgement, confirm it with the appropriate adviser.
FAQ
Should I include complimentary rooms in occupancy?
Be consistent, and know which convention you're using. Including them flatters occupancy and depresses ADR.
Are out-of-order rooms in the denominator?
Convention varies. Excluding them measures your operating performance; including them measures your asset's performance. Pick one and don't switch.
What's a good RevPAR?
There's no universal figure — it's entirely dependent on market and segment. Your own trend is the meaningful benchmark.
How should a hotel test this before rolling it out?
Use the real tenant, property context and staff role. Complete one ordinary case and one exception from start to finish, then ask the receiving role to verify the saved result without relying on a private message.
What should the team do if the verified product path does not cover its case?
Keep a documented manual control, name the person responsible for reconciliation and avoid describing the unsupported step as automated. Recheck module provisioning and permissions before concluding that a capability is absent.
The bottom line
Occupancy and ADR are levers. RevPAR is a result. If you only look at the levers, you'll pull one of them hard in the wrong direction and be pleased about it for a whole quarter.
See how rate plans control ADR, how night audit produces the numbers, or pricing.
Know the number that matters. Start free →
Comments