Reporting and planning
Hotel occupancy forecast: a practical weekly worksheet
Build a hotel occupancy forecast from confirmed room nights, new booking assumptions and cancellations, with scenarios and a weekly accuracy check.
The short answer
Add expected new room nights to confirmed room nights at a recorded cutoff, subtract expected cancellations once, then divide by available room nights for the target period. Document assumptions and check each date and room type. Save each forecast version so it can later be compared with actual occupied nights.
A hotel occupancy forecast estimates how many rooms a small hotel in Azerbaijan may use during a future period. It helps prepare staffing and supplies. A confirmed booking total is the starting position; it is not the final expected occupancy.
The worksheet below is an original fictional example. Its assumptions are not market statistics, measured probabilities or a guarantee of accuracy.
Separate a forecast from observed pickup
SiteMinder’s forecasting overview describes forecasting as using past performance, current bookings and market context to estimate future hotel performance. These inputs inform occupancy expectations; the forecast remains an estimate.
A pickup report measures a change already observed between two snapshots. A forecast adds explicit assumptions about changes that have not happened yet. Keep the labels separate when historical pickup informs an assumption.
Choose a future stay period and a precise cutoff. For example, save confirmed bookings at 09:00 Baku time on 7 October for the nights of 12–18 October, with departure on 19 October. Count room nights, not reservation documents or guest nights: two rooms occupied for three nights contribute six room nights regardless of guest count.
Record evidence beside each assumption
Record the cutoff, target dates, confirmed room nights, available inventory, expected gross additions and expected cancellations. Add the author, version and evidence behind each assumption. Retain the source extract for reproducibility.
Comparable previous weeks can inform expectations, but note differences in weekday mix, local events, room availability and booking conditions. Check booking lead time when deciding whether earlier booking patterns are relevant at this cutoff. Describe missing evidence explicitly; do not fill gaps with an invented conversion rate.
Keep group inquiries and waiting-list requests separate from confirmed bookings. Record their requested dates, rooms and decision deadlines, without assigning a fixed probability unsupported by evidence. An inquiry must not increase confirmed totals.
Calculate three transparent weekly scenarios
Assume 20 rooms are available on each of seven nights: 20 × 7 = 140 available room nights. The cutoff extract contains 84 confirmed room nights. No rooms are out of order in this example.
Expected room nights = confirmed room nights + expected gross additions − expected cancellations.
Forecast occupancy = expected room nights ÷ available room nights × 100.
| Scenario and assumptions | Expected room nights and occupancy |
|---|---|
| Conservative: 14 gross additions, 14 cancellations | 84 + 14 − 14 = 84; 84 ÷ 140 = 60% |
| Base: 28 gross additions, 7 cancellations | 84 + 28 − 7 = 105; 105 ÷ 140 = 75% |
| Strong: 35 gross additions, 7 cancellations | 84 + 35 − 7 = 112; 112 ÷ 140 = 80% |
Here, gross additions exclude cancellations. Each cancellation assumption covers losses from both currently confirmed and newly expected room nights, counted once. If using an expected net pickup figure that already includes those losses, do not subtract cancellations again.
These are planning cases, not probability ranges. Use them to discuss housekeeping shifts or supplies; none guarantees pricing or revenue results.
Check every night and room type
A weekly total below 140 does not prove every request fits. Additional demand might fall on an already full Saturday. Build a daily grid by room type, including existing stays, expected arrivals, lengths of stay and departures. A multi-night booking needs suitable capacity for every night.
Before sharing the forecast, check:
- Stay nights and booking statuses match the defined scope.
- Additions and cancellations have no duplicate entries.
- Each date and room type respects its available capacity.
- Out-of-order rooms follow a documented denominator rule.
- Assumptions have a source, owner and review date.
Use the same availability rule across scenarios and actual results. If available room nights are zero, report “not calculable.” A forecast is never permission to oversell a full date or substitute an unsuitable room type.
Save versions and compare with actual occupancy
Keep the original forecast unchanged; save updates as new dated versions. When the week closes, compare actual occupied room nights with the saved forecast using the same dates, room scope and denominator.
If actual occupancy is 98 room nights, the base forecast of 105 was seven room nights too high. Actual occupancy is 98 ÷ 140 = 70%, against 75% forecast: a difference of five percentage points, not five percent. Review which additions failed to arrive, cancellations differed or inventory assumptions changed.
BirOtel offers reservation management, occupancy and ADR reports, and Excel reporting. Bring this worksheet to a reporting demonstration to check the available source fields. Automatic forecasting, RMS functions, AI predictions and historical snapshot storage are not confirmed capabilities. Keep the versioned forecast separately and interpret it alongside occupancy and revenue metrics.
Frequently asked questions
Is confirmed occupancy the forecast? It is the cutoff starting position. Future additions and losses require explicit assumptions.
Can an unconfirmed group enter the base total? Keep it separate until confirmed; discuss its possible effect as a documented scenario.
How often should the forecast change? Review it on a consistent schedule and when material evidence changes, preserving every previous version.
These guides are published by BirOtel. General methods, illustrative examples and current product capabilities are identified separately. Sources appear beside the relevant explanations.
[email protected]Explore these workflows for your own hotel
Use your room inventory and daily tasks to assess whether BirOtel fits your hotel in a live demo.
