A shared view.Every hotel in context.
Management needs to compare. Local teams need to act. Connect both perspectives with clear sources, definitions and responsibilities for each property.
Comparison starts with shared definitions.
A portfolio report loses value when each hotel interprets the period, channel or figure differently. Start with comparable sources and criteria while retaining each property’s context.
The same report. Different questions.
Three fictional properties help prepare the group meeting. Switch roles to see what needs review, keeping illustrative statuses separate from real results.
| Property | Working basis | Pending review |
|---|---|---|
| Property A | Period defined | Review reservation source |
| Property B | Period defined | Validate report currency |
| Property C | Period pending | Agree on the same cut-off |
Agree on the reporting basis
Before comparing performance, leadership checks the period and source used by each property. A pending status is a review task, not a hotel result.
Resolve property C’s period definition before comparing all three.
| Property | Working basis | Pending review |
|---|---|---|
| Property A | Example environment 1 | Review preferences |
| Property B | Example environment 1 | Validate team access |
| Property C | Example environment 2 | No cross-environment profiles |
Define each audience’s scope
Marketing reviews the data environment and preferences before preparing segments. Properties in another tenant are not added to a shared audience simply because they belong to the group.
Keep environment C’s audience separate and review permissions within the shared environment for A and B.
| Property | Working basis | Pending review |
|---|---|---|
| Property A | Booking pace | Review stay dates |
| Property B | Channel mix | Review classification |
| Property C | Budget | Confirm comparable basis |
Prepare each hotel’s decision
A common view helps locate the questions; the local team reviews its reservations and budget in detail. The comparison does not apply prices or change inventory.
Open the relevant hotel’s detail and agree on an action with its revenue owner.
Manual exploration. These scenarios do not send messages or change any hotel data.
Coordinate without losing the differences.
The group defines the framework; each hotel keeps the information it needs to decide.
Agree on a reporting basis
Review periods, currencies, sources and filters before placing properties in the same report. Keep observed data traceable.
BI → Revenue · comparable criteriaRespect data scope
Organise properties and access within the configured environment. Group workflows do not imply sharing profiles across separate tenants.
CDP · defined environment and permissionsTurn reporting into local action
Use booking pace and reports to prepare a conversation with each hotel. Define what to review, who decides and what evidence is missing.
Revenue · team decisions
Before taking the first step.
Is data shared automatically across every hotel?
No. The environment, properties and access must be defined. The product structure separates data by tenant; a profile view spanning separate tenants is not assumed.
Can I compare hotels using different sources?
First review coverage, definitions, currency and periods. If the bases are not equivalent, the report must show that difference before conclusions are drawn.
What should we bring to the demo?
A report used by management, the sources for two properties and a decision that is difficult to prepare today. We will use illustrative examples to define the workflow.
Connect your group’s view.
Tell us what leadership compares and what each hotel needs. We will start with the report, sources and access scope.
Request a demo for my groupExplore other solutions