What we mean, and what we don't
A few terms come up every time we plan a park day, and they get read in different ways. Here is how we use them on this page, so nobody books a trip expecting something we never promised.
A day plan is a schedule, not a ticket
When we say we map your park days, we mean ride blocks, meal windows, transfer times and rest gaps written into one timeline. Park entry, shuttle seats and add-on attractions are booked separately, and the coordinator confirms what is actually reserved before anyone pays.
Height rules belong to the park
Our ride height guide reflects published limits at the time we check, but operators adjust them without notice and staff measure at the gate. A child who clears the mark at home can still be turned away on the day, so we build a second option into every block.
Queue estimates are ranges
Peak-season wait times we quote come from past school holiday patterns and park apps, not live tracking. Weather, ride breakdowns and local event days move them by an hour or more, which is why the schedule leaves slack instead of stacking rides back to back.
Wet-weather backups are alternatives
An indoor attraction or city add-on on your plan is a swap we can trigger, not a guaranteed reservation. Some parks run shortened hours in heavy rain and some ticket types cannot be moved to another date, so we read the operator's policy with you before purchase.
One coordinator, one group
Group bookings get a single point of contact who checks dates, opening hours and ticket bundles. That person coordinates the plan; they do not escort you inside the park, and they cannot override a ride operator, a transfer driver or a park's own safety decisions.
Mixed ages stay in the plan
Splitting a group is normal, not a failure. Grandparents on a show-and-garden route, teenagers on coasters and younger kids in water play can share the same day and the same meeting points. We plan those splits openly rather than pretending everyone rides together.