How to read your demand forecast without being an analyst

You open the forecast panel and see numbers that do not speak to you yet: on the books, pace, pickup, projection. This guide teaches you to read them with confidence and to audit where each one comes from, no analyst required.

Why learning to read it pays off

A forecast you do not understand is a number you do not use. Once you can read what is booked, the rhythm and the momentum of each date, you stop deciding on gut feel: you know which nights are on track, which ones call for a price move, and how much to trust the projection in front of you.

Step 1: start with what is booked (OTB)

OTB (on the books) is what you already have reserved for a future date: your confirmed demand as of today, bookings minus cancellations. It is the only number in the forecast that is not an estimate; everything else is built on top of it.

1. Pick a future date and find its on-the-books figure: those are the rooms already confirmed for that night.
2. Remember it is a snapshot of today: tomorrow, with new bookings or cancellations, the number changes.
3. Never read it alone: 12 rooms booked (illustrative example) mean nothing without knowing how many days out you are. That context comes from pace.

Step 2: read pace, your position against your own history

Pace compares what you have booked for a date against what you had for comparable dates in your history, at the same lead time. It answers the question occupancy alone cannot: am I ahead of or behind what is normal for me?

1. Locate the lead time: how many days remain until the date you are reading.
2. Compare your OTB against your own history at the same lead time, not against last month and not against another hotel.
3. Read the verdict in three states: ahead (you hold more than your normal pattern), in line (tracking as usual) or behind (you hold less, and it pays to review the price in time).

Step 3: read pickup by time window

Pickup is the net change in bookings for a date (new bookings minus cancellations) over a recent window: the last day, the last week, the last two weeks. If pace is your position, pickup is your speed right now.

1. Look at the short window first (the last day) to catch sudden surges or stalls.
2. Cross-check with the week and two-week windows: one good day on its own is not a trend; three straight weeks of weak pickup is.
3. Interpret the combination: a behind pace with strong pickup suggests the date is recovering on its own; a behind pace with weak pickup calls for action today.

Step 4: audit the projection before trusting it

The month-end projection is not magic: Sentinel AI takes your OTB and divides it by the fraction of demand that was historically already booked at that same lead time. Every number exposes its method so you can verify it.

1. Check the method: the pace fraction used and which part of your history it comes from.
2. Check the sample size: a projection built on many comparable dates carries more weight than one built on two.
3. Check the events moving it: a conference or a long weekend flagged on the calendar explains why the projection departs from the normal pattern.
4. Verify the honesty limits: the projection never falls below what is already booked and never rises above your capacity. If a number breaks that, you are reading something wrong.

When the system says there is not enough history

If your hotel has little booking history for a date or a lead time, Sentinel AI tells you so instead of inventing a projection that looks precise. Take it as information, not as a failure: it means that figure deserves more of your judgment and less blind trust, and every month of operation sharpens the curves.

Common mistakes when reading a forecast

• Reading occupancy without the lead time: 50% booked (illustrative example) is excellent at 90 days out and worrying at 7; the number only makes sense with the anticipation next to it.
• Comparing against last month: the right reference is your own comparable date at the same lead time, not the previous month with a different seasonality.
• Treating the projection as a promise: it is a snapshot of today that recalculates with every booking, not a commitment on how the month will close.
• Ignoring the sample: two identical projections are not worth the same if one comes from years of history and the other from a handful of dates.
• Watching a single number instead of the trio: OTB, pace and pickup are read together; any one of them alone can mislead you.

How it looks in Sentinel AI

In Sentinel AI, inside R2 OS, the forecast lives next to your reservations: every date shows its OTB, its pace against your history at the same lead time and its pickup by window, and every projection exposes its method, pace fraction, sample and events. No black boxes: you read, you audit, you decide.