Chapter 1Same Hotel, Different Numbers

Chapter 1 - Same Hotel, Different Numbers

Why common definitions must come before performance explanations

Let us begin at Hotel Blue Moon.

It is the fifth working day of the month. Finance has closed March, and Anika, the General Manager, has an owner call in one hour. Around the table sit Amara, the Financial Controller; Noelle, the Rooms Division Manager; Mari, the Housekeeping Manager; and Rafael, the Food and Beverage Director.

Everyone has the same monthly pack. The headings are familiar: Rooms, Food and Beverage, Departmental Profit, Gross Operating Profit, EBITDA, budget, prior year, and variance.

“Let us start with the headline,” Anika says. “ADR is behind the competitive set, GOP margin is below budget, and the owner will ask why.”

Rafael leans forward. “Exactly. The report makes it look like we are discounting the hotel and not converting enough profit.”

Noelle shakes her head. “Our selling price is not weaker. We allocate more of the package to breakfast. Some competitors leave more inside Rooms, so their ADR looks higher because the numerator contains something different.”

Rafael turns a page. “Average check has the same problem. We include beverage-only patrons in the total customer count. A hotel that divides all outlet revenue only by food purchasers will report an artificially higher average check. Same outlet, incomplete denominator.”

Mari taps the labor page. “Housekeeping looks expensive because recurring contract cleaning is visible as labor. Another hotel may leave similar work in contract services. The work did not change. The classification did.”

Anika looks at Amara. The meeting is using performance language, but the disagreement is about what the numbers contain.

“Before we explain performance,” she says, “let us check the definition.”

“We are not yet arguing about good or bad performance,” Amara continues. “We are testing whether ADR, average check, and labor cost are built on the same definitions.”

“So the first question is not, why is the number bad? The first question is, what is the number measuring?”

The tone changes. The meeting has not become easier, but it has become more honest.

Anika looks back at the report. “Then the first action is to separate operating movement from definition movement.”

“Exactly,” Amara says. “After that, we can discuss performance. Before that, we are comparing labels.”

The lesson hidden in the story

The Blue Moon team had three examples of one problem: identical labels did not guarantee identical content.

Package allocation can change ADR. Cover conventions can change average check. Labor presentation can change labor ratios. Each difference can move a KPI without changing guest demand, price, cash collected, or work performed.

Most hotel teams can calculate the ratio. The harder task is proving that the ratio, budget, prior year, and benchmark are measuring the same version of the hotel.

USALI gives lodging professionals a common structure for classifying, presenting, and analyzing operating results. It does not remove judgment or replace other reporting requirements. It gives the meeting a disciplined starting point.

From operating event to management decision

Hotel information becomes useful when an operating event can be followed into the reporting structure and then into a decision. This Chapter establishes the first control point: define the number before interpreting it.

You can follow these four steps when a reported number is challenged:

1. Identify the operating event and the source evidence.

2. Confirm what the reported number includes and excludes.

3. Separate operating movement from classification, allocation, mapping, timing, or denominator movement.

4. Only then explain the result and decide the action.

Enlarge figureOpen full-size file

Definition drift: when a number changes meaning

In my experience, hotel operating statement is a translation device. It turns thousands of guest, labor, purchasing, and contract events into a structure that managers and owners can discuss.

Translation fails when the same label contains different items. Rooms Revenue may include a non-room fee in one report. A cover may mean every paying guest in one outlet and only food-ordering guests in another. Recurring support work may be visible as labor in one hotel and contract services in another.

This quiet movement away from shared meaning is definition drift: the loss of comparability caused by inconsistent classification, allocation, mapping, timing, or denominator logic. It often begins with an apparently minor system code, package setup, payroll mapping, contract term, or posting shortcut.

The danger is not merely technical imperfection. Definition drift can trigger the wrong pricing, staffing, outlet, benchmark, or owner decision.

You should use below table to review the definition for every new term before relying on numbers before making comparisons and decisions.

Table 1.1 — The Definition Check Card

Lets understand the impact with the help of an worked example: ADR at Hotel Blue Moon

In March, Hotel Blue Moon sold 10,000 rooms at a room rate of $150 and also charged a $30 nightly destination-style fee. Guest cash is identical in both presentations below. Only the classification changes.

Under the reporting basis used in this example, the fee sits outside Rooms Revenue. ADR therefore measures the room component rather than a mixture of room price and a non-room fee.

Source note: STR Benchmark P&L reporting guidance states that resort/destination/urban fees are reported as Miscellaneous Income rather than Rooms Revenue, and that only the room portion of multi-service packages should be reported as Rooms Revenue. The example above is a simplified teaching illustration. (STR Benchmark/CoStar, “P&L Data Reporting Guidelines”; see References and Source Basis.)

The incorrect version does not show stronger room pricing. It shows a larger Rooms numerator. The hotel can appear to outperform a benchmark and then appear to decline when the classification is corrected, even though guest demand and price did not change.

Enlarge figureOpen full-size file

When definitions move, decisions move

Definition errors rarely stay inside accounting. They enter a KPI, then the commentary, then the meeting, and finally the action.

A package-allocation problem can produce the wrong pricing response. A cover-definition problem can hide an outlet-volume issue. A labor-classification difference can lead to a staffing cut even though the work performed has not changed.

Before explaining a movement, label it as operating, classification, allocation, mapping, timing, denominator, or presentation-related. More than one label may apply; the bridge should show each material cause.

Table 1.2 — Common confusions to check before explaining performance

A common label is not enough

A dangerous habit is to say, “We use USALI,” and stop asking questions. Two hotels can use the same headings while applying different package, service-charge, cover, outsourcing, or mapping policies.

The framework is useful only when policy and system mapping preserve a comparable meaning. A label does not resolve a different operating model or a changed reporting basis; it makes the required bridge visible.

When work moves from employees to an outsourced arrangement, payroll can fall while contract expense rises. The hotel should bridge the operating-model change before claiming that productivity improved.

Protect the decision boundary

A definition change can alter departmental margin, GOP, EBITDA, or owner reporting without changing the underlying operation. Chapter 1 establishes only the control: identify the basis change before assigning performance or accountability.

The statement ladder and owner-economics bridge are developed later. Here, the rule is simpler: do not let a presentation movement become a performance conclusion.

Enlarge figureOpen full-size file

Questions That Arise in Practice

Is USALI the same as GAAP, IFRS, tax reporting, or statutory reporting?

No. USALI is a lodging operating reporting framework. GAAP, IFRS, tax reporting, and statutory reporting answer different external reporting questions. A hotel may need to reconcile between them, but they should not be confused.

Why can two hotels using USALI still report different results?

Because the structure does not remove differences in package policy, service-charge treatment, system mapping, operating model, or denominator convention. Those differences must be documented and bridged before ranking performance.

What should we do when the system setup does not match the reporting logic?

Do not let a system default become policy. Map PMS, POS, payroll, procurement, and contract codes to the intended treatment, use a controlled monthly bridge where necessary, and correct the source setup when practical.

End-of-chapter action prompt

Take one monthly pack from your hotel, or a sample pack if you are studying. Choose one frequently discussed number. Write its numerator, denominator, source system, definition owner, and any change in mapping, timing, allocation, or policy.

Then ask: if the number moved next month, could the team prove whether the operation moved or the definition moved? If not, create a definition note or controlled bridge before using the number for action.

The Blue Moon team did not solve every issue in one meeting. It changed the order of the conversation.

Before we explain performance, let us check the definition.

Decision Lab - Diagnose Definition Drift

Situation: The owner ranks Hotel A above Hotel Blue Moon because it reports stronger ADR, stronger restaurant average check, and lower housekeeping labor cost per occupied room. Hotel A includes a nightly urban fee in Rooms Revenue, counts only food-ordering guests as covers, and records outsourced housekeeping outside labor visibility. Blue Moon uses the opposite conventions.

Reader task:

• Identify the definition difference behind each KPI.
• Decide which conclusions must be withheld until the bases are normalized.
• Create a two-sentence owner caveat and a three-line normalization bridge for Rooms Revenue, restaurant customers, and housekeeping labor.

Decision standard: Separate guest cash from Rooms Revenue, identify the customer denominator difference, normalize in-house and outsourced work, and refuse the ranking until the definitions are aligned.

Next: Chapter 2

Chapter 1 established the definition check. Chapter 2 adds the hotel-context lens: the same definition can still require different interpretation when the service model, guest journey, and revenue structure differ.