Use case: roll up a hotel group into a single view

Picture a group with five properties. Monday morning each hotel sends its spreadsheet: one reports in pesos, another in dollars; one calls a column “occupancy,” the one next door calls it “% occ”; one nets out comps before counting revenue and the other does not. By Friday someone has finished pasting it all into a master file, and by then the numbers are already a week old. The roll-up exists, sure, but it arrives late and no one quite trusts it. This is an illustrative use case of how Spider Data turns that weekly puzzle into a single view you watch live.

The symptom: every property reports its own way

The first pain is not a lack of data. It is that there is plenty of data, but each piece speaks a different language. When a group grows by acquiring hotels, it inherits each one’s format: the spreadsheet the manager of Property A built looks nothing like Property B’s, and Property C’s was designed by someone who no longer works there. It is not bad faith; it is entropy. Each hotel solved its own report as best it could, in its own moment, with its own people.

The problem shows up the instant leadership wants a single question answered: how is the group doing? To answer it, someone has to open five files, learn five different logics, rename columns by hand, line up currencies, decide what counts as revenue and what does not, and only then add it up. That “only then” is the bottleneck.

The deeper problem: no common structure, no fair comparison

Comparing two hotels seems trivial until you try to do it right. If Property A computes its ADR over rooms sold and Property B computes it over rooms available, the two numbers carry the same name and mean different things. Ranking them side by side is not just useless: it is misleading, because it suggests a conclusion the data does not support.

It helps to be explicit about three acronyms used constantly in hospitality, because the roll-up lives or dies by how they are defined:

• Occupancy: what percentage of your available rooms actually sold on a given night. It measures how full the hotel was.
• ADR (Average Daily Rate): how much, on average, each room sold for. It measures the price at which you sold.
• RevPAR (Revenue per Available Room): room revenue divided by every room you had to sell, occupied or not. It folds full-ness and price into one number, which is why it is the metric most compared across properties.

The rule is simple: if each hotel defines these numbers its own way, the group does not have one truth, it has five opinions. A fair comparison requires that everyone measure the same thing the same way. That is not fixed with discipline and memos; it is fixed with a common structure that computes the metrics identically for all, once, over each property’s real data.

The solution: one view for the whole group

Spider Data brings together eight sources from each hotel’s operation, reservations, cash, channels, payments, guests, orders, shifts, and cash movements, into a single common structure. You do not ask each manager to change how they work: each property’s raw data comes in as it is, and the metric is computed once, the same way for all. Occupancy at Property A and Property E mean exactly the same thing because they come from the same formula.

Calculated fields and joins, no code

The roll-up is built in a drag-and-drop report builder, with no programming. You define calculated fields once, ADR, room nights, booking lead time (how many days before arrival the reservation was made), cash reconciliations, and reuse them across every property. You cross tables together (what data people call a JOIN: pairing, say, reservations with payments to see not just what was booked but what was actually collected) and you get totals by level (what is called a ROLLUP: subtotals per hotel, per brand, per region, and the grand group total, all in the same table).

Compare, rank, and give each team its own slice

On that base you can see the group the three ways leadership tends to think about it: by individual hotel, by brand (if the group runs several flags), and by region. And you can rank: order properties by occupancy, by ADR, by RevPAR, or by margin, to see at a glance who is pulling and who is dragging. Dashboards are live with cross-filters: click a region and the whole board refocuses to it instantly.

Team-based access closes the loop. Each property sees its own numbers and not the others’ kitchen; leadership sees the entire group. No one wastes time building a report to send upward, because upward is already watching it on the same platform, at the same moment.

What to consolidate from a group

Not everything consolidates the same way or for the same purpose. Here is a practical list of what is worth unifying into a single group view:

1. Occupancy, ADR, and RevPAR per property, with the same definition for all, so you can compare without asterisks.
2. Revenue and margin by hotel, brand, and region, with subtotals that add up to the grand group total.
3. Channel mix: what share of business comes through online agencies, direct booking, or phone at each property.
4. Booking lead time: how far in advance guests book at each hotel, to anticipate the pace of occupancy.
5. Payments and collections: what was booked versus what was actually collected, plus cash reconciliations by shift.
6. Returning guests: which properties retain best and which always lean on new customers.
7. R2-Index: how each property and the group as a whole measure against a reference index, not just against themselves.

The result: see the whole group, live

The change is not cosmetic. Before, the question “how is the group doing?” took a week and was answered with last week’s data. After, it is answered by opening a view that is already built and refreshes with the real operation, not last night’s close. The conversation moves from “are these numbers right?” to “what do we do about them?”.

And AI helps you read the group without designing every report: you can ask in plain language, for example, “which property dropped its RevPAR this month, and why?”, and get a clear summary. AI also watches the group in the background: it flags anomalies (a sharp drop in collections at one hotel, a reconciliation that will not close) and hidden patterns that are hard to see staring at five tabs at once. If you want, scheduled deliveries and alerts make the roll-up arrive on its own, every morning, to whoever should see it.

A group that cannot see itself together does not operate as a group: it operates as separate hotels that happen to share an owner.Spider Data

One property pulls, another drags: now you can tell

The real value of consolidating is not the pretty report. It is that, when everything is measured the same and seen together, it becomes obvious which property is pulling the group up and which is dragging it down, and, above all, why. Maybe the hotel that looked behind on occupancy actually holds the best ADR in the group, or the one boasting high occupancy gets there by giving away rate. Without a common view, those stories stay buried in files that never talk.

Consolidating well is not stacking files: it is giving the group a single language to look at itself. From there, leadership stops guessing with old data and starts deciding on what is really happening, property by property, today.