Know Thursday will be brutal, before you build Tuesday’s roster.
Hotel demand forecasting software predicts arrivals, departures, occupancy and covers, per department, per hour, from the live pickup in your property system (OPERA Cloud, Mews, Cloudbeds). Manual 90-day forecasts run about 28% error. A forecast driven by live pickup refreshes as bookings change, and in HotelCadence worked examples department-level accuracy rises from about 71% to 94%, so Tuesday’s roster is built on what Thursday will look like.
HotelCadence is workforce software for hotels. It reads the bookings already in your property system, forecasts how busy each department will be hour by hour, builds the roster to match, records worked hours and prepares payroll. Department heads approve every roster. From US$6 per scheduled employee per month.
Hotel demand forecasting is the prediction of how many guests a hotel will serve, per department and per hour, over the coming days and weeks: arrivals and departures at the desk, rooms to turn in housekeeping, covers in each outlet. The forecast draws on property-system reservations and pickup, history, and signals such as holidays and events, and its purpose is to size the roster before the shift. Pricing is the revenue management system's job.
A spreadsheet forecast is about 28% wrong at 90 days
Only 28% of hotels run a dedicated revenue management system (Skift Research, 2026), the rest forecast in Excel, and the error grows with every week of horizon. Staffing budgets, casual-pool sizing and rosters all inherit that error: 60% of shifts end up overstaffed (Unifocus, 2024) while the real peaks queue. Every point of forecast error is paid in idle hours on one day and in review scores on the next. Run your own rooms and wages through the hotel labor savings calculator to see the size of the leak.
The data behind this chart
| Forecast horizon | Manual forecast error (MAPE) |
|---|---|
| 7 days | 8% |
| 14 days | 11% |
| 30 days | 15% |
| 60 days | 22% |
| 90 days | 28% |
How hotel demand forecasting works: per department, per hour, rebuilt as pickup changes
The forecast uses your own property-system data: internal history (up to two years of reservations, occupancy and covers) plus the real-time bookings and pickup flowing in today. On top of that it blends external signals, weather, day of week, public holidays and local events, because a rainy Songkran Tuesday does not book like a dry one. The result is demand per department, per hour: check-ins at the desk, room turns for housekeeping, covers at breakfast.
When a tour block books 80 rooms on Thursday night, Friday morning’s forecast already shows it. Where you load a budget, HotelCadence shows actuals and forecast against it, so you see the variance per department while the month is still open.
The same forecast feeds AI hotel staff scheduling: rosters are drafted from it, and published shifts get flagged the moment pickup drifts away from them. Connection details per system: Oracle OPERA Cloud integration · Mews integration · Cloudbeds integration. The housekeeping waves and desk shifts that follow from the forecast are on the housekeeping scheduling page, and the hotel staffing calculator shows the arithmetic from forecast to staff per hour.
The data behind this chart
| Day | Actual covers | HotelCadence forecast | Manual forecast |
|---|---|---|---|
| D1 | 230 | 244 | 310 |
| D2 | 195 | 210 | 310 |
| D3 | 410 | 385 | 310 |
| D4 | 380 | 357 | 310 |
| D5 | 240 | 254 | 310 |
| D6 | 210 | 198 | 310 |
| D7 | 285 | 268 | 310 |
| D8 | 420 | 395 | 310 |
| D9 | 250 | 265 | 310 |
| D10 | 215 | 203 | 310 |
| D11 | 235 | 249 | 310 |
| D12 | 395 | 372 | 310 |
| D13 | 415 | 390 | 310 |
| D14 | 300 | 282 | 310 |
Worked example, figures indicative, 250-room Bangkok property in tour-group season.
Every number opens to the pickup behind it
Every number opens into the pickup behind it: which segments, which group blocks, which day-of-week pattern. F&B managers see covers by arrival mix; housekeeping sees departures and stay-overs. The conversation changes from “the system says 340” to “two tour groups check out Tuesday.”
We measure accuracy the way we measure savings: against your actuals every week, in the same report you see. Guest service stays the constraint. The forecast exists so peaks are staffed as much as so quiet hours are cut.
Tokyo, business hotel: Golden Week housekeeping tracked departures
A 30-day-out manual forecast (~15% error) flattened the Golden Week departure waves into an average: overtime on the wave days, rooms returned late, arrivals queuing in the lobby. A departure-driven forecast per day rebuilt the housekeeping plan as pickup firmed: overtime −18%, every room back by 15:00, review scores unchanged. Read how it was measured in the Tokyo Golden Week housekeeping case study.
Measured result, property anonymized at client’s request.
Forecasting questions revenue and ops teams ask
What is hotel demand forecasting?
Hotel demand forecasting is the prediction of how many guests a property will serve per department per hour over the coming days and weeks: arrivals and departures at the desk, departure and stayover rooms for housekeeping, covers per outlet. HotelCadence builds it from property-system reservations, pickup and history plus holidays and events, re-forecasts daily, and uses it to size the roster.
How accurate are hotel demand forecasts?
A manual spreadsheet forecast runs about 8% error (MAPE) 7 days out, 15% at 30 days and 28% at 90 days. In HotelCadence worked examples, department-level accuracy improves from about 71% with a flat manual number to about 94% with a forecast driven by live pickup, enough to staff to the curve. Accuracy is tracked weekly against your own actuals.
What data does forecasting need from Opera, Mews or Cloudbeds?
A secure connection that only reads your property-system data: reservations and pickup, arrivals and departures, occupancy, rate and segment mix, and F&B covers where available. OPERA Cloud, Mews and Cloudbeds each connect directly, and HotelCadence never changes anything in your property system. The model combines this internal data (history plus real-time bookings) with external signals such as weather, day of week and public holidays. No guest payment data is needed.
Can it compare the forecast and actuals against our budget?
Yes. If you load a budget or an existing forecast, HotelCadence shows actuals and the AI forecast against it per department, so variance is visible while there is still time to act on it. Where no budget exists, the agreed baseline plays that role.
How is this different from a revenue management system?
An RMS forecasts rooms to set prices. HotelCadence forecasts operations to set staffing: per department, per hour, check-ins at the desk, room turns for housekeeping, covers at breakfast. The two run side by side; only 28% of hotels use a dedicated RMS anyway (Skift Research, 2026), and neither replaces the other.
How often does the forecast update?
Every time pickup changes in your property system: a tour block booked Thursday night shows up in Friday morning’s forecast. Published rosters are flagged when they no longer match the updated forecast, so managers can adjust before the shift.
Can it forecast tour groups, public holidays and local events?
Yes. Group blocks and nationality mix come straight from the property system; holiday calendars (Golden Week, Chinese New Year, Songkran) and local event patterns are configured per property during onboarding. These are the days manual forecasts miss by the widest margin.
How much history do you need to start?
12-24 months of property-system history where available for seasonal calibration; the model can work with less. We pull history through the same secure connection that only reads during onboarding, and we validate the forecast against your own recent months before any roster relies on it.
30 minutes · your own property-system data if you share access · no obligation.