When analyzing performance for a property or across a portfolio, there may be periods where a hotel was not operating. This can include:
Pre-opening periods
Renovations
Seasonal closures
Temporary operational pauses
If these dates remain in your analysis, performance metrics can become misleading.
For example:
Occupancy may appear artificially low
ADR and revenue may not reflect true trading periods
Capacity may still appear against dates when the hotel was closed
Portfolio-level views may be skewed if different properties had different closure timelines
To ensure your reporting reflects only active operating periods, you can use Property Closure events within the Calendar.
Why Filtering by Opening Date Isn’t Enough
It may seem logical to filter by an opening date or manually adjust stay date filters. However, this approach:
Requires property-specific filtering
Does not scale well across multiple properties
Becomes difficult to maintain in shared dashboards
Can create inconsistencies when aggregating portfolio data
Using Property Closure events is more flexible and dynamic. It allows each property’s operating timeline to be respected automatically — whether you’re analyzing one property or many.
The Solution: Property Closure Events
Property Closure events allow you to formally define non-operating periods in the Calendar.
Once created, these events can be excluded from your analysis so that:
Closed stay dates are removed from performance calculations
Capacity aligns with active selling periods
Occupancy, ADR, and revenue reflect only trading days
Portfolio-level aggregations remain accurate
This approach ensures a more representative and reliable performance overview.
How to Set Up Property Closures
Step 1: Navigate to the Calendar
Open the Calendar within the platform.
Step 2: Create a Property Closure Event
Select the appropriate date range (for example, January–March 2024).
Choose the event type: Property Closure.
Assign the event to the relevant property.
Save.
Repeat as needed for any historical or future closures.
If the property had not yet opened, you may need to create a closure event from the earliest stay date where data exists up until the official opening date.
Step 3: Exclude Closure Dates in Your Analysis
In your workbook or dashboard:
Add a filter for Property Closure.
Set the filter to exclude closure dates (for example, “is not Property Closure”).
Apply the filter.
Your analysis will now automatically exclude all dates marked as closures.
What Changes in Your Reporting
For Individual Properties
Closed months no longer distort occupancy
Capacity reflects only operating days
Revenue and ADR represent active trading periods
For Portfolio Views
Each property’s closure timeline is respected
Aggregated performance excludes non-operating periods
No manual property-by-property filtering is required
This is especially valuable when properties opened at different times or experienced different closure periods.
Important Considerations
In some cases, data may exist prior to a property’s official opening date due to integration timing. You may want to:
Confirm the first stay date where data is received
Create closure events covering non-operating periods
Adjust closure ranges as needed
This gives you full control over how operating timelines are reflected in reporting.
Best Practice
We recommend:
Creating Property Closure events for any period when a property was not operating
Applying a consistent closure exclusion filter in shared dashboards
Reviewing historical opening dates to ensure performance reporting aligns with operational reality