Zerf home

2 Its last run

What the routine produced last Monday: the report and the insights, the same work as level 2. Deck and email come in level 4.

01 · Report · next 7 nights

Fictional data from an OPERA Cloud test hotel (HOTEL-001). Business date 2027-10-18. Threshold 63.0%.

Night Day Occupancy on the books Rooms available Below threshold Group rooms (allocated / picked up) Source
2027-10-18 Mon 60.4% 490 Yes 2 / 0 hotel-001.json · occupancy[7]; availability[0]
2027-10-19 Tue 66.0% 421 2 / 0 hotel-001.json · occupancy[8]; availability[1]
2027-10-20 Wed 64.8% 436 0 / 0 hotel-001.json · occupancy[9]; availability[2]
2027-10-21 Thu 63.4% 453 0 / 0 hotel-001.json · occupancy[10]; availability[3]
2027-10-22 Fri 63.5% 451 0 / 0 hotel-001.json · occupancy[11]; availability[4]
2027-10-23 Sat 62.7% 461 Yes 0 / 0 hotel-001.json · occupancy[12]; availability[5]
2027-10-24 Sun 85.0% 186 0 / 0 hotel-001.json · occupancy[13]; derived from inventory

Next 7 nights: 66.6% on the books. Last 7 nights: 57.3%. Change: +9.3 points.

Warnings

  • rooms_available for 2027-10-24 is derived from the inventory and the occupancy: the export has no hotel-level availability row for that date.
  • The group grid covers 1 of 25 blocks listed in the export. Group numbers cover only the blocks in the grid.
  • rooms_with_open_maintenance is one count for every date: the export has no end dates for maintenance records.

02 · Insights

1. The next 7 nights are at 66.6% on the books, against 57.3% in the last 7 nights: up 9.3 points.

Why: More rooms are already sold for the coming week than were sold for the week that just ended.

What to look at: Whether the gain also reaches the two nights that are still below 63%.

Evidence: report.json last_7_days: occupancy_avg 0.5727, next_7_days_occupancy_avg 0.6656, change_vs_last_7_days 0.0929

2. Monday Oct 18 is at 60.4% on the books, below the 63% threshold, with 490 rooms available.

Why: It is the business date itself, so there is very little time left to sell those rooms.

What to look at: The two rate options for tonight in the rates note.

Evidence: hotel-001.json occupancy[7]; availability[0]

3. Saturday Oct 23 is at 62.7% on the books, just below 63%, with 461 rooms available.

Why: Sunday Oct 24 is at 85%, so Saturday is the weak night inside a strong weekend.

What to look at: The rate options for Saturday, five days ahead, and two-night stays with Sunday.

Evidence: hotel-001.json occupancy[12]; availability[5]; hotel-001.json occupancy[13]; derived from inventory

4. Groups picked up 0 of the 2 allocated rooms on Oct 18 and on Oct 19.

Why: The block has not picked up yet, and the group grid covers only 1 of the 25 blocks in the export.

What to look at: The release date of this block, and the 24 blocks that are outside the grid.

Evidence: hotel-001.json occupancy[7]; availability[0]; hotel-001.json occupancy[8]; availability[1]; report warning: the group grid covers 1 of 25 blocks listed in the export

5. 45 rooms have open maintenance before Sunday Oct 24, the busiest night at 85% with 186 rooms available.

Why: The export has no end dates for maintenance, so the same count shows on every date.

What to look at: Which of the 45 rooms can be back in service before Sunday.

Evidence: hotel-001.json occupancy[13]; derived from inventory; report warning: rooms_with_open_maintenance is one count for every date; report warning: rooms_available for 2027-10-24 is derived from the inventory and the occupancy