One occupancy number for a hotel group

A hotel group usually has more than one system that thinks it knows occupancy. The property management system has one view. Channel tools have another. A spreadsheet from last week has a third. On Monday, the commercial call spends the first twenty minutes deciding which file to trust.

That delay is expensive. Rate and staffing for the week ahead get set late. A local event does not get an override in time. Labour is planned from last week’s occupancy, not from the pickup you can already see.

What “pickup” means here

Pickup is how bookings change as you get closer to the stay date. If Tuesday night was 62 percent booked last Friday and is 71 percent booked this morning, that rise is pickup. Group commercial needs that picture across properties. Each hotel still needs room to mark a wedding, a match, or a road closure.

Build one property-level model

Pull occupancy, rate, and channel mix into one weekly, or daily, view per property. Use the same room and date keys everywhere. Do not force every hotel to look identical on the page. Force the definitions to be identical: what counts as a room night, how you treat out-of-order rooms, how you treat complimentary stays.

Add a 7 to 14 day forecast that a revenue manager can override, with a short reason. Feed a simple labour and outlet signal so operations is not guessing. Group commercial should see the same pickup the hotel sees, on the same day, without waiting for a property pack.

What to watch

Do the Monday numbers match across properties without a debate? Are shoulder nights, the quieter nights around a busy period, getting a rate or staffing change in time? Is the override used when a local event is real? If the override is never used, the forecast is either ignored or too rigid.

A useful occupancy pack is not a prettier chart. It is one number the group and the hotel can both defend, plus room for a human to change it.