Split Stays
This post is based on information provided by poster @hiroMYhero.
The many possible combinations of split stays can make planning for the different FP booking windows difficult. This post lists the most common scenarios and summarizes how the FP booking windows should work for each. Real-world experiences and posts that would improve this information are welcome.
If the reader is not interested in getting FPs for any of the high-demand attractions mentioned here in Availability, then the information in this post can be ignored. The simplest FP booking strategy in this case is to wait until all trip dates are within the booking window and schedule all FPs at the same time.
Please note that
onsite package tickets are not considered valid by the MDX system until the package check-in date. (This behavior is different than separately-purchased tickets, which are considered valid as soon as they are linked.) The 60-day FP booking window will not appear in MDX until 60 days before the check-in date.
Before this point, it is normal for various members and/or their tickets to not appear in the MDX account. The entire traveling party and their tickets will appear at the 60-day mark in most cases. The FP booking window for package tickets will range from the package's check-in date to the check-out date.
Two Onsite Stays (Back-to-Back)
- Package Stay followed by Room-Only (RO) Stay. The 60-day FP booking window will open at 60 days before the check-in date of the first (package) stay and will extend until the checkout date of the second (RO) stay.
- RO Stay followed by Package Stay. The 60-day FP booking window will open at 60 days before the check-in date of the first (RO) stay and will extend until the checkout date of the second (package) stay. FPs can be booked for the package stay only; FPs cannot be booked for the room-only stay until tickets are activated at Guest Relations.
- Two RO Stays. The 60-day FP booking window will open at 60 days before the check-in date of the first RO stay and will extend until the checkout date of the second stay (and potentially beyond). This assumes valid tickets are linked to the MDX account.
Onsite Stay followed by Offsite Stay
- Onsite Package Stay followed by Offsite Stay. The 60-day FP booking window will open at 60 days before the check-in date of the onsite package stay and will extend until the checkout date of the onsite package stay. Additionally, the booking window will roll forward (a “rolling 60”) each day beyond the onsite package checkout date until the guest checks out of the onsite resort.
- Onsite RO Stay followed by Offsite Stay. The 60-day FP booking window will open at 60 days before the check-in date of the onsite RO stay and will extend until the checkout date of the onsite RO stay. Additionally, the booking window will roll forward (a “rolling 60”) each day beyond the onsite RO checkout date until the guest checks out of the onsite resort. This assumes valid tickets are linked to the MDX account.
Offsite Stay followed by Onsite Stay
- Offsite Stay followed by Onsite Package Stay. The 60-day FP booking window will open at 60 days before the check-in date of the onsite package stay and will extend until the checkout date of the onsite package stay. This booking window will not include the dates of the offsite stay because the package tickets are not considered valid until check-in date of the onsite package stay. The ticket portion of the package can be activated up to 10 days prior of the onsite package check-in date (so that the package tickets can be used during the offsite stay).
- Offsite Stay followed by Onsite RO Stay. The 60-day FP booking window will open at 60 days before the check-in date of the onsite RO stay and will extend until the checkout date of the onsite RO stay. Since the offsite stay precedes the onsite RO stay, this window already includes booking for the offsite stay. Additionally, the booking window will roll forward (a “rolling 60”) each day beyond the onsite RO checkout date until the guest checks out of the onsite resort. All of this assumes valid tickets are linked to the MDX account.
