Minimum-Stay Rules by Weekday: The Cheapest Way to Protect a Turn

A two-night gap between two bookings costs more than the nights it earns. Setting the minimum by weekday is cheaper than discounting the gap away.

Last updated: October 21, 2026

A two-night gap between two bookings looks like two unsold nights. It's usually a changeover you pay for twice: once to turn the unit for the guest leaving, once for the guest arriving. Add the longer booking the gap blocked, and the two nights can cost more than they earn. The fix isn't a discount. It's a minimum stay that varies by weekday.

Key Takeaways

• A gap costs a turn, not just nights. Two bookings where one would fit means two changeovers, two sets of linen and two check-ins.
• Occupancy hides it. The nights look sold either way; the cost sits in the turns, which no dashboard puts on the same line.
• Set the minimum by arrival weekday. The weekend needs protecting; a Tuesday usually doesn't.
• A uniform rule backfires. A high minimum on every night empties the midweek, which is often the most profitable part of the week.
• Measure turns, not nights. Gap nights, turns per month and net per available night tell you more than occupancy alone.

What a gap actually costs

Start with the turn. A changeover has labour, linen, consumables and a check. When a unit runs continuously, one turn covers the transition from one guest to the next. When a gap splits two stays, you still pay that turn at the start of the gap and another at the end — and the gap itself produces no revenue to carry either.

Then add displacement. A two-night hole in the middle of a week can't take the six-night booking that would have spanned it. The gap doesn't just earn nothing; it makes a better booking impossible. That's the part hosts underestimate, because the calendar shows an empty pair of nights rather than a lost week.

Then add the admin. Two check-ins mean two sets of arrival messages, two chances of a late arrival, and twice the odds of a question at an inconvenient hour. None of that appears in a nightly rate calculation.

The arithmetic is uncomfortable. A four-night stay and two two-night stays across the same four nights produce the same occupancy. The second version costs two turns instead of one. If the short booking was discounted to fill the gap, it also earns less.

That's why filling a gap is not automatically good. The question isn't whether the nights sold. It's whether the booking left anything after the turn it created.

Setting minimums by weekday

The minimum stay doesn't have to be a property of the listing. It can be a property of the arrival day, which is where the demand actually differs.

Friday and Saturday arrivals carry the weekend, and they're the ones worth protecting with a two or three-night minimum. A Friday arrival with a one-night minimum sells Friday and leaves Saturday exposed, which is the worst version of a sold weekend: one night gone, one night stranded.

Sunday to Thursday arrivals are the filler nights. A one or two-night minimum there lets you pick up the business trip, the airport stopover and the gap between two longer stays. Keeping these low is what stops the weekday calendar from going dark.

The setting also interacts with your changeover day. If your cleaner works Tuesday and Friday, a Wednesday arrival adds an off-schedule turn, and those cost more than the nights they fill. Then the minimum isn't about demand; it's about routing the calendar through the days your operation already runs.

Where channels allow different minimums, keep them close. A wide difference invites the same guest to book the shorter version elsewhere, and it makes your calendar harder to read.

One habit worth keeping: check next month's calendar weekly for orphan nights. A single night stranded between two bookings is a turn waiting to be paid for, and extending a minimum is usually cheaper than discounting it.

Where the rule backfires

The first failure is uniformity. A three-night minimum on every arrival looks tidy and quietly kills midweek demand. Corporate stays, early flights and stopovers don't negotiate with a rule; they book elsewhere. You end up with a weekend business and an empty Tuesday.

The second is seasonal. The minimum that protects a peak weekend leaves a hole in a shoulder week, where nobody books three nights if two is the norm. Then you discount to fill it, which is the exact move the minimum was meant to avoid.

The third is the holiday edge. A holiday weekend followed by a normal week leaves a single stranded night on the Monday. A minimum applied to arrival days only handles this better than a rule applied to every night of the stay, because it can block the short arrival without blocking a longer stay that happens to include the holiday.

The fourth is the exception you'll need anyway. Repeat guests, a guest already in the building, a booking that fills four empty nights — a rigid rule refuses all of them. Write the exception down, with its condition, so nobody decides it at 11pm.

The fifth is a misread channel. If one channel sends mostly short stays, a new minimum can make it look as though demand collapsed, when what changed was the filter. Check the channel's own numbers before concluding anything about the market.

Measuring it after a month

One month is short. Read direction rather than level, and don't call two data points a trend.

Track four things. Gap nights: nights between bookings that your minimums now make unsellable. Turns per month, including off-schedule ones. Nights per turn, which should rise if the rule is working. Net per available night: revenue minus cleaning and linen, divided by nights available — the number the other three exist to move.

Compare the same weekday block against last month, and against the same weeks a year earlier if you have them. The year-on-year view is the only one that separates your rule from a change in demand.

The decision rule is simple. If turns fell and net per available night held, keep the minimum. If turns fell but one specific weekday emptied, loosen that weekday only — the rule is usually right in shape and wrong in one place. If neither turns nor net moved, the minimum is doing nothing and can go.

Don't test several changes at once. A new minimum, a new cleaning fee and a new discount in the same month produce a result you can't attribute.

LOCALSBNB keeps Airbnb, Booking.com, Agoda and Trip.com on one calendar and shows each channel's source rate and status beside the dates, so a hole that's genuinely unsold is distinguishable from one a channel hasn't updated. localsbnb.com is where that comparison happens before you decide whether the gap is worth a discount or a rule.

FAQ

Is a minimum stay better than a discount?

Usually, for a gap. A discount buys a booking that still costs a turn, so it has to clear the turn before it earns anything. A minimum prevents the booking that creates the turn.

Should the minimum be the same on every channel?

Keep them close. A wide gap between channels sends the same guest to the shortest version, and it makes your calendar harder to read. Where a channel won't support the setting, adjust the rate there instead.

What if a good repeat guest wants one night?

Take the booking and note why. A written exception with a condition is cheaper than a rule so rigid that it refuses the guests who pay on time.

The gap is a cost, not an empty space, and the cheapest way to handle it is usually to refuse the booking that creates it rather than to discount the nights it leaves behind. If you want the four channels and their status in one view while you decide, localsbnb.com is the calendar those decisions are made on.

---

This article is general guidance for hosts and isn't legal, tax or insurance advice. Minimum-stay settings, channel rules and cleaning costs differ by market and change. Confirm the current terms with each platform you use and check your own numbers before you change a rule.