How to use the Travel Budget Planner.
A travel budget should state the currency, trip length and whether costs are per person or shared. Keep estimates distinct from booked prices and include a contingency explicitly.
Make the workflow fit your task.
Define the number of travelers, nights and spending days, then separate shared and per-person costs. Label booked prices and estimates, use a stated exchange rate if needed, and add contingency explicitly. Keep missing categories outside the confirmed subtotal.
- What you provide
- User-supplied prices, itinerary and spending limits.
- What you get
- Cost model and contingency without invented live prices.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Two people travel for three nights. Shared hotel USD 90/night; food USD 25/person/day for four days.
Completed example
Hotel: USD 270. Food: USD 200. Known planning subtotal: USD 470. Add transport, activities, fees and a separately stated contingency before calling it the trip total.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Why can a three-night trip require four days of food spending?
Arrival and departure days can both involve meals. State the days counted for each cost category.
Why does the budget appear cheaper than the booking checkout total?
Taxes, fees, baggage or transfers may be absent from headline prices. Reconcile against final quotes before treating the budget as complete.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑