Recipe 14 - The Rate Visibility and Availability Watch: Catch Pricing Errors Before Demand Books Elsewhere
Catch Pricing Errors Before Demand Books Somewhere Else
From The Spiral Sales Office Recipe Vault | By Paul Woodley
Every hotel has dates where demand is walking to a competitor in real time and nobody in the sales office knows it. The rate is wrong for the date. The hotel shows as unavailable while two comp-set properties are still selling. The search ranking has dropped so far that the property is effectively invisible to the customer already shopping.
Recipe 14 is the prompt that catches those dates before the demand is gone. It takes your rate-shop export and surfaces the specific dates that need attention this week, with clear flags that tell you exactly what kind of problem each one represents.
What This Recipe Makes
A weekly watch list of specific dates where the hotel's pricing, availability, or search visibility is costing it transient revenue it could be capturing, with clear flags distinguishing sold-out-while-competitors-sell situations from rate positioning issues from search ranking problems.
- Head Chef: Revenue Manager, reviewed with DOSM
- When to Cook It: Weekly, and before any high-demand date
- Ingredients: A forward daily rate-shop export comparing your live rate to your named comp set, for the next several weeks, including a market demand score and your search ranking on the OTA where available
The Three Flags This Prompt Raises
- Sold Out While Competitors Are Still Selling - Every date where the hotel shows sold out or unavailable while two or more comp-set hotels are still selling. This is lost transient demand moving to a competitor in real time. The flag triggers an immediate review of whether the closure is intentional or an inventory or availability error
- Priced at the Top While Demand Is Low - Dates where the hotel is priced significantly above the comp set median on a low-demand date, without a visible differentiator that would justify the premium. These are dates where the pricing position may be deterring bookings rather than maximising rate
- Invisible in Search on High-Demand Dates - Where search ranking data is available, dates where the hotel ranks materially lower than its comp position on a date where demand score is high. Being on page two of an OTA search on a peak demand date is a revenue problem with a specific fix
Why the DOSM Needs to See This Report
Rate visibility and availability watching is typically positioned as a revenue management function. And it is. But there is a specific reason for the DOSM to review the output: the decisions this report surfaces affect the group sales team as well as transient, and the DOSM is the person who has to connect the transient picture with the group displacement decisions being made at the same time.
A date that shows sold out while the comp set is still selling may be correct, because a group is holding the space and the displacement decision was right. Or it may be an inventory error. The DOSM is the person who can tell the difference and who needs to know which situation exists before the weekly revenue strategy meeting.
The Weekly Rhythm This Prompt Supports
Recipe 14 is designed to run weekly, not monthly. Rate and availability issues are time-sensitive. A pricing error on a high-demand date that is caught seven weeks out can be corrected. The same error caught two days out is a lost revenue conversation, not a fixable one.
The weekly cadence turns this from a reporting exercise into a real-time management tool. The goal is not to document errors after demand has passed. It is to catch them while there is still time to capture the business.
Where the Output Goes
The weekly revenue strategy meeting agenda, where rate and availability decisions are made. The revenue manager's correction list for the current week. The DOSM's awareness of which high-demand dates have open issues before group displacement conversations happen.
The Mirror
On your highest-demand date in the next thirty days, do you know right now whether your hotel is priced correctly against the comp set, showing available, and ranking where it should in OTA search? If any of those three questions cannot be answered without pulling a report, Recipe 14 is how you build the habit of answering them proactively.
A Note on Data Handling
Confirm what your employer, owner, brand, and management company permit before pasting rate-shop data into any AI platform. Comp-set rate data, particularly at the individual property level, may be subject to data-use restrictions depending on the source. When in doubt, consult your revenue management system vendor and your brand guidelines. Every output is a starting position. The decisions still belong to you and your revenue manager.
Your Next Step
Export your rate-shop data for the next six weeks today. Run Recipe 14 before your next weekly revenue strategy meeting. Walk in knowing which dates have flags, what kind of flags they are, and what the team needs to do about each one before they close.
The demand that books somewhere else this week does not come back. Recipe 14 is how you catch it before it leaves.
Paul Woodley | The Spiral Sales Office
