Creating an intake process for complex multi-stop trips
Intake complex multi-stop trips through anchors, a night ledger and dependency checks before detailed Nowah route research.

Create a multi-stop intake process around dependencies: fixed events, travel boundaries, nights, room needs and the decisions that affect several components at once. Agree the trip structure before researching every hotel or activity. Use Nowah to explore editable route concepts and map/timeline views, then verify the actual arrangements through the appropriate suppliers.
A complex itinerary needs more than a long destination list. The intake should reveal what can move, what must stay fixed and who can approve a change. That lets you investigate coherent alternatives instead of assembling individually attractive components that do not work together.
Start with anchors and home-airport boundaries
Ask what must happen on a particular date and where the traveller must be. Record the local date, required arrival time if relevant and any preparation or rest period needed around the event. A wedding day and the latest acceptable arrival before it are different inputs.
Use Nowah to sketch the route around fixed events before filling the remaining days. The multi-city itinerary guide helps challenge unnecessary moves.
Separately record the earliest departure from home and latest return home. Do not treat those as hotel check-in and check-out dates. Long journeys, overnight flights and time differences can affect the number of destination nights available.
Keep the source and status of each anchor visible. A tentative event date should not silently become the basis for non-changeable bookings. Ask who will confirm it and when the planning decision needs to be revisited.
Build a stop ledger before a detailed itinerary
Use a compact row for each proposed base:
Compare the stop ledger with the Nowah hotel-night allocation before researching individual offers. The multi-city proposal guide supports a connected presentation.
Stop | Purpose | Arrival/departure basis | Nights | Essential requirement | Flexibility |
|---|---|---|---|---|---|
[A] | [Reason to stay] | [Dates or open window] | [Count] | [Room/event/access] | [What may change] |
[B] | [Reason to stay] | [Dates or open window] | [Count] | [Room/event/access] | [What may change] |
The ledger is not a reservation record. It maps the concept so you can count nights, identify hotel changes and ask whether each stop earns its place. A destination mentioned in passing may be an optional excursion rather than another overnight base.
Ask how much moving the party is willing to do. Clarify packing, luggage handling, early starts and tolerance for transfer days. Do not infer that experienced travellers want a fast pace or that a shorter route always meets their interests.
Collect party and room requirements by segment
A traveller may join for only part of the trip. Record the roster for each segment, with relevant ages at the stay and the room allocation needed. Avoid one whole-trip headcount when the actual party changes.
Identify essential room features and distinguish an internal connecting door from nearby rooms. Record whether bedding alternatives are acceptable, then verify the actual room and rate later. A supplier's general property description does not establish a particular arrangement.
Use the approved process for identity, access or dietary information. For preliminary planning, functional requirements and traveller labels may be sufficient. Do not copy every participant's personal documents into an AI planning prompt to make the brief feel complete.
Use a dependency worksheet
This copyable artifact identifies changes that spread across the trip:
MULTI-STOP DEPENDENCY RECORD
Trip version / date:
Anchor or decision:
Confirmed, preferred or tentative:
Source / person responsible:
Stops and components affected:
What changes if this moves:
Required supplier checks:
Client decision needed:
Action owner / due time and zone:
Approval reference, when applicable:For example, moving an event may affect two hotel stays, a transfer and the international return. Adding a traveller can affect occupancy and transport capacity without changing the route. Write those consequences down before presenting a seemingly small adjustment.
In the Italy example, the Florence event is one dependency record. Its date is confirmed, but the latest acceptable arrival still needs an answer. The affected components include the Rome check-out, Florence check-in and intercity journey. If the clients must attend an additional gathering on 12 May, that may change the proposed transfer day.
The adviser assigns the client clarification before searching a final transport offer. That is more useful than adding a general “event” note to a day plan and hoping every affected component remains consistent. When the answer arrives, update the stop ledger and record which assumptions changed.
The worksheet belongs in your agency records. Nowah supports trip exploration; it does not automatically maintain the dependency log or obtain authority from everyone affected.
Worked hypothetical example: four Italy bases
This fictional party consists of two adults planning fourteen destination days and thirteen nights in Italy. They propose arriving on 8 May 2027 and departing on 21 May 2027. A family event in Florence on 14 May is a confirmed anchor for the exercise.
Inspect the fictional Italy route in Nowah for transfer dependencies between the four bases. The realistic transfer-time guide helps identify decisions needing clarification.
Their initial stop ledger is:
Base | Check-in | Check-out | Nights |
|---|---|---|---|
Rome | 8 May | 12 May | 4 |
Florence | 12 May | 16 May | 4 |
Venice | 16 May | 19 May | 3 |
Milan | 19 May | 21 May | 2 |
Total | 13 |
These dates describe a concept, not available accommodation or verified transport. The adviser still needs to check home-airport boundaries and actual flight arrangements. The event fits within the proposed Florence stay, but the clients must confirm when they need to arrive and whether any associated gatherings affect other days.
Identify the unresolved decisions in the example
The clients say they want unhurried mornings and dislike frequent packing. Four bases create three intercity moves, so the adviser asks which stops are essential and whether Milan is a desired stay or merely a possible departure point.
The answer changes the research plan. If Milan is optional, a three-base concept may be worth investigating. That does not prove a particular return flight exists or that the revised route will cost less. It creates an alternative whose transport and accommodation need checking.
The adviser also asks whether the event requires formal clothing or additional luggage. That may affect flight research and transfer arrangements. The intake is exposing linked tasks rather than assuming that a generic day plan covers every practical need.
Develop the route concepts in Nowah
Nowah's features include conversational research, editable day itineraries, map/timeline views and flight or hotel research. Use them to explore the stop ledger before committing to a detailed proposal.
Try this copyable fictional prompt:
Develop a fourteen-day, thirteen-night Italy concept for two adults, with destination arrival 8 May 2027 and departure 21 May 2027. Initial allocation: Rome four nights, Florence four, Venice three and Milan two. A family event in Florence on 14 May is fixed; ask what arrival buffer and related events matter. Compare this structure with a three-base alternative if Milan is optional. Priorities are unhurried mornings and fewer packing days. Mark transfers, allocate nights and list dependencies. Do not invent schedules, prices or confirmed rooms. Identify inputs needed for actual flight and hotel research.
Review the night totals, event placement and whether the alternative changes the international departure assumptions. Inspect the geography in Nowah, then verify actual journeys and supplier conditions. A map inspection helps identify questions; it does not establish a workable transfer by itself.
Agree a decision order
Research the decisions that constrain later work first. In this example, confirm the event arrangements and available travel boundaries before comparing final room options. Investigate the route and international flight structure before polishing daily activities around an uncertain last base.
Use a simple sequence: confirm anchor, compare route, select direction, investigate actual offers, review conditions, obtain booking approval. The sequence can change when a genuine deadline exists, but document the reason and affected decisions.
Do not manufacture urgency because the itinerary is complicated. Record exact supplier deadlines with their time zone where they actually exist. A tentative concept has no automatic hold or price protection.
Send a structured read-back
Summarise the agreed anchors, night allocation, party by segment, budget scope and open questions. Ask the client to confirm the planning direction and identify anything missing.
Distinguish permission to investigate a route from authority to book its components. A reply saying “the three-base idea looks good” does not approve an unknown fare, room or payable total. Obtain separate approval of the exact selected services and conditions before booking or payment.
If another decision-maker must agree, identify that person and the scope of their authority. Avoid treating one enthusiastic participant as the authorised representative for the whole party.
Keep the intake useful as the route changes
Update the stop ledger and dependency record when a date, participant or base changes. Check affected components rather than editing only the visible itinerary paragraph. Keep old versions distinguishable from the current brief.
Use Nowah to explore the revised trip structure and inspect its pacing. Maintain the source, status and approval record in your normal agency process. The intake remains useful when an adviser can see what is fixed, what is proposed and what needs evidence next.
Open Nowah with a fictional stop ledger and review the planning features before building the next multi-stop research brief.




