Preparing a multi-city travel proposal
A route-first method for agents to prepare a multi-city travel proposal, with a worked example, build sheet, QA rubric, and copyable Nowah prompt.

Build your multi-city proposal route-first in Nowah: establish the hotel-night allocation and transfer days, then develop the editable itinerary. Use the planning and booking features to investigate flights and hotel options against that connected route.
Your outcome is a proposal the client can skim and instantly answer:
- Where do we sleep each night?
- How do we move between places, and how “hard” are those days?
- What do you need from us next to firm it up?
The route-first workflow (8 steps)
Build the connected route in Nowah before selecting hotels or polishing the proposal. The multi-city itinerary guide helps challenge unnecessary stops early.
- Confirm anchors
- Start/end city, target dates (or date windows), trip length, and any fixed commitments.
- Define what each stop is “for”
- Give each city a job (food hub, nature reset, culture immersion, finale). This prevents repetition and helps justify night allocations.
- Choose a direction that minimises backtracking
- Linear routing often reduces fatigue and makes ground transport easier to explain.
- Set move-day rules (in writing)
- Examples: door-to-door target, max connections, no very early starts, “no more than one move day every 3–4 days.”
- Draft the connected itinerary in Nowah
- Request explicit transfer blocks and free time. This makes pacing visible early.
- Run an agent feasibility pass
- Check that the itinerary follows the move-day rules and doesn’t rely on “perfect” timing.
- Assemble the client-facing proposal in your normal tools
- You’ll use your agency’s approved document workflow for formatting, pricing, and client delivery.
- Send with a clear decision list
- Keep next steps limited and specific so the client can respond in one message.
The minimum proposal structure that works for multi-city
Keep the pack lean. A practical structure is:
- Trip Snapshot (skim page): dates (or windows), party, route, total nights, and the 4–6 priorities.
- Master Timeline: day-by-day overnights, with move days highlighted.
- Transfers & Logistics Summary: each segment’s likely mode, effort level, and assumptions.
- Day-by-day Itinerary: morning/afternoon/evening blocks with breathing room.
- Decisions Needed to Proceed: the few items you must confirm to progress.
Worked example (hypothetical): 14 days / 4 cities with family pacing
Fictional brief (anonymised):
Review the fictional family's Nowah transfer days alongside their rest needs. The family rest-break guide helps explain the proposed distribution of nights.
- Travellers: 2 adults + 2 children (ages 8 and 12)
- Duration: 14 local destination days / 13 hotel nights; international travel may make the total time away longer
- Route constraint: arrive City 1, depart City 4
- Style: mid-range, family-friendly, private bathroom
- Priorities: food-focused days, hands-on culture, one “hot-springs-style” evening, two “big fun days” (one early in the trip, one late)
- Pace rules: no consecutive long travel days; include free afternoons
1) Route spine + night allocation (with “jobs”)
Illustrative sequence: City 1 → City 2 → City 3 → City 4. These placeholders demonstrate night allocation, not a verified geographical route.
Night allocation with purpose:
- City 1: 4 nights — arrival cushion + first big fun day + food neighbourhood exploration
- City 2: 2 nights — reset stop; hot-springs-style experience; low-effort days
- City 3: 4 nights — culture hub; hands-on class; optional day trip
- City 4: 3 nights — finale city; second big fun day; shopping/last-meal flexibility
Move-day rules (recorded in the file):
- Target door-to-door travel: ≤ ~3 hours where possible
- Avoid very early departures
- Move days: no more than one anchor (often none)
- Protect one free afternoon per city
2) Master Timeline (client skim view)
Day | Overnight | Focus | Intercity move? | Pacing note |
|---|---|---|---|---|
1 | City 1 | Arrive + settle | No | No timed commitments |
2 | City 1 | Food focus + free afternoon | No | One anchor, then flexible |
3 | City 1 | Big fun day | No | Easy evening |
4 | City 1 | Culture + downtime | No | Buffer day |
5 | City 2 | Transfer + reset | Yes | Aim mid-afternoon arrival |
6 | City 2 | Light morning + possible evening experience | No | Afternoon explicitly free |
7 | City 3 | Transfer + orientation | Yes | Light evening |
8 | City 3 | Heritage day | No | Two zones max |
9 | City 3 | Hands-on class + free time | No | Margin around class |
10 | City 3 | Optional day trip | No | Option A/B |
11 | City 4 | Transfer; food exploration only if practical | Yes | Duration and effort to verify |
12 | City 4 | Big fun day | No | Protect next morning |
13 | City 4 | Flexible finale day | No | Packing-friendly |
14 | — | Depart | — | Confirm departure transfer |
The allocation totals thirteen hotel nights: 4 + 2 + 4 + 3. Arrival on Day 1 and departure on Day 14 are also travel days, even though the intercity-move column distinguishes only moves between bases. Their transport and rest buffers still need protection.
Transfers & logistics summary (the section that prevents surprise fatigue)
For a real route, research each actual segment before describing its mode or duration. Generic City 1–4 placeholders cannot establish that rail exists, that a journey is short or that reserved seats are offered.
Use Nowah's map and timeline to inspect the transfer sequence, then verify actual journeys. Follow the realistic transfer-time method before presenting the logistics summary.
Segment | Investigation needed | Proposal field to complete |
|---|---|---|
First to second base | Actual connections, access and luggage handling | Verified mode, approximate door-to-door range and buffers |
Second to third base | Timetable, transfer tasks and arrival access | Practical departure/arrival window and remaining free time |
Third to fourth base | Whole journey burden, not map distance alone | Effort explanation and any effect on finale activities |
Final base to departure point | Access, operating hours and required check-in margin | Departure-day transport plan and contingency allowance |
The three-hour target is a preference to test, not an established duration. If a real segment exceeds it, show the full implication and ask whether the client prefers a different route, fewer bases or a longer travel day.
Using Nowah to draft the connected itinerary (copy/paste prompt)
Nowah prompt (fictional brief; anonymised):
Create a connected 14-day / 13-night multi-city family itinerary for 2 adults + 2 children (ages 8 and 12). For the conceptual exercise use City 1 → City 2 → City 3 → City 4 with 4/2/4/3 nights. Ask me for actual cities and dates before making transport claims.
Requirements:
- Include explicit transfer blocks on move days and note the information needed to establish an actual mode, duration and appropriate buffers.
- Keep door-to-door travel under ~3 hours where possible and avoid very early departures.
- Include one hot-springs-style evening experience in City 2.
- Include two “big fun days”: one in City 1 and one in City 4 (describe the type of day without naming specific venues).
- Each city must include at least one protected free afternoon.
- Suggest mid-range, family-friendly hotel types and flag occupant allocation, age rules and actual bedding for four people, with adjacency treated as a request unless explicitly confirmed, without promising availability, rates, or cancellation outcomes.
Output:
- Day-by-day with morning/afternoon/evening blocks
- A short rationale for the night allocation and pacing
The agent review pass (what you must verify before reuse)
Use this quick rubric:
- Count and sequence: 14 days / 13 nights; correct city order.
- Move-day discipline: transfer days are light; no stacked commitments.
- Free afternoons: genuinely open blocks appear in each city.
- Energy realism: meal breaks, early nights after big days, and “do nothing” space.
- Language control: remove certainty (“will be available/open/on time”); keep conditional phrasing.
- Accommodation logic: hotel notes are framed as options to verify for occupancy and bedding.
Once the itinerary is stable, Nowah can also support your shopping steps (multi-city flight search; hotel search/booking; eSIM purchase) as appropriate (capabilities: Nowah features). Final booking outcomes remain governed by supplier availability and terms, and you obtain client approval before payment.
Internal Multi-City Proposal Build Sheet (usable artifact)
This is an internal worksheet you can drop into your file notes or CRM. It’s deliberately compact so it stays current.
Field | What you write | Example (from the worked trip) |
|---|---|---|
Anchors | Start/end, dates/windows, fixed events | Arrive City 1 / depart City 4; 14 days |
Route spine | City order + why | 1→2→3→4; actual geography to check |
Nights by stop | Nights + “job” | 4/2/4/3 with reset + finale logic |
Move-day rules | Max time/changes/early starts | Target ≤3h; no very early departures |
Pace protection | Free time policy | 1 free afternoon per city |
Accommodation rules | Budget band + room needs | Mid-range; allocation and actual room category to verify |
Transfer assumptions | Buffers + luggage approach | Station buffer; reserved seats preferred |
Must-haves | Top priorities | Food days; hands-on culture; 2 big fun days |
Flex items | Nice-to-haves | Optional day trip from City 3 |
Client decisions | What you need next | Confirm whether to prioritise fewer changes vs later arrivals |
How to use it with Nowah: paste the key constraints (move-day rules, must-haves, nights by stop) into your next prompt so revisions don’t drift.
Managing changes without rewriting the whole proposal
When clients request changes, keep options bounded and route-aware:
- “Add one more stop.” Offer only:
- Option A: extend the trip length, keeping pacing rules.
- Option B: reallocate nights, explicitly naming what becomes shorter.
- “Slow it down.” Establish whether the problem is activity load or frequent relocation:
- Ask Nowah for a lower-activity version or a fewer-base alternative, according to the client’s priority.
- “Fewer hotel changes.” Investigate whether removing a stop improves the route:
- Ask Nowah for redistributed nights. Offer a day trip only if actual travel time, access and client preferences support it.
This preserves client trust: you’re showing the trade-offs rather than silently “making it work.”
Show cost scope and approval requirements
State whether the comparison includes transport between every base, full hotel quantities and relevant mandatory charges. A route can be well paced while its displayed total omits important travel costs. Then explain:
- Availability is confirmed only at booking time and depends on suppliers.
- Changes and refunds follow supplier terms and conditions.
- You will obtain client approval before payment.
Keep it short so the proposal stays centred on the multi-city plan and decisions.
Create your next multi-city proposal draft in Nowah: https://app.nowah.xyz. For current membership terms, refer to /pricing.




