SNIPPET DEFINITION — A minimum length of stay (MinLOS) restriction requires guests to book at least a set number of nights to reserve a given arrival date. Hotels use it on high-demand dates to stop short stays from displacing longer, higher-value ones and to capture the shoulder nights around a peak. Set it only where demand supports it, and release it as the date approaches.
It’s your best Saturday of the year and it sells out fast — to one-night bookings. The guest who wanted Friday and Saturday couldn’t get a room, because a string of single-night stays got there first. You filled the peak and lost the shoulder night attached to it.
A minimum length of stay restriction fixes exactly this. Set right, MinLOS protects your highest-demand dates and captures the nights around them. Set wrong, it turns paying guests away. Knowing which is which is the whole skill.
A one-night Saturday booking blocked a Friday–Sunday guest on our best weekend of the year. That single night cost us two. That’s the entire case for MinLOS.
Quick scope note: MinLOS is one of several stay controls, and it’s also one of the rate fences covered in the broader fences guide. This post is the stay-restriction deep-dive — when to use MinLOS, when not to, and how to set it — sitting under your hotel pricing strategy.
Key takeaways
- MinLOS requires a minimum number of nights to book an arrival date.
- Use it to protect peak dates and capture shoulder nights.
- It’s a scalpel — wrong dates or too-high minimums turn demand away.
- MinLOS is not CTA: one sets minimum nights, the other blocks arrivals.
- The real skill is knowing when to release the restriction.
What is minimum length of stay (MinLOS)?
A MinLOS-2 on a Saturday means a guest arriving Saturday must book at least two nights. It doesn’t stop Sunday arrivals or one-night stays on other dates — it applies to the arrival date you set it on. That precision is what makes it useful and what makes it easy to misuse.
MinLOS vs CTA, CTD, and MaxLOS: the stay-control toolkit
MinLOS is one of four common stay controls. They’re often confused, but each does a different job.
| Control | What it does | Use it to |
|---|---|---|
| MinLOS (min nights) | Requires N+ nights on an arrival date | Capture shoulder nights, block short peak stays |
| MaxLOS (max nights) | Caps nights on an arrival date | Stop long low-value stays consuming a peak |
| CTA (closed to arrival) | Blocks new arrivals on a date | Protect a sold-out or near-sold date from new check-ins |
| CTD (closed to departure) | Blocks departures on a date | Push stays through a soft night in the middle |
The most common mix-up is MinLOS versus CTA. MinLOS says “you can arrive, but stay at least N nights.” CTA says “you can’t arrive on this date at all.” If the vocabulary trips up your team, the revenue glossary has each term; the table above is the fast version.
When to use a MinLOS restriction
MinLOS earns its place in four situations. In each, the goal is the same: keep a short stay from taking a room a longer stay would have paid for.
- Peak dates with orphan-night risk — a sold-out Saturday that would otherwise fill with one-nighters.
- Events and holidays — when demand for the peak night is far higher than the nights around it.
- Need periods — pairing a strong night with a soft adjacent night to lift both.
- Compression dates — when a citywide event lets you require longer stays without losing demand.
When NOT to use MinLOS
This is the section most guides skip, and it’s where the money is lost. MinLOS turns demand away by design — so on the wrong date, it just costs you bookings.
On soft dates
A restriction on a date that isn’t filling is self-sabotage. If you need bookings, don’t add a reason to decline them. MinLOS belongs on strong dates, not weak ones.
When the minimum is too high
A 3-night minimum on a 2-night demand pattern turns away the exact guests you want. Match the minimum to how people actually book the date, not to how you wish they did.
When you forget to release it
A MinLOS left on as the date approaches blocks late, short-stay demand you’d happily take once the longer stays haven’t materialized. Restrictions need an exit plan; watch pickup and release them to protect occupancy when the longer stays don’t show.
How to set a MinLOS restriction
Setting MinLOS well is a five-step loop. The last step — releasing it — matters as much as the first.
- Spot the high-demand date (event, holiday, compression, historical peak).
- Check the booking pattern — how many nights guests typically stay around that date.
- Set the minimum (2, 3, or 4 nights) to match the pattern, not exceed it.
- Test displacement — would the restriction turn away more than it protects?
- Monitor pickup and release — loosen the minimum if the longer stays don’t materialize.
Where MinLOS goes wrong
Beyond over-restriction, a few operational slips quietly cost revenue.
- Restriction left stale — a MinLOS from a past event still blocking a normal date.
- Applied to the wrong arrival date — protecting the shoulder instead of the peak.
- Inconsistent across channels — the restriction holds on the direct site but not on an OTA.
- No displacement check — assuming a 2-night rule helps when the pattern was already 2 nights.
MinLOS for resorts and peak-demand hotels
Resorts are the heaviest MinLOS users, and for good reason. Holiday weeks, long weekends, and event dates concentrate demand into a few nights, and short stays on those nights are the most expensive bookings a resort can accept. A well-run resort revenue management calendar uses MinLOS to turn a peak Saturday into a peak weekend — and releases it the moment the pattern softens.
The same logic applies to any compression-driven hotel: convention-adjacent properties, ski towns, beach markets. The rule is constant — restrict where demand is deep, open where it isn’t, and never leave a minimum on past its date.
Case study: timing restrictions at scale
Set against manual restriction management, RM Copilot delivered a 13.7% RevPAR lift in 10 days across 47 properties while cutting 60–70% of the repetitive work RMs used to do by hand. Timing stay restrictions across a portfolio — setting them on the right dates and releasing them at the right moment — is exactly the kind of repetitive, high-stakes judgment that doesn’t scale property by property.
How RevEvolve helps you time restrictions
RM Copilot is an operator-facing AI revenue copilot. It analyzes demand, surfaces the dates that warrant a restriction, simulates outcomes, and recommends MinLOS and other stay-control actions with the reasoning attached — then your team reviews and applies them. It does not auto-publish restrictions or push to your PMS, CRS, or OTAs.
For MinLOS specifically, the What-If Simulator runs the displacement test before you commit — it shows the projected revenue impact of a restriction, and of releasing it, so an over-restriction that would turn away demand gets caught on screen, not in next week’s pickup report.
MinLOS: three common objections
Restrict deep demand, open the rest
A minimum length of stay is one of the sharpest tools a revenue manager has — and one of the easiest to cut yourself on. On a deep-demand date it turns a one-night booking into a two-night stay and protects the revenue around your peak. On a soft date, it just turns guests away.
Spot the date, match the minimum to the pattern, test the displacement, and — above all — release it when the longer stays don’t come. Restrict where demand is deep, open where it isn’t, and never leave a minimum on past its date.
Keep going: BAR & rate fences · Hotel pricing strategy · Hotel occupancy rate · Resort revenue management.
