A Saturday has 26 rooms booked out of 47, 21 days before arrival. Good or bad? From that alone, nobody knows. Booking pace is how many rooms you have on the books for a night at a given distance from arrival, measured against something. Without the distance and without the yardstick, 26 is just a number.
Two questions that look the same
“How full is the night?” and “how is it doing against its own schedule?” are not the same question. A night three months ahead with a third of the rooms sold is empty — and may be doing very well for that early. A night the day after tomorrow at two thirds looks good — and may have fallen behind where it should be.
That is why, in the WisDom RM Demand Calendar, the colour of each day shows only the first one: the occupancy already on the books. Pace is written separately, on the Pace line when you open the day. If both were painted in the same colour, you would have to guess every time which one it was telling you.
What you compare with: your own similar nights
The fairest yardstick is your own hotel. Not every night of it, but the nights that look like the one in front of you: the same season (as you set it, month by month), the same group of days (Friday–Saturday or Sunday–Thursday) and the same distance from arrival, in five windows: 0–3, 4–7, 8–14, 15–30 and 31+ days. For each of those nights that has already happened, you count how many rooms it had at the same point. Then you see where today’s night falls among them.
23 · 25 · 27 · 28 · 29 · 30 · 31 · 32 · 33 · 34 · 36 · 38
Expected (median) 30.5 rooms → 65% · today 26 rooms → 55%
As full or fuller than 2 of the 12 → Soft
Tuesday · 12 similar Sun–Thu nights, rooms 21 days out:
14 · 16 · 17 · 18 · 19 · 20 · 21 · 22 · 23 · 24 · 25 · 27
Expected (median) 20.5 rooms → 44% · today 26 rooms → 55%
As full or fuller than 11 of the 12 → Very strong
Same 26 rooms, same distance, opposite signals. Both at 55% today — the position among your own similar nights tells you how it is going. The Saturday is behind, because your Saturdays are usually fuller at this point. The Tuesday is ahead, because your Tuesdays rarely get there this early. The expected value is the median, not the average: one night with a cancelled group would drag the average down, but it does not move the median.
The five signals are positions in that row. Very strong means as full or fuller than 3 in 4 similar nights, strong than half of them, normal than 1 in 4, soft than 1 in 10, and problem emptier than 9 in 10. These are definitions you can explain, not a measurement of what will happen.
And if you do not have twelve such nights yet? Then there is no row to stand in. The app falls back first to the season, with all days together, and if that is not enough either, to a general estimate with fixed limits. Under the signal it says which one applies and how many nights you have so far.
Last year — but at the same point
The second yardstick is last year, and it has a trap that catches almost everyone. The rooms booked for a night that has not come yet are not compared with last year’s final. They are compared with what you had last year at the same distance from arrival. Otherwise you see a permanent shortfall that does not exist — more on this in the same time last year article.
The trickiest version of the trap is the STLY column of your PMS. Some systems put a true “same time last year” there and others put last year’s final, under the same column name. WisDom RM does not assume; it measures it every time you upload the daily report. The simplest of its checks: on dates two months ahead, where you have no bookings yet, a genuine “same time last year” would also be almost empty. If the column shows a large part of the hotel sold there, it is the final. Then the number reads as “how much of last year’s final you have already reached”, not as pace. Until it has been measured, it is read neither as pace nor as a target. And when you have your own report uploaded exactly 364 days earlier, on the same weekday, the comparison uses that: same system, same distance.
A photo and a film
The position among similar nights is a photo: where the night is today. It does not say how it got there. The 26 rooms may have come in during the last week, or they may have been 26 seven days ago too. Booking speed is the film: how many rooms per day came in over roughly the last seven days, against what you would expect at this stage from the same similar nights.
The week before +4, the last week +6
20 → 26 rooms = +0.9/day · expected 0.6/day
Soft level, bookings coming in → no cut
Tuesday · 26 → 26 rooms = 0/day · expected 0.5/day
Very strong level, no new bookings → no increase
The photo asked for a cut on Saturday and an increase on Tuesday. The film stops both. The Saturday is behind, but bookings are arriving faster than expected — a discount there could give away revenue that is already on its way. The Tuesday is ahead, but its level is old: no one has booked for a week.
The WisDom Suggestion reads booking speed exactly like this, as a brake. It does not suggest a cut while bookings arrive at the expected speed, nor an increase once they have stopped. It does not use speed to push the rate, because it does not yet know how many euros an acceleration is worth. And from 95% upwards it does not judge speed at all: there, the pace drops because the rooms run out, not the demand.
Did you know? Pace does not exist unless you take the photo. Every daily report uploaded to WisDom RM becomes a snapshot: how many rooms each future night had on that day. From those snapshots come the booking curve of each date, the booking speed and, a year later, the comparison with yourself. A missed upload cannot be made up: today you upload today’s report, not yesterday’s on-the-books. And with no report, the Pace line says “No daily report”, so no rate suggestion is made.
Try it free for 14 days →When pace does not say what you think
- A day with an event. Bookings for a holiday or a local event follow a different rhythm: they come late and then all at once. Compared with a normal day, that looks like “behind” when it is simply early. That is why, on a public holiday or a local event you have entered, the WisDom Suggestion does not suggest a cut because of soft pace. Which events are worth entering is covered in holidays and local events.
- By room type. Pace is always for the whole hotel. Rate suggestions come by room type; pace does not. Which type is selling out is shown by your PMS, and from there you set the rate gap between your room types.
- The first year. With few past nights, most signals rest on the general estimate, and they say so. That is not a fault. It is a hotel that does not yet have enough history of its own.
Conclusion
Keep three things. Compare a night with your own similar nights, at the same distance, and read its position, not its number. Compare with last year only at the same point, and find out what your PMS really puts in its STLY column. And do not trust the photo without the film. One thing worth trying: next to next Saturday’s booked rooms, write how many days are left until arrival. Then look up how many rooms your last twelve Saturdays of the season had at the same distance.
Mathematician with studies in hospitality management and years of night shifts in hotels. WisDom RM — and this blog — were born on the night shift.
LinkedIn ↗