A hidden holiday is a recurring three-day weekend that drives a predictable demand spike but gets priced like an ordinary weekend. Think Memorial Day, Labor Day, Presidents Day, MLK weekend, the Fourth of July when it lands next to a weekend. They are not one-off mega events you have to forecast from scratch. They are on the calendar every single year, and the guests who want those dates know it. They book early and they pay a premium. The operators who treat the dates as normal weekends are the ones who never see the money they left behind.
I spent years at Vacasa watching this exact leak repeat across thousands of units. It is not a pricing-tool failure and it is not a demand problem. The demand is real and it is reliable. It is a calendar-discipline problem. Nobody sat down in February and marked the long weekends that would matter in May, June, and September, so the rates got set on autopilot and the premium guest booked at the standard number.
"The guests who want a long weekend book it early and pay for it. If your rate has not moved, the premium guest just booked at your normal price."
Why the long weekend is different from a normal weekend
A normal Friday-Saturday fills on a roughly two to three week booking window in most leisure markets. A holiday long weekend fills much earlier, because the guest is coordinating around a fixed three-day block, often travel, often a group. That earlier window is the whole opportunity. The demand shows up before your standard rate logic has any reason to react, so the calendar quietly fills at the wrong number weeks ahead of when a reactive tool would have nudged the price up.
There is a second cost that is easy to miss. When you price a long weekend like a normal weekend, you do not just undercharge. You let the wrong guest take the date. A standard-rate booker grabs your peak inventory early, and the premium guest who would have paid more arrives a few weeks later to a calendar that is already gone. You lost the rate and you lost the better booking, and neither one ever showed up as a problem. It showed up as a reservation.
The recurring long weekends, and how far ahead to price each
Here is the core US calendar. The lead time is how far out the premium demand starts committing, which is when your rate needs to already be right, not when you start thinking about it.
MLK weekend (mid-January).
Price 8 to 10 weeks ahead. Strong in ski and warm-winter escape markets, soft most everywhere else. Treat it as a market-specific spike, not a national one.
Presidents Day weekend (mid-February).
Price 8 to 12 weeks ahead. A real peak in ski country and winter-sun destinations. The school-break overlap in many regions extends the window beyond the three days, so check the local calendar.
Memorial Day weekend (late May).
Price 10 to 12 weeks ahead. The unofficial start of summer and the first big lake, beach, and mountain spike of the year. This is the one operators most reliably underprice because they are still in shoulder-season pricing mentally.
Fourth of July (early July).
Price 12 to 16 weeks ahead. When the holiday lands on a Tuesday or Thursday, guests bridge it into a four or five-night block. Price the whole bridge, not just the weekend, and set the minimum stay to capture it.
Labor Day weekend (early September).
Price 10 to 12 weeks ahead. The last summer long weekend, which makes it the highest-intent one in seasonal markets. Demand is strong and price-tolerant because guests know it is their last window.
Indigenous Peoples / Columbus Day weekend (mid-October).
Price 8 to 10 weeks ahead. Underrated. Strong in fall-foliage and shoulder-season markets where it is often the last real spike before the off-season.
Veterans Day weekend (mid-November).
Price 6 to 8 weeks ahead. Modest in most markets, but a genuine three-day block when it lands adjacent to a weekend. Worth a premium in warm-weather and event-driven destinations.
Regional and local spikes.
Price 8 to 12 weeks ahead. State holidays, school breaks, university parents and graduation weekends, regional festivals on a fixed annual date. These are invisible nationally and decisive locally. They belong on the same calendar.
Build this once as a recurring annual layer for each market you operate in, then revisit it each quarter. It is the cheapest revenue work in this business because the dates never move more than a day or two, and the demand pattern repeats.
Pricing the date is only half of it. Set the stay rule too.
A premium rate on a long weekend with no minimum-stay logic is a half-built move. If a guest can book just the Saturday of a three-day weekend, you have orphaned the Friday and the Sunday, two of the most bookable nights of the year, and you will scramble to fill them at a discount or eat the gap. The right structure forces the full block. On a true long weekend that usually means a three-night minimum across the holiday dates, set when you set the premium, not after the calendar starts fragmenting.
Then think about the shoulder days, the Thursday before and the Monday or Tuesday after. Those are your gap-fill consideration. If the holiday creates a natural four-night bridge, price and open it as a bridge. If it does not, decide deliberately whether to hold a tight minimum and risk a one-night gap, or relax the rule a few weeks out to catch a longer stay that spans the shoulder. That decision is a judgment call on real-time pace, and it is exactly the kind of thing a set-it-and-forget-it rate never makes. Someone has to be watching the block.
"A premium rate with no minimum-stay rule orphans the best nights of the year. Price the date and force the block in the same move."
What this looks like when you do it right
Geneva Lakes Vacations, a 116-unit Wisconsin lake operator on our book, is the clearest example I have. Memorial Day weekend is the first big spike of their season. We priced it as a recurring premium block well ahead of the demand window, with the minimum-stay logic to force the full long weekend rather than let it fragment into single nights. The lift did not come from charging more per night. It came from filling units that sat empty the same weekend the year before, because the pricing anticipated the demand instead of reacting to it.
That is the pattern across the whole book. Geneva Lakes ran same-store Adj. RevPAR from $88 to $128 year over year, a 46% lift on the KeyData same-store methodology. Across Pacer's managed book, first-year clients (12-24 months on Pacer) ran +21% pooled same-store Adj. RevPAR on the same methodology, while the broader market sat flat to slightly down. A meaningful slice of that comes from getting the predictable spikes right before the calendar fills.
How far ahead should I actually start, and what if I am late?
For the major summer long weekends, Memorial Day, the Fourth, Labor Day, three to four months out is the right altitude, because the premium group bookings commit early and you want your rate set before they do. For the smaller ones, six to ten weeks is enough. If you are reading this and a long weekend is already six weeks out and underpriced, it is not too late, but the move changes. You are no longer setting the opening rate. You are repricing the unsold inventory upward and tightening the minimum stay on what is left, which still captures real money even after the early block has booked. Late is better than never. On time is better than late.
The free audit
If you are running 20 or more units and you suspect your long weekends are getting priced like ordinary ones, that is a checkable claim. We run a free revenue audit that benchmarks your ADR and RevPAR against your actual comp set and shows you exactly where the recurring spikes are leaking, no commitment. Worst case, you walk away with your annual holiday calendar built and a sharper read on where you stand. We also back the engagement with the Pacer Promise: cancel in the first six months and we return 50% of fees paid.
Adapted from Pacer's editorial archive, May 2026.