Orphan nights get missed by almost everybody. Most revenue management software does not go looking for them, and most hoteliers have never had a reason to know the term. It is one of the things we are genuinely passionate about picking up for our clients, partly because the fix takes about a minute, and partly because the money is real and nobody else is claiming it.
What an orphan night is
Say you run a two-night minimum. For the sake of this, assume it applies every night of the week.
Room one has a booking for the Thursday and the Friday. It has another booking for the Sunday and the Monday. Both of those are perfectly good two-night stays, and both of them are exactly the business your minimum was set up to bring in.
That leaves the Saturday.
Nobody can book that Saturday. They cannot take it with the Friday, because the Friday has gone. They cannot take it with the Sunday, because the Sunday has gone too. There is no two-night stay left anywhere that includes it, so the night is unbookable.
It is as if the night is booked, except you have none of the revenue to show for it, and none of the guests in the building who would have enjoyed your hotel.
And it is a Saturday. Both nights either side sold, which tells you everything about how much demand there was for that date.
Why they are so easy to miss
The awkward part is that you cannot see one coming. An orphan night does not exist until a booking creates it. Somebody takes the Sunday and the Monday, and at that moment a Saturday you were happily selling last week quietly becomes unsellable. Nothing announces it. No alert, no flag, no line in a report.
Very few property management systems catch this for you. It is a manual job, going through the book room by room looking for gaps, and most owners get to it late, if they get to it at all. By then the guests who would have loved that Saturday have already searched the date, seen nothing available, and booked somewhere else. As far as they were concerned, you were full.
Meanwhile your own screen shows the room as free, because it is free. The restriction that makes it unbookable sits on a different page entirely, usually one you visited when you set the rule up and have not opened since. At the end of the month it lands in your reporting as an unsold night, filed alongside every genuinely quiet Tuesday in the calendar, with nothing to tell you the difference.
What you do about it
The job is mechanical. Find the gap, open it, hold your rate.
| Step | What it means in practice |
|---|---|
| Look room by room | Occupancy percentages will never show you this. For each individual room, find a free night where the night before and the night after are both sold. That specific shape is the whole definition. |
| Check which days your rule covers | Minimums are usually set per day of the week. If yours only runs Friday and Saturday, a stranded Tuesday was never blocked and needs nothing doing to it. |
| Release the night | Drop the minimum length of stay to one night, for that single date and that single room. In most systems this is a per-date override on the Min LOS restriction. Not a blanket change, and not a change to your standing rule. Check you are editing the restriction your channel manager actually sends out, because some restriction types stay inside the PMS and never reach the OTAs. |
| Hold your rate | The night sells or it does not, but it should not sell cheap. More on that below, because it is where most automated systems go wrong. |
| Put it back | If a neighbouring booking cancels, the gap is no longer one night long and the two-night minimum should return. |
Step two is worth dwelling on, because we got it wrong ourselves. At one property we assumed the two-night minimum ran all week and went hunting for orphan nights on that basis. The owner then told us it only ever applied on Fridays and Saturdays. Every stranded midweek night we had carefully flagged had always been perfectly bookable as a single night. Two-thirds of our list was not real. So before you start counting what this is costing you, confirm which nights your rule actually covers.
The other thing to understand is that this job never finishes. Even if your minimum is weekends only, orphan nights keep appearing as bookings come in, because every new booking reshapes the gaps around it. Clear them all today and you have bought yourself about a week. That is exactly why it tends not to get done.
What it is worth
Between early July and early August we opened 49 blocked nights across two client properties, one with eleven rooms and one with ten. Both run a two-night minimum.
About a third of the nights we release end up booked. Looking only at the ones whose date has already come and gone, so the answer can no longer change, close to half of them sold.
In revenue terms that has been worth up to three per cent of room revenue for the dates involved. The word that matters there is extra. This sits on top of what our dynamic pricing is already delivering, not inside it. We count the two separately on purpose, so that a night which sold because we opened it can never also be claimed as a pricing win.
That is one month at two hotels, so treat it as a marker rather than a promise. What makes it unusual is that there is no counterfactual to argue about. Normally, when somebody claims a revenue improvement, the fair question is what would have happened anyway. Here the answer is nothing, and not as a matter of opinion. Every one of those nights had a sold booking on either side and a rule forbidding one-night stays. No guest could have booked it at any price, through any channel, at any point.
The benefit does not stop at the night either. Those are extra guests through your door on dates you were closed, which means more reviews, more people who might come back, and a hotel that looks busier than the one down the road.
Why dynamic pricing software will not fix this
You would reasonably expect a revenue management system to handle this, and on the property management systems that most UK independents run, it does not.
Automatic minimum-stay correction does exist in the market, but on the major tools it tends to be limited to a handful of smaller PMS integrations and higher price tiers. If you are on one of the systems common in UK independent hotels, the odds are that your RMS has no way of opening a blocked night at all. It can move your rates up and down all day and never once touch the restriction that is doing the damage.
What it will do instead is worse. A pricing model sees a night that is not selling while the nights around it fill up, and draws the obvious conclusion: too expensive. So it discounts. Documentation for tools in this category describes automatic reductions of fifteen or thirty per cent applied to exactly these nights, precisely because their neighbours are full.
The night was never too expensive. It was closed. Cutting the price of a room nobody is allowed to reserve achieves nothing at all, right up until the moment it achieves something bad.
Follow that through. While the restriction stands, the discount does nothing, because the night still cannot be booked at any price. If the restriction later lifts, whether because a neighbour cancels or because somebody finally spots the gap, you have now put your cheapest rate of the season on the one date you had hard evidence of demand for. The software has taken your strongest night and marked it down.
None of which is really a failure of pricing intelligence. It is a category error. The problem was never the number. Every pricing tool in the world is built to answer the question "what should this room cost", and the honest answer here is "the same as it always did, but somebody needs to go into the PMS and let people book it".
Which is where outsourced revenue management comes in
So that is what we do. We track orphan nights automatically for every client who has the quirk. Whenever a booking lands either side of a free night and strands it, the night appears on our list, we go in and release it to a one-night minimum, and we hold the rate while it sells. Then we do it again the next morning, because by then there are new ones.
Otterly Booked is an outsourced revenue management service for small UK independent hotels, which means a person is accountable for this actually getting done rather than a dashboard telling you it should be. We run the dynamic pricing as well, and the two jobs support each other: the rate work makes each night worth more, and the restriction work makes sure the night can be sold at all. It comes with pricing judgement from someone who spent over 12 years running pricing at travel companies such as Premier Inn and National Express, applied to a property small enough that a full-time revenue manager was never going to make sense.
If you want the wider context first, our guide to what revenue management means for a small hotel covers the commercial logic, and our piece on dynamic pricing for hotels covers the rate side of the same job.
Frequently asked
What is an orphan night in a hotel?
An orphan night is a single empty night with sold nights on either side of it, in a room where a minimum stay of two or more nights applies. The gap is shorter than the minimum, so no guest can book it. It behaves like a booked night, except you get none of the revenue and none of the guests.
Why can an orphan night not be booked?
Because there is nowhere for a qualifying stay to go. A two-night minimum means any booking has to cover two nights, and both neighbouring nights are already sold to someone else. The night is closed rather than unpopular.
Should I discount an orphan night?
No. Discounting changes nothing while the restriction stands, because the night still cannot be booked at any price. It also throws away rate on one of the strongest dates you have, since both neighbouring nights selling out is direct evidence of demand. Release the night first and hold your rate.
How do I find orphan nights in my PMS?
Look room by room, not at your overall occupancy. For each room, find a free night where the night before and the night after are both sold. Then check whether your minimum stay actually applies on that day of the week, because many minimums are weekend-only. Whatever is left is a genuine orphan night.
Does dynamic pricing software fix orphan nights?
Usually not. Automatic minimum-stay correction exists in some revenue management systems, but on the major tools it is limited to a handful of smaller PMS integrations and higher price tiers. On the systems most UK independents run, dynamic pricing software has no way to open a blocked night, and will often discount it instead, because the model reads a night that is not selling as a night that is priced too high.
What is the difference between a revenue management system and an outsourced revenue management service?
A revenue management system (RMS) is software that recommends or sets rates, and you are left to run it. An outsourced revenue management service puts a person in charge of the outcome, which covers the work software cannot do on its own: changing restrictions in the PMS, releasing orphan nights, pricing local events, and judging when a signal is real. For a small independent hotel the practical difference is whether the work actually gets done each day.
How much revenue do orphan nights cost a small hotel?
At two small UK hotels we opened 49 blocked nights over one month. About a third have sold so far, worth up to three per cent of room revenue for the dates involved, on top of what dynamic pricing was already delivering. That is a small sample rather than a rule, but the money is entirely incremental, because none of those nights could have sold any other way.
Want to know how many nights your own rules have closed this month?