The host problem
Most hosts set a minimum-stay rule once — often two nights — and leave it there. That rule applies equally to a high-demand Friday in October and a slow Tuesday in January. The same rule that protects revenue in one context limits conversion in another.
Minimum-stay rules are booking-shape tools. They shape what kind of reservations fill your calendar. Used well, they protect ALOS and Net RevPAR. Used poorly, they create orphan gaps and kill midweek conversion.
The number, concept, or decision
ALOS as the organizing metric
ALOS — Average Length of Stay — measures the average number of nights per booking.
Formula: ALOS = Live Booked Nights ÷ Live Bookings
A 0.5-night ALOS improvement across a month can lift Net RevPAR meaningfully without any change in ANR. The improvement comes entirely from reducing the number of turnovers relative to occupied nights.
Three minimum-stay failure modes
A minimum-stay rule creates problems when it:
- Blocks short fills of genuine orphan gaps
- Prevents midweek conversion by requiring longer stays than the demand supports
- Allows short stays in high-demand event windows where longer stays would capture more revenue per available night
Each failure mode requires a different rule adjustment.
What this helps you decide
Your minimum-stay system should answer five questions:
- What is my default minimum for weeknights, weekends, and event windows?
- Do I apply a longer minimum during high-demand periods to protect ALOS?
- Do I allow a shorter minimum in late-cycle windows to absorb orphan gaps?
- Does my current minimum create gaps that cannot attach to adjacent demand?
- What does a change to the minimum do to my projected Net RevPAR?
Example
A host runs a two-night minimum across the board. In October, her calendar shows a five-night block from Tuesday through Saturday with two nights already sold on the weekend. The three open midweek nights cannot fill because no guest books Tuesday through Friday at a two-night minimum.
She temporarily drops to a one-night minimum on Tuesday and Wednesday only. Two one-night bookings fill those nights. She accepts the extra turnovers because the alternative is two empty nights — which produce no revenue and no turnover cost but also no income.
Now she runs the Net RevPAR math: two one-night bookings at $95 each generate $190. Two turnovers at $174 TCP each cost $348 in turnover drag across two nights. Net accommodation revenue after turnover: negative $158 across those two nights.
The math tells her those one-night fills hurt Net RevPAR. She needed to price those midweek nights higher — or leave them open and protect her weekend rate integrity — rather than accepting short bookings at a rate that does not cover turnover.
What most hosts get wrong
Most hosts use minimum-stay rules to protect weekends without realizing those same rules create midweek orphan gaps that either fill badly or do not fill at all.
The second mistake is applying a uniform minimum across event windows and normal weeks. A three-night minimum during a major local festival keeps your ALOS healthy during high demand. That same three-night minimum in late January kills midweek conversion on nights that need a one-night or two-night absorber.
What to do this week
- Pull your last month’s ALOS from your KPI sheet.
- Identify any nights that stayed open because your minimum blocked shorter bookings.
- Calculate what those nights would have produced at a lower minimum — and whether the turnover cost made the fill economically worthwhile.
- Review your minimum-stay settings and add at least one day-specific or date-range rule for the next event window or peak period.
Where this fits in the STR Signals framework
Minimum-stay rules belong to the booking-shape layer of the pricing framework. They do not replace rate decisions. They shape which bookings arrive so that rate decisions work on a better inventory mix.