For Australian and New Zealand partners, Vietnam often has to justify itself against Thailand, Japan, Cambodia or a wider Indochina route. The programme needs visible value, workable pacing and clean on-ground support before it is priced.
We keep the review practical: does the duration carry enough contrast, does the route work after long-haul flights, and are the inclusions useful rather than simply numerous?
A 10–14 day Vietnam programme should show clear regional contrast without adding hotel changes only to make the map look fuller.
We test whether Cambodia genuinely strengthens the programme, or whether Vietnam alone gives better pacing, value and operating control.
AUD-facing quote assumptions can be kept visible before final supplier confirmation, especially for domestic flights, upgrades and optional extensions.
Arrival recovery, guide quality, coach time, meal rhythm and weather exposure are checked before the itinerary becomes a client-facing programme.
ANZ group, 13 days, Vietnam with optional Cambodia extension. The first route tried to include too much southern Vietnam and Cambodia in one flow, which weakened both pace and value.
The route looked generous but created too many transitions, with limited recovery after long-haul arrival and a thin Cambodia extension.
We strengthened the Vietnam-only version, then priced Cambodia as a cleaner optional extension rather than a squeezed inclusion.
The partner could present value more clearly, with a stronger base route and an honest extension choice.
Final AUD-facing assumptions held domestic flights, hotel upgrades and extension minimum numbers separately.
Strong fit: ANZ partners who need Vietnam to stand clearly on route value, regional contrast, long-haul recovery and practical on-ground handling.
Less suitable: programmes that try to win by adding countries or inclusions without protecting pace, recovery time or operating logic.
Share the draft route, travel month, group profile, budget position and whether Cambodia is essential or optional. We can check the route value before pricing.
For partner files that move beyond route discussion, we keep quote versions, currency assumptions, inclusions, revisions, client boundaries, and operating handover visible before confirmation.
The sample route review note shows how route pressure, quote assumptions, guide briefing, and handover points are marked before a proposal becomes an operating file.
Where the route is still flexible, we prefer to review the operating version before quoting rather than price a structure that may need to be rebuilt later.