Hotel Stay Restrictions: When Minimum-Stay Rules Earn Money and When They Bleed It
A 30-room boutique hotel puts a two-night minimum on a marathon Saturday. The Saturday sells out anyway, but Friday finishes at 60 percent and the front desk turned away nine one-night requests at 290 dollars each. The owner sees a sold-out Saturday and calls it a win. The revenue manager sees roughly 2,000 dollars of contribution that walked out the door. Both are looking at the same weekend. Only one of them ran the math.
Stay restrictions are the most misused tool in hotel revenue management. Every glossary defines minimum length of stay, closed to arrival, and closed to departure. Almost none show you the arithmetic that decides whether a restriction fills your shoulder nights or strands your peak inventory. This article gives you that arithmetic, a decision rule with a real break-even number, and a review cadence so the rule never outlives the demand that justified it.
Table of Contents
- The four stay controls, in plain terms
- Why most restrictions quietly lose money
- The displacement question every restriction has to answer
- A worked example: the 63 percent rule
- When to use each control: a demand-based decision table
- The orphan-night trap
- Setting, then reviewing: a pace-based cadence
- How this runs inside PriceLabs, Wheelhouse, and your PMS
- Frequently Asked Questions
- Conclusion
The four stay controls, in plain terms
Four restrictions do almost all the work. Learn what each one actually blocks, because the names mislead people constantly.
Minimum length of stay (MinLOS) forces any guest arriving on a given date to book at least N nights. Set a two-night minimum on Saturday and a guest searching for Saturday only never sees your hotel in results. It is the bluntest control and the one operators reach for first, usually too soon.
Maximum length of stay (MaxLOS) caps how many nights a booking can run. It sounds strange until you have a discounted midweek rate you do not want a guest riding through a high-demand weekend. MaxLOS protects the peak from being bought at the trough price.
Closed to arrival (CTA) stops new check-ins on a date while still allowing guests already in-house to stay through it. If Saturday is CTA, a guest can book Friday to Sunday and sleep Saturday, but cannot start a stay on Saturday. CTA is a scalpel where MinLOS is a hammer. It pushes demand onto the shoulder night without turning away every short stay.
Closed to departure (CTD) stops guests from checking out on a date. It sounds obscure and it is the least used, but around a compression weekend it keeps a guest from checking out Saturday morning and freeing a room you would rather sell as part of a longer stay. Treat CTA and CTD as yield tools rather than availability tools. The distinction matters when you configure them in a channel manager, because they shape the stay pattern without simply zeroing out inventory.
The instinct is to treat these as on-off switches for busy dates. They are not switches. Each one turns away a specific slice of demand in exchange for a specific slice you hope to capture instead. Whether that trade pays depends entirely on numbers you can forecast.
Why most restrictions quietly lose money
The failure mode is always the same: the restriction goes on when demand looks strong, and it stays on after demand fades. Two costs follow.
The first is turned-away demand you cannot recover. A two-night minimum on a Saturday that does not actually sell out means you refused one-night bookings and got nothing in their place. The room sits empty. That is not a break-even outcome, it is a pure loss of contribution.
The second is the gap night. When a minimum stay is applied across a stretch of dates, it can leave single nights wedged between two bookings that no one can legally book, because the remaining window is shorter than the minimum. Overly rigid minimums manufacture these orphan nights faster than demand can fill them, and the fix, covered later, is to let the minimum flex rather than sit static.
There is a real upside on the other side of the ledger, which is why the tool survives. Longer stays cut turnover. Cost per occupied room is climbing fast: industry labor data from HotelData.com shows average labor CPOR rose from 42.82 dollars in 2024 to 48.32 dollars in 2025, a 12.8 percent jump. Every avoided turnover is real money kept. But that saving only counts when the restriction fills the room. A restriction that empties the room saves you a cleaning you did not need because you have no guest. That is not a win.
The displacement question every restriction has to answer
Displacement analysis usually shows up in the context of group business: do I accept this group, or do I hold the rooms for higher-yielding transient demand? The same logic governs stay restrictions, and almost nobody applies it there.
Every restriction displaces demand. A Saturday CTA displaces one-night Saturday arrivals in the hope of capturing two-night stays that spill onto Friday. The question is not “is Saturday busy.” The question is: is the demand I am holding the room for larger than the demand I am turning away?
The formula the industry uses for group displacement, laid out by Hospitality Net, reduces to comparing the contribution of the business you accept against the contribution of the business you give up. Rooms times ADR, minus the variable cost of servicing each room, plus any ancillary spend. For a stay restriction the version you need is simpler, because it is one room type and no catering. You compare two contributions per contested room:
- The one-night booking you would turn away: its rate, minus the variable cost of one occupied room.
- The multi-night stay you hope to capture instead: the sum of each night’s rate, each minus one variable cost, but only counted when that demand actually shows up.
The trap is that the first number is close to certain and the second is a forecast. A one-nighter searching your compression date is a bird in the hand. The two-night stay you are holding out for is a bird you have not seen yet. Weigh them accordingly.
A worked example: the 63 percent rule
Numbers make this concrete. The figures below are illustrative, but the method is the one to use on your own property. Take a 30-room boutique hotel with a race weekend. Saturday is the peak. Rates on the books: Friday 190 dollars, Saturday 290 dollars, Sunday 160 dollars. Assume a variable cost of 45 dollars per occupied room, which sits in the mid-range of published cost-per-occupied-room benchmarks reported by Lighthouse for select and full-service hotels.
Saturday demand exceeds your 30 rooms, so Saturday will sell out one way or another. The real decision sits on the last 10 Saturday rooms, the contested inventory. You can fill them two ways.
Option A, accept one-night Saturday arrivals. Each contested room earns its Saturday rate only.
Contribution per room = 290 minus 45 = 245 dollars. Ten rooms, all filled with near certainty, = 2,450 dollars.
Option B, put CTA or a two-night minimum on Saturday. Each contested room is now held for a guest who books Friday and Saturday. That guest pays for two nights.
Contribution per room = (190 minus 45) plus (290 minus 45) = 145 plus 245 = 390 dollars. But this only lands when two-night demand actually fills the room. Any held room that two-night demand does not reach sits empty at zero, because you turned the one-nighter away.
Now solve for the fill rate that makes the restriction worth it. Let f be the fraction of the 10 held rooms that two-night demand fills.
| Two-night fill rate (f) | Expected contribution per held room (f x 390) | vs. one-night certainty (245) | Verdict |
|---|---|---|---|
| 100% | 390 | +145 | Restriction wins clearly |
| 80% | 312 | +67 | Restriction wins |
| 63% | 246 | +1 | Break-even |
| 50% | 195 | -50 | Restriction loses |
| 30% | 117 | -128 | Restriction loses badly |
The break-even is f = 245 divided by 390, which is 0.628. In plain terms: only hold Saturday for two-night stays if you are confident at least 63 percent of the held rooms will fill with multi-night demand. Below that line, the one-nighters at 290 dollars beat the gamble, and the sold-out Saturday the owner was celebrating actually cost money.
That single ratio is the thing competitors leave out. The break-even fill rate moves with your rates. Widen the gap between the shoulder rate and the peak rate and the restriction gets easier to justify, because the incremental Friday night is worth more. Narrow it and the one-nighter wins more often. Run the number for your own dates before you touch the setting. This is exactly the kind of judgment we build into every calendar we manage through our outsourced revenue management for hotels service, and it is why blanket restrictions almost never survive contact with the actual pace data.
When to use each control: a demand-based decision table
The control you pick should follow the demand pattern, not habit. Here is how the four map to real situations.
| Situation | Best control | Why |
|---|---|---|
| Single peak night flanked by soft shoulders, strong multi-night demand forecast | CTA on the peak | Pushes arrivals onto the shoulder without turning away every short stay |
| Multi-night event, whole weekend compresses | MinLOS across the arrival dates | Captures the full pattern when nearly all demand is multi-night anyway |
| Cheap midweek rate you must protect from the weekend | MaxLOS on the low rate | Stops a bargain stay riding through the peak |
| Sold-out Saturday, soft Sunday you want to protect | CTD on Saturday | Keeps guests from checking out into your empty night |
| Uncertain pace, demand not yet proven | No restriction, reprice instead | Raise rate to ration inventory without turning away short stays |
Notice the last row. When you are unsure, price is the safer lever than a restriction. A higher rate rations inventory while still letting a one-nighter buy the room if they value it enough. A restriction refuses the sale outright. Pricing and restrictions are complements, not substitutes, and getting the sequence right is the core of any real dynamic pricing strategy. Reach for the restriction only when repricing alone cannot shape the stay pattern you need.
The pre-flight checklist before any restriction goes live
Run this list before you flip a single control:
- Have I checked length of stay by arrival date for this pattern in prior years?
- Is my current pickup ahead of, on, or behind the same point last year?
- What is the realistic two-night fill rate, and does it clear the break-even ratio?
- Will this restriction create an orphan night on an adjacent date?
- Have I set a review date to reassess as the arrival date approaches?
- Could a rate increase achieve the same shaping without refusing demand?
The orphan-night trap
The most common self-inflicted wound with minimum stays is the orphan night, a single unbookable night trapped between two reservations. Guest A books through Thursday. Guest B arrives Saturday. Friday sits open, but a two-night minimum on Friday means no one can book it, because a one-night Friday stay is not allowed and there is no room for a two-night stay. The restriction that was supposed to protect revenue now guarantees an empty night.
The fix is not to abandon minimums. It is to let them flex as the gap appears. Modern systems can drop the minimum on an orphan night automatically once the surrounding dates fill, converting a stranded night into a bookable one-nighter at whatever rate the last-minute market supports. For short-term rental operators the same logic drives gap-night pricing, and the mechanics carry straight over to hotels. The principle is identical to what we lay out for Airbnb revenue management: a minimum stay is a demand-shaping tool, not a permanent fence, and it has to open when the demand pattern changes.
Practically, that means never setting a minimum and forgetting it. A minimum stay that made sense 60 days out, when the whole weekend looked like it would compress, can become the reason a single Friday sits empty at 14 days out when the multi-night demand did not fully arrive. The setting has to be reviewed against pace, which is the next section.
Setting, then reviewing: a pace-based cadence
A restriction is a bet on a forecast. As the arrival date approaches, the forecast becomes fact, and the bet has to be re-examined. The discipline that separates a revenue manager from a channel-manager operator is the review cadence.
The logic is straightforward. When pickup is running ahead of forecast and the market is compressing, restrictions are justified and can even tighten. When pickup lags, restrictions should ease or come off entirely to recover momentum. Cornell’s revenue management faculty frame length-of-stay controls as tools that demand active management, reviewed against booking pace rather than set once and left. The set-and-forget minimum is where revenue goes to die.
A workable cadence for a peak date looks like this:
| Days to arrival | What to check | Action if pace is behind |
|---|---|---|
| 60 to 45 | Is the multi-night forecast holding? Any new events? | Hold restriction, monitor |
| 30 to 21 | Actual two-night pickup vs. the break-even fill rate | Loosen minimum from 2 nights, keep CTA |
| 14 to 7 | Remaining rooms, orphan nights forming | Drop restriction on stranded nights |
| 7 to 0 | Last-minute one-night demand | Open fully, capture any remaining short stays |
Notice the direction of travel. Restrictions start tighter and loosen as certainty rises and the window to recover an empty night closes. The cost of an empty room on the night itself is total. The cost of accepting a one-nighter two weeks out, when your two-night demand has clearly not materialized, is nothing. Let the approaching date make your decisions less conservative, not more.
This is also where the current demand backdrop matters. CoStar and Tourism Economics project US hotel occupancy near 62.8 percent for 2026 with ADR up about 2 percent, a soft, price-sensitive market outside of genuine compression events. In a market like that, aggressive blanket restrictions are the wrong instinct. Reserve them for the dates where compression is real and provable, and price the rest.
How this runs inside PriceLabs, Wheelhouse, and your PMS
The arithmetic above is the strategy. The execution lives in your systems, and the systems only do what you configure. A pricing platform can automate minimum-stay logic tied to occupancy thresholds, so the minimum lifts on orphan nights and tightens as a date fills, but it applies the rules you give it. Point it at the wrong dates and it will strand inventory efficiently.
We configure these controls daily. In PriceLabs that means occupancy-based minimum-stay rules and gap-night overrides tied to the real pace of each date, not a static calendar. The same demand-shaping logic applies through Wheelhouse and inside the PMS or channel manager where CTA and CTD ultimately fire. The tool is not the strategy. The forecast and the break-even math are the strategy, and the tool executes them without judgment of its own.
One more execution point: restrictions have to be consistent across every channel. A two-night minimum on your direct site that does not replicate on Booking.com or Expedia means the OTA sells the one-nighter you were trying to shape away, and your displacement logic collapses. Restriction parity across channels is part of clean Booking.com listing optimization and it is where a lot of otherwise sound stay-control strategies leak revenue.
Frequently Asked Questions
What is the difference between MinLOS and CTA?
A minimum length of stay forces every guest arriving on a date to book at least N nights, so a one-night searcher never sees your hotel. Closed to arrival stops new check-ins on a date but still lets a guest already in-house stay through it. CTA is more precise because it shapes arrivals without banning short stays entirely, which usually turns away less recoverable demand.
How long should a hotel minimum stay be?
Only as long as the demand pattern supports. Match the minimum to the actual multi-night demand for the date, not to how busy the date feels. If two-night stays make up most of the demand for a weekend, a two-night minimum fits. If a meaningful share of demand is genuine one-night business you can profitably take, a minimum will cost you. Run the break-even fill rate before setting it.
Do stay restrictions hurt my ranking on Booking.com or Airbnb?
Indirectly, yes. A restriction removes you from search results for guests whose desired stay violates it, which lowers your impressions and can dent booking velocity. That is a real cost to weigh against the revenue the restriction protects. It is another reason to apply restrictions narrowly, on proven compression dates, rather than across broad stretches of the calendar.
When should I remove a minimum stay restriction?
When booking pace falls behind forecast, when an orphan night forms that the minimum makes unbookable, or as the arrival date nears and your multi-night demand has clearly not reached the break-even fill rate. Restrictions should loosen as certainty rises, because the window to recover an empty night is closing and a late one-night booking is better than an empty room.
Are minimum length of stay requirements legal?
Yes. Minimum stay requirements are a standard, widely used yield management practice, applied transparently at the point of booking. They are a condition of sale, not a hidden charge, and guests see the requirement before they book. The practical constraints are commercial, around lost demand and search visibility, not legal.
Should I use price or restrictions to manage a peak date?
Start with price. Raising the rate rations inventory while still letting a guest buy the room if they value it, which loses less demand than an outright restriction. Reach for a restriction only when repricing alone cannot produce the stay pattern you need, for example when you must push arrivals off a sold-out night onto a soft shoulder. Price and restrictions work together, in that order.
Conclusion
Stay restrictions are not a busy-date reflex. They are a displacement decision, and every one of them has a break-even fill rate hiding inside it. Find that number before you flip the switch. Hold the peak for multi-night demand only when you are confident enough of that demand to clear the threshold, and let the restriction loosen as the date approaches and the forecast turns into fact. Do that and restrictions become one of the sharpest tools you own. Skip the math and they quietly hand your compression revenue back to the market.
If your calendar is full of set-and-forget minimums that no one has revisited since they went on, that is exactly where recoverable revenue is sitting. We build the forecast, run the displacement math, and manage the controls date by date across your pricing platform and every channel, month to month with no long-term lock-in. Talk to us about your compression dates and we will show you where the restrictions are earning and where they are bleeding.