Skip to content
Back to Blog

Travel agent resources7 min read

Documenting the assumptions behind a travel quotation

A practical method to document the assumptions behind a travel quotation, with an assumptions log template, worked example, and a Nowah prompt to validate inputs.

Editorial illustration of travel-planning work: documenting the assumptions behind a travel quotation

Document the assumptions behind a travel quotation as a short, client-checkable record of the inputs you used to build the numbers—dates, routing, pace, rooming and supplier parameters. Nowah helps you develop the itinerary and expose unanswered planning questions before those inputs become a quotation.

What “assumptions” are (and what they are not)

In quoting terms, an assumption is any unconfirmed variable you selected (or left as a default) that could change:

  • Total cost (fare type, room category, number of rooms, transfer style)
  • Trip shape (number of bases, order of stops, travel-day length)
  • Client experience (pace, downtime, “early starts” tolerance)
  • Options available (schedule windows, direct-only vs connections)

Assumptions are not your inclusions/exclusions list, and they are not a quote validity notice. They are the “working inputs” that make the quote interpretable and auditable.

A simple test: if a reasonable client could say, “I didn’t realise you were basing it on that,” then it’s an assumption you should document.

Make unconfirmed inputs visible

Unstated assumptions can leave important differences between your calculation and the client’s expectations:

Enter confirmed details in Nowah and mark unresolved ones in the working brief. The brief audit helps identify assumptions before research begins.

  • You price two rooms, the client expected one family suite.
  • You assumed one-stop flights were fine; the client only wants direct.
  • You built a four-base itinerary; the client wanted two bases with more downtime.

When assumptions are explicit, two things happen:

  1. The client can correct inputs early (before you spend time refining the wrong plan).
  2. You can trace the affected components, including dependencies such as flights, hotels and transfers when a date changes.

The four-field format: a durable way to write assumptions

A reliable assumptions entry has four fields. Keeping this structure consistent matters more than making it long.

  1. Variable: the thing that can change
  2. Value used: what you priced/planned against
  3. Source: where it came from (client email date, call notes date, intake form)
  4. Re-check trigger: the client-facing condition that forces you to revisit pricing/availability/terms

The “re-check trigger” is the difference between an assumptions list and generic commentary. It signals the need for review rather than promising that a small-looking edit will have a small effect. Identify unconfirmed agent defaults explicitly, with an owner and a date for resolving them.

Where assumptions belong so clients will actually read them

Use two layers, both client-visible:

Connect the assumptions beside an option to the matching Nowah research version. The quotation version-control guide helps prevent superseded inputs being reused.

  • Assumptions summary (6–10 bullets near the top of the quotation)
  • Full Assumptions Log (a compact table within the quote)

Then, in your delivery message, ask the client to confirm or correct assumptions before you progress to supplier confirmation and payment approval. Availability, changes, and refunds remain governed by supplier terms and inventory at the time of booking; the client should approve before payment.

Worked hypothetical example: 14 nights Thailand + Vietnam family trip

This is a fictional, anonymised scenario for training.

For the fictional family, compare the Nowah hotel-night allocation with the party and room requirements. The family room guide supports the occupancy review.

Brief (hypothetical):

  • Travellers: 2 adults + 2 children (ages 8 and 12)
  • Length: 14 nights
  • Target window: early July 2027
  • Priorities: family-friendly pace, minimise long travel days, include downtime
  • Preferences: private transfers; premium economy for longer flight segments; economy for short hops

Assumptions summary (paste-ready)

  • Hotel dates assumed: check-in 1 July 2027, final checkout 15 July (14 nights); international flight dates still need alignment
  • Proposed allocation: 4/3/4/3 nights across four bases; suitability for the client’s pace remains to be checked
  • Proposed order: Thailand city, north and beach, then one Vietnam base; actual connections and travel burden need investigation
  • Pace preference: avoid consecutive heavy days; a three-hour door-to-door target is a client preference, not an established journey time
  • Flights assumed: premium economy on longer segments; economy on short segments
  • Rooming: two rooms, with ages at stay, occupant allocation and supervision rules to check; connecting rooms remain a request unless explicitly confirmed
  • Transfers assumed: private for airport/hotel and between bases
  • Accommodation style assumed: family-friendly 4-star style in convenient areas
  • All options are subject to supplier availability and terms at booking

This is short, specific, and designed to prompt corrections.

Full Assumptions Log (example)

Variable

Value used in this quotation

Source

Re-check trigger

Dates & length

Check-in 1 July to checkout 15 July 2027 (14 hotel nights)

Call notes (5 Nov 2026)

Any date/length change.

Travellers

2 adults + 2 children (8, 12)

Intake form (5 Nov 2026)

If ages/party size change (rooming and fares may change).

Stop count

Four bases, 4/3/4/3 nights

Agent proposal, unconfirmed

If client wants fewer/more bases, rework routing and transport.

Routing order

Thailand: city → north → beach; then Vietnam base

Agent plan

If client changes order/countries, re-shop flights/hotels.

Travel-day tolerance

Aim for transfer legs around ~3 hours or less

Client preference

If longer travel days are acceptable, more routing options open.

Flight cabin approach

Premium economy for longer sectors; economy for short hops

Client stated

If cabin preference changes, re-check fares and availability.

Schedule window

Departures roughly 08:00–19:00 preferred

Agent default (unconfirmed)

If red-eye/earliest/latest only, re-shop flights.

Direct vs connections

Connection tolerance unresolved

Client answer required

If direct-only is required, re-shop flights.

Baggage baseline

Traveller baggage needs and selected fare allowances unresolved

Agent follow-up

If baggage needs differ, adjust fare type and totals.

Accommodation category

Family-friendly 4-star style

Client budget direction

If 5-star/suite/villa is required, re-shop hotels.

Rooming

Two rooms; occupant allocation and actual bedding pending

Email (6 Nov 2026), incomplete

If bedding/adjacency is mandatory, re-check inventory.

Transfers

Private transfers assumed

Client preference

If shared/self-arranged is acceptable, re-cost ground.

Downtime

Lighter days spaced throughout (pool/beach/rest)

Agent interpretation

If client wants intensive touring, restructure day plan.

Currency basis

Display currency, supplier currencies and conversion basis to record

Agency calculation

If client wants currency exposure minimised, revisit at booking.

Using Nowah to surface hidden assumptions before you price

Copyable Nowah prompt (fictional brief)

Edit the brackets before pasting.

You are assisting a travel adviser preparing a quotation assumptions list. Create a 14-night family itinerary for [1–15 July 2027] for two adults and two children (8 and 12), visiting Thailand and Vietnam with culture plus beach time. Priorities: family-friendly pace, minimise long travel days (a three-hour door-to-door preference must be checked against actual transport), include downtime most days. Preferences: private transfers; premium economy for flight segments longer than 4 hours and economy for shorter flights.

Output:

1) Investigate a 4/3/4/3-night allocation and explain whether the resulting travel fits the brief.

2) Day-by-day outline (avoid promising specific attraction opening times).

3) At least 12 assumptions you had to make to build this plan.

4) For each assumption, a client-friendly re-check trigger.

5) 10 clarifying questions to confirm the most impactful assumptions.

A paste-ready assumptions artifact: log + confirmation script

Keep this record with the proposal and update it when a client corrects an input.

Assumptions Log (template)

Variable

Value used

Source (client/agent + date)

Re-check trigger (client-facing)

Dates & length

If dates/length change, I will re-check availability/pricing.

Travellers (count/ages)

If party/ages change, I will re-check fares/rooming.

Routing & bases

If routing/bases change, I will revise transport and re-price.

Pace / travel-day tolerance

If longer travel days are OK, I can open more options.

Flight cabin approach

If cabin preference changes, fares and availability may change.

Schedule window

If you need earlier/later flights, I will re-shop schedules.

Direct-only vs connections

If you require direct-only, I will re-check flight options.

Baggage baseline

If baggage needs differ, fare type and totals may change.

Accommodation category/style

If you want a different category/room type, I will re-shop.

Rooming & bedding

If room adjacency is mandatory, I will confirm inventory.

Transfers (private/shared)

If transfer style changes, the ground total will change.

Downtime vs touring intensity

If you prefer more touring, I will restructure days/costs.

Supplier terms sensitivity

If you need specific flexibility, I will target matching terms.

Client confirmation script (send with the quote)

Please review the “Assumptions used for this quotation” section first. Reply with any corrections (dates, routing, pace, flights, rooming, or service level). Once you confirm the assumptions, I will proceed to re-check current availability and supplier terms for the final confirmation step before any payment approval.

This keeps the client focused on inputs, not only totals.

Prioritise by consequences, then check dependencies

Put unresolved dates, rooming, essential travel requirements and major cost inputs near the top. Keep lower-impact preferences in the table. These are triage decisions, not fixed risk categories: a cabin request can change available routes, and a later start can make a connection impossible. Review the linked services before describing an amendment as minor.

Putting it into practice with Nowah (repeatable workflow)

  1. Draft the trip shape in Nowah: routing + day outline + rough flight/hotel direction (see Nowah features).
  2. Extract assumptions Nowah exposed (pace, number of bases, flight constraints) and convert them into the four-field format.
  3. Place 6–10 high-impact assumptions at the top of your quote; include the full log table.
  4. Send the quote using the confirmation script; incorporate corrections.
  5. Re-check the affected components in Nowah (flights, hotels, itinerary structure) and update the assumptions log so the quote always reflects what was actually used.

Used this way, Nowah becomes your planning workbench for turning “implicit defaults” into explicit, client-verifiable assumptions—without bloating your quote.

Build your next assumptions-first quotation workflow in Nowah at Open Nowah, and review supported capabilities at Nowah features. For current membership terms, refer to /pricing.

Share this article