Your Hotels Against Each Other: Portfolio Benchmarking for Independent Groups
A portfolio-wide guest score blends strong and weak hotels into one number that describes none of them. For a group of 3 to 20 independent hotels, the first benchmark isn’t a competitor. It’s your own other hotels. This article explains why the average misleads, how a property-by-aspect grid shows where a group is uneven, and how to tell a property-specific weak spot from a group-wide one.

SENTEEZ
Guest Experience Insights

Picture an operator running six independent hotels. The group-wide guest score looks healthy, the quarterly summary reads well, and nobody is worried. Yet one property keeps generating the same complaints, and the team can feel it, even though the number says otherwise.
That’s the problem with the portfolio average. It’s built from every property at once, so a weak hotel can sit inside a strong total and never show up as a finding.
For a group of 3 to 20 independent hotels, the first benchmark isn’t a competitor. It’s your own other hotels. Before asking how you compare with the market, ask how each of your properties compares with its siblings, aspect by aspect. A strong average is a hiding place, not a finding. This article explains how to look behind it.
Why the portfolio average misleads
An average blends strong and weak properties into a single number. The strongest hotels pull it up, the weakest are diluted, and the result describes none of them accurately.
Volume makes this worse. A group score is usually dominated by the properties with the most reviews, so a large, well-performing hotel can mask a smaller one that’s struggling. The opposite also happens. In one UK coastal sample of 20 hotels, the review-weighted rating was 4.12 while the simple average was 4.26. The gap came from a handful of very small, highly rated hotels: 8 of the 20 had fewer than 100 reviews, including two rated 5.0 on 21 and 30 reviews. The lesson applies to any group. A 4.8 built on 40 reviews isn’t the same evidence as a 4.8 built on 600.

There’s also the question of what the number is made of. Two properties can share the same overall score for completely different reasons. One may be excellent on service and weak on rooms, the other the reverse. The average erases that difference, and it’s exactly the difference an operator needs.
If you want a related view on reading risk across several assets, see our article on. That piece is about where to look first. This one is about comparing the aspect profiles once you’re looking.
What a side-by-side view looks like
The method is simple. Take each property’s recurring guest-experience aspects, such as Front Desk & Staff, Room Quality, Noise Levels and Maintenance & Upkeep, and lay them out in one grid: properties down the side, aspects across the top, the group mean as a reference.
Read across a row and you see one hotel’s profile. Read down a column and you see how the whole group performs on one aspect. Three questions then become easy to answer:
- Which property trails its siblings, and on which aspect? A hotel scoring 20 points below the group mean on Room Quality is a different conversation from one that’s simply a little below average overall.
- Which property has already solved a problem the others share? If one hotel handles an aspect well while the rest struggle, the group already owns a working model.
- Is a problem group-wide or isolated? One weak cell points to a local cause. A weak column points to something the whole group does.

A quick note on terms. Aspect counts are Review Mentions, not unique reviews, because one guest review can speak to several aspects. Each aspect score should always be read together with how many properties and mentions sit behind it.
How wide the spread can be inside one market
How different can hotels be when they share a town, a season and a guest base? Our public dataset gives a concrete picture. In one Swiss alpine and lake destination covering 42 hotels, ratings run from 2.76 to 4.80, a spread of more than two stars. On Front Desk & Staff, individual hotel scores run from 40% to 99% positive, and that aspect is reported by all 42 hotels.
Split the same hotels into thirds by rating and the gaps are just as clear. The top third scores 89.0% positive on Room Quality against 56.1% for the bottom third, a gap of 32.9 points. On Front Desk & Staff it’s 91.4% against 62.8%, a gap of 28.6 points. Both aspects are reported by every hotel in the sample.

The point isn’t about that destination. It’s that hotels facing the same market and the same guests can differ by 30 points or more on the aspects operators care about most. A portfolio can hold the same spread inside it, and a group average won’t show it.
Important caveat: these are independent hotels in one market, not a portfolio. They show how large internal spread can be, not what any particular group looks like. Markets also differ in type, hotel mix and traveler base, so these figures shouldn’t be compared directly with other regions. All figures are based on publicly available review data and describe what guests say, not what happens inside a hotel.
Group-wide or property-specific?
Once the grid is in front of you, the most useful question is the shape of each weak spot.
Property-specific. One hotel scores low on an aspect its siblings handle well. The cause is probably local: a team, a process, a manager or a single building. The fix belongs to that property’s general manager, and the siblings can show what good looks like.
Group-wide. Every property is weak on the same aspect. That points above the property level, to a brand standard, a shared supplier, a group policy or a common building type. The owner of the fix is the group, not any single hotel.

The same distinction shows up in public market data, which makes a helpful analogy. On Value for Money, one Swiss destination shows a hotel-specific pattern, where the best hotels have largely solved the problem and the weakest haven’t. A US coastal village shows a market-wide pattern, where most hotels score poorly together. The same low score calls for a different response in each case. These are market examples, not portfolio data, but the logic carries over.
The takeaway is practical. Before you spend money or management time, know which shape you’re looking at, because the fix and the owner are different.
Moving what works between properties
A side-by-side view does more than flag problems. It shows where the answer may already exist inside your group.
If one property scores strongly on Front Desk & Staff while two others trail, the group has an internal reference point: a team, a training approach or a handover routine that guests respond to. Comparing against a sibling is often more persuasive than comparing against an outside benchmark, because the same owner, standards and brand voice sit behind both.
A word of care. Guest reviews show where friction appears. They don’t show why it exists, or what it will cost to remove. A strong score at one hotel is a prompt to go and look, with the manager or an engineer, at what that property actually does differently. It isn’t proof that the practice will transfer, and it says nothing about cost or payback. Treat it as a lead worth testing, not a conclusion.
How to start with your own group
You don’t need a new system to begin. The steps are straightforward:
- Gather public reviews for every property. Use the same sources and the same time window for each hotel, so the comparison is like for like.
- Apply the same aspect categories to all of them. Front Desk & Staff, Room Quality, Noise Levels and Maintenance & Upkeep need to mean the same thing at every property.
- Check review volume. A property with only a few dozen reviews can swing sharply. Flag it rather than ranking it.
- Lay the results side by side in a property-by-aspect grid, with the group mean alongside.
- Read for shape. Mark each weak cell as property-specific or group-wide before deciding anything.
Be cautious with thin data. An aspect with fewer than 50 Review Mentions, or reported by fewer than three properties, shouldn’t drive a conclusion. Always show how many properties report each aspect next to its score. And remember the limits of the method: it uses publicly available review data only, so it describes what guests say, not what happens inside a hotel. Signals are a starting point for investigation, not proof of cause.
Compare your hotels against each other first
Competitor benchmarking tells you how you stand in the market. Portfolio benchmarking tells you where your own group is uneven, and that’s often the quicker place to find an improvement, because the comparison group shares your standards and your owner.
A portfolio score can look comfortable while one property quietly carries the weakness. The side-by-side view makes that visible. Compare your hotels against each other before you compare them against anyone else.
See it on your own properties
If you operate a small group of independent hotels and want to see how this looks on your own properties, we can walk you through a demo of Cross-Location Benchmarking.
Cross-Location Benchmarking demo page
Frequently Asked Questions
Key answers regarding hospitality sentiment diligence and data methodology.
We rank hotels only with 100 or more reviews. Below that, a score can still be shown, but it should be flagged as thin and read with care.
Yes, with limits. Three properties are enough to see which one trails on a given aspect and whether a weakness is shared. They’re too few to split into tiers, so keep the reading simple and descriptive.
No. It comes first or alongside it. Knowing how your own hotels differ makes any comparison with competitors more useful, because you know which of your properties to compare.
Publicly available guest reviews only. SENTEEZ doesn’t see a hotel’s financials, bookings or internal records.
See what your guests are really saying about your hotel.
A free, analyst-built snapshot of your guest sentiment and how you compare with one competing hotel, delivered within 48 hours.
- Your hotel's rating, with a clear summary
- One-competitor benchmark: where you win and lose
- Your top recurring guest themes
- Delivered within 48 hours
- Free, with no commitment

Written by SENTEEZ
Guest Experience Insights
Related Insights

One Benchmark, Four Readers: What Owners, GMs, Department Heads and Revenue Managers Each Need from the Same Comparison
A guest experience benchmark is usually written for no one in particular, so it ends up used by no one in particular. This article reads one anonymized Lucerne benchmark through four sets of eyes: the owner, the general manager, the department head and the revenue manager. It ends with a one-page meeting format that gives each reader one question to take to the next meeting.


What a Guest Sentiment Benchmark Can’t Tell You (and What to Pair It With)
A guest sentiment benchmark describes what public reviewers say about a hotel. It doesn’t measure revenue, operations or the opinions of guests who didn’t write a review. This article covers the five questions a review-based benchmark can answer, the five it can’t, why refreshed datasets can mislead, and which sources to pair it with, including STR and PMS data.


Is It Your Hotel or Your Market? How to Separate Local Problems from Structural Ones
A weak guest score can mean your hotel has a problem or your whole market does, and the fix, budget and upside differ in each case. Using SENTEEZ town-level benchmarks across four Swiss markets, this article shows how three tests sort a weak score into market-wide, hotel-specific or tier-specific. It also covers what the diagnostic can’t tell you, and a three-step checklist for acting on the result.
