Forecasting demand, reading pace and pickup, and planning for seasons and events. 7 questions, with the answer first and the working after it.
How do I forecast hotel demand?
Forecast hotel demand by starting from the rooms already on the books for each future date, adding expected pickup based on how bookings normally arrive, and adjusting for events, seasonality, and how this year compares to last. A working forecast projects occupancy, ADR, and revenue per date, and you refine it as pace data comes in and confidence grows.
The backbone is on-the-books plus pickup. For each future date you know how many rooms are already booked; from history you know roughly how many more you typically pick up in the remaining window. Add those together for a base forecast, then adjust: an event or holiday lifts it, a soft comparable last year or a lagging pace pulls it down.
Segment your forecast where you can — transient and group behave differently, and group is often known further ahead. Compare the shape of this year pace curve to last year for the same date: tracking ahead suggests upside, tracking behind suggests you may need to stimulate demand. Update the forecast on a regular cadence as new bookings land.
Accuracy improves with rhythm and honest inputs, not complexity. A simple, consistently maintained forecast beats a sophisticated one nobody updates. Platforms such as RevPerfect read a hotel’s own pace and pickup to surface how each date is tracking, which shortens the manual work of assembling the picture. The judgement — what to do about it — stays with the revenue manager.
Pickup is the number of new room nights booked for a given date (or period) between two points in time. If you had 40 rooms on the books for next Saturday yesterday and 46 today, your one-day pickup is 6. It measures the pace of new bookings coming in and is the core input to short-term forecasting and pricing.
Pickup is always measured over an interval: daily pickup (since yesterday), weekly pickup (since last week), or pickup since a fixed reference. It can be for a single arrival date or a whole month. The point is momentum — not how full you are, but how fast bookings are arriving, which tells you whether a date is heating up or stalling.
Strong pickup on a still-distant date is a signal to hold or raise rate; weak pickup as the date approaches is a signal to stimulate demand. Pickup also feeds the forecast: your projected final position is on-the-books plus expected remaining pickup, based on how that lead time normally behaves.
Most teams read pickup from a daily pickup report that compares today on-the-books with earlier updates. Assembling it by hand from the property management system is the tedious part. RevPerfect can automate that report from validated exports supplied by supported hotel systems, so the numbers are ready to review each morning.
Booking pace is how your bookings for a future date accumulate over time compared with a reference — usually the same date last year or your budget. Where pickup is the new bookings in one interval, pace is the whole trajectory. Tracking ahead of last year pace suggests strength; tracking behind suggests a date needs attention.
Pace is best pictured as a curve: on the vertical axis, rooms on the books; on the horizontal, days before arrival. You compare this year curve for a date to last year at the same lead time. If today, 30 days out, you hold 55 rooms versus 48 at the same point last year, you are pacing ahead by 7.
Pace answers the question pickup cannot: is this normal? Ten pickups in a day sounds good, but if last year you had twenty by now, the date is actually soft. Reading pace stops you from misjudging a date on raw booking counts and is the foundation of confident rate decisions weeks and months out.
Pace works at every level — by date, by month, by segment. Group pace and transient pace often diverge and should be watched separately. The limitation is that it needs clean historical data for a fair comparison; a hotel with less than a year of history, or an unusual prior year, has to lean more on market signals and judgement.
The booking window, or lead time, is how far in advance guests book before they arrive. It varies by segment and season: business travellers book days out, leisure and group book weeks or months ahead. Knowing your typical window per segment tells you when to expect pickup for a date and how early your pricing decisions actually matter.
Booking window shapes your whole calendar of attention. If most of your leisure demand books 30 to 60 days out, the rate you set two months ahead is the one that captures it — waiting until the last fortnight means the window has already closed. Conversely, a heavily last-minute market rewards holding inventory and rate later.
Windows shifted after 2020 toward shorter lead times in many markets, then partly rebounded, and they differ sharply by segment: corporate and crew book short, weddings and conferences book a year or more out, OTA leisure sits in between. Averaging them together hides the pattern, so analyse the window per segment where you can.
Practically, the booking window tells you which future dates are still live. Dates inside your typical window are where pricing and pickup decisions have the most leverage; dates far beyond it will barely move yet and mostly need monitoring, not action. It stops you from over-managing dates that are simply too early to react to.
What is wash (wash factor) in hotels?
Wash is the difference between rooms blocked or reserved and rooms actually materialising — the portion that washes away through cancellations, no-shows, or unpicked group blocks. A wash factor is the percentage you expect to fall off, applied so your forecast reflects likely real arrivals, not optimistic block counts. It is essential for accurate group forecasting and overbooking decisions.
Group blocks are the classic case. A conference reserves 100 rooms but historically only 85 get picked up by attendees — the block washes by 15%. If you forecast on the full 100 you overstate occupancy and may turn away transient business you could have sold. Applying a wash factor forecasts the realistic 85 and frees the rest.
Wash also applies to transient business through cancellations and no-shows. Non-refundable rates wash less; flexible rates and certain OTA bookings wash more. Tracking your actual wash by segment and rate type turns a guess into a number you can forecast with, and it directly feeds how much you can safely overbook.
The discipline is measuring wash from your own history rather than assuming it. Over-estimating wash means you release rooms that were really coming and end up oversold; under-estimating it means you sit on empty rooms a washed block would have vacated. Review wash assumptions against what actually materialised, and adjust.
What is seasonality in hotel revenue management?
Seasonality is the predictable pattern of demand rising and falling across the year — peak, shoulder, and low seasons — driven by weather, holidays, school terms, and local events. Revenue management uses it to set base rate expectations and inventory strategy per period, so you push rate in peak, drive occupancy in low, and manage the transitions in shoulder season.
Almost every hotel has a demand calendar with distinct seasons, and they differ by market: a ski resort and a beach resort peak in opposite months, a city hotel swings with corporate and conference cycles plus weekday-weekend patterns. Mapping your own seasonal shape — by month and by day of week — is the first step in any annual plan.
Strategy flips by season. In peak, demand exceeds supply, so the job is to maximise rate and use length-of-stay controls to capture full value. In low season, demand is scarce, so the job shifts to driving occupancy and base business — packages, longer stays, and segments that travel off-peak. Shoulder seasons are where careful pricing earns the most, because demand is genuinely elastic.
Seasonality is a starting assumption, not a fixed rule — each specific date still moves with events, competitor moves, and pace. Use the seasonal pattern to set expectations and staffing, but let current pace and incoming pickup fine-tune the actual rates. The risk is pricing purely on the calendar and missing an unusually strong or weak year.
What is the difference between a budget and a forecast?
A budget is the annual revenue target set once, before the year begins — the plan you are held to. A forecast is your current best estimate of what will actually happen, updated regularly as bookings arrive. The budget rarely changes; the forecast changes constantly. You manage against the forecast and report performance against the budget.
The budget is a commitment. Built during annual planning from historical trends, market outlook, and ownership targets, it sets the occupancy, ADR, and revenue goals for each month and stays fixed so performance can be measured against a stable line. Changing the budget mid-year would defeat its purpose as an accountability baseline.
The forecast is a living estimate. It starts from on-the-books plus expected pickup and is revised as pace data, events, and market conditions evolve — often weekly for the near term, monthly further out. A good forecast is judged on accuracy: how close it lands to actual results, not how closely it matches the budget.
You need both. The budget tells you whether you are on plan and drives cost and staffing commitments; the forecast tells you what to do now to influence the outcome. When the forecast drifts below budget, that gap is the revenue manager call to action — adjust pricing, push a segment, or open demand — well before month-end.
