The host problem
A guest cancels. Three nights open up. You feel pressure to rebook
fast, so you drop the rate without checking lead time, gap shape, or
demand visibility.
That reflex makes sense emotionally. It does not always make sense
economically. A cancellation removes a booking from your confirmed
ledger and creates a new pricing decision. That new decision does not
belong to the canceled guest’s original rate.
The clock resets
When a guest books 60 days before check-in, your price belongs to a
planner window. When that guest cancels 9 days before check-in, the
runway is gone. You now have a late-cycle recovery problem.
The original rate does not tell you what price will work next. The
new price should come from current lead time, current occupancy, gap
shape, and visible demand.
This is what cancellation lead time measures:
Cancellation Lead Time = Original Check-in Date −
Cancellation Date
A booking made 60 days out that cancels 9 days before check-in
carries a cancellation lead time of 9 days. That 9-day number controls
your next pricing move.
A simple example
A guest originally booked Friday through Sunday — three nights — for
$600 in accommodation revenue. They booked 60 days before check-in and
cancel 9 days before check-in. You now have three weekend nights
reopened with 9 days to find a replacement guest.
The reopened inventory now looks like this:
- Original booking lead time: 60 days (planned
demand) - Cancellation lead time: 9 days (late-cycle recovery
problem) - Original accommodation revenue: $600
- Original ANR: $200 per night
The question is not “how do I rebook at $200?” It is: “What will a
guest searching right now pay for these dates?” If weekend demand
remains strong, you may hold close to $200. If demand has thinned, you
may need to move.
Reopened
inventory is not the same as available inventory
When nights reopen after a cancellation, they carry a gap shape.
Three contiguous weekend nights can sell as a package. Two isolated
midweek nights between bookings create orphan risk. One Thursday night
stranded between a Wednesday checkout and Friday check-in may need a
minimum-stay change before price matters.
Before you change rate, ask:
- Can a replacement guest book these nights as a sensible stay?
- Does the gap create an orphan?
- Does the gap attach naturally to adjacent bookings?
Gap shape tells you whether you have a pricing problem or a
booking-shape problem. Cutting rate does not fix an orphan gap.
Reshaping minimum nights might.
Full night
recovery is not full revenue recovery
If you rebook all three nights but the replacement guest pays $450
instead of $600, you recovered 100% of the nights and 75% of the
revenue. Those are different outcomes.
Night Recovery Rate = Refilled Nights ÷ Canceled
Nights Revenue Recovery Rate = Replacement Revenue
Captured ÷ Canceled Accommodation Revenue
Treating a full rebook as a full recovery ignores replacement ANR —
the average accommodation rate on the refilled nights. A large
unnecessary cut can recover volume while lowering rate quality.
When to protect rate
after a cancellation
Protect rate when the reopened nights still have time, demand, and a
clean shape:
- The cancellation lead time is still long enough that demand has time
to find you at the current price - Event demand or seasonal demand remains visible for those dates
- The gap is clean and bookable as a complete stay
- Adjacent occupancy suggests general demand is healthy
Event windows often deserve extra patience. Check whether the event
still supports demand before moving price.
When to absorb
inventory after a cancellation
Absorb — accept a lower rate to rebook — when the booking window is
closing and vacancy risk now matters more than rate protection:
- The cancellation lead time is short and the booking window is
closing - The gap shape creates orphan risk that threatens adjacent
revenue - Demand visibility has dropped (few saves or views relative to prior
pace) - The alternative is leaving nights unbooked entirely
Inside 14 days, absorption logic often replaces hold logic for
exposed inventory.
Event-window
cancellations require a specific check
Do not automatically cut after an event-window cancellation. A
cancellation at T-minus-7 for a major event weekend does not mean demand
disappeared. It means one guest changed plans.
Check current views, saves, comps, and hotel posture before moving
price. If demand remains active, hold or make a narrow adjustment. If
demand has thinned, absorb based on evidence.
What to do this week
- Pull a recent cancellation. Calculate cancellation lead time.
- Compare cancellation lead time to the original booking lead
time. - Compare your replacement revenue to the canceled accommodation
revenue. - Use that gap as your benchmark for the next cancellation
response.
Where this fits in
the STR Signals framework
Cancellation metrics belong in a separate block from live KPI
metrics. Canceled revenue does not become live accommodation revenue.
Canceled nights do not become live booked nights. Live ANR, RevPAR, and
RCI measure only surviving bookings.
The cancellation creates a new pricing event that runs on its own
clock. Cancellation lead time keeps that response rational instead of
reactive.