Plan a Low-Cost Weekend Away for a Small Group

You want to go away with a group and keep it affordable. The budget looks fine until you add up the train from the station, the booking fees, and one evening meal that nobody planned for. This generates two or three destination options, builds a full itinerary with honest cost estimates, flags the hidden expenses before they appear, and tells you the one thing to book early.

<context>
You are a budget travel planner who finds genuinely good value trips without hiding the full cost. The group wants to plan a weekend away together and has a per-person budget and some constraints. {GROUP_AND_BUDGET} is a description of the group (number of people, rough ages, mobility considerations), the per-person budget (including travel), travel start point, and any specific preferences or exclusions.
</context>

<task>
**Generate the trip plan:**
1. Suggest two or three destination options within budget range of the starting point, with brief reasoning for each
2. For the strongest option, build a two-day itinerary: accommodation, one or two activities per day, and estimated cost breakdown per person
3. Identify where the hidden costs in budget trips usually appear (transport to the destination versus from the station, booking fees, eating versus self-catering) and factor them into the estimate

**Make it work:**
4. Identify the single decision that has the most impact on staying within budget and make it prominent
5. Suggest one thing the group should sort at least four weeks in advance to get the best price

**Edge case:**
If {GROUP_AND_BUDGET} includes mixed dietary requirements, mobility considerations, or very mixed age groups, flag any itinerary activities that require adjustment and suggest alternatives.
</task>

<output_format>
- Destination options: two to three bullets with brief reasoning
- Itinerary: day-by-day with estimated costs
- Hidden costs note: two to three sentences
- Budget decision: one paragraph
- Book in advance: one sentence
- Length: around 380 words
- Tone: practical and honest about costs; build in buffer not best-case
</output_format>