The owner's data problem: what you inherit when you buy a hotel

Picture the first ownership review after a close. The deal team is gone, the asset manager is in the chair, and the management company sends the monthly package. It arrives as a PDF and three spreadsheets. The P&L follows USALI, more or less. The segment detail does not match the offering memorandum you underwrote against. The flash report uses a definition of occupancy that includes comp rooms one month and excludes them the next. You ask for the same cut across the two hotels you bought in the same portfolio and you get two different formats, because they came from two different operators on two different systems. You wanted one number. You got a reconciliation project.

That is the owner’s data problem, and almost nobody underwrites for it. You did not buy a hotel. You bought someone else’s chart of accounts, someone else’s segment codes, someone else’s PMS configuration, and someone else’s idea of what counts as a comp. The asset sits on a foundation of data decisions you did not make and cannot see. Hotel ownership reporting is the one deliverable that determines whether you can actually run the asset, and it is the one that arrives least standardized.

What you actually inherit

You inherit a stack, and the stack was built for the operator’s convenience, not yours.

You inherit a PMS, Opera or OnQ or Maestro, configured years ago by a property team that has since turned over. The market segment codes were set up for a demand mix that may no longer exist. The rate codes accreted over a decade of promotions. Nobody documented why “corporate negotiated” splits into four sub-segments at one hotel and one at another. You inherit a sales-and-catering system, Delphi or Amadeus or Tripleseat, with its own segment logic that does not map cleanly to the PMS. You inherit a POS, Toast or otherwise, where the menu hierarchy was rebuilt twice and the historical mix is now uncomparable across the rebuild line.

Then you inherit the reporting layer that sits on top of all of it. A flash report somebody on the property built in Excel on a Sunday night years ago. An STR subscription pointed at a comp set the prior owner chose. A monthly package assembled by hand from exports, where the assembler is the only person who knows which tab is authoritative. None of this is malicious. It is the ordinary sediment of a working hotel. But it is sediment you now own, and it is the substrate of every number you will report to your investors.

The gap is simple to state. You need portfolio-comparable, trustworthy reporting. The operator hands you property-specific, operator-convenient reporting. Those are not the same artifact, and the distance between them is the work nobody priced into the deal.

Why portfolio-comparable is the hard part

A single hotel is a manageable problem. You can learn its quirks. The pain compounds the moment you own more than one, because the whole point of a portfolio is comparison and comparison requires common definitions.

Consider RevPAR, the number everyone assumes is universal. RevPAR is only comparable if occupancy, ADR, and available rooms are defined the same way across properties. One operator counts out-of-order rooms against inventory, another does not. One nets comp and house rooms out of occupancy, another leaves them in. Both are reporting RevPAR. Neither is lying. The numbers are simply not the same number, and when you stack them in a portfolio roll-up you are averaging two different metrics and calling the result a trend. The same trap waits in F&B contribution, in cover counts, in labor as a percentage of revenue, in every operating line that depends on a definition the property set without telling you.

This is the same disease that kills internal reporting from the inside, the one we wrote about in five systems that disagree. The owner just inherits it pre-assembled, across multiple operators at once, with no institutional memory of how any of it was defined. A management company at least lived through its own definition drift. You walk in cold, holding a package that looks authoritative because it is formatted well, and you have no way to know which numbers survive comparison and which ones quietly do not.

The tell shows up fast. You try to build one portfolio dashboard across your hotels and you cannot, because every property answers the same question with a slightly different definition. You either flatten everything to the lowest common denominator and lose the detail that matters, or you keep the detail and lose comparability. Most owners pick a third option, which is to live in the operator’s PDF and never build the portfolio view at all. That is the option that costs you the most, because it means every strategic question takes a week and a reconciliation.

What good ownership reporting actually requires

Good ownership reporting is not a prettier package. It is a set of definitions you own, applied identically across the portfolio, traceable back to the source systems. Three things make it real.

First, a definition layer that belongs to the owner, not the operator. Before you can trust a number you have to decide what it means: how you count occupancy, how you segment demand, what goes into F&B contribution, where labor sits. Those decisions are an ownership asset. Once you own the definitions, the operator’s data feeds into them instead of dictating them, and a new acquisition gets mapped into your standard rather than forcing you to learn its standard.

Second, one connected source of truth that sits above the operator’s stack. The PMS, the sales-and-catering system, and the accounting export each hold a piece of the picture and none holds all of it. Ownership reporting that lives in a monthly PDF is reporting you cannot interrogate. When a number looks wrong, you cannot trace it. When you want a cut the operator did not provide, you wait a week. The fix is to land the source data in one place you control, so the reporting is yours to query, not yours to request. This is also the heart of the build versus buy decision every owner eventually faces: whether to keep renting the operator’s reporting or to own the layer that makes the portfolio comparable.

Third, reporting that reads the way an owner thinks. An asset manager does not think in USALI line order. An asset manager thinks in NOI against budget, in RevPAR penetration against the comp set, in where the F&B drag is, in which property is carrying the portfolio and which is leaking. Good ownership reporting answers those questions on one screen, in the owner’s language, current as of this morning, without a human assembling it by hand. If you have to read four reports and reconcile them to answer one question, the reporting failed, no matter how clean each report looks on its own.

The asset you actually wanted

Here is the honest part. Almost everything you need is already in the building, the same way it always is. The PMS holds the demand and the rooms revenue. The sales-and-catering system holds the group and banquet pipeline. The accounting system holds the actuals. STR holds the comp set. You are already paying for every system that holds a piece of the truth. What you do not have is the layer that joins them into definitions you own and a view you can read without a week of reconciliation.

That layer is the work. One connected source of truth that sits above whichever operator runs the asset, a definition standard that belongs to ownership and survives the next acquisition, an intelligence layer that answers an asset manager’s questions in an asset manager’s language, and an operating cadence that puts the same numbers in front of you every month without a heroic manual assembly. That is the Operator Intelligence model applied to the owner’s chair. Ownership reporting is just the part of it you feel first, on the first review after the first close.

You can build this yourself. Map the operator’s segments to your standard, land the source feeds in one place, write the definitions down and hold the operator to them, and you will own reporting that survives the next deal. Some owners should do exactly that. If you would rather inherit a portfolio and have it already speak one language, that is the kind of thing we build. Either way, stop accepting the operator’s PDF as the source of truth for an asset you own. You bought the hotel. You should own the numbers too.