Unit 3 · Creating Your Pricing Strategy · Lesson 3.13
Orphan nights
An orphan night is a gap between two bookings that is shorter than the minimum stay covering those dates, so guests cannot book it at any price. An orphan night policy fixes this automatically by overriding the minimum stay whenever a gap qualifies. Defining one takes three decisions: your longest minimum stay, the shortest stay you will accept, and whether orphan gaps get a fixed minimum or one matching the length of the gap.
The full lesson text below is an edited transcript of the video, published 2026-08-24. The complete course is free at the playbook.
What an orphan night is
An orphan night is a gap in your calendar between two bookings, or between a booking and a blocked date, where the minimum stay set for that date range is longer than the gap itself. Say you run a five-night minimum through July and two bookings land with a three-night hole between them. Those three nights are available, and you might have the best price in the market, but nobody can book them: the calendar demands five nights and only three exist. Guests will not even see the dates in search results.
That is what separates an orphan night from an ordinary gap night. A normal gap can be sold; it is just waiting for the right price. An orphan night cannot be sold at any price, because the rule covering it makes the booking impossible.
Orphan nights versus variable minimums
A variable minimum stay policy works off lead time: how many days remain before check-in. Outside 30 days you might hold a three-night minimum, for example, and relax it as check-in approaches. An orphan night policy ignores lead time entirely. It checks one thing: is the minimum stay covering a date longer than the gap between the unavailable dates on either side of it? If so, it overrides that minimum according to the rules you set.
The longer your minimums, the more this matters. With a five or seven-night minimum through a peak season, or a longer minimum applied to everything beyond 90 or 180 days out, a two-night hole can sit unbookable for months while it waits for the lead-time rules to finally relax. All that time, those dates could have been visible in search, collecting traffic and potential bookings. An orphan night policy releases them the moment they become stranded.
Manual patching or a policy
Without a policy, the fix is manual: check the calendar every week or so, find each stranded gap, and override its minimum stay by hand. It works, and it never stops being a chore. A dynamic pricing tool such as PriceLabs can apply an orphan night policy automatically instead, registering each stranded gap as it appears and adjusting the minimum stay without anyone touching the calendar.
Three decisions define the policy
First, find the longest minimum stay setting anywhere in your strategy, variable or seasonal. If everything beyond 90 days carries a five-night minimum, or high season runs at seven, that longest setting becomes the top of the range the policy watches: any gap shorter than it is potentially an orphan.
Second, decide the shortest stay you are willing to accept. If you never want a one-night stay under any circumstances, the policy can be set to exclude one-night gaps entirely rather than opening them up. Set the shortest acceptable stay at two nights and a one-night hole simply stays closed.
Third, decide what minimum stay the orphan nights should get: a specific number, or the length of the gap itself. With length of gap, a five-night orphan gap gets a five-night minimum, so one booking fills it exactly. With a specific two-night minimum, that same five-night gap opens to two-night stays, which increases your visibility in search results but invites a new problem: a guest books two of the five nights and leaves another awkward hole behind, and the cycle repeats. The length of the gap is usually the neater default because it fills the calendar cleanly instead of constantly spawning new orphan gaps to chase; a shorter fixed minimum trades that tidiness for search visibility. Whether you prioritise visibility or calendar utility is your call.
A worked example
Suppose the longest minimum stay currently in your strategy is three nights, set by your lead-time rules, with no seasonal minimums above it. And suppose one-night stays are acceptable for this property in this market. The policy then writes itself: watch gaps from one to three nights, and give any orphan gap a minimum stay matching the length of the gap. Record those three settings in the strategy sheet. There is no maths in this one; the settings follow directly from the minimum stays you already hold, and the stranded nights that used to sit invisible until the last minute become bookable the day they appear.