A tool that suggests a move every day is not helping you; it is keeping you busy. Most nights need nothing, and the job of a decision tool is to tell you which ones do. “Hold” is not doing nothing — it is a conclusion, and it has its reason written next to it.
How the signal is made, before we get to what stops it
The WisDom RM Dashboard crosses two things for every date: booking pace — how full the night is compared with similar nights, in the same season and at the same distance — and your position against the comp set, that is your rate against the adjusted average of the competitors you record: the ARI. Out of that cross comes one signal, the WisDom Suggestion: raise, hold, watch, cut. At 100% the night is sold out, which is a separate state — there is no room left to sell at any rate, so there is no rate to discuss.
Without a rate to start from — recorded, a decision on the Rate Sheet, or the base rates — it does not decide. Without pace, neither. The cell stays empty instead of guessing. And on top of that table sit rules that can cancel a cut after it has been worked out. That is not timidity; each of them has, at some point, corrected a mistake that would have cost money.
No comp set, no cut — ever
Your pace is soft and you have recorded no competitor rate for that night. Two explanations fit your data equally well:
- The market has collapsed. Nobody is coming to the area, everyone is behind, and the rate really is the problem.
- You are already the cheapest. The others sell higher and fill more slowly, and a discount just gives away revenue that would have come anyway.
Same number, two worlds, opposite actions. Without a reference point they cannot be told apart — and because a mistake does not cost the same in both directions, the WisDom Suggestion never suggests a cut without a comp set. Ever. A wrong cut is revenue lost for good; a wrong hold is revenue delayed.
And the reason is stated separately, because it is not the same: “nobody has recorded any rates” is different from “the competitors are closed”. The first is fixed with some work tonight. The second is not. Remember too that the rate you compare is gross — what is left of it depends on the channel, and the hotel next door may sell at the same euros with a completely different net.
Why twelve nights
The “expected pace” is not a constant. Where the hotel has enough past nights in the same cell — same season, same distance from the date and, when the sample allows, the same group of days — the night is judged by its position among your own similar nights: “very strong” means fuller than 3 in 4. Where it does not, a general assumption is used, and the screen says which of the two applies. The threshold is twelve nights. Here is why a threshold is needed, using the centre of the sample, the median:
38% · 41% · 44% · 52% · 55% · 61% · 63% → median 52%
Two more nights come in, 30% and 33%:
30% · 33% · 38% · 41% · 44% · 52% · 55% · 61% · 63% → median 44%
Shift in the expected value: 8 points ≈ 4 rooms
Today’s on-the-books 46%: behind on the first sample, ahead on the second
Nothing changed about the date you are looking at. What changed is what you know about your hotel — and the recommendation flipped. Twelve is a choice, not a theorem; having a threshold is not. A spreadsheet has no rule of silence: the average comes out just as willingly from two nights as from twenty, and it never tells you how much sample is behind it.
Two details matter more than they seem. First, the rule does not leave you in the dark: when the sample is missing, you are told how many nights are missing, not just “hold”. Second, it separates “I calculated and found too few” from “I have not calculated yet”. They are different states and should not look the same.
Did you know? Every rate suggestion in WisDom RM comes with its basis written underneath — how many nights the cell has, whether the expected value is measured or a general estimate, why the comp set is missing. And the Decision Log keeps your decision next to what happened afterwards.
Try it free for 14 days →An event day is a different day
On a public holiday or a local event, soft pace is a false signal. Bookings for those days follow a different rhythm — they come late and then all at once — so a comparison with a normal Tuesday says “you are behind” when you are not. That is why the cut is cancelled on a public holiday and on a local event you have entered.
For a hotel in Greece, public holidays, Easter included, are worked out by the app on its own; anywhere else, you enter them yourself. Local events, though, you always enter yourself: the app does not go looking for which event matters to your hotel. A village festival ten kilometres away fills one property and leaves another completely untouched, and no holiday is worth the same as another.
When the market asks for two nights
In the rate recording form, next to the rates, there is a MinLOS column: the minimum stay the market is asking for on that date. It is not your setting — it is an observation, just like the rate next door.
When the market asks for two nights, someone has already judged that the date can carry a condition. That is no proof they are right, but it is enough not to cut your rate at the same moment the market around you is tightening. It is recorded per date and per room type, because the minimum stay is not necessarily the same for the standard room and the suite — just as the rate gap between them is not the same either.
The closed competitor: a reason not to cut, not a reason to raise
The hotel next door is not selling tonight. The temptation is to read it as an opportunity or a threat, depending on your mood. Both are guesses, because there are at least two explanations with opposite meanings: it is full, or it is closed — renovation, season, its own reasons. In the first case the market is getting tighter. In the second, nothing has happened at all.
From one closed cell they cannot be told apart — and because a wrong cut costs more than a wrong hold, the closed competitor drops out of the average (there is no rate to include) and does not give you permission to cut.
It does not create an increase on its own either. If your own data says “hold”, the suggestion stays “hold” and simply notes that you could check whether an increase would hold. If your data already asks for an increase, each closed competitor adds 3% of your rate to it: demand looking for a room, at the moment you have one. The trigger always comes from your own hotel.
When bookings say something different from the level
Pace is a photo: how full the night is today. Three more brakes look beyond it, and each one stops a cut that the photo asks for:
- Speed. The night is low, but over the last few days bookings have been arriving at the expected speed or faster. The level is slow; demand is coming. The cut waits.
- Last year. You have already passed last year’s final occupancy for the same night — the same weekday, or the same event by name. Last year’s demand carried less; it does not support a discount.
- Forecast. From 14 days out and closer, when there is a forecast of final occupancy and its whole range is above the season’s target: you will reach it without a cut.
None of the three moves the rate on its own. They stop movement; they do not create it. And the reason is written with its numbers: how many bookings a day, which night last year, which range.
What you do instead of cutting
“Hold” does not mean “do nothing for that date”. It means “do not touch the rate”. Everything else is still open: late checkout on days the room is not needed early, breakfast, an upgrade when the higher room type would stay empty. They cost less than a discount and show more, because the guest compares them with the list rate while you pay your own cost — the arithmetic is worked out in the article on direct bookings.
There is also the unpleasant version: sometimes “hold” means the day will keep some empty rooms and no rate move will change that. That is information for next year, not an action for today — as long as you have kept a record of what you knew when you decided.
Conclusion
A tool that suggests a move every day tells you something about itself, not about your hotel: that it has no way to say “I don’t know”. The useful part is not the recommendation — it is the line underneath that says what it was based on. When it says “five nights are missing from the sample”, it gives you both the recommendation and the measure of trust it deserves. And most days, once the data speaks clearly, you will find that your rate was already right.
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 ↗