[ 5.12 / THE PLAYBOOK ]

Unit 5 · Maximizing Performance Through Iteration · Lesson 5.12

When bookings stop

When a listing that used to book stops booking entirely, the cause is usually a market that moved while the pricing stayed still. This diagnosis walks a four-bedroom Big Bear Lake property from zero bookings back to a working calendar: check the listing is still being seen, read occupancy and price positioning against the market, then reset rates well below where the market sits and rebuild from there.

The full lesson text below is an edited transcript of the video, published 2026-08-24. The complete course is free at the playbook.

The pattern behind the silence

The setup is familiar. A listing was booking steadily, the calendar looked healthy, and then bookings fell off a cliff. It happens to operators who have never run a pricing strategy at all, and it happens just as often to operators who ran one well and then lost focus. Occupancy across their market slid, market rates moved, and their own prices did not change. Nothing about the listing broke. The market moved underneath it.

That distinction matters before you touch a single rate, because it points at a different fix than a listing problem does. If the market changed and the pricing did not, the pricing has to be rebuilt from current conditions rather than nudged down from where it used to sit.

Rule out the listing first

Two checks come before any rate discussion. The first is conversion: are people who search the market seeing this listing, are they clicking it, and are the people who click going on to book. The second is visibility: are views still coming through at all, or has the listing quietly stopped appearing in search results. If guests cannot see the property, no price fixes that, and every hour spent on rates is wasted.

In this case both checks passed. The conversion behaviour was healthy, the property was still being seen, and it simply was not being booked. That puts the problem squarely on rates and on what has happened in the market.

The listing and its inputs

The property is a four-bedroom in Big Bear Lake. Its three steps are set by booking window: the hedge step covers nights zero to four days out, the control step covers five to 42 days out, and the test step covers 43 to 365 days out. The cost inputs behind every net number are cleaning at $290, tax at 13.5%, and a platform commission of 15.5%. The review period is the two-week iteration just finished.

Confirm those inputs are right before reading anything else. The step boundaries and the deductions filter every occupancy and price number you are about to interpret, so an error there quietly corrupts the whole diagnosis.

Zero bookings everywhere

The first read of any iteration is where the bookings landed. Here the answer was nowhere. Not one booking in the hedge step, the control step or the test step. That changes both the urgency and the shape of the response.

When bookings are landing somewhere, you adjust around the gaps. When nothing is booking anywhere, the move is to get conservative fast and then build back up from a price point that has actually produced bookings. The reason is the asymmetry of being wrong. Cut too little, run another two weeks, and you have bought yourself another two weeks at 0% occupancy. Cut too far and you lose some margin on nights that at least sold. One mistake is recoverable, the other is a fortnight of nothing.

What the hedge showed

The hedge step is the last-minute window, zero to four days out. Listing occupancy was 0%. Market occupancy was 8.05%, expected to finish around 8.46%. That is a market where almost nobody is getting booked. Where it may have run somewhere around 21% a year earlier, under 10% of it is now selling.

The trend confirmed the picture: occupancy across the trailing 90 days was down 12.66% against the same period a year earlier. This is a declining market, and holding a high price into a decline like that leaves no realistic path to a booking.

Then the price positioning. The midweek hedge price was $575, which sat between the 50th and 75th percentile of the comp set. That is a high number for a hedge step in any conditions, and an impossible one at 8% market occupancy. With nothing booking anywhere, the target moves below the 25th percentile, which put the midweek hedge price at roughly $225.

The control period trap

The control step, five to 42 days out, ran from 2 December through to 1 January. Listing occupancy was again nothing. Market occupancy was very low, though expected to pick up slightly, which is the one encouraging signal in the picture. The trend underneath it was still negative.

A look at the month by month market data showed something odd: the market had raised its December rates year over year, even with occupancy expected to fall. Rates going up while demand goes down means the operators in that market have not adjusted yet. That is a reason to be more conservative in the control step than in the hedge step, not less.

There is a second trap in this window. The control period spans Christmas and New Year, so any blended midweek average across the whole step gets pulled upward by peak nights. Price the step off that blended figure and you charge holiday money for ordinary December weekdays. Those rates have to come from month level data with the peak period excluded.

The test period

The test step reaches 43 to 365 days out. That far ahead there is no expected market occupancy to read, so the evidence is the prior year’s occupancy and the direction of travel. Prior-year occupancy was not high, the trend is negative, and there is no reason to expect a market that has fallen this far to reverse on its own.

So the test step stays conservative, but not as conservative as the hedge. Midweek moves to the 25th percentile at $325. Weekends sit below the 50th percentile at $595, because prior-year weekend occupancy came in under 50% and the trajectory points down. That leaves a clear step up from the $225 hedge price to the $325 test price, which is the shape you want when the nights closest to check-in are the ones in trouble.

Reading the months underneath

Three prices could not be set from the step-level view: the weekend hedge price and both control prices. Those come from the month by month market data, with November, December and January in view.

November weekends, for the hedge price. Exclude the weekend sitting against Thanksgiving, which distorts the average, and weekend market occupancy came out around 35%. Weekend prices in the same period averaged about $320 at the 25th percentile and $435 at the 50th. At 35% occupancy you belong near the bottom of that range, so the weekend hedge price was set at $325, a shade above the 25th percentile, because the hedge covers the last minute and the last minute is where conservatism pays.

December midweek, for the control price, with Christmas and New Year excluded. Prior-year occupancy averaged about 34% and expected occupancy about 36%. The 25th percentile averaged $341 and the 50th averaged $486. Cross-checking against November midweek, where the 25th percentile was only $275, shows how much the market lifted its December pricing even in the quiet part of the month. With occupancy this weak, even the 25th percentile is too rich, so the midweek control price was set at $275.

December weekends, same method. Occupancy averaged 38% across the three non-holiday weekends. The 25th percentile prices ran $450, $495 and $668, averaging about $540, while the 50th percentile averaged $715. Occupancy of 38% does not support a 50th percentile price, so the weekend control price was set at $540.

The rebuilt price set

The next iteration runs two weeks, from the 26th through to the 10th, with the new rates loaded into a dynamic pricing tool such as PriceLabs.

Hedge, zero to four days out: $225 midweek, $325 weekend. Control, five to 42 days out: $275 midweek, $540 weekend. Test, 43 to 365 days out: $325 midweek, $595 weekend.

Set against a midweek hedge that started at $575, that is a reset rather than an adjustment. The old numbers were built for a market that no longer exists, so they were thrown out and rebuilt from current conditions. Note also that nothing here involves seasonality yet. This is the three-step read on its own, and seasonal layering comes after the listing is booking again.

After the reset

What you watch now is bookings, not the calendar filling. If a run of bookings arrives inside a few days, end the iteration early. A flood of bookings is enough information to say the price is working, and there is nothing to gain from holding a deliberately conservative rate for the full two weeks once it has proved itself.

Then reassess with real bookings behind you. The $275 and $540 control prices may well turn out to be far too low, and that is the expected outcome of a deliberate undershoot rather than a mistake. Raising rates off a calendar that is filling is a much easier problem than pricing into an empty one, and with nothing on the books there is no revenue to protect in the first place. Expect to walk the numbers back up in increments, iteration by iteration, toward where they used to sit.

Record the intent alongside the numbers. The goal of this iteration is booking traction, and the next decision depends entirely on how fast that traction arrives.

When the market ignores demand

The closing observation is the useful one. Occupancy in this market was trending down by more than 12%, and the operators in it responded by raising prices. That does not follow from anything in the data. It usually means a market pricing off what worked a year earlier rather than off what is happening now.

That is the same error this listing made, which is how a $575 midweek hedge price survived into a market running at 8% occupancy. The price was not absurd in isolation. It was absurd for these conditions. When the market moves against its own demand data, following it is how you end up with an empty calendar and a headline rate nobody actually paid. Read the occupancy, read the trend, and set rates that will get booked.

← 5.11 When you are booking up too fast 5.13 When your comp set outprices you →
Rather have the people who teach this run your pricing instead? Get my revenue map with Jack
Get my revenue map with Jack
Report