Destination budget planners

A destination-first budget planner begins with the place you want to visit rather than the airport from which you depart. That makes it useful when you are still deciding where to stay, how long to spend there and which parts of a trip need a current price. Origin-first hubs answer a different question: they help you start with a departure market. Both approaches use the same calculation model and the same source rules. There is no separate catalogue of invented destination prices behind this collection.

Choose a city from the published planners below. Each page explains how to organise a stay and provides date-specific inputs for the cost calculation. A duration in the title describes an itinerary framework, not a package. You still need to specify the hotel nights, actual arrival date, guest count and relevant destination location. Those details can change the scope of the calculation, so they should be kept consistent when comparing one option with another. The aim is a useful, inspectable plan rather than a headline number that hides its assumptions.

Start accommodation research with the property's exact address and your intended activities. Group nearby places together and check the practical journey from the airport or other arrival point. Compare the selected room configuration, occupancy limits and cancellation conditions alongside the amount. A facility mentioned on a property page is not automatically included in every rate. Mandatory charges, parking, breakfast and other extras need checking in the final supplier breakdown. A lower first number is not proof of a saving when the two offers contain different conditions.

The hotel component comes from a scheduled LiteAPI refresh for the actual dates and guest count, from the scheduled cache, without a per-call spending ceiling. A government lodging ceiling is never substituted for a real room offer. If a fresh cached result is unavailable, the hotel line is omitted. That choice keeps an incomplete subtotal honest: the missing component is unknown, not zero. It also prevents a cached city average from being presented as if a traveller could book a specific property for that amount.

Daily allowances are shown with their proper scope. GSA supplies US meals-and-incidental reimbursement bands through an exact ZIP and locality match. The State Department supplies foreign allowances for the named location and applicable season. Neither source measures everything a leisure visitor will spend. Conditional, unmatched or stale rates are withheld. Arrival-and-departure reductions are not silently applied, and the displayed explanation identifies how many full daily allowances are included. These distinctions matter when using a benchmark as context for a personal plan.

Transport has its own evidence requirements. US DOT Consumer Airfare Report observations are quarterly market averages, not live ticket quotes. They retain their original source period and use the latest available release regardless of age, clearly labelled as a historical average. Driving uses routed distance, current regional EIA fuel data and vehicle-specific fuel efficiency, with no default MPG. Fuel does not include parking, tolls, vehicle hire or insurance. A missing transport source does not trigger a fixed transfer price or a guessed per-mile amount to make the total appear complete.

Use the resulting information to refine a shortlist and identify the next actual price you need. Attractions, local transport, insurance and personal purchases remain outside the subtotal unless separately verified. Check admission arrangements and any timed reservations directly with the operator. Read the final conditions in the existing search and booking product before committing. The planners themselves do not create supplier quotes, reservations or payments, and they do not change that product's workflow.

This collection grows through the content registry. A new planner becomes visible only after its required fields, original text, independent dated sources, image rights and duplicate checks pass. Publication is automatic; no editorial approval queue is required. An administrator can still correct or unpublish a page. The sitemap reads the published registry at request time, so adding eligible content does not depend on a separate deploy-time list. A failed candidate stays draft with its reason visible to the administrator rather than becoming an empty indexed page.

Published destination planners