Building a travel proposal handoff for another agent
Hand a travel proposal to another adviser with a clear status brief, supplier evidence, deadlines and a Nowah planning outline.

Build the handoff as a two-part package: (1) the latest client-facing proposal you already prepared in your normal tools, and (2) a one-page internal brief that tells the next agent what is true right now—what’s been quoted or held, what’s been promised, what expires, and what must happen next. Use Nowah to reconstruct the trip’s planning context (routing ideas, pacing, day-by-day structure, and options to research), then translate that into your agency’s handoff template with real supplier references and deadlines.
Define the goal: continuity, not creativity
A handoff isn’t an improved proposal. It is a continuity document so another agent can continue service without unnecessarily re-asking the client for basics or accidentally contradicting you.
Use the current Nowah itinerary to explain the planning logic the receiving adviser needs. The cover-file preparation guide helps define the handoff scope.
The receiving agent should confirm access to the latest file and acknowledge ownership of urgent actions before the outgoing adviser leaves. An AI outline does not prove the status of a booking.
The handoff package: what you send internally
The handoff package can contain:
Keep the reviewed Nowah route alongside the current proposal and unresolved research questions. The revision log guide helps distinguish prior decisions from pending changes.
- Internal Handoff Brief (1–2 pages) — your structured summary (template below)
- Proposal artifact — the current client-facing proposal/quote you already prepared in your approved tools
- Evidence attachments — supplier emails/PDFs/screenshots, fare rules summaries, hotel policies, and any written confirmations (stored per your agency’s data-handling process)
Nowah fits before item (1): use it to regenerate a clean itinerary outline and research prompts when you’re under time pressure or returning to a trip after a gap.
The five sections every handoff needs (and what “done” looks like)
Use a consistent order, adapted to your agency’s service and privacy requirements.
1) Client snapshot (service-critical only)
Include:
- Primary contact + backup contact (names, email/phone, time zone)
- Traveller count + traveller types (adults/children; note ages only if relevant)
- Names as they must appear on tickets (or “awaiting required name details”)
- Special needs that affect bookings (accessibility, dietary/allergy, bedding)
- Communication preferences (channel, level of detail, decision pace)
2) Trip overview (north star)
Include:
- Dates (and what flexibility exists)
- Destinations/routing at a high level
- Trip purpose (celebration, family break, business add-on)
- Priority list (top 3 “must-haves,” top 3 “avoid”)
- Budget posture (range or “value-focused / comfort-focused / premium-leaning”)
3) Proposal status table (truth table)
This is not a marketing comparison. It’s operational reality. For each component:
- Supplier / consolidator / wholesaler / DMC (as applicable)
- Reference number(s): PNR, booking ID, option/hold reference
- What’s currently held/quoted and what is not
- Time limits / expiry / deposit triggers
- Key terms you were given (change/cancel highlights)
Remember: supplier availability and terms govern what can actually be booked/changed/refunded; the client approves before payment.
4) Action log (next moves)
Write tasks as verbs with owners and deadlines:
- “Call ___ to re-check availability for ___ by ___ (date/time)”
- “Send client approval request for ___ once ___ received”
- “Ask supplier to confirm ___ in writing”
5) Communication notes + risk flags (continuity + caution)
Include:
- Last client touch: what they agreed, what they asked, and what you promised to check
- Any sensitivities (e.g., budget stress, decision-maker dynamics)
- Risk flags: approaching deadlines, name mismatches, tight connections, allergy notes to pass to operators
Copyable Nowah prompt (handoff-oriented)
Use Nowah to draft the itinerary skeleton.
Prompt:
“Draft a family-friendly 12-day, 11-night Costa Rica trip outline for a hypothetical client: 2 adults + 2 children (8 and 11). Travel in July 2027. Use the same gateway for arrival and departure; investigate its suitability before recommending it. Split time between a rainforest/volcano region (4 nights) and a beach/coastal nature region (5 nights), with one night near arrival and one night before departure.
Provide:
1) a day-by-day itinerary with a realistic pace (no exact opening times),
2) suggested activity types per day (e.g., canopy, wildlife cruise, hot springs),
3) what to research/book for each day (tours, transfers, car vs driver, room types), and
4) a short list of questions the agent should confirm with the client before booking (dietary/allergy, bedding, budget sensitivities).
Keep vendor names generic (no brand names).”
What the agent checks before using the output
Nowah’s output is a draft planning outline. Before it informs your handoff brief, the handing-off agent should:
- Compare the outline to the client’s stated must-haves and constraints
- Align travel days with the dates actually discussed (and note where dates are flexible)
- Mark where real quotes/holds exist in your files (PNRs, option numbers, supplier emails)
- Remove anything that could be mistaken for a confirmation (only your actual supplier documents are confirmations)
Reconcile the Nowah planning outline with the documented supplier status before handoff.
Worked example: 12‑day family trip handoff (anonymised)
Scenario (hypothetical): Agent A has an in-progress proposal for the “Chen family” (hypothetical names), travelling July 2027 for 12 days and 11 nights. Agent A is going on leave; Agent B will take over.
Inspect the fictional Costa Rica outline in Nowah before handing over the next research task. The proposal quality checklist supports a consistent transition.
Agent A uses Nowah for the itinerary structure, then completes the internal brief from the supplier documents. The unresolved decisions include ground transport, family room arrangements and activity suitability.
Internal Handoff Brief (example)
1) Client snapshot
- Primary contact: Mrs. Chen (email preferred; replies within ~1 business day)
- Backup contact: Mr. Chen (phone ok after 5pm local)
- Travellers: 2 adults + 2 children (8, 11)
- Names for tickets: Awaiting passport name spellings (do not ticket until received)
- Service notes: likes clear “next step” direction; prefers two options rather than many
- Needs: a food-related requirement needs supplier confirmation through the approved process; do not put unnecessary health details in a general handoff.
2) Trip overview
- Dates: Mid‑July, 12 days total (departure day flexible by ±2 days)
- Routing intent: Gateway city (1 night) → rainforest/volcano area (4 nights) → coastal nature/beach area (5 nights) → gateway city (1 night)
- Must‑haves: canopy-style adventure day; wildlife-focused excursion; one rest/pool day in each region
- Avoid: overly early starts on consecutive days; long multi-stop transfers
- Budget posture: comfort-focused; willing to pay for convenience where it reduces friction with kids
3) Proposal status table
Component | Supplier type | Reference(s) | Current state | Deadline/trigger | Notes to receiving agent |
|---|---|---|---|---|---|
Flights (gateway routing) | Major carrier via GDS | PNR on file (see attachment A) | Held / not ticketed | Ticketing time limit in PNR | Waiting for passport spellings. Verify names before ticketing. Review fare rules in attachment. |
Hotel: rainforest/volcano (4 nts) | Lodge/resort direct | Quote email thread (attachment B) | Quoted | Exact supplier expiry + time zone required | Two room configurations discussed: family suite vs two rooms. Confirm bedding preference before confirming. |
Hotel: coastal region (5 nts) | Family resort direct | Option/hold reference (attachment C) | Option held | Exact deposit deadline + time zone required | Confirm the relevant dietary requirement with the property through the approved process; a reservation remark alone does not establish suitability. |
Ground: transfers or car | Local ground operator (not selected) | – | Undecided | Decide before hotel confirmations | Client leaning private driver, but wants price check vs self-drive. |
Activity: canopy-style day | Local tour operator (not selected) | – | To quote | Reserve once dates fixed | Verify operator eligibility, suitability and availability before recommending a slot. |
Activity: wildlife excursion | Local operator (not selected) | – | To quote | Reserve once dates fixed | Prefer shorter duration; consider private vs small group. |
4) Action log
Priority | Task | Owner | Due | Inputs needed |
|---|---|---|---|---|
1 | Obtain required traveller details through the approved secure process | Agent B | Exact date/time/zone required | Client reply |
1 | Review exact flight deadline now; resolve missing details and obtain booking approval | Agent B | Before recorded TTL | PNR, rules and approval |
2 | Ask rainforest/volcano lodge to re-confirm family suite vs two rooms availability for requested dates | Agent B | Next business day | Supplier email thread |
2 | Present transfer approach (private driver vs self-drive) as a single question to client; capture preference | Agent B | Within 48 hours | None |
3 | Request quotes for canopy-style day and wildlife excursion (kid-friendly duration) | Agent B | Within 3 days | Finalized day order |
5) Communication notes + risk flags
- Last client note: wants “a trip that feels easy,” willing to pay for convenience, but doesn’t want constant early starts.
- Promise made: Agent A told client we’d come back with one clear transfer recommendation and why.
- Risk flags:
- Flight deadline runs independently of receiving names. Record the exact date, time and zone; escalate before it expires.
- Confirm provider capability for the disclosed food requirement before recommending relevant services.
- Avoid stacking two long transfer/activity days back-to-back (Nowah draft itinerary reflects a rest day after the main adventure day).
All holds and references here are fictional examples of agency records, not claims that Nowah creates or transfers holds. Replace placeholder deadlines with exact times before a real handoff.
The handoff template (copy/paste)
Use this as your standard internal brief.
INTERNAL HANDOFF BRIEF — Travel Proposal
A) Client snapshot
- Primary contact (name / email / phone / time zone):
- Backup contact:
- Travellers (count + types):
- Names for ticketing (status: confirmed / awaiting):
- Key needs (accessibility/dietary/allergy/bedding):
- Communication preferences (channel, detail level, decision style):
B) Trip overview
- Dates (fixed vs flexible):
- Routing/destinations (high level):
- Purpose/occasion:
- Must-haves (top 3):
- Avoids (top 3):
- Budget posture (range or description):
C) Proposal status table
Component | Supplier type | Supplier/contact | Reference(s) | State (quoted/held/confirmed/paid/etc.) | Deadline/trigger | Key terms/notes |
|---|---|---|---|---|---|---|
Flights | ||||||
Hotel 1 | ||||||
Hotel 2 | ||||||
Ground/Transfers | ||||||
Tours/Activities | ||||||
Other |
D) Action log
Priority | Task | Owner | Due | Notes / inputs needed |
|---|---|---|---|---|
1 | ||||
2 | ||||
3 |
E) Communication notes + risk flags
- Last client contact summary (date + what was agreed):
- Promises made / expectations set:
- Sensitivities / decision dynamics:
- Risk flags (deadlines, name issues, constraints):
Build your next handoff with Nowah supporting the planning layer, then finalize the internal brief in your agency’s approved tools. Start here: Open Nowah.




