The host problem

A cancellation arrives. Four nights open up. Your first question is
usually “how much should I drop the rate?”

That question skips a step. Ask what the signal says about those
nights right now. Sometimes you hold. Sometimes you cut. Sometimes you
do neither. You reshape minimum nights and let demand find a better
fit.


The three responses

Use hold, cut, or reshape based on lead time, occupancy risk, demand
visibility, and gap shape.

Hold

Hold rate when the signal still supports the original price on those
dates.

Signals that support holding:

A guest cancels a Friday-Saturday weekend booking 18 days out. The
event still runs, and two inquiries came in last week. That is a hold
signal. Drop immediately and you may rebook below what the market would
have paid.

Cut

Cut rate when inventory risk is real and the window is closing.

Signals that support cutting:

Inside 7 days, many listings shift from hold logic to absorption
logic. Cut enough to signal availability, not so much that you collapse
rate quality for surrounding bookings.

Reshape

Reshape minimum nights when the gap shape is blocking conversion.

Sometimes cutting rate is not the problem. The reopened calendar
cannot convert because the minimum-night setting blocks likely
buyers.

A cancellation leaves Thursday, Friday, Saturday, and Sunday open.
Your minimum stay is three nights, so a Friday-Saturday guest cannot
book. Dropping rate does not fix that. Opening the weekend to two nights
may recover the high-value dates at a better replacement ANR than a
broad cut.


A four-night example

A guest cancels a Thursday-through-Monday booking — four nights, $800
in accommodation revenue — with 11 days until check-in. Original
accommodation revenue was $200 per night on average. You now have
Thursday, Friday, Saturday, and Sunday reopened with 11 days to
rebook.

Here are three responses and when each fits:

Response A — Hold weekend rate, soften shoulder
nights

Keep Friday and Saturday at the original rate. Drop Thursday and
Sunday modestly. Open minimum nights to two so a weekend-only guest can
book Friday-Saturday. This fits when weekend demand still exists and the
listing shows saves, views, event demand, or seasonal support.

Response B — Cut the full stay

Drop the per-night rate across all four nights. Keep minimum stay at
three or four nights only if that stay pattern still has a buyer. This
fits when demand has genuinely thinned and the alternative is leaving
multiple nights unbooked. The risk is losing rate quality on weekend
nights that might have held.

Response C — Reshape minimum nights, protect weekend
rate

Open minimum stay to two nights for Friday-Saturday. Keep Thursday
and Sunday lower to attract a longer run. Price Friday and Saturday at
or near the original rate. This often produces better Revenue Recovery
Rate than a full-stay rate cut because the high-value nights stay priced
correctly.


Night recovery vs. revenue
recovery

Recovering all four nights does not mean recovering all the
revenue.

Revenue Recovery Rate = Replacement Revenue Captured ÷
Canceled Accommodation Revenue

If the original booking produced $800 and the replacement bookings
produce $640, you recovered 100% of the nights but 80% of the revenue.
Track both numbers. Night recovery tells you whether you filled the
calendar. Revenue recovery tells you whether the pricing decision
worked. A full night recovery at low replacement ANR may mean you cut
more than necessary or chose the wrong reshaping logic.


What to do this week

  1. Look at your last cancellation. Note the cancellation lead time and
    the gap shape.
  2. Identify which response you used: hold, cut, or reshape.
  3. Calculate the revenue recovery rate on that cancellation.
  4. Ask whether a different response would have produced a better
    outcome.

Where this fits in
the STR Signals framework

Cancellation recovery is a pricing problem with a specific structure:
new lead time, new gap shape, new demand signal.

The five moves — hold, cut, reshape, wait, or combine — still apply.
The difference is the urgency created by the cancellation clock.

Keep cancellation metrics in a separate block from your live KPIs.
Canceled revenue is not live accommodation revenue. Canceled nights are
not booked nights. The recovery metrics live in their own column so you
can evaluate them cleanly.