Revenue blog · 12 min read · 28 May 2026
Length-of-Stay Restrictions: When to Use Them and When They Cost You Bookings
The first time I watched a peak Saturday sell out at flat rate, I thought the property had won. Ninety-eight occupied, A$289 ADR, zero walks. Then the report showed the Thursday and Sunday on either side had crawled in at sixty-five and fifty-eight. The Saturday filled with single-night bookings that took the room and left the shoulders. Length-of-stay restrictions in hotels are the surgical instrument that decides whether a peak night sells the building or strips it for parts. Used right, they protect a sold-out Saturday by forcing a Friday or Sunday to come with it. Used wrong, they quietly cost shoulder bookings the property never sees.
What length-of-stay restrictions actually mean in 2026
Length-of-stay restrictions are pricing rules that limit which reservations a hotel will accept based on the number of consecutive nights the guest intends to stay. They do not change the published rate. They change which bookings the rate is offered to. Restrictions are an inventory tool, not a pricing tool — even though most channel managers store them next to the rate. Three forms cover ninety-five percent of operating use:
- Minimum length of stay (MinLOS) — every booking touching the restricted date must be at least N nights.
- Maximum length of stay (MaxLOS) — every booking touching the restricted date can be at most N nights. Used in long-stay markets to keep nights free for higher-yielding short stays.
- Minimum length of stay on arrival (MLOS-on-arrival) — only bookings arriving on the restricted date must meet the minimum. Through-stays that started earlier are accepted.
Closed to arrival (CTA) and closed to departure (CTD) sit in the same family of inventory rules but solve a different problem — covered separately. The frame for this article is a deliberate, dated, segment-aware overlay on a base inventory position. Not a default. A specific decision for a specific date, signed off and reviewed.
The formula: how length-of-stay restrictions actually decide a booking
The arithmetic is simple. The restriction is a logical gate evaluated at the time a booking is attempted, against every night within the requested stay window. If any night fails its rule, the whole booking is rejected.
A reservation is accepted if and only if, for every night N within the requested stay, the booking's total length meets the MinLOS rule at N, falls under the MaxLOS rule at N, and, if N is the arrival night, satisfies the MLOS-on-arrival rule at N.
A worked example on a 120-room urban property. Saturday 22 August has MinLOS 2 applied — strong leisure demand expected, the property wants to pull either Friday or Sunday with it. Three reservation attempts arrive the same morning:
- Booking A: Saturday only, one night, A$329 → rejected.
- Booking B: Friday + Saturday, A$259 + A$329 = A$588 → accepted.
- Booking C: Thursday–Sunday, four nights, A$986 total → accepted.
One night displaced. Three to four shoulder-night rooms gained. Blended ADR on Booking C is A$246.50 — below the A$329 the single-night booker would have paid, but bringing in three additional room-nights at decent rate the building would otherwise have sold cheap or not at all. The question is not which booking has the higher ADR. The question is which booking pattern wins the week.
Reading the week, not the night
Length-of-stay restrictions only make sense at the week level. A peak Saturday with soft shoulders is a different problem to a peak Saturday inside a sold-out three-night festival window. The first wants a MinLOS to pull the shoulders. The second does not — the shoulders are already firming, and a restriction only costs short-stay bookings the property could accept at high rate.
The signal lives in the daily pickup-and-pace reading covered in hotel revenue management strategies for 2026. Saturday pacing +15 STLY and Friday pacing flat → MinLOS 2 is defensible. Both pacing +15 → restriction unnecessary, will leak short-stay revenue.
The decision input is a small table, built once a week for the next eight weekends. One row per peak night, columns for Saturday on-the-books, shoulder on-the-books, STLY pace on each, and the proposed restriction. The discipline is in writing the proposed restriction down and reading the table out loud before committing it to the channel manager.
The three restrictions, side by side
A cheat sheet I keep on the wall of every revenue desk I have run:
| MinLOS | MLOS-on-arrival | MaxLOS | |
|---|---|---|---|
| What it does | Forces a minimum stay length on every booking touching the date | Forces a minimum stay length only on arrivals to the date | Caps the maximum stay length on bookings touching the date |
| Typical use | Peak night with soft shoulders | Peak night that already has through-stay demand | Long-stay segment crowding out short-stay rate |
| Accepts a 1-night Saturday booking on a restricted Saturday? | No | No | Yes |
| Accepts a Thursday–Sunday through-stay on a restricted Saturday? | Yes | Yes | Depends on MaxLOS value |
| Risk | Blocks high-rate short bookings if shoulders fill anyway | Allows arrivals to drift to other dates | Caps premium long-stay revenue |
| Reviewed | Weekly for next 8 weekends | Weekly, paired with arrival-pattern data | Monthly, segment-led |
Three instruments. Three different problems. The mistake I see most often is using MinLOS for every problem because it is the one the channel manager defaults to.
Where length-of-stay restrictions break down
Four failure modes I have watched cost real revenue:
1 — Copy-paste from last year's calendar. A MinLOS 2 on a Saturday that was a sell-out last August is defensible if this August is pacing the same way. It is a quiet disaster if pace is soft and the Saturday is sitting at sixty on the books two weeks out — the restriction blocks the short-stay rescue bookings the date now needs.
2 — Setting MinLOS on every weekend night in a row. A MinLOS 2 on Friday and a MinLOS 2 on Saturday stack together. A one-night Friday booking is rejected. A one-night Saturday booking is rejected. A one-night Sunday booking can come through — but Sunday is the night the property was trying to fill. The pair filters out the only short-stay traffic that could have helped.
3 — Applying restrictions without segment awareness. In a corporate-heavy market the structural stay is Tuesday–Thursday three nights. A MinLOS 2 on a Wednesday catches almost nothing — corporate bookings are already two or three nights — but blocks the rare one-night Wednesday booking at full BAR.
4 — Forgetting the channel layer. A MinLOS applied uniformly across every channel may make sense on direct (low acquisition cost, protect the shoulder). It may not make sense on high-commission channels where the cost stack covered in OTA commission rates 2026 already eats the marginal revenue on the shoulder night.
The way out is the same in every case: write the restriction down, write the reason next to it, and review against actual outcome at month-end.
What to do about it — the five-step length-of-stay playbook
The weekly sequence I run on every property with weekend compression. Forty minutes once a week for the next eight weekends. It is the difference between protecting peak nights and accidentally muzzling shoulder demand.
- Pull the next 8 peak nights with on-the-books and STLY pace. One row per peak night. Two columns: pace versus same-time-last-year, pace versus forecast. Both green → the peak is firming on its own. Amber or red → restrictions cannot rescue a peak that is not coming.
- Pull the shoulder pace for each peak night. Friday and Sunday pacing flat or red while Saturday paces green → shoulders soft, MinLOS or MLOS-on-arrival can pull them. All three green together → restriction unnecessary.
- Choose the surgical instrument. Soft shoulders, weak through-stay base → MinLOS. Soft shoulders, strong through-stay base → MLOS-on-arrival. Long-stay segment crowding out higher-rate short stays → MaxLOS.
- Write the override note. One line per restriction: date, instrument, value, reason, expected impact, review date. Without it the calendar is a black box.
- Review the previous fortnight's restrictions against actual outcomes. Did restricted Saturdays sell out at rate with shoulders filled? Did the MinLOS catch multi-night bookings, or just turn away short-stay revenue? Adjust the next set accordingly.
The ritual is deliberately small. Eight nights, five steps, forty minutes. The advantage is not in any one weekend — it is in the cumulative effect of running the discipline for a year.
A real scenario: 120-key CBD property, August festival weekend
A 120-key CBD property, August 2025, three-week-out view. The Saturday of a known annual festival weekend was on the books at 92 (forecast 110, STLY at the same days-out 104). Pace red. Friday at 58 (forecast 76). Sunday at 41 (forecast 62). All three nights pacing soft, but the Saturday already had eighty percent of the short-stay traffic on it.
The default move would have been to lift rate on the Saturday and hold. The reading was different — the festival had moved its main programme to Friday night, taking the through-stay base with it. A flat MinLOS 2 would have blocked the short-stay Saturday bookings still trickling in for the supporting events. Instead the call was an MLOS-on-arrival 2 on the Saturday only: fresh Saturday arrivals had to come with a Sunday, but through-stays that already started Friday were waved through. Rate held.
Two weeks of result: 14 of the next 22 Saturday arrivals were two-night bookings. Saturday closed at 116 occupied. Sunday closed at 79 (forecast 62 — the restriction pulled 17 rooms of shoulder business). Friday at 84. Across the three nights, the restriction contributed roughly 28 additional room-nights at a blended A$241 ADR — about A$6,700 in incremental revenue against the no-action baseline, with almost no effect on the Saturday-only refusal rate.
The instrument matters. A MinLOS 2 would have blocked the same Saturday arrivals but cost the short-stay Saturday-only revenue still on offer. The MLOS-on-arrival caught the right traffic without filtering the recovery. One letter of difference in the channel manager. About A$2,000 of difference in net result on a single weekend.
How length-of-stay restrictions fit the rest of the stack
Length-of-stay restrictions are not a strategy. They are an inventory overlay on a strategy. The strategy lives upstream — in the pace reading, the demand calendar, the segment mix, the rate ladder. The restriction is the lever for when the strategy says protect this night without lifting rate or shape the stay pattern around this event.
If rate is too soft for the demand the property is getting, a MinLOS will not rescue ADR — it will sell the same nights cheap to fewer bookers. The metric stack covered in ADR vs RevPAR vs GOPPAR is the upstream check. Public visitor-arrival data from the Australian Bureau of Statistics and event-calendar overlays from Tourism Research Australia are free inputs into peak-night identification.
FAQ — length-of-stay restrictions in hotels
What are length-of-stay restrictions in hotels?
Pricing rules that limit which reservations the hotel will accept based on the number of consecutive nights the guest intends to stay. They do not change the published rate; they change the set of bookings the rate is offered to. Three common forms: MinLOS, MaxLOS, and MLOS-on-arrival.
What is MinLOS?
Minimum length of stay. Every booking that touches the restricted date must be at least N consecutive nights. A MinLOS 2 on a peak Saturday means a one-night Saturday booking is rejected; a two-night Friday–Saturday stay is accepted.
What is the difference between MinLOS and MLOS-on-arrival?
MinLOS applies to every booking that touches the restricted date. MLOS-on-arrival applies only to bookings that arrive on the restricted date. MLOS-on-arrival is more surgical — it blocks fresh single-night arrivals while still accepting through-stays that started earlier in the week.
When should a hotel use length-of-stay restrictions?
On nights where compression is genuine, the shoulder nights are soft, and a single-night booking would block a higher-value multi-night reservation. Peak event nights with weak weekday shoulders, single peak Saturdays in a leisure market, and tightly compressed conference windows are the textbook cases.
When should a hotel avoid length-of-stay restrictions?
When demand for the peak night is unverified, when the property has multiple peak nights in the same week, when the segment mix is short-stay-dominated, or when the restriction is being copy-pasted from last year's calendar without checking current pace.
How do length-of-stay restrictions affect ADR?
They do not change a published rate. They change the mix of bookings accepted. Blended ADR moves depending on whether the displaced short-stay bookings would have priced higher or lower than the multi-night stays brought in, and on the rate of the shoulder nights pulled with the peak.
Can length-of-stay restrictions be applied to specific channels only?
Most channel managers support channel-specific rules. A common pattern is a tighter MinLOS on OTA channels and a looser restriction on direct and group channels for the same date. The strategic question is whether the restriction is intended to shape demand or to manage acquisition cost.
A note on what this is for
Length-of-stay restrictions are one of the cheapest, most surgical tools in revenue management. No licence, no commission, no new channel — a single field in the channel manager, applied with care for a specific date and a specific reason. The cost of getting them wrong is invisible (refused bookings the property never sees). The cost of getting them right shows up in shoulder-night occupancy, blended ADR on weekend windows, and the slow accumulation of well-protected peak nights across a year.
That discipline is what we built RevPerfect for: a weekly view of the next eight weekends, pace and shoulder-pace side by side, the proposed restriction written down before it reaches a channel manager, and override notes that compound month over month. One input into the broader habit covered in hotel revenue management strategies for 2026. Try RevPerfect free → or book a 20-minute walkthrough.