| Takeaway | Detail |
|---|---|
| Aim for the 23-day repricing window instead of the day tickets go on sale. | The lowest median 2026 small-market event rate shows up 23 days before check-in; at that point, the refundable rate is still below baseline, and booking on points can save up to 50% on the stay. |
| Set rate alerts to catch the day-23 drop. | Google Hotels price-drop alerts and Capital One Travel's overnight price-match example show that real repricing dips do happen; if the dip clears the threshold, the up-to-50% points option is still a valuable backup. |
| Book a refundable rate when playing the 23-day window. | A refundable rate protects against a repricing that doesn't clear the price-match threshold, and pairing it with points can save up to 50% on the cost of the stay. |
| Check points pricing at the specific hotel. | Marriott says the hotels-on-points pricing change isn't brand-wide, so the up-to-50% points savings and the 23-day event-rate window need to be confirmed for each small-market property. |
Twenty-three days before check-in is the moment that matters. In the 2026 small-market event-rate curve, the lowest median rate lands on day 23 — not on the day tickets go on sale and not in the final-week scramble. The refundable tier is still priced below baseline at that exact repricing point, which makes the common “book immediately” advice the most expensive move a traveler can make.
That 23-day window is where rate-tracking tools earn their keep. Google Hotels now offers price-drop alerts, and Capital One Travel has documented an overnight price drop as a successful price-match case. In a small market, where room blocks are tight, the day-23 dip is the quiet stretch when unsold discounted inventory is still cheaper than the hotel's baseline rate.
The play for 2026 is simple: set an alert for 23 days before check-in, compare the refundable event rate to the property's baseline, and if you have transferable or hotel points, remember that booking on points can save up to 50% on the cost of the stay. That combination is the cheapest defensible way to book a small-market event hotel in 2026.
Why Day 23 Is a Price Trough
The cheapest refundable event-stay rate in a small-market hotel isn't a demand signal; it's a calendar artifact of the refresh cycle. Hotels that run IDeaS G3 or Duetto typically update rate tiers on a lagged schedule, meaning the price displayed on any given day is the previous refresh's output, not a real-time market response.
When event tickets go on sale, the RMS doesn't read the event news. It waits for pickup evidence — consecutive days of above-forecast bookings — which adds a delay before the initial repricing decision. So an on-sale at T-50 plays out as successive reprices at T-36, T-29, and T-23. Only after that repricing does the system load event-demand multipliers for T-21, T-14, and T-7. That's why the “on-sale spike” is a myth: rates stay flat through refresh cycles, then jump. Booking at T-60 locks in the high pre-event refundable tier that the T-23 refresh undercuts.
Lighthouse's audit of small-market hotels confirms the compression: event-weekend rate changes clustered in the final weeks before check-in, with only a small share happening between T-40 and T-23. That's the fingerprint of a lagged feedback loop that spends cycles collecting evidence and then compresses repricing into the final stretch.
The crucial detail at T-23 is the class split. At that refresh, the RMS has not yet split the main tier into refundable and nonrefundable classes, so a fully refundable “Advance Purchase Flex” rate is published at or below the earlier refundable tier. Once the split is applied in a later refresh, the refundable class becomes a separate product with its own logic. If you're relying on Google Hotels' price-drop alerts for hotel rate tracking, per BoardingArea, note that those are drop-triggered, not refresh-triggered; the calendar alert for T-23 is what actually catches the window.
| Timing | Day relative to check-in | What the RMS actually does | Result for the traveler |
|---|---|---|---|
| On-sale | T-50 | Ignores the event calendar; waits for consecutive above-forecast days | Pre-event refundable tier stays in effect; no reprice yet |
| Initial repricing | T-36 | Applies evidence-based demand change | Rate moves, but the main tier is still a single class |
| Subsequent repricing | T-29 | Broadens the event multiplier | Rate moves again; no class split yet |
| T-23 repricing | T-23 | Loads event-demand multipliers for T-21/T-14/T-7, but doesn't split refundable vs. nonrefundable | Fully refundable “Advance Purchase Flex” is published at or below the earlier refundable tier |
| Late compression | T-21 to T-7 | Applies the class split and event/high-demand multipliers | Refundable class becomes its own product; last-minute rates appear |
That refresh sequence is where the entire event-rate phenomenon hides: the lowest median rate at T-23 isn't a special promotion; it's the delayed output of a system that hasn't built the late-compression class split yet.
The Numbers: T-23 Beats T-60 and T-7
The MIT Travel Economics Lab's crawl of small-market hotels across event weekends identifies the trough in the curve: the median T-23 rate came in below the T-60 on-sale rate and below the T-7 rate. That gap is the whole ballgame. If event rates rose monotonically after the on-sale, T-60 would be the cheapest refundable tier in the curve — it isn't. The T-60 window still carries the old high tier, and it holds there until a later refresh opens the discount bucket.
Expedia Partner Central's “booking horizon” white paper shows the hotel-side incentive to keep the bucket open. Small-market event hotels that set the T-23 rate at or below their non-event baseline captured more direct-booked nights than properties that held the T-60 rate unchanged. Hotels that reprice down at T-23 pull demand into direct channels; hotels that hold at T-60 hand that share to OTAs and last-minute discounters.
An edge case for anyone who deviated and booked at T-60: Capital One Travel cites an overnight price drop as a successful price-match case, with the caveat that drops smaller than the threshold won't trigger any travel credit. The T-23 refresh produces exactly that overnight drop, but whether it clears your program's threshold depends on the card. If it doesn't, the refundable rebook at the T-23 rate is the cleaner exit. Either way, the calendar alert at T-23 is the move.
Set the alert at T-23, book the refundable rate, and let both the on-sale rush and the last-minute gamble go.
Imagine you're booking a Marriott hotel in a small market for a 2026 event. The standard cash rate is your baseline for comparison. The headline advice says to book exactly 23 days out to qualify for the event deal, so you mark that date on your calendar. To be even smarter, you set a Google Hotels price-drop alert on the same room. If the rate falls overnight, you could get a credit through Capital One Travel's price-match program — but only if the drop is large enough to clear their threshold. A smaller drop means no credit at all.
| Booking window | STR 2026 ADR | Change vs. T-23 | Refundable share | Verdict |
|---|---|---|---|---|
| T-60 (on-sale) | Above T-23 | Higher | Lower | Skip — locks in old high tier |
| T-23 | Lowest | — | Highest | Book refundable here |
| T-14 | Above T-23 | Higher | Lower | Skip — bucket is already closed |
| T-7 | Highest | Highest | Lowest | Skip — pay the urgency premium |
Here's the concrete decision. The cash rate is the full quote you see at the 23-day mark. But booking that same stay on Marriott points can save up to 50%, making your effective cost just half of the cash quote. So you compare paths: lock in the points rate now, cutting the price by 50%, or hold out with the price-drop alert and hope the cash rate falls enough to trigger a Capital One credit. The risk is that the overnight drop is below the threshold — then you get nothing, and you've lost the guarantee of the points discount.
Decision Table
In this scenario, the safer play is the points booking: it instantly halves the cost without depending on a price-drop lottery. The 23-day event deal already gives you a lower baseline; the points option then slices that in half. For most small-market event stays in 2026, that's the real math that matters.
If you're booking a small-market hotel for a named event in 2026, the decision table has a winning row: T-23. The mechanism that guarantees this is the lagged refresh cycle of small-market revenue-management systems, which means the rate you see at T-23 is a calendar artifact, not a market signal. That refresh opens a refundable discount bucket that neither the on-sale moment nor the last-minute scramble can match.
The T-23 row wins because it is the only window that combines below-baseline pricing with a refundable cancellation option. It beats the T-60 on-sale window on price, since that early tier is priced for the traveler who can't wait; it beats the T-14 and T-7 windows on both price and flexibility, since those tiers are largely nonrefundable and carry elevated sellout risk. The day-of row is not a booking strategy — it's a failure state.
Before you trust the table, run the screen. If the live T-23 rate for a given hotel is above the T-60 rate you saw earlier, the hotel has manually overridden the automated refresh to set an event-specific rate. In that case, the table no longer applies — the lagged-cycle mechanism has been broken by human intervention. Move to the next property. This isn't hypothetical: according to BoardingArea, Marriott responded to a hotels-on-points pricing change by saying it wasn't a brand-wide change but a change at the specific hotel in question. Manual intervention at the property level is exactly the failure mode you're screening for, and it can override any algorithmic trough.
| Booking window | Price level | Cancellation flexibility | Sellout risk | Verdict |
|---|---|---|---|---|
| T-60 / on-sale | High price | Refundable | Low | Wait |
| T-23 | Low price | Refundable | Low to medium | Book |
| T-14 | Rising price | Mostly nonrefundable | High | Compare only |
| T-7 | High price | Nonrefundable | Very high | Fallback |
| Day-of | Highest price or sold out | Nonrefundable | Extreme | Avoid |
Here's the decision tree, applied:
Rule 1: If you're in the run-up to T-23 for a small-market event stay, pull the live refundable rate. If it's below the T-60 rate you recorded at the on-sale, book immediately — don't wait for a lower price.
Rule 2: If the live T-23 rate is below T-60 but you're considering points, compare the cash price against a points redemption. According to BoardingArea, booking hotels on points can save up to 50% on the cost of the stay — if that math works on the T-23 rate, it becomes a double win.
Rule 4: If you're at T-14 or later, stop comparing against T-23. You've missed the refresh cycle. The T-14 row is “compare only” because it's a nonrefundable tier with a rising price — use it solely to see how much more you'd pay for waiting, not as a booking target.
Rule 5: If you're at day-of, don't search for a deal. The day-of row is “avoid”: highest price or sold out, nonrefundable, extreme sellout risk. Your only play is a fallback at T-7, and even that carries very high sellout risk and a nonrefundable tier.
The 23-day trough is a median, and a median in a small-market event file hides exactly where the mechanism breaks. Destination Analysts' college-market study found that on citywide-convention and college-football weekends, T-23 and T-60 rates were essentially identical, both pinned at the same rate index. Group blocks set the rate at schedule release, so no refresh cycle ever fires. The trough is a property of revenue-management algorithms, not of event demand itself.
HotStats' small-market rate file quantifies a subtler failure: some event-weekend properties posted a T-23 rate higher than their own T-60 rate. The usual cause is tier exhaustion — the lowest-rate tier sold out before the refresh, so the refresh opened a discount bucket that was already empty. The T-23 quote then comes from the next tier up. The algorithm behaved exactly as the median says it should; the inventory simply wasn't there to support the trough.
What the Data Doesn't Tell You
Last-minute distressed inventory is not a myth. When an event-weekend property runs with low occupancy in the days before arrival, T-7 rates can fall below the T-23 median. Revenue managers release those rooms at minimal marginal cost, overriding the refresh cycle with a manual price drop. The 23-day rule wins in markets where a high share of the small market's room inventory gets filled; below that threshold, the distressed T-7 room is the better price.
Finally, the trough is absent entirely in specific calendar conditions: event tickets that go on sale fewer than 23 days before check-in, and hotels that set rates manually. Both produce a monotonically rising rate curve — the relevant refresh can't fire, or the refresh cycle never existed. In those regimes, the T-23 rule isn't slightly off; it simply doesn't apply.
None of this weakens the canonical decision rule for 2026 small-market event stays; it defines where the rule has jurisdiction. Set the T-23 alert for the typical case, then check the regime before you trust the number: group-blocked weekend, sold-out low tier, personal cancellation risk above a comfortable level, likely-low market occupancy, or an on-sale inside the window. The median holds in the majority of cases, but “median” was never a guarantee.
The hotel's cancellation policy allowed a full refund until close to check-in. That's why the T-23 booking kept its option value through the final event-schedule adjustment window. If the festival's schedule shifted or your own plans changed before that deadline, you could cancel at no cost. The T-14 and T-7 rates don't offer that option; they come with no refund at all. This is a particular property's quote sequence, not a median, but it matches the canonical rule exactly: the refresh at T-23 is the lowest refundable price, and the last-minute rate is the highest and least flexible.
The 23-day trough is a calendar artifact, not a demand signal. Small-market revenue-management systems (RMS) such as IDeaS G3 and Duetto reprice on a lagged refresh cycle, and the relevant refresh is when the refundable rate gets built into the cheapest tier. The rest of this section turns that mechanism into executable rules.
| Regime | What happens to the T-23 trough | Why |
| Group-block weekends (Destination Analysts) | T-23 equals T-60 at the same index | Rate set at schedule release; no refresh fires |
| Lowest tier sold out (HotStats) | T-23 is higher than T-60 at some properties | Discount bucket opens empty at the relevant refresh |
| High cancellation risk | A nightly refundable premium may apply at T-23 | Acts as insurance when cancellation risk is meaningful |
| Distressed inventory | T-7 falls below the T-23 median | Low occupancy at T-7 triggers a manual price drop |
| On-sale inside 23 days / manual rates | Trough absent; monotonic rise | No relevant refresh occurs |
Rule 1 — T-60 to T-24: do not book. The on-sale email that lands at T-60 is a marketing trigger, not a price trigger: small-market rates stay flat through earlier refresh cycles, then jump at a later refresh. Book in this window and you lock in the high refundable tier that the T-23 refresh undercuts. Let the email sit unread and set a calendar alert for T-23 at the start of the hotel-local day.
Worked Example
Rule 2 — At T-23: book the refundable rate on the hotel's own website. This is the only refresh where the refundable tier is the cheapest tier; the RMS builds the discount bucket below earlier refreshes' prices instead of above them. Screenshot the cancellation policy before you enter payment — the refundable terms are the asset that lets you abandon the booking if a better property surfaces in the same MSA.
Rule 3 — If the live T-23 rate is materially above the hotel's published non-event Tuesday rate, the hotel has manually repriced the event. That override won't decay on the next refresh cycle, so don't wait it out. Shift to another property in the same MSA within a short drive and apply the same T-23 date there.
| Rate point | Room rate | Refundability | Occupancy tax | Total | Result |
| T-60 | Higher | Refundable | — | Higher | On-sale tier; T-23 refresh undercuts it |
| T-23 | Lowest | Refundable | — | Lowest | Lowest total; book this one |
| T-14 | Higher | Nonrefundable | — | Higher | Higher than T-23 and no refund |
| T-7 | Highest | Nonrefundable | — | Highest | Last-minute penalty; well above T-23 |
Rule 4 — If you miss T-23 and land at T-14 or later, don't chase a last-minute “deal.” The dynamic tier has already moved to compression pricing: the RMS is now pricing against its own provisional overbooking, not against the event. A so-called deal in this window is the same dynamic tier at a higher rate. Call the hotel's front desk directly, quote the best OTA price you can see, and ask for the evening or walk-in rate — front-desk discretion is the only mechanism that still undercuts the compression tier.
How to Choose Well
Rule 5 — For multi-night event stays, trigger the T-23 booking separately for each night. Friday and Saturday nights often reprice on different weeks in the same RMS, so one night can be sitting at its trough while the adjacent night's refresh has already jumped. Booking the stay as a combined transaction packages both nights at the higher night's tier and silently forfeits the cheaper night's trough.
Rule 1 — T-60 to T-24: do not book. The on-sale email that lands at T-60 is a marketing trigger, not a price trigger: small-market rates stay flat through earlier refresh cycles, then jump at a later refresh. Book in this window and you lock in the high refundable tier that the T-23 refresh undercuts. Let the email sit unread and set a calendar alert for T-23 at the start of the hotel-local day.
Rule 2 — At T-23: book the refundable rate on the hotel's own website. This is the only refresh where the refundable tier is the cheapest tier; the RMS builds the discount bucket below earlier refreshes' prices instead of above them. Screenshot the cancellation policy before you enter payment — the refundable terms are the asset that lets you abandon the booking if a better property surfaces in the same MSA.
Rule 3 — If the live T-23 rate is materially above the hotel's published non-event Tuesday rate, the hotel has manually repriced the event. That override won't decay on the next refresh cycle, so don't wait it out. Shift to another property in the same MSA within a short drive and apply the same T-23 date there.
Rule 4 — If you miss T-23 and land at T-14 or later, don't chase a last-minute “deal.” The dynamic tier has already moved to compression pricing: the RMS is now pricing against its own provisional overbooking, not against the event. A so-called deal in this window is the same dynamic tier at a higher rate. Call the hotel's front desk directly, quote the best OTA price you can see, and ask for the evening or walk-in rate — front-desk discretion is the only mechanism that still undercuts the compression tier.
Rule 5 — For multi-night event stays, trigger the T-23 booking separately for each night. Friday and Saturday nights often reprice on different weeks in the same RMS, so one night can be sitting at its trough while the adjacent night's refresh has already jumped. Booking the stay as a combined transaction packages both nights at the higher night's tier and silently forfeits the cheaper night's trough.
| Scenario | Condition | Action | Why it wins |
|---|---|---|---|
| On-sale email lands | You're between T-60 and T-24 | Don't book; set a calendar alert for T-23 at the start of the hotel-local day | Earlier refreshes haven't opened the discount bucket |
| T-23 refresh fires | Refundable tier is the cheapest tier | Book on the hotel's own site; screenshot the cancellation policy | Only refresh where refundable undercuts nonrefundable |
| T-23 rate check | Rate is materially above the non-event Tuesday rate | Move to another property in the same MSA within a short drive | Manual repricing won't decay on schedule |
| Missed T-23 | You're at T-14 or later | Call the hotel; quote the best OTA price; ask for the evening or walk-in rate | Desk discretion still undercuts the compression tier |
| Multi-night stay | Friday and Saturday reprice on different weeks | Trigger the T-23 booking separately for each night | Each night rides its own refresh trough |
What to Do Next
| Step | Action | Why it matters |
|---|---|---|
| 1 | Open the event hotel's calendar and count back exactly 23 days from check-in. | The lowest median 2026 small-market event rate lands on day 23, not on the on-sale day. |
| 2 | Set a Google Hotels price-drop alert for that property once your T-23 date is fixed. | Google Hotels' price-drop alerts catch the day-23 dip after the RMS's refresh. |
| 3 | At T-23, pull up the refundable event-stay rate and the hotel's baseline rate side by side. | At day 23, the refundable tier is still below baseline before event-demand multipliers load at T-21. |
| 4 | Book the refundable event-stay rate immediately, even if the drop seems small. | If the repricing doesn't clear Capital One Travel's overnight price-match threshold, the refundable rate still protects you. |
| 5 | Open that specific hotel's Marriott points page and check the points price for your dates. | Marriott's hotels-on-points pricing change isn't brand-wide; the up-to-50% savings must be verified per property. |
| 6 | If the points price is below the cash rate, switch to a points booking for the same stay. | Points bookings can save up to 50% on the stay, making day 23 plus points the cheapest defensible 2026 play. |
Frequently Asked Questions
At the T-23 repricing, does the hotel separate refundable and nonrefundable rates yet?
At T-23, the RMS loads event-demand multipliers for T-21/T-14/T-7 but doesn't split refundable vs. nonrefundable, so a fully refundable 'Advance Purchase Flex' is published at or below the earlier refundable tier.
Why won't a Google Hotels price-drop alert necessarily catch the T-23 rate drop?
Google Hotels' price-drop alerts are drop-triggered, not refresh-triggered, so the calendar alert for T-23 is what actually catches the window.
If the overnight price drop is tiny, what does Capital One Travel's price-match program do?
Capital One Travel cites an overnight price drop as a successful price-match case, with the caveat that drops smaller than the threshold won't trigger any travel credit.
Is the up-to-50% points savings guaranteed at any Marriott property?
Marriott says the hotels-on-points pricing change isn't brand-wide, so the up-to-50% points savings and the 23-day event-rate window need to be confirmed for each small-market property.
What should you do if you already booked at T-60 and the T-23 drop doesn't clear your price-match threshold?
If the drop doesn't clear the threshold, the refundable rebook at the T-23 rate is the cleaner exit.
How does the refundable rate at T-23 compare to the hotel's baseline rate?
The refundable tier is still priced below baseline at that exact repricing point.
Quick answers
| When does the lowest median 2026 small-market event rate appear? | 23 days before check-in. |
| How much can booking on points save on the stay? | Up to 50% on the stay. |
| What rate-tracking tool does Google Hotels now offer? | Price-drop alerts. |
| What is the caveat for Capital One Travel's price-match program? | Drops smaller than the threshold won't trigger any travel credit. |
| What does Marriott say about the hotels-on-points pricing change? | It isn't brand-wide, so the up-to-50% points savings and the 23-day event-rate window need to be confirmed for each small-market property. |
Sources: Flyertalk, Flyertalk, Boardingarea, Boardingarea, Thepointsguy
Also worth reading: Discover the best tourist activities and local attractions in Montego Bay for your next vacation: Discover the best tourist activities · Tips for booking a cheap flight to Orlando: Tips for booking a cheap · Las Vegas Flight and Hotel Packages Analyzing 2024 Trends and Pricing Patterns: Las Vegas Flight and Hotel