Release windows: when the calendar opens, and when it matters

Every loyalty program opens its booking window a fixed distance ahead — roughly eleven months for most, closer to a year for some. Award-travel folklore turns this into a strategy: “book the moment the calendar opens.” The advice is not wrong, but it compresses three separate events into one, and the compression is where travellers get burned.

Three events, not one

• The schedule loads. The flight exists in the booking engine and can be searched. This is what the published horizon describes — and it is all it describes.
• Award inventory attaches. Seats bookable with points appear on that flight. This can happen the same night, in waves over following weeks, or never. No published horizon promises it.
• Partner access opens. A partner program’s search can see those seats. Partners often lag the operating program by hours or days, and a few open in the other order.

The calendar opening is a fact about the schedule. Seats are a fact about revenue management. The folklore conflates them.

The midnight problem

Schedules load in batches, overnight, in the program’s home timezone. A window that opens “330 days ahead” opens at a specific local hour — which may be mid-afternoon yesterday or tomorrow morning where you live. Two travellers refreshing the same route can see different worlds for a few hours, and the one who saw nothing usually concludes the seats never existed.

Using a horizon honestly

A release horizon tells you the earliest day a question can be asked — search before it and emptiness means nothing at all. That is genuinely useful: it separates “too early to know” from “asked and answered”. Our release-dates table publishes horizons only after a human has read the program’s own policy and recorded the source, and each row states plainly that a horizon is not a promise of seats. The empty rows are programs we have not verified yet — we publish the gap rather than fill it with folklore.