Hotel rate restrictions explained: minimum stay, CTA and CTD

Hotel rate restrictions are rules attached to a date and a rate plan that limit who may book or how long they stay: minimum and maximum stay, closed to arrival (CTA), closed to departure (CTD) and stop sell. They shape the mix of stays; they are not prices and not inventory.

The holiday week is nearly full, one Tuesday in the middle sits empty, and nobody can see why. The cause is usually not price and not demand: it is a restriction on the nights either side that quietly ruled out every stay that would have covered it. After reading this you will know what each restriction blocks, how your system interprets it, and how to find and fix the nights your own rules have stranded.

What are hotel rate restrictions?#

A rate restriction is a condition attached to one date and one rate plan that limits who may book that night or how long they may stay. It is not a price and it is not a stop sell.

Restrictions sit on the calendar cell: the intersection of a single date and a single rate plan. The same night can carry different restrictions on different rate plans, which is why a guest on the flexible rate may be blocked while the non-refundable rate is open. Five restrictions cover most hotel practice: minimum stay, maximum stay, closed to arrival (CTA, no stays may begin on the date), closed to departure (CTD, no stays may end on the date) and stop sell (the date is off sale).

Price changes what the guest pays. A restriction changes whether the stay is allowed at all, so a restriction can remove a booking that a price cut would never have won back. A stop sell closes the night entirely; a restriction keeps the night on sale under conditions, which is why restrictions are the softer tool and the one to reach for first.

The guest usually sees nothing: no explanation, just "not available" or a minimum-night message. Every restriction therefore carries a hidden cost, the booking that went elsewhere without telling you. Restrictions travel with the rate plan to channels, but only as far as each channel accepts them, and that gap is where most inconsistency between channels begins.

Is a minimum stay checked on arrival or on every night of the stay?#

It depends on the system. Some check the minimum only against the arrival date; others require every night the stay touches to allow it. The same rule can therefore produce two different calendars.

In the arrival-date model, the booking is tested once, against the rule on the night the guest checks in. A two-night minimum on Saturday does not stop a guest arriving Friday for two nights, because Friday carries no minimum. In the stay-through model, the booking must satisfy the rule on each night it touches. The same Friday arrival for two nights is now blocked, because the stay touches Saturday and its total length is below Saturday's minimum.

The practical difference is largest on shoulder nights. The arrival-date model lets you fill a weak Thursday even while the weekend is protected; the stay-through model closes Thursday to anyone who will not stay through the protected nights. Ask your provider two questions before you rely on either: which model applies, and whether the rule is set per rate plan or across the property. A property-wide rule on a stay-through model can close more than you intended.

Maximum stay raises the same question and is a blunter tool. Use it only where one long booking would displace several shorter high-value ones, and check group and long-stay bookings separately, since they often bypass the rule. Check what the guest sees, too: some booking engines explain a minimum-night rule, many simply show no availability, and the guest leaves without learning that a longer stay would have worked.

Write down the model, the rule, the dates and the person who set it. A restriction nobody can explain is a restriction nobody dares lift.

What do closed to arrival and closed to departure actually block?#

Closed to arrival blocks stays that begin on that date. Closed to departure blocks stays that end on it. Neither blocks a guest already in-house, and neither blocks a stay that only passes through the night.

CTA on a date means no new check-ins that day. In-house guests are unaffected, and a guest can still book a stay that includes the night as a middle night. CTD on a date means no check-outs that day, so a guest must either leave before it or stay past it; it is the tool for a weak night that sits between two strong ones.

Put CTA and CTD on the same date and you have closed it to almost everything except a stay passing through. Add a minimum stay and it becomes a stop sell in practice. Use CTA where an arrival night would consume inventory you want for longer stays, or where the operation genuinely cannot take arrivals: a refurbishment, a late event, a staffing gap.

Both are invisible to the guest. A CTA left on for a week is a closed week, and no report will tell you what it cost. Date every one of them and give it a review date: a restriction with no end date is a decision you have stopped making.

Stop sell versus restriction, and release dates in agency allotments#

A stop sell closes a date to all sales; a restriction keeps the date on sale under conditions. Neither reaches rooms already committed to an agency block unless the contract says so.

Stop sell is an inventory decision: the night is off sale on a rate plan or across the property. A restriction is a condition decision: the night stays on sale to the stays you will accept. An agency allotment works differently from both. It is a number of rooms held for the agency with a release date, the date by which unsold rooms come back to the hotel, and until that date those rooms are not yours to restrict. A restriction you set on your own calendar does not automatically override a contracted block; the contract governs, not the calendar.

Read four things in every allotment contract: the release date, whether the agency may sell past it, what happens to unsold rooms, and whether the agency must follow your minimum stays and closed dates. When a block is not moving, the lever is the release date, not a new restriction: moving the release earlier returns rooms to you in time to sell them yourself. Contract questions belong with your legal adviser; this article describes the mechanism, not the terms of any particular agreement. The harder question, when to close a channel entirely, is a separate decision: it turns on the cost of the channel against the revenue it brings, and on whether the rooms it holds can be sold elsewhere before the date arrives.

How do restrictions create orphan nights?#

An orphan night is a night that no allowed stay can cover, left behind when the restrictions on the nights around it rule out every combination that would have included it.

The mechanism is simple. Each restriction removes a set of possible stays. The orphan appears when the only stays still allowed to cover a night are longer than anyone is willing to buy. For example: a hotel sets a three-night minimum on the first full holiday night and also closes that night to arrival. The night before can now only be sold to a guest staying three nights from there, and if nobody buys that, the night sits empty beside a full week.

The half-day start of a bayram makes this worse. Under Law No. 2429 on national and general holidays (Mevzuat Bilgi Sistemi, consolidated text, July 2024) (opens in a new tab), the holiday begins at 13:00 on the eve, so the eve is a short night that many guests want on its own; a minimum that treats it like a full night strands it.

To find orphans, walk the calendar night by night and ask one question: which allowed stay covers this night? If the answer is none, or only a stay longer than your guests buy, you have found one. There are four fixes: relax the rule on the shoulder night, allow arrival on the orphan date, use a closed-to-departure rule to force departures past it, or accept the gap deliberately and stop watching it. An orphan is not always a mistake; a night you chose to close is fine. The mistake is a night you closed without knowing. The wider context of shaping demand is covered in hotel revenue management: a working guide for independent hotels.

A bridge holiday on the calendar, for example#

Here is a hypothetical five-night window around a mid-week public holiday, restricted night by night, with one orphan created and then removed.

The legal shape matters before the example. Under Law No. 2429, Ramazan Bayramı lasts 3.5 days and Kurban Bayramı 4.5 days, each starting at 13:00 on the eve (arefe); the other general holidays are 1 January, 23 April, 1 May, 19 May, 15 July, 30 August and 29 October, the last starting at 13:00 on 28 October (Source: Mevzuat Bilgi Sistemi, Law No. 2429, Articles 1 and 2, consolidated text, July 2024).

For example: a hotel with five nights on the calendar, where nights 3 and 4 are the holiday itself. The hotel sets a two-night minimum on nights 3 and 4 and leaves nights 1, 2 and 5 open. Every night is covered by at least one allowed stay, and the window sells.

Now the mistake. The hotel raises the minimum on night 3 to three nights and also closes night 3 to arrival, to keep the first holiday night for longer bookings. Night 2 can now only be sold to a guest staying three nights from there, and it orphans. The fix is one change, not three: drop the minimum on night 3 back to two nights, or allow arrival on night 3. Then check the calendar again, night by night, because the fix on one night can open a gap on another.

The rule of thumb: the shorter the window and the stronger the demand, the more a minimum stay earns; the longer the shoulder, the more it costs. The eve night is always a shoulder, whatever the calendar calls it. No real holiday dates are used here; check the official calendar for the year you are selling before you copy any pattern.

How do you check every channel and contract, and when should you lift a restriction?#

Search each channel as a guest would, read each contract, and review every live restriction on a fixed weekly rhythm with one named owner.

Systems differ. Not every channel accepts every restriction: some take a minimum stay and not a closed-to-arrival date, and some translate a restriction into a stop sell. Do not assume your calendar is reproduced exactly anywhere. Test by search, not by report: for a date you restricted, run one search that should be blocked and one that should be allowed, on each channel, in a clean browser, far enough out that the result is meaningful.

Contracts carry their own rules. An agency contract may state its own minimum stays, release dates and cancellation terms, and a restriction in your system does not rewrite a signed agreement. Keep the two in step, and take contract questions to your legal adviser. The wording of the terms around bookings is its own subject; see hotel cancellation policy: how to write clear, consistent terms.

Keep a restriction log: one line per restriction with the date, the rule, the reason, who set it, the review date, and what happened. It is the only record that will tell you whether the rule earned anything. Review weekly with four questions: is the night still weak or still strong, did the restriction produce bookings or only remove them, is the orphan still there, and has a contract changed since last week. Lift in order: shoulder nights first, then the minimum, then the closed dates, because lifting everything at once hides which change did the work. There is no reliable outside benchmark for what a restriction earns; the only evidence you will ever have is your own pickup before and after, which is why the log matters.

What to do next#

Open your calendar for the next holiday window and walk it night by night, writing down which allowed stay covers each night; then search one restricted date on each channel as a guest would. Those two habits, done weekly, catch almost every orphan night and every channel that is not showing the rule you think you set.