ADR vs. average rate: the confusion that costs money

Ask three people at the same hotel what their average rate was last month and you will frequently get three different answers. Not because anyone is lying, but because each of them calculated something different and called all of it “average rate.” That is where an expensive misunderstanding begins: mistaking the average of your rate sheet for your ADR (Average Daily Rate). They look alike, they sound alike, and they are almost never the same number.

What ADR actually is

ADR is one division and only one: room revenue divided by the room nights sold in a period. If on a given day the rooms you sold added up to a certain lodging revenue, and you sold a certain number of nights, the ADR is the first figure over the second. It is the average price each occupied night truly paid, not the price you put on the list.

The key word is “sold.” ADR weights by reality: a rate you sold a hundred times counts a hundred times more than one you sold once. That is why it reflects what happened in operations, not what you hoped would happen when you built the rate sheet.

The silent error: averaging the rate sheet

The most common trap is taking the rates from your price list and computing a simple average. You have, say, a standard room rate, a suite rate, and a family room rate; you add them, divide by three, and declare “this is my average rate.” The problem is that this calculation completely ignores how many nights each one actually sold.

Imagine (an illustrative example) that your suite is expensive but barely sells, while your standard is cheap and sells constantly. The rate-sheet average will hand you an inflated number, dragged upward by a high rate that is rarely charged. Your real ADR, by contrast, will sit much closer to the standard price, because that is where the volume lives. Averaging list prices means averaging intentions; ADR averages facts.

Averaging your rate sheet is asking the menu how much people ate. ADR asks the bill.Principle of honest measurement

The table that makes it obvious

Let us see it with made-up numbers for illustration. Suppose one day with three room types, each with its list rate and the nights that actually sold. Compare the “naive” rate-sheet average (add the three rates and divide by three) against the real ADR (weighted by nights sold).

The gap is not a decimal: the naive average says $2,733 and the real ADR says $1,480. If you made decisions believing you charge $2,733 a night, you would be living in a hotel that does not exist. And note something important: neither number is “miscalculated” in itself; the naive one simply answers a different question (the average of your list) and dresses it up as ADR.

What counts and what does not (the part almost nobody defines)

Even when you do divide revenue by nights, ADR can come out differently depending on what you choose to include. These decisions are rarely written down, which is exactly why two people “calculating ADR” land on figures that do not match:

• Extras (breakfast, spa, parking, charges): do they go into room revenue or stay out? Classic ADR is lodging only; folding in extras inflates it.
• Comps and complimentary rooms: if a night was given free, does it count as a night sold at $0 (lowering ADR) or not count as sold at all? It changes the denominator.
• No-shows: if it was charged but nobody slept, is it a night sold or not? Depending on how you treat it, ADR rises or falls.
• Upgrades and rate changes: if you sold a standard and moved the guest to a suite with no extra charge, at which rate does that night count?
• Long stays at negotiated rates, groups, and staff comps: they distort things if mixed in with no clear rule.

None of these answers is universally “the right one”; what matters is choosing a rule and applying it the same way every time. ADR does not break because of the rule you pick, it breaks when each report picks a different one.

Why a poorly defined ADR contaminates RevPAR

ADR does not live alone. It is one of the two ingredients of RevPAR (Revenue Per Available Room), the headline metric of lodging. RevPAR can be read two equivalent ways: room revenue divided by available rooms, or ADR multiplied by occupancy. That second form means any error in your ADR flows straight into RevPAR.

If your ADR is inflated because you averaged the rate sheet or folded in extras, your RevPAR inflates too, and so you believe your per-room performance is better than it is. You compare against other periods, other properties, an index, and every one of those comparisons inherits the error at the source. A crooked foundation never shows in the brick; it shows on the floor above.

The real cost: decisions made on a false number

This is where the confusion “costs money.” With an inflated ADR you may believe you have room to hold prices when in fact you are selling cheaper than you think. With a deflated ADR (from miscounting comps or no-shows) you may punish rates that are actually working. In both cases the decision is sound in form and wrong at the core, because the input was lying.

The fix is not to argue, it is to define once

The cure for this confusion is not for people to “be more careful when averaging.” It is for ADR to stop being a manual calculation that everyone assembles their own way and become a calculated field, defined once, identical for everyone. The formula lives in a single place, with its explicit rule on extras, comps, and no-shows, and any report that asks for “ADR” receives exactly that number.

In Spider Data, ADR is precisely that: a calculated field that crosses the operation’s sources, reservations, the cash desk, payments, channels, orders, and applies the same definition of room revenue over nights sold across every dashboard, every filter, and every scheduled send. When two people look at the same period’s ADR, they see the same number, because it came from the same traceable formula and not from three different spreadsheets. And if someone asks in plain language “what was my ADR last week?”, the answer leans on that same definition, not on an improvisation.

Traceability is the other half of the matter. It is not enough for the number to be correct; you have to be able to open it and see where it came from: which nights went in, what was counted as room revenue, how comps were treated. An ADR you cannot audit is an ADR you trust on faith, and faith is a poor basis for setting prices or comparing against an index.

A datum is not a number: it is an agreement

In the end, “average rate” and “ADR” are not synonyms by accident or by carelessness: they are two answers to two different questions, and the damage appears when we treat them as one. The good news is that this is solved at the root with a decision, not with surveillance: define ADR once, make it consistent, make it traceable, and let everyone read from the same place.

Deciding better does not begin with better reports or more dashboards. It begins with numbers that mean the same thing to everyone who looks at them. Because a poorly defined number is not a datum: it is a misunderstanding with decimal places.