Lorixen.
EN

Holiday Cottage Booking Rules: Changeover Days and Minimum Stays

Short answer: A cottage calendar needs three separate rules, not one: which weekday a stay may start, how many nights it must last, and what is allowed to fill the odd gaps between bookings. Write them down per season before you touch any software, because most booking tools can express them but none can guess them. Peak weeks usually stay strictly Saturday to Saturday, shoulder weeks loosen to a weekday choice with a three or four night floor, and winter opens short breaks. The guest should never be able to pick a date range your rules would later reject.

Why the rules belong in the calendar, not the small print

A cottage owner often starts with a sentence on the booking page: "Weekly lets run Saturday to Saturday." That works until a guest sends an enquiry for Friday to Tuesday in August, you decline by email, and they book elsewhere before you reply. A rule written in prose protects nothing. A rule expressed in the date picker makes the invalid choice impossible to click, so your replies shrink to genuine questions.

The cost of getting this wrong is not dramatic, it is steady. Every impossible request costs a reply, every reply costs a day, and some of those guests would have taken a legitimate alternative if the calendar had shown it.

The three rules, kept apart

Arrival day

Arrival day says which weekdays a stay may begin. Some owners also restrict departure day, which is a different field in most tools. Do not merge them. A cottage that allows Saturday arrival but any departure is a different product from one that allows Saturday arrival and Saturday departure only, and your cleaner's rota usually decides which one you really have.

Minimum nights

Minimum nights is a floor measured from the arrival date. It can differ by arrival weekday: a Friday arrival might need three nights while a Monday arrival needs only two. Hold this as a lookup table rather than a single number.

Gap handling

Gap handling covers the leftover nights between two confirmed bookings. If a Saturday to Saturday week ends on the 12th and the next one starts on the 15th, there are three open nights that no standard rule can sell. You either allow an exception that overrides the minimum when a stay fits the gap exactly, or you accept that those nights stay empty.

A decision table for seasons

Use a table like this as your planning document. The values are an illustrative example for one cottage, not a recommendation.

Period Arrival days Minimum nights Gap exception
School summer holidays Saturday only 7 None
Spring and autumn shoulder Friday or Monday 3 Allow if it fills a gap exactly
Winter midweek Any day 2 Allow any length that fits
Christmas and New Year Fixed dates As listed None
Bank holiday weekends Friday 3 None

Fixed-date periods are worth treating separately. Christmas and New Year are usually sold as named packages with set start and end dates, and forcing them into a weekday rule produces odd results.

Setting it up step by step

  1. List every season with its start and end date, and put school and bank holiday dates in once for the whole year.
  2. For each season, write arrival weekdays, departure weekdays and minimum nights as three separate cells.
  3. Mark which seasons allow gap exceptions, and decide whether the exception overrides minimum nights, arrival weekday, or both.
  4. Enter the rules in your booking tool as date-ranged rule sets. If the tool only supports one global minimum, that is a sign to look at alternatives or a small custom layer.
  5. Test five invented bookings that should be refused, such as a Wednesday arrival in August, and five that should pass.
  6. Check what the guest sees when a date is blocked by a rule. A greyed square with no explanation is worse than a short message such as "Summer weeks start on Saturday".
  7. Review the rule table every autumn, after you know next year's school dates.

What the guest should see

The calendar is the main page of the whole site for a cottage, so it deserves a plain explanation next to it. Show the current rule for the dates they are looking at, not the whole annual table. If they pick a Monday in the Saturday-only season, offer the two nearest valid arrival dates as buttons. If they pick a short stay in a minimum-week period, say what the nearest longer option costs and keep the message neutral rather than apologetic.

Also show the changeover times next to the dates: arrival from a stated hour, departure by a stated hour. Guests plan travel around those two numbers, and a cottage that says nothing invites a 9 a.m. arrival.

Multi-cottage sites

If you run several properties, resist one rule set for all. A coastal cottage and a farmhouse a mile inland can have different peak seasons. Give each property its own table and a common template to copy from, so changes at the portfolio level are quick but not forced.

Common mistakes

  • Setting the minimum stay as a global number, which blocks perfectly sellable gap nights in winter.
  • Applying the arrival-day rule to the departure day without noticing, which turns weekend breaks into impossible requests.
  • Forgetting that a rule applies to the arrival date only. A stay arriving in a shoulder week and leaving in a peak week needs a decision: reject it, or price it as peak.
  • Hiding the rule in a terms page that few guests open.
  • Changing rules mid-season without checking provisional holds. Bookings already confirmed keep the rules they were made under.

Where structured data helps

Search engines can read basic facts about a lodging business if you mark it up, and the vocabulary at schema.org/LodgingBusiness lists the properties available. Markup will not enforce your changeover rules, but a clear page that states them in text helps both guests and anyone summarising your site.

FAQ

Should I allow short breaks in the summer at all?

That depends on how often you actually fill the peak weeks. A common compromise is to keep the strict weekly pattern until a date a few weeks out, then relax it. Whatever you choose, write it as a rule with a trigger date, so the calendar changes automatically rather than relying on your memory.

How do I handle a guest who wants to arrive a day early?

Treat it as a separate paid add-on only if the cottage is genuinely empty the night before. Check the previous booking first. Offering it as a request, rather than a button, keeps you in control.

Can a gap exception hurt my average rate?

It can lower the average nightly figure, because short gap stays are often priced below a full week. Decide a floor price for gap stays in advance so you are not negotiating each one.

Do I need custom software for these rules?

Often not. Many channel managers and booking plugins cover seasonal minimums and arrival days. Custom work is worth discussing when your rules depend on several properties at once or on a cleaning rota.

If your calendar rules are more tangled than a plugin can express, tell us how your cottages are booked and we will sketch what a rule-aware calendar would involve.

Sources

WhatsAppBook a call