Multi-Property Hotel Groups: 6 Steps to Build a KPI Goal Tree
Month-end in a five-property group runs like this. Corporate asks the properties for their files. The properties send them. Corporate opens them and finds that none of the numbers reconcile. The next three days go into digging for where each number came from, not into producing anything.
That is not measurement. That is archaeology.
The properties are not being sloppy. The group simply does not have a shared goal tree. This piece builds one in six steps: a four-layer structure running from objective down to indicator, a definition set locked across every property, and a single named owner and single data source behind every number. It ends with a checklist to clear before the scorecard goes live.
The balanced scorecard comes from Kaplan and Norton's 1992 Harvard Business Review article, The Balanced Scorecard. Hospitality adds one complication they did not have to solve: they wrote for a company, and you are designing for a company that behaves like five companies.
Where month-end consolidation turns into archaeology
There is an easy test for whether the scorecard is working. If someone at corporate is on the phone to a property asking "how did you calculate this," it is not.
The symptoms repeat across groups, and each has a structural cause underneath it.
| Symptom | What is actually broken |
|---|---|
| The same indicator returns two different numbers at two properties | The formula was never defined, so each property invented one |
| One property's data is always late | The indicator is owned by a department, not a person |
| The scorecard total moves and nobody can explain why | Weights were never documented |
| The GM reads their own report instead of the scorecard | The scorecard does not drive an operational decision |
| Month-end close takes more than three days | Data sources were never mapped indicator by indicator |
Not one line in that table is a spreadsheet problem. They are all design problems. Change the spreadsheet and you will hit the same problems faster.
It is not a spreadsheet problem, it is a definition problem
How many things can "occupancy" mean inside one group? Count them.
One property runs rooms sold over total rooms. The second runs rooms sold over rooms available and strips the floor under renovation out of the denominator. The third books house-use and comp rooms on the sold side. The fourth counts group blocks on the contract date rather than the arrival date.
All four are defensible. None is wrong on its own. Roll all four into one scorecard and the resulting number measures nothing.
This is the most expensive quiet failure in a measurement system, and it behaves like a cost nobody has priced. Like the hidden line items on the P&L, it goes unmanaged because nobody ever put a figure against it.
The fix is not picking a tool. It is writing down four layers before you measure anything:
- Objective — intent at group level
- Goal — the numeric commitment at property level
- Sub-goal — accountability at department level
- Indicator — one measurable number
The six steps below build those four layers in order.
Step 1 — Write the objective layer
The objective layer carries no numbers. It carries sentences.
Write five objectives at most. More than five means you have not prioritised, and the scorecard will expose that within a quarter. Every objective has to clear three tests:
- Is it group-level? Anything a single property can deliver on its own is a goal, not an objective.
- Will it move within a year? Five-year intent belongs in the strategic plan, not on a scorecard.
- Would it change a management decision? If not, it is a slogan.
A workable set: lift profit per available room, deepen guest loyalty, hold continuity in key positions, level brand standards across the portfolio.
Watch that fourth one. Most groups carry it as an unspoken priority, never write it into the scorecard, then act surprised when properties drift apart.
Accept up front that the non-financial objectives have a financial shadow. Staff continuity looks like an HR topic; in the accounts it is a cost line. Tying an HR score to financial impact is the most commonly skipped part of this layer, and the part that pays back fastest.
Step 2 — Push goals down to the property
The classic mistake here is dividing the group goal by the number of properties. Whatever revenue growth the group has committed to, writing the same figure against each property is easy and wrong.
Those properties are not operating under the same conditions. One opened last year, one just came out of renovation, one is mature and already brushing its occupancy ceiling. The goal has to reflect where the property starts and how much room it has to move.
Use this as the decision rule.
| Property situation | Goal logic |
|---|---|
| New opening, first two years | Ramp goal on a cumulative curve, not an absolute number |
| Mature, near the occupancy ceiling | Goal on ADR and channel mix, not on occupancy |
| Repositioned after renovation | Compare against the new segment's comp set, not last year |
| Seasonal resort | Goal per season window, not per calendar year |
| Steady city hotel | Prior year plus market growth |
Goals differ by property. Indicators do not. Hold that line: two properties may target the same indicator at different levels; they may not calculate it with different formulas.
Once the property goals are written, check that they add up to the group goal. If they fall short, either one property is carrying too much or the group goal was never realistic. Run that check in Step 2 or you will run it in November.
Step 3 — Attach sub-goals to departments
A property goal does not describe anything a person can act on when they sit down at their desk tomorrow morning. That is what the sub-goal layer is for.
Break each property goal down to the departments that move it directly. One rule governs the split: a sub-goal has exactly one department owner. Anything written jointly against two departments ends the month owned by neither.
A worked chain:
- Objective: lift profit per available room
- Property goal: raise net contribution per room across the season
- Sub-goal (Front Office): grow the direct channel share
- Sub-goal (Housekeeping): hold room turnaround time inside the target band
- Sub-goal (HR): shorten time-to-fill on key positions
Three departments, one property goal, three distinct accountabilities. Nobody is doing anybody else's job.
Cap how many sub-goals a department carries — three to five works. Past seven, the department head stops reading the scorecard as a priority list and starts reading it as a compliance burden.
Step 4 — Define the indicator: formula, unit, source, owner
The indicator layer is what the whole scorecard stands on. Defining an indicator does not mean naming it. It means filling in four fields.
| Field | What goes in it | Example |
|---|---|---|
| Formula | Numerator and denominator spelled out, exclusions included | Room nights sold / room nights available |
| Unit | Percentage, days, count, currency | Percentage |
| Source | One system, one named report | PMS — daily rooms statistics report |
| Owner | A person, not a job title | Front Office Manager, named |
If any one of the four is blank, the indicator does not go on the scorecard. Every indicator you let through half-defined becomes an argument six months later.
Watch the distance between the name and the formula too. If survey completion rate is reported under a heading that says "guest satisfaction," the scorecard is measuring survey discipline. Catch the gap between what an indicator is called versus what it captures in Step 4, or spend the year managing the wrong thing.
Naming a person rather than a title in the owner field is practical: titles go vacant, people hand over. Keep a backup owner field so the indicator is never orphaned mid-handover.
Step 5 — Lock the shared definition set
The definition set is the group's measurement dictionary. It lives in one place, it carries a version number, and properties cannot edit it.
Locking it means making three decisions.
- Which indicators are group-mandatory and which are property-discretionary? Keep the mandatory set small. Anything that has to be comparable across properties is mandatory; everything else stays local.
- Who can change a definition, and how often? Recommended: once a year, in the budget cycle. A definition that shifts mid-year destroys prior-period comparison.
- What happens to historical data when a definition changes? There are two options. Pick one and write it down.
| Approach | When to use it | What it costs |
|---|---|---|
| Restate history under the new definition | Formula correction, data error | Heavy workload, trend survives |
| Set a cut-off date and freeze what came before | The concept itself changed, or the business model did | Cheap, but the trend breaks |
The industry already gives you a foundation for this. USALI, the uniform system of accounts for lodging, standardises revenue and expense lines by department; the 12th revised edition was published in July 2024 with an adoption date of 1 January 2026 (AHLA announcement). Build your financial indicators on that structure instead of inventing them, and add only your operational and HR indicators on top.
Do not keep the definition set in a Word file. It needs versioning, a date stamp, and a single source of truth.
Step 6 — Map the data source and the collection calendar
An indicator whose data arrives late is an indicator you are not measuring. Step 6 puts that on a calendar.
For each indicator, write down three things: which system produces the data, who pulls it, and what day of the month it is ready.
| Indicator type | Typical source | Frequency | Close day |
|---|---|---|---|
| Occupancy, ADR | PMS | Monthly | Month + 2 |
| Departmental expense | Accounting | Monthly | Month + 5 |
| Guest feedback | Survey / reputation platform | Monthly | Month + 3 |
| Employee turnover | Payroll / HRIS | Monthly | Month + 3 |
| Training completion | HRIS | Quarterly | Quarter + 5 |
| Brand standard audit | Audit report | Half-yearly | Period + 10 |
The working column is the last one. Set the close date off the slowest input, not off the average. If accounting lands on the fifth, the scorecard cannot publish on the fourth.
Write a separate rule for the quarterly and half-yearly indicators: one whose measurement period has not arrived shows as blank on the monthly scorecard, never as zero. If your setup cannot draw that distinction, your GMs will read a false alarm every month.
Testing whether the four layers actually hold together
The design is done. Run four tests before it goes live.
Trace up. Pick an indicator at random and walk upward: which sub-goal does it serve, which property goal does that serve, which objective does that serve? If the chain breaks, the indicator is dead weight. Most groups delete a handful the first time they run this — a good outcome.
Trace down. Start from each objective and walk down: is there at least one indicator measuring it? If not, the objective is written but unmeasured.
Weight test. Do the weights inside each layer total 100, and does the distribution match the priority? If your most critical objective carries the smallest share of the scorecard, the design contradicts the intent. Indicator weighting also varies by property — a city hotel and a seasonal resort do not have to carry the same weight set.
Comparability test. Put the same indicator from two properties side by side. Is the gap between them a real performance gap or a calculation gap? If you cannot answer, go back to Step 5.
Once all four tests pass, you will see why holding all four layers in one structure matters as much as it does: while the layers live in separate files, you have to repeat these tests by hand every single month.
Three mistakes almost every group makes during setup
One — too many indicators. A scorecard carrying thirty indicators per property communicates no priority. The Balanced Scorecard Institute's core framework rests on a small, balanced set for exactly this reason. Fifteen to twenty per property works; above that you are buying maintenance load.
Two — measuring what is measurable. An indicator chosen because the data was easy to get drifts away from the objective and drains the scorecard of meaning. Start at Step 1 and work down. Never start from the data you happen to have and work up.
Three — scoring before the design is finished. Start the weighting argument before the definition set is locked, and the definitions will bend to make the scores look better. Hold the order: definitions, then weights, then scores.
Checklist before the scorecard goes live
Do not publish until all ten of these read yes.
- Five objectives or fewer
- Every objective has at least one indicator
- Every property goal is differentiated by that property's situation
- Every sub-goal has exactly one department owner
- Formula, unit, source and owner are filled in on every indicator
- The owner field names a person, not a title
- Group-mandatory and property-discretionary sets are separated
- The definition set is versioned and date-stamped
- Every indicator has a close day written against it
- Trace-up and trace-down have been run with no broken chains
A few will come back as no the first time you run the list. That is expected. Fixing them before launch costs a fraction of fixing them after.
Conclusion
Building a scorecard across a group is a definitions job, not a reporting job. Five of the six steps happen before anything gets measured.
Hold the sequence: write the objective, push the goal down to the property, attach the sub-goal to a department, define the indicator across four fields, lock the definition set, map the data to a calendar. Then run the four tests and clear the checklist.
Get the design right once and month-end stops being an excavation and becomes a reading exercise. That is where the real return sits: the management meeting stops arguing about whether the number is correct and starts arguing about what it means.
If you are building your group's goal tree and the definition gaps between properties are where it keeps stalling, that is worth a conversation. The HRMIM team works with hotel groups on measurement structure — get in touch to walk through it with your own property set.


