How We Rate Hotels

An aggregate is only honest if it is backed by a real dataset, published guest reviews we can name, with a score, a scale, and a review count. Catalog ratings assigned in bulk do not qualify. Until a hotel has that research, we do not invent a replacement formula or show the old number.

That is why two hotels in the same destination can look uneven on our site: one has a live Hotel Flock Score with named platforms, the other has none yet. Absence of a number is not a smear. It is an unfinished research job. We would rather show you dining venues and Good to Know than a decorative 9.2.

The overall Hotel Flock Score is a review-count-weighted average of named public platforms, each normalized to /10. Category scores, location, cleanliness, rooms, service, dining, design, and value, are our editorial reading of those reviews and of any published category breakdowns. Cleanliness and location are required before a score goes live.

We do not reweight a hotel upward because it is Aman, Belmond, or George V. A palace can still have a dining-room miss. A 26-room garden hotel can still have a location caveat (you will take a taxi). Category scores exist so a sky-high design number cannot hide a weaker value or dining read.

Those sections are review consensus, not marketing copy. Themes have to come from what guests actually repeat, views, service, a car-dependent hill, a dining room that does not always match the star. Factory filler stays off the page.

On a page like Amangiri you should expect land, silence, and architecture to show up as loves, and isolation or price as warnings, if that is what guests repeat. On George V you should expect service and dining to dominate, with the usual big-hotel caveats if reviewers mention them. We will not invent a "hidden gem" line for a 244-room palace off the Champs-Élysées.

We do not accept payment from any hotel, brand, or booking platform to influence a listing, a score, or a Best Of placement. Hotel Flock is not affiliated with Tripadvisor, Booking.com, Trivago, or any other review site. Awards appear only when we can name the awarding body.

Best Of lists (city, beach, safari, desert) are editorial shortlists, not a reskin of the score. A hotel can belong on a list because the building is irreplaceable even when the value score is the least flattering number on the page.

Use the overall number as a confidence check, then read the categories that match your trip. Dining-heavy anniversary: look at dining, then at the actual venue pages. Landscape trip to Aman Kyoto or Amangiri: design and location will tell you more than restaurant count. Family week: ignore romance copy and look at room product plus Guests Warn.

Then leave the score and read Good to Know, seasonal notes in the timing guide, and a featured compare if you are down to two hotels. The number is a filter. It is not the trip.

These examples do not change the math above. They show how to use it. On Aman Tokyo, a live score with strong design and service, plus a view caveat in Good to Know, should push you to request the Imperial Palace side rather than to hunt a different brand. On George V, strong dining plus a large room count should tell you the hotel can absorb a celebration. It should not tell you it is a 26-key garden. On Amangiri, design and location will dominate; value may look stern. That is information, not a veto, if the mesa is why you flew.

On a Belmond like Cipriani, expect the building and the launch to show up as loves, and city price or seasonal crowding as warnings if guests repeat them. We will not write around that to protect a brand. If a page has no score yet, use dining venue pages, room categories, and Good to Know. Then come back. Compare pairs: Compare.