These are not customer projects
No property is described here and none is implied. We do not publish named customer portfolios, use hotel names as proof or imply relationships that would need permission we do not hold — that position is set out in full on the about page.
What is published instead is the reasoning. A named property tells a reader that somebody bought something; a worked scenario shows how the decisions were reached, which is the part that transfers to a different property with different conditions.
How each one is built
Each scenario states its conditions first — scale, climate, stay length, populations, what is already installed — because every conclusion depends on them. It then works through the decisions in the order they actually get made: count something, establish the technical constraint, narrow the construction, decide the artwork, then size the order.
Each ends with what would be ordered, so the arithmetic is visible rather than implied. Change a condition and the conclusion should change; if it does not, the scenario was not doing any work.
Read the one closest to your conditions
Scale and water exposure matter more than category. A 480-key all-inclusive and a large water park have more in common operationally than two properties that both call themselves resorts.
If none of the five is close, the guides cover the same decisions in the abstract and the resort-use pages cover the settings.