Groups and chains: consolidate without losing the detail

When a hotel group grows, a quiet temptation appears: reduce everything to a single number. One total revenue, one average ADR, one overall occupancy. The dashboard looks clean, the board is pleased, and without anyone noticing, the group goes blind. Because the real challenge of running several properties is not adding them up, any spreadsheet can add, it is comparing fairly without flattening what makes each hotel unique. This essay is about that tension, and about how a shared data structure finally lets you see the forest and the tree at once.

The temptation of a single number

A consolidated view is necessary. A group’s leadership needs to know, at a glance, how the whole is doing: how much came in this month, where occupancy is heading, which receivables are still open. The problem is not consolidating; the problem is over-consolidating, until the average swallows reality.

An average is honest when the things it averages resemble each other. But a 120-room beach hotel in high season and an 18-room boutique city hotel resemble each other in almost nothing: different market, different size, different demand curve across the year. Adding them carelessly produces a number that describes neither. It is the classic danger of comparing apples and oranges: the result looks precise, but it does not mean what you think.

A well-built consolidation does not hide the detail; it organizes it so you can drop down to it whenever you need to.Spider Data design principle

The tension between the group view and each hotel’s reality

Two truths coexist, and they seem to fight. The first is the consolidated view: the entire group as a single entity, useful for portfolio decisions, for talking to investors, for allocating attention and resources. The second is the detail: each property with its own market, size and season, where the operation actually happens day to day.

The common mistake is to pick one and sacrifice the other. Either you live only in the total, and then no one understands why the group looks “fine” while two hotels are sinking, or you live only in the detail, and then no one sees the forest, nor the trends that cut across every property at once. The good news: you do not have to choose. You need a data structure that holds both views without contradicting itself.

Why a shared data structure changes everything

Spider Data cross-references eight operational sources, reservations, cash, channels, payments, guests, orders, shifts and cash movements, inside a single structure. The key word in that sentence is not “eight”; it is “single”. When every hotel in the group describes its reservations, payments and shifts in the same language, the total stops being a sum forced together at the end and becomes something computed naturally, without losing where each part came from.

That traceability is what enables movement in both directions.

Up: from detail to total (ROLLUP)

A ROLLUP aggregates upward: it takes each hotel’s revenue and accumulates it into the group total, the brand total, or the region total. Because every hotel speaks the same data language, the total is not a figure someone typed by hand into another sheet, it is the living sum of its parts, with every component still intact beneath it.

Down: from total to detail (drill-down)

Drill-down is the path back. You see that group revenue dropped this month and, instead of sitting with the anxiety of the number, you open that total: which region dragged it down? Which hotel within that region? Which channel of that hotel? You step down level by level until you touch the concrete reservation that explains the story. Without traceability, a total is a dead end; with it, it is a door.

Comparing by hotel, by brand and by region

On a shared foundation, cross-table joins stop being a multi-week project and become a question. You can compare property against property, group by brand to see which flag performs best, or by region to understand a whole market. The no-code report builder, drag and drop, in Spanish, lets an operations director assemble that comparison without asking anyone in IT.

Here is an important subtlety. Comparing is not just placing figures side by side; it is choosing the right figure so the comparison is fair. Total revenue always favors the largest hotel, but size is not merit: a 120-room hotel will almost always bill more than an 18-room one, and that says nothing about who operates better. This is why relative metrics, ADR, occupancy, revenue per available room, usually tell a more honest story than absolute totals.

How to compare properties fairly

Before ranking anything, it pays to have a method. These rules help you avoid comparing apples to oranges:

• Normalize for size: prefer per-available-room or per-occupied-room metrics over absolute totals, so a large hotel does not “win” simply for being large.
• Respect seasonality: compare the same period against the same period (this July versus last July), not a beach hotel’s July against a city hotel’s November.
• Group by comparable categories: cluster similar properties, same brand, same size range, same market type, before placing one next to another.
• Look at the mix, not just the average: two hotels with the same ADR can have opposite clienteles (one full of direct bookings, one of expensive channels); the average hides it and the detail reveals it.
• Separate volume from efficiency: the biggest is not the best; tell “how much it sold” apart from “how well it sold it”.
• Verify you measure the same thing everywhere: a metric is only comparable if every property computes it with the same definition, something only a shared structure guarantees.

Rank with care: the biggest is not the best

A ranking is a powerful and dangerous tool at once. Powerful because it orders attention: it shows at a glance who needs help and who is ahead. Dangerous because, if you rank by the wrong metric, you reward the large hotel for being large and punish the boutique for being small, when the boutique might be the best-run property in the whole group.

The practical rule: rank by relative efficiency to judge management, and by absolute volume only when what matters is the contribution to the total. These are two different questions, “who operates best?” and “who brings in the most money?”, and merging them into a single ranking confuses whoever decides. To see it clearly, it helps to keep them apart:

Everyone sees their own: access by team

Consolidating well is also a matter of permissions. In a healthy group, each property manager sees their own, their operation, their reservations, their cash, without being distracted by numbers that are not theirs and that they cannot move. Leadership, by contrast, sees everything: the full consolidated view and the ability to drop down to any hotel when something catches their eye.

This is not just tidiness; it is trust. When each team knows its dashboard reflects exactly its own reality, and no one is blending its performance with the hotel next door’s, the data stops feeling like surveillance and starts feeling like a tool. And a team that trusts its numbers actually uses them.

Measuring against the world: R2-Index and human support

Comparing hotels against each other inside the group answers “who is doing better in here?”. But one question remains: “and how do we do against the world?”. That is what R2-Index is for, a benchmark against an index that gives you an external reference. Knowing your best hotel leads the group is useful; knowing whether that lead also stands out against a reference index is another, more ambitious conversation.

It pays to be clear about what Spider Data is and is not. Spider Data consolidates and explains: it tells you what happened at each property and why, with live data, not last night’s close, with AI to ask in natural language, summarize, detect anomalies and surface hidden patterns, and with scheduled deliveries and alerts so the data comes looking for you. What it does not do is set prices per property: it is not an RMS. It measures and understands; the decision of what to charge at each hotel stays with whoever runs it. And as part of R2 OS, it opens its connectors, Power BI, Tableau, Looker via API with a Bearer token; your data does not live in a cage. When you need it, on the other end there is human support that speaks your language.

Traveling between the forest and the tree

A hotel group is not a single hotel multiplied; it is a set of distinct realities that share a direction. Governing it well demands both views at once: the view of the whole, which orders strategy, and the view of each property, where the day is truly won or lost. The false choice between “consolidate” and “see the detail” dissolves when there is a shared data structure underneath: the total is computed from the detail and the detail is reached from the total, without losing the trail along the way.

In the end, a good consolidation does not flatten the group into a number; it gives you a map to move through it. It lets you go up when you need to see the forest and down when you need to touch the tree, and, above all, it lets you decide better, because at last you are comparing what is comparable.