What MinLOS, CTA, and CTD Actually Do
Price is not the only lever in revenue management. Length-of-stay restrictions let you shape the shape of demand rather than just its price. The three core tools are minimum length of stay, closed to arrival, and closed to departure, and used well they can meaningfully lift revenue on your busiest dates without you touching the rate at all.
- MinLOS (minimum length of stay): any reservation that includes the restricted date must be at least N nights long. A two-night MinLOS on a Saturday means a guest cannot book Saturday alone; they must add Friday or Sunday.
- CTA (closed to arrival): guests may stay through the date but cannot start a new stay on it. Useful for pushing arrivals to a more convenient day while still selling the night.
- CTD (closed to departure): guests cannot check out on the date, which forces stays to continue past it. Useful for protecting the far side of a peak period.
These are availability rules, not prices, and they are applied per date and often per rate plan. The skill is knowing when scarcity justifies them and when they simply cost you occupancy.
Why Restrictions Beat Pure Price on Peak Dates
Imagine a single Saturday that will clearly sell out because of a local event. If you only raise the rate, you still accept whoever books first, including guests who want just that one night. Every single-night Saturday booking you take may block a guest who wanted Friday and Saturday, or all three weekend nights. The single-night guest fills one high-demand room; the multi-night guest fills that same room plus one or two rooms on adjacent, softer dates that might otherwise sit empty.
MinLOS solves this by refusing to let your scarce peak inventory be consumed by low-total-value single nights. You are not just charging more for the peak night; you are using the peak night as leverage to sell the nights around it. That is the central insight behind length-of-stay controls.
A Worked EUR Example
A 30-room hotel has a Saturday that will sell out because of a regional festival. The Friday and Sunday around it are only moderately busy. Your rate is EUR 200 on Saturday, EUR 130 on Friday, and EUR 120 on Sunday.
Without any restriction, suppose you fill Saturday with 30 single-night bookings. Revenue for the weekend from those rooms is 30 times EUR 200, or EUR 6,000, and Friday and Sunday fill only partially from other demand.
Now apply a two-night MinLOS across the peak, requiring Saturday guests to also book Friday or Sunday. Say this converts even 18 of the 30 rooms into two-night stays and you still fill Saturday completely. Those 18 two-night stays each add a EUR 130 or EUR 120 adjacent night. That is roughly 18 times EUR 125 average, about EUR 2,250 of incremental revenue on nights that would otherwise have been soft, on top of the EUR 6,000 Saturday.
The catch is real: a strict MinLOS might deter some pure single-night demand and, if the date does not truly sell out, could leave Saturday rooms empty. That is why the restriction belongs only on dates you are genuinely confident will fill. The worked point is that when scarcity is real, capturing adjacent nights can add thousands of euros that a rate increase alone never touches.
The Trade-Off: Revenue Per Booking Versus Occupancy
Every restriction trades higher value per booking against the risk of lost volume. The decision hinges on one question: will this date sell out without the restriction? If yes, MinLOS almost always helps, because you are turning away low-value demand you did not need. If no, MinLOS can hurt, because you are turning away demand you did need to reach full occupancy.
This is why length-of-stay controls should never be set and forgotten. As a peak date approaches and your pace tells you whether the sell-out is materialising, you should be ready to relax the restriction. A common, costly mistake is leaving a three-night minimum on a date that softened, and watching rooms go empty that a flexible guest would happily have filled.
Match the restriction strength to the confidence
Use a graduated approach. A near-certain sell-out event might justify a three-night MinLOS far out, relaxed to two nights as the date nears, and lifted entirely in the final days if pace disappoints. A merely strong weekend might only warrant a two-night MinLOS or a simple CTA to steer arrivals. The stronger and more certain the demand, the stronger the restriction you can safely impose.
Managing Orphan Nights
Restrictions create a side effect called orphan nights. An orphan night is a single empty night stranded between two booked stays, for example a free Tuesday sandwiched between a stay ending Tuesday morning and one starting Wednesday. A rigid two-night MinLOS makes it impossible for anyone to book that isolated Tuesday, so it stays empty and earns nothing.
Good orphan-night management means detecting these gaps and deliberately opening them up, often by lowering or removing the MinLOS for that specific stranded date, and sometimes discounting it to attract a one-night filler. The tools for this include:
- Selective MinLOS release: drop the minimum on the orphan date only, leaving surrounding restrictions intact.
- CTD on the night before: discourage check-outs that would create the orphan in the first place.
- Targeted last-minute pricing: price the orphan night to move, since a filled single night at a modest rate beats an empty one.
Orphan nights are easy to miss when you manage restrictions by hand across dozens of dates, and they quietly erode occupancy. Catching them is one of the clearest places where automation pays off.
How an RMS Automates Length-of-Stay Controls
Doing all of this manually across a rolling 90 or 180 day calendar, several rate plans, and multiple channels is genuinely hard. A revenue management system helps in four ways. First, it forecasts demand and typical length-of-stay for each future date, so restrictions are set where the data supports them rather than on a hunch. Second, it recommends or automatically applies the appropriate MinLOS, CTA, or CTD, and crucially relaxes it as pace evolves. Third, it detects orphan nights and suggests releasing or repricing them. Fourth, it pushes the rules consistently to your channel manager so a restriction you intend on one channel is not silently ignored on another, which is a common source of leakage.
The point of automation here is not to remove your judgement but to remove the tedium and the errors of scale, so that every date on your calendar gets the attention that, by hand, you could only give to a handful.
Common Mistakes to Avoid
- Blanket restrictions: applying MinLOS across a whole season rather than specific high-demand dates suppresses occupancy on nights that never needed protecting.
- Forgetting to relax: leaving a minimum in place after demand softens is the single most common way MinLOS destroys value.
- Ignoring orphans: restrictions without orphan-night management steadily leak occupancy.
- Channel inconsistency: a restriction that applies on your direct site but not on an OTA undermines the whole strategy.
- Over-restricting a weak market: if you rarely sell out, length-of-stay controls will usually cost more than they earn.
Where Nexorev Fits
Nexorev is a pilot-stage AI revenue-management tool built by a solo founder for independent and boutique hotels, focused initially on North Italy. As of July 2026 it has no production hotel deployments. Its published numbers come from backtests on public North Italy market data: a 9.8 percent occupancy-forecast MAPE, a 6.4 percentage-point RMSE, and a simulated plus 7.6 percent RevPAR lift versus a static-rule baseline, all of which are simulated and market-data figures rather than customer outcomes. The pilot is EUR 499 per month for the first five hotels, with a planned production tier of EUR 1,200 to 2,400 per month. For length-of-stay strategy specifically, the value of a forecasting tool is knowing which dates will genuinely sell out, so MinLOS and related controls are applied where they help and relaxed before they hurt, and so orphan nights get surfaced rather than lost. The strategy and the final call remain yours.
Next Steps
- Explore the Nexorev live demo — the real product, no email wall.
- Contact the founder directly — questions answered by the person building the system.
- Book a 15-minute intro call — no sales team, no pressure.
Related Reading
- A practical guide to dynamic pricing for boutique hotels
- Group booking pricing strategy
- Last-minute hotel pricing tactics
- Boutique hotel yield management 101
Disclaimer
This article is general educational material as of July 2026 and is not investment, financial, or contractual advice. Any industry references are provided neutrally and based on public information available at the time of writing. Nexorev performance figures mentioned here come from backtests and simulations on public North Italy market data, not from Nexorev customer outcomes, because as of July 2026 Nexorev is pilot-stage with no production hotel deployments. Length-of-stay restrictions carry occupancy risk; validate any strategy against your own property data and local demand before acting.