Orphan nights: selling the single night between two bookings

An orphan night is a single unbooked night trapped between two bookings, usually because a minimum-stay rule makes one night unsellable. You can sell it by relaxing the minimum stay for that date only, fencing a price to that night, or moving a booking with the guest's consent, then measuring what the night actually earned.

Your calendar shows a three-night stay ending on Thursday and the next arrival on Saturday. Friday sits alone: one empty night, surrounded by sold ones, and no one can book it because your minimum stay is three nights. That is an orphan night, and it is one of the few revenue problems you can fix with a rule rather than a price.

After reading this you will be able to find these nights on your calendar, name the restriction holding each one shut, choose between three ways to close it, and measure whether the fix actually earned money.

What is an orphan night on a hotel calendar?#

An orphan night is a single unbooked night between two confirmed stays that your own rules stop you from selling. The room is empty, the night is real, and no one can book it.

The shape is always the same: a departure on one date and the next arrival two dates later leaves one night alone in between. It is unsellable rather than merely empty because a minimum-stay rule attaches to the arrival date, so a one-night request is refused at the search step, before any price is shown. The guest never sees a rate; the channel simply returns no availability.

The same hole appears in other ways. A guest shortens a stay after booking. A group block is released. A room returns from out of order and its neighbours are already sold. Restrictions that differ by channel can also create the appearance of a gap on one site and not another.

The distinction that decides your response is this: an empty night in a quiet week is a demand problem, while an orphan night is a rules problem. A discount does not fix a rule, and a rule change does not create demand. Diagnose first, then act.

The money sits in the marginal cost. The room is already carried in fixed costs, so any rate above housekeeping, laundry, breakfast and channel cost beats zero, provided the fill does not block a longer stay. That proviso is the trap: filling a gap can split one long sellable window into two short ones, so the test is the net effect on the surrounding nights, not the single night.

Teams use "gap night" and "orphan night" interchangeably. Some reserve orphan for a night whose two neighbours are both sold, which is the case that most often needs a rule change rather than a price move.

For the background on how these rules work, see minimum stay, closed to arrival and closed to departure explained.

How do I find gap nights on the calendar?#

Scan a fixed horizon once a week, room type by room type, and list every free night whose two neighbours are sold. Then name the restriction holding each one shut.

Fix the horizon first. The next 8 to 12 weeks is long enough to matter and short enough that the decision will still be valid when you make it. Anything further out will change before your action takes effect.

Work room type by room type. A hole in one room type disappears in the property total, which is why most gaps are found late or not at all. The property-level calendar will not show you the problem; the room-type level will.

For each candidate, write down the restriction that blocks it: minimum stay, closed to arrival, closed to departure, or a rate that was never loaded for that date. Then separate two cases that look alike: a night between two sold nights, which usually needs a rule change, and a free night at the edge of a busy block, which is a pricing question.

Check pickup on the surrounding nights before touching anything. If the block around the hole is filling, a longer booking may close the gap without your help. Intervening too early can be worse than doing nothing.

Keep one log: date, room type, blocking restriction, action taken, result. Without it you remake the same decision every week and learn nothing from it. Assign the scan to a named person and a fixed day, because a weekly scan that depends on someone remembering is a scan that stops in the first busy month.

Option 1: relax the minimum stay for the gap#

Open the single night and nothing else: lift the minimum stay for that one arrival date and keep every other restriction in place.

The mechanism is precise because the rule is attached to the arrival date. Lifting it for one date opens exactly one night without opening the rest of the month. This is why orphan nights are a rules problem with a rules answer: the fix is as narrow as the cause.

Protect the shoulders. Keep closed-to-arrival on the day before a busy period and closed-to-departure on the day a busy period begins, so the new one-night booking cannot cut into a longer window. A one-night booking that arrives into the shoulder of your peak week has not solved your problem; it has trimmed your best selling window.

Decide who may book it. Opening the night everywhere at once is the fastest route to a parity argument; opening it on your own site first gives you a day to watch what happens before the change travels.

Accept the trade-off honestly. A one-night booking taken now can block a three-night booking later, and that is a real cost. Decide in advance how close to arrival you are willing to open a gap. A workable rule of thumb is to open gaps inside a short window, for example the next 14 days, and leave distant gaps closed until pickup shows the longer stay is not coming.

Tell the front office. A one-night stay in the middle of the week changes housekeeping sequencing and may need a room move, so check the room assignment before you sell it. And write the policy down: a rule that lives in one person's head is applied differently in a busy week, and the calendar then shows the inconsistency.

Option 2: a fenced gap price#

A fenced price sells the gap night at a lower rate without lowering your published rate for anyone else, because the conditions of the offer, not the calendar, keep it contained.

A fence is a condition that makes the offer unattractive to the guests you want to keep at full rate: single night only, non-refundable, no date changes, room only, direct channel only. The guest who would have paid your best available rate for a three-night stay is not interested in a non-changeable one-night rate, so your published price survives.

Fencing beats a plain discount because a plain discount on the date is visible to everyone and resets the price expectation for the whole period around it. Price against the alternative, not against your best rate: the comparison is the gap night's revenue against zero, minus the marginal cost of the stay and the channel cost.

Single occupancy is the natural fence in a double room. A one-night gap sold to one guest at an occupancy-based rate is a different product, not a discount on the same one; see per-person pricing and occupancy-based rates for how to set that up.

Read your parity terms before publishing. A condition-bound offer is easier to defend than a public rate cut on the same date, but the agreement you signed still applies, so ask your market manager first. Track the fence with its own rate plan or code, so you can see afterwards whether the offer stayed inside its conditions or leaked into the rest of the month. Promo codes on a booking engine and how to track them covers the mechanics.

Keep the fence visible to staff. A non-refundable single-night rate that the desk quietly extends to a three-night stay has stopped being a fence.

Option 3: move a booking, with the guest's consent#

Sometimes the cheapest way to close a gap is to move an existing booking by a night or into another room, and that only works when the guest agrees and the change is documented.

There are two different moves. One shifts a booking by a night, so the guest arrives a day later or leaves a day earlier. The other moves a booking to another room type so a whole block becomes contiguous and sellable as one window.

Consent comes first. The guest booked specific dates and often a specific room, so a move is a change to their contract: it is offered, never applied. Make the offer worth more than the inconvenience, with a rate adjustment, an upgrade, a transfer or a flexible check-in. If the offer costs more than the night earns, the move is not worth making.

Protect the price. A moved booking should not silently change the guest's total; if the new dates carry a different rate, say so before the move, not at checkout. Document everything: new dates, new room, who agreed, when, and what was promised. An undocumented move becomes a complaint at the desk and an argument about the bill.

The trade-off is staff time and service risk, so this option fits a gap that makes a longer sale possible, not a single night in a quiet week. A move often creates an early arrival or a late departure request, which needs its own answer before the guest asks for it; see setting an early check-in and late checkout policy.

Do the channels accept a one-night gap rate?#

Usually yes, but only if the restriction you changed reaches every channel at the same time and in the form that channel understands.

Restrictions travel through the channel manager. A minimum stay removed in your system but still held at a booking site means the gap stays closed where most of the demand is. The change is not done when you save it; it is done when every channel reflects it.

Parity has two halves: rate and restriction. Changing a minimum stay on one channel only is the change most likely to be flagged, so make it everywhere or not at all. Some channels read restrictions at room-type level and some at rate-plan level, so check which one your connection uses before you conclude the change worked.

Metasearch and AI assistants read the same inventory. A night closed by a restriction is invisible to them too, even though the room is empty. When you open the night, it becomes visible everywhere the inventory flows.

Test from the outside: search the date as a guest on each channel after the update, for one night, and confirm the room appears at the price you set. Record the date and time of every restriction change, because a parity question is settled by timestamps and the hotel that cannot show them usually loses the argument. Expect a delay: channels refresh at different speeds, so a change made this morning may not be visible everywhere until later in the day.

How do I measure what a gap night was worth?#

Measure the gap against zero, not against your best rate, and judge it on the surrounding nights as well as the one you filled.

The baseline is zero. The room was not going to sell under the old rule, so any net revenue is an improvement, and comparing it to the rack rate tells you nothing useful. What tells you something is the full record: the rate achieved, the marginal cost of the stay, the channel cost, and whether the fill blocked a longer booking that later tried to come in.

Watch the neighbourhood. If opening gaps is followed by more one-night bookings and fewer three-night bookings in the same weeks, the rule change is costing more than it earns. For the underlying logic of how bookings respond to rate and rule changes, see price elasticity for hoteliers.

Give the policy a review window of four to six weeks of decisions before judging it, and keep the written record of what changed so the comparison is honest. Compare like with like: a gap filled in a strong week and a gap filled in a quiet week are different results and belong in different lines.

Set a stop rule. If the same gap reappears in the same week of the year, the cause is the restriction pattern, not the individual night, and the fix belongs in the rule rather than in the calendar. Report the result in nights and in net revenue, not in occupancy alone, because a filled single night barely moves an occupancy figure but does move cash.

What to do next#

Pick one room type, scan the next eight weeks, and write down every free night with both neighbours sold and the restriction holding it shut. Then choose one option per night, log the decision and review it in a month.

The three options are not a ladder. Relaxing the rule costs you flexibility, a fenced price costs you rate integrity at the margin, and moving a booking costs you staff time and goodwill. The measurement is what tells you which of the three your hotel should be using, and the log is what turns a weekly chore into a policy.