The host problem
An orphan night is an isolated one- or two-night gap that cannot attach to adjacent demand. It sits between two bookings with minimum-stay rules that prevent it from filling on its own terms.
Orphan nights can arrive from two sources. A cancellation creates one when the reopened inventory does not span enough nights to meet the minimum stay. A minimum-stay rule creates one when it pulls longer stays in a way that leaves a short residual gap.
Either way, the gap requires a specific decision — not a reflexive rate cut.
The number, concept, or decision
What makes a night an orphan
A night qualifies as an orphan when:
- It sits as a one- or two-night gap between two existing bookings, and
- The minimum-stay rule prevents a new guest from booking just those nights, and
- The surrounding bookings do not allow the minimum to flex to cover the gap
At that point, the orphan has three possible outcomes: fill at a shortened minimum, drop to the current last-minute rate without a minimum, or accept the loss and hold the adjacent rates intact.
The turnover test
Before deciding to fill an orphan, run the turnover test. An orphan one-night booking at $90 with a $174 TCP produces a negative net contribution on that night. Filling for occupancy at an economic loss is not recovery.
Turnover Drag for one night at $174 TCP = $174 ÷ 1 = $174 per occupied night Net contribution = $90 accommodation revenue minus $174 = negative $84
In that scenario, the empty orphan night is economically preferable to the filled one. Your RevPAR takes a small hit. Your Net RevPAR improves.
BLT and late-cycle absorption
Every orphan analysis starts with BLT — how many days remain before the gap opens. Inside 14 days, orphan nights enter late-cycle pricing logic. The absorption decision becomes: does the gap create enough occupancy risk to justify rate concessions, or does the surrounding calendar absorb the loss without damaging the wider pricing structure?
What this helps you decide
An orphan night forces three connected decisions:
- Is the orphan worth filling at any rate given turnover cost?
- If yes, does lowering the minimum stay to fill it create a new orphan elsewhere in the calendar?
- If yes, which loss is smaller?
Example
A cancellation creates a two-night Tuesday–Wednesday gap at 10 days out. The surrounding bookings — Monday check-out and Thursday check-in — each carry a two-night minimum. No guest can book just Tuesday and Wednesday under the existing rule.
The host has four options:
- Lower the minimum to two nights for those specific dates: a two-night booking fills the gap cleanly with one turnover
- Lower to one night: two one-night bookings may fill both nights but produce two turnovers
- Price the gap aggressively and accept one booking at a significant discount: fills both nights at one turnover if the guest takes both
- Accept the loss: two empty nights cost zero turnover but also produce zero accommodation revenue
Run the numbers at each scenario using the turnover drag formula before deciding. At $174 TCP and a rate of $80 per night, two one-night bookings produce $160 in revenue and $348 in turnover drag. The loss scenario wins on Net RevPAR.
At a rate of $120 per night for both nights in one booking (two-night minimum), the result is $240 revenue and $174 turnover drag. Net contribution: $66. That is the fill worth pursuing.
What most hosts get wrong
Most hosts treat every open night as a problem that requires a price cut. Orphan nights are different. Filling an orphan at a rate below turnover cost makes the empty alternative preferable on a net-revenue basis. The correct response is to calculate first, then decide.
The second mistake is lowering the minimum stay to fill one orphan without checking whether the shortened minimum creates a new orphan on either side. A one-night booking Monday may solve the Tuesday gap while creating a new Wednesday orphan — and the chain repeats.
What to do this week
- Identify every open gap of one or two nights in your calendar right now.
- Check whether those gaps fall inside your minimum-stay rule.
- Calculate the Net RevPAR impact of three scenarios: fill at a lower minimum, fill at a one-night exception, or accept the loss.
- Flag any gap inside 14 days for late-cycle absorption logic.
- For gaps beyond 14 days, do not panic. Orphan gaps at 30+ days often resolve without intervention as adjacent bookings shift.
Where this fits in the STR Signals framework
Orphan-night strategy sits at the intersection of cancellation recovery, minimum-stay rules, BLT, ALOS, and Net RevPAR. Use it when a short gap needs a decision that rate alone cannot solve.
Connected articles
- Airbnb Cancellation Recovery Playbook
- Airbnb Minimum Stay Strategy
- Net RevPAR and Turnover Drag
- Booking Lead Time Explained for Airbnb Hosts
- ALOS Explained for Airbnb Hosts
- Airbnb Shoulder Night Pricing: Using Thursday and Sunday as Booking-Shape Levers
- Airbnb Cancellation Recovery Worksheet
Educational note
This page is educational. It is not tax, legal, investment, or guaranteed-income advice.