Minimum-Stay Rules Without Killing Your Bookings

A minimum-stay rule refuses certain revenue today in exchange for hoped-for revenue that has to actually turn up. That is the whole trade, and it is worth making only when demand for a night clearly exceeds the rooms you have. Before you set one, work out your real stay mix — what percentage of your bookings are one, two, and three nights — because if 70% of your business is one-nighters, a two-night minimum on your best Saturday empties it. Most operators set these by feel and never check the homework.

The five controls, defined

Every property management system and channel manager offers these, usually with unhelpful abbreviations and no explanation. Here is what each one actually does.

MLOS — minimum length of stay. The guest must book at least this many nights or the date is not available to them. A 2-night MLOS on Saturday means a Saturday-only booking is refused.

MaxLOS — maximum length of stay. The guest may book no more than this many nights. Rarely used by independents, but useful when a long low-rate stay would occupy a room through a high-value date.

CTA — closed to arrival. Guests may not start a stay on this date, but a stay already running through it is fine. This is how you keep a peak Saturday available to someone arriving Friday.

CTD — closed to departure. Guests may not end a stay on this date. Used to push checkouts off a morning when you need the rooms, or to force stays to extend through a weak night.

Stay-through. A rule requiring the booking to cover a specific date to be valid — the guest must be in-house on that night, whenever they arrive.

What each one is actually for

MLOS is the one nearly everyone reaches for. CTA is the one nearly everyone should use more, because it is far less destructive — it protects the peak night without refusing every short booking outright.

The real purpose is the shoulder night

The point of a stay control is almost never "we want longer stays." It is arithmetic about the nights around your peak.

Picture a Saturday that will sell out regardless, at $250, next to a Friday that runs 60% at $150. A one-night Saturday booking earns you $250. A two-night Friday-and-Saturday booking earns you $400, and it fills a Friday room that was probably going to sit empty.

The restriction turns your scarce night into a bargaining chip for the weak one. That is the whole mechanism. If there is no weak night beside your peak, the case for MLOS is much thinner — you are just making yourself harder to book on a night that was going to sell anyway.

The trade you are actually making

Say it plainly, because the polite version hides the risk: you are refusing money in hand for money you hope arrives.

Every one-night guest you turn away on that Saturday is real revenue, from a real person, right now. The two-night bookings you are holding out for are a forecast. If they do not show up, you sold fewer rooms at the same rate and you are simply worse off.

That makes the decision conditional, not permanent. Apply the restriction when demand for the night visibly exceeds your inventory — your comp set showing sold-out nights is the clearest signal. Remove it the moment pace tells you the demand is not there.

Set a review date at the same time you set the rule. Write it in the same place. An unreviewed restriction is the most expensive thing in this post.

The homework almost everyone skips

Before you restrict anything, pull twelve months of arrivals out of your PMS and count them by length of stay. One night, two nights, three nights, four or more. Turn it into percentages.

That table is a worked illustration, not a benchmark — run it on your own data, because the answer varies enormously by property type. A city hotel serving one-night business travelers and a coastal hotel with a five-night average stay should reach opposite conclusions.

Then do it again by day of week. Your Saturday stay mix is probably nothing like your Tuesday's, and the restriction only ever applies to specific dates.

If you cannot produce that table, you are not ready to set a stay control. That is not a criticism — it is just the order the work goes in.

What the evidence supports, and what it does not

There is no independent study that says "two-night minimums raise RevPAR by X." Anyone who quotes you a figure like that is quoting a vendor.

What the research does support is the underlying premise — that holding rate discipline on high-demand dates beats chasing occupancy. Cornell researchers analyzed 67,008 hotel observations from 2001 to 2007 (Enz, Canina & Lomanno, Competitive Hotel Pricing in Uncertain Times, Cornell Hospitality Report Vol. 9 No. 10). Hotels priced 20–30% below their comp set ran about 15 points higher occupancy and roughly 12% lower RevPAR. Hotels priced 5–10% above ran 0.5 points lower occupancy and 6.7% higher RevPAR. The authors note this is correlation, not causation.

The parallel to stay controls is direct: filling every room is not the objective, and refusing some demand can be the profitable choice. But that logic only holds where demand genuinely exceeds supply — which is why the honest advice is always conditional.

Cancellation behavior is worth factoring in too. In the Cloudbeds 2026 State of Independent Hotels panel (90 million bookings, 180 countries, 2025 data), OTA bookings cancelled at 21.8% versus 10.6% direct. A restricted night that looks full through OTA bookings is less full than it appears.

The mistakes that make restrictions backfire

Setting a blanket rule. "Two nights minimum every weekend, all summer" ignores that half those weekends were never going to sell out. Restrictions belong on specific dates.

Restricting before checking your stay mix. If most of your demand is one night, a two-night minimum is a decision to run at 50%.

Reaching for MLOS when CTA would do. Closed-to-arrival protects your peak night while still letting you take the one-night guest who arrives the day before.

Leaving it on too long. Set the review date when you set the rule. Two weeks out, if pace is soft, take it off.

Applying it to every room type. Your suites and your standard rooms rarely face the same demand. Restrict the constrained inventory, not all of it.

Not telling the front desk. Staff who do not know a rule exists will apologize for it, override it, or quote around it — and you will never learn whether it worked.

The bottom line

Learn the five controls and what each one refuses. Pull twelve months of stay-length data and break it down by day of week, because that table decides whether any restriction is safe at your property. Apply MLOS only to specific dates where demand visibly exceeds your rooms, prefer CTA where it will do the job with less damage, and always set a review date at the same moment you set the rule.

The correct mental model is a trade, not a policy: you are giving up certain revenue for probable revenue. Make that trade deliberately, on dates where the odds are clearly in your favor, and take it back off when they are not.

Where this gets tedious is doing it per room type across sixty nights and remembering which dates you restricted. Our multi-calendar view puts room types and dates in one grid with minimum stay editable per night, so the rules you set stay visible instead of disappearing into a channel manager.