Closed to arrival vs closed to departure: choosing the surgical restriction
The first time I watched a closed to arrival hotel restriction misfire, I was sitting in front of a Saturday-night sell-out at a 180-key urban property. CTA had been set on Saturday to protect the compression, and we had quietly killed the Friday pickup that fed Saturday's stay-through. The OTA listing had gone dim for the high-demand arrival date, and the Friday-night ADR opportunity decayed in real time. The restriction did exactly what it was designed to do. The mistake was that we had used the wrong one.
What closed to arrival actually means in 2026
Closed to arrival, almost always shortened to CTA, prevents any new reservation from starting its stay on a specific date. A traveller searching for a one-night Saturday stay on a CTA-restricted Saturday will be offered nothing. A traveller searching for a two-night stay arriving on the Friday will still be offered the room, because the arrival is on the unrestricted Friday and the Saturday is stay-through, not arrival.
Closed to departure, CTD, is the opposite tool. It blocks any reservation from ending on a restricted date. A guest can arrive or stay through, but cannot check out. The arithmetic effect is to push the departure into the night that follows.
Two restrictions, opposite mechanics. They are often discussed together because the underlying decision is the same one — which date is the compression, and which night is doing the work — but they are not interchangeable.
The reason this matters in 2026 is that booking lead times have shortened on transient business in most Australian markets, and the operator who responds with a blunt minimum length of stay closes off pickup that the property would otherwise capture. CTA and CTD are the surgical alternatives. Used well, they protect ADR without killing the stays that surround the compression. Used badly, they hide the property from search on dates that needed every booking.
The mechanics: how the two restrictions actually work
It is worth being precise about what each restriction does to a booking funnel.
Closed to arrival (CTA)
CTA hides the arrival date from any new reservation. The restricted date can still appear in the middle of a stay or at the end of one. The property is sellable for stays that touch the date, but not as a starting point. The traveller who wants to arrive that night cannot.
Closed to departure (CTD)
CTD hides the departure date from any new reservation. The restricted date can still be an arrival or a stay-through night. The traveller who wants to leave that day cannot finish the stay there — they must extend at least one more night.
CTD uses the restricted date to extend stays into the next one.
That single sentence is the whole decision. CTA is defensive — it is a wall around the compression date. CTD is propulsive — it pushes existing demand forward into the night after. The right tool depends on which night you are trying to protect, and whether the restricted date is the compression or the date that follows it.
A worked example: the Saturday compression weekend
Take a 150-room property in a state capital. A Saturday concert in a 40,000-seat venue has compressed the city centre for three years running. The Friday picks up softly with corporate stay-throughs. The Sunday is quiet.
| Night | Forecast demand | Forecast ADR | The pricing job |
|---|---|---|---|
| Thursday | Soft, midweek corporate | A$185 | Sell every room |
| Friday | Compression, leisure pickup | A$245 | Yield rate, protect inventory |
| Saturday | Full compression, event night | A$320 | Protect from one-night stays |
| Sunday | Soft, post-event | A$165 | Sell anything available |
The temptation on Saturday is to set a two-night MinLOS. The problem is that the MinLOS closes off Saturday arrivals entirely — including the Saturday-only one-night stay that would have paid A$320, and the Saturday-Sunday two-night stay that would have stretched the high-rate night across a soft Sunday at a blended ADR worth keeping.
The CTA alternative is surgical. Apply CTA on Saturday. New Saturday-only one-night arrivals are blocked. Friday-Saturday two-night stays are still sellable. The property keeps the high-yield Friday arrivals and protects the Saturday from one-night low-yield stays that would have displaced higher-rate Friday-arrival demand.
Now flip the question. The Saturday is at compression rate, and the Sunday is the problem. CTD applied on Saturday forces stays that would have ended on Saturday to extend into Sunday. Rate on the Sunday can be set at a soft-night level that still pays for the room, and a portion of the high-rate Saturday demand carries through. Same date, opposite work. CTA protects Saturday. CTD uses Saturday to fill Sunday.
Where the CTA / CTD decision breaks down
The framework is simple. The application is where most properties stumble. Four failure modes show up repeatedly.
The restriction is set on the wrong date. CTA is set on the compression date when CTD would have done better, or CTD is set when the night that follows is just as soft as the one being protected. The restriction is a function of the demand curve on the surrounding nights, not of the compression itself.
The restriction is applied as a blanket policy across all channels. Direct guests on a compression date are a different operational picture to OTA guests. The cancellation behaviour, the ADR, the willingness to stay-through — none of it is uniform. A CTA that hides the property from OTA search may be the right answer while direct stays remain open.
The restriction is left on too long. Properties that leave CTA / CTD set as default protection — on every weekend, on every event date — bleed pickup on the dates that were not actually compressing. The restriction should be tied to a specific demand signal, with a defined trigger and release.
The restriction is set without pricing the alternative. The whole point of a stay restriction is to redirect demand to a more profitable stay shape. If the property has not priced the alternative — the two-night stay the CTA leaves open, the Saturday-Sunday stay the CTD creates — the restriction is moving demand to a stay shape the rate model has not been calibrated for. The restriction worked, the rate did not.
CTA protects the compression. CTD propagates it. Most properties pick one as a habit and never ask which one the demand curve was actually asking for.
The interaction between stay-length controls and the broader demand forecast is the subject of hotel demand forecasting for revenue managers. The CTA / CTD lever is only as good as the forecast it is built on.
What to do about it — a five-step playbook
The workflow I run on properties that have CTA / CTD available in their channel manager and want to start using it surgically.
- Identify the night, not the date. The first question is "which night is the compression and which adjacent night needs protecting from displacement". The restriction comes after the answer, not before. If the concern is a cheap Saturday arrival displacing a high-yield Friday-arrival stay, CTA on Saturday is the tool. If the concern is the empty Sunday following the full Saturday, CTD on Saturday is the tool.
- Price the alternative stay shape before setting the restriction. A CTA on Saturday redirects demand to Friday or earlier arrivals. The Friday rate has to reflect that. A CTD on Saturday forces stays into Sunday. The Sunday rate has to capture the forced extension at a level the guest will accept. The restriction without the matching rate move is half the lever.
- Set the restriction by channel where the volume justifies it. If 70% of the compression demand is coming through OTA and 30% direct, the cleaner application is to restrict OTA and leave direct open. Channel-by-channel restriction is more administrative work, but the recovery is real.
- Define the trigger and the release. Every CTA / CTD should have a written rule — "set when pickup hits X" and "release when remaining inventory falls below Y" or "release at T-7". A restriction without a release rule becomes a default policy.
- Review every restricted date post-stay. Did the restriction redirect demand to the stay shape you wanted? Did the alternative stay clear at the rate you priced it? Was there a cohort of demand the restriction lost that you would have wanted to capture? The post-stay review is what calibrates the next compression date.
The principle running underneath all five steps is that the restriction is a function of the surrounding demand, not of the compression alone. The discipline of reading the surrounding nights is the discipline at the heart of every hotel revenue management strategy that earns its keep in 2026.
A real scenario — anonymised, but the shape repeats
I worked with a 220-key full-service property in a coastal city last year. The market hosted a major sports event over three nights — Friday, Saturday, Sunday. The hotel had been running a standing two-night MinLOS across the three dates for as long as anyone could remember. The owner believed the policy was protecting ADR.
The MinLOS had been closing off two cohorts the hotel did not realise it was losing. The one-night Friday business stay — corporate guests who switched to a competitor when the MinLOS denied them. And the one-night Sunday leisure stay — guests who had attended the event, stayed somewhere else, and would have happily booked Sunday at a soft rate if the property had been searchable.
We replaced the MinLOS with two surgical restrictions. CTA on Saturday — protecting Saturday from one-night low-yield stays. CTD on Friday — using the Friday compression to push event-attendee stays into Saturday at the compression rate. Sunday was left open at a soft-leisure rate.
Across the three event nights, RGI moved from 108 to 117. ADR fell three dollars on Friday and rose A$14 on Saturday. RevPAR rose 9%. Sunday occupancy lifted from 51% to 79%. The improvement was not from a new rate model — it was from replacing a blunt instrument with two surgical ones. The deeper RGI decomposition that came out of the review is in the companion piece on ADR vs RevPAR vs GOPPAR.
How CTA / CTD interact with the rest of the pricing stack
Stay restrictions are a refinement of the rate decision on a specific date. The rate sets the price for the room. The restriction sets which stays can buy that room. Used together, they define both the price and the eligible stay shape — which is how revenue management works once it stops being about a single rate per night.
The pickup review is the calibration loop. If CTA is on Saturday and the Friday pickup has slowed unexpectedly, the restriction may need to come off — the protection was a function of the forecast pickup, and if the pickup has not materialised, the restriction is now hiding the property from demand that would book. That daily review is the engine of hotel pickup and pace done properly.
FAQ
What does closed to arrival mean in a hotel?
CTA prevents any new reservation from starting its stay on a specific date. A guest can stay through it or end their stay on it, but cannot check in on it. The restriction protects a high-demand date from being filled with short, low-value arrivals that would displace higher-yield stay-throughs.
What does closed to departure mean in a hotel?
CTD prevents any reservation from ending on a specific date. A guest can arrive or stay through, but cannot check out. The restriction pushes stays into the night that follows, propagating demand from a compression night into a soft night.
What is the difference between CTA and CTD?
CTA blocks arrivals. CTD blocks departures. CTA protects the restricted date from being filled badly. CTD uses the restricted date to force stays into the next night.
When should I use CTA instead of a MinLOS?
CTA is more surgical. A MinLOS closes off every booking that touches a date if it does not meet the length threshold. CTA only restricts the specific arrival date, leaving stay-throughs and earlier-arrival stays open. If the compression is on one night and the surrounding nights are soft, CTA preserves the surrounding pickup.
Does closed to arrival hurt OTA visibility?
Yes, but narrowly. The property will not appear in OTA search when a traveller specifies the restricted date as their arrival. It still appears when the traveller searches with an earlier arrival whose stay covers the restricted date. The visibility cost is date-specific, not channel-wide.
When does CTD backfire?
When the night that follows the restricted date is itself soft. The forced extension delivers occupancy at a rate that erodes the average. CTD is only profitable when the forced extension night carries a rate at or above the average of the stay.
Should I apply restrictions globally or channel-by-channel?
Channel-by-channel where the operational picture justifies it. Direct and OTA bookings on a compression date often look different. The most precise restriction is the one applied where the displacing demand is coming from.
The honest dashboard
A property using CTA / CTD as standing policies is leaving demand uncaptured on the dates that did not actually compress. The right use is precise, calibrated to the demand forecast, paired with a rate move on the alternative stay shape, and reviewed post-stay.
If your daily pace view does not surface the restrictions currently active by date and by channel — and whether the alternative stay shape is being priced to match — you are running the restriction stack from memory. Try RevPerfect free → or book a 20-minute walkthrough and I'll show you what your CTA / CTD calls have been doing to your compression weekends.