Recording a client's acceptance of a travel proposal
A practical SOP and templates to capture clear, auditable client approval for travel proposals before payment, with a worked hypothetical example.

Record acceptance as a specific, dated approval of a specific version of your proposal, including the traveller names, total authorised amount (or limits), key conditions (change/cancellation/payment deadlines), and what you are authorised to do next (hold, ticket, deposit, full payment). Use Nowah to organise the itinerary and research selected components, then maintain the acceptance evidence in your agency’s approved record system. Planning agreement, payment authority and supplier confirmation are separate statuses.
What “acceptance” must capture (and what it doesn’t need to be)
Treat “Looks good” as a request to clarify scope if it does not identify the relevant version and authorised action. This workflow is an operational record, not a determination of legal enforceability.
Use the current Nowah itinerary and actual offer details to describe what the client is accepting. The version-control guide helps identify the right proposal.
A practical acceptance record should capture:
- Who accepted: name, role (lead traveller/payer), and contact channel used.
- What they accepted: proposal/quote identifier and version/date/time.
- What you’re authorised to do: book flights, confirm hotels, purchase eSIM, pay supplier, etc.
- Financial authority: currency, total authorised amount or “not to exceed” amount, plus how/when payment will be taken under your process.
- Key commercial terms: supplier cancellation/change terms as disclosed, ticketing/payment deadlines, fare/hotel rate variability, and any non-refundable items.
- Important assumptions relevant to this booking action: traveller names as per passport, dates, routing, room type, baggage, inclusions, and any special requests that are not guaranteed.
- Evidence: the client’s written approval (email/reply/e-sign), and the exact documents/attachments they approved.
Acceptance triggers: when you should ask for it
Ask for recorded acceptance before any booking commitment or any action that creates a fee exposure for the client or your agency.
Common triggers include:
- Before charging any card / taking payment (deposit or full amount).
- Before ticketing flights (including “instant purchase” fares).
- Before confirming non-refundable hotel rates.
- Before purchasing travel eSIMs.
- Before agreeing any additional chargeable service under your agency process.
- Whenever the itinerary materially changes (dates, routing, property, room type, cancellation terms, total cost).
A simple, repeatable SOP (the 9-step acceptance capture)
Use this SOP as your internal standard. It is tool-agnostic and works whether you take acceptance by email reply, an e-sign tool, or a client portal.
Compare the accepted direction with the Nowah research before proceeding to purchase checks. The pre-booking approval checklist helps keep those stages explicit.
- Freeze the proposal version
- Assign a unique ID (e.g., “Q-2026-0147”) and a version stamp (e.g., “v3 – 19 Nov 2026 14:10”).
- Export/attach the exact itinerary and pricing summary you are asking them to approve (in your usual format).
- Write a one-page Acceptance Summary
- A short block of text or table summarising: travellers, dates, routing, booked components proposed for booking, total, deadlines, and key terms.
- Ask for explicit instruction
- Use wording that identifies the authorised action: “Please reply ‘APPROVE’ to authorise us to book and charge up to …”
- Confirm traveller identity data
- Check the identity fields the relevant supplier requires; collect only necessary data securely.
- Use your agency’s approved data-handling process for sensitive information.
- Confirm price/availability variability
- State that supplier availability and terms govern bookings, changes and refunds; client approval is required before payment.
- Capture payment authority
- Record how the client will pay per your process (do not request passwords or store card data outside your compliant method).
- Store the evidence bundle
- Save: client approval message + Acceptance Summary + proposal attachments + any supplier term links/PDFs you provided.
- Log time, channel, and agent
- “Approved by X via email on date/time; handled by agent Y.”
- Proceed to booking
- Only after acceptance is recorded and complete.
The Client Acceptance Record (copy/paste template)
Use the following as an internal record (and adapt a client-facing “Acceptance Summary” from it). This is editorial guidance—not a Nowah feature.
Client Acceptance Record (CAR)
- Agency / Consultant: [Name]
- Client / Lead traveller (approver): [Name]
- Approval channel: [Email reply / e-sign / portal message]
- Date & time (with timezone): [YYYY-MM-DD hh:mm TZ]
Proposal identification
- Quote / Proposal ID: [Q-YYYY-####]
- Version: [v#]
- Version timestamp: [YYYY-MM-DD hh:mm TZ]
- Documents included in approval:
- [Itinerary summary PDF v#]
- [Pricing summary v#]
- [Supplier terms / cancellation screenshots or PDF, if provided]
Travellers
- Traveller list: [Approved secure record reference; exact required identity fields verified]
Trip outline
- Dates: [Start–End]
- Routing: [City A → City B → City C]
- Components authorised for booking:
- Flights: [Yes/No] (fare type if relevant)
- Hotels: [Yes/No]
- Ground/other: [Yes/No]
- Travel eSIM: [Yes/No]
Financial authority
- Currency: [USD/EUR/etc.]
- Total authorised amount: [Amount] OR Not-to-exceed: [Amount]
- What this authorises: [Deposit only / Full payment / Ticketing]
- Payment timing: [Immediately upon approval / On date / Before deadline]
Key conditions acknowledged
- Supplier change/cancel terms acknowledged: [Yes/No]
- Deadlines acknowledged: [Ticketing/payment date-time]
- Price/availability may change until booked: [Acknowledged]
- Name accuracy required (passport match): [Acknowledged]
Requirements and requests (record supplier status separately)
- [Distinguish an optional preference from an essential rooming or access requirement; stop if essential suitability is unresolved]
Client approval wording (verbatim quote)
- Copy/paste the approval message or reference the e-sign envelope ID.
Agent notes (internal)
- [Any clarifications, call notes, exceptions]
Worked example (hypothetical): turning “Yes, book it” into clean, auditable acceptance
The scenario below is hypothetical and anonymised.
For the fictional acceptance, inspect the selected Nowah route and component conditions before summarising the instruction. The booking-status guide supports precise wording.
Situation: Two fictional adults plan ten hotel nights in Portugal: Lisbon three, Coimbra four and Porto three. The agency record Q-2027-0147 v3 lists checked flights and hotels totalling EUR 4,800. These invented numbers demonstrate a record, not an offer. The client’s separate EUR 5,000 budget does not permit you to spend the difference automatically.
Acceptance Summary excerpt:
- Proposal: Q-2027-0147 v3, issued 4 February 2027 at 14:10 Europe/Lisbon.
- Stay: 20–30 September 2027; each hotel’s check-in/out and flight travel dates listed in the attached component schedule.
- Scope: the specified flights and hotel rates only; no eSIM or other extra authorised.
- Price: EUR 4,800 total for two, with taxes and any separately payable amounts identified in the schedule.
- Authority: purchase only those components at those prices and stated conditions; ask again for a material change.
- Terms: exact supplier cancellation, change and payment conditions attached to each component, including any non-refundable amount.
Request: “Please confirm that the traveller details in the secure record are correct and reply ‘APPROVE Q-2027-0147 v3, listed flights and hotels at EUR 4,800 under the attached conditions.’ This is authority for the listed purchase; it is not confirmation that suppliers have booked it.”
The fictional client gives that reply. Before purchase, a hotel offer changes to EUR 150 more. You pause and request approval of v4, showing the EUR 4,950 total and any changed terms. Being below EUR 5,000 does not establish authority for this revised offer. You preserve both requests and the new reply in your normal records.
After each purchase, match supplier confirmations to the approved selections. If only one component succeeds, record that status and resolve the remaining components without describing the whole trip as confirmed.
Use Nowah to cross-check the planning structure against researched flights and hotels. Its multi-city flight search can support route research; the exact offers and client instruction still control the purchase (see Nowah features).
Copyable Nowah planning prompt (to generate the approval-ready summary)
Use this prompt in Nowah, then check its output against the actual offers.
You are assisting a travel adviser preparing an approval-ready trip summary. Use the brief below.
Trip brief (hypothetical):
- Travellers: 2 adults (names to be confirmed later)
- Hotel stay: 10 nights, 20–30 September 2027; origin London; Portugal trip, exact flight dates to check
- Routing: Lisbon (3 nights) → Coimbra (4 nights) → Porto (3 nights) then return home
- Priorities: minimise backtracking; mid-range to upper-mid hotels; walkable areas; one “rest day” with light activities
- Flights: prefer 1 stop max each segment; include a multi-city flight search outline
- Hotels: propose 2 hotel options per city with concise differentiators (location style, cancellation flexibility where available, breakfast included/not if known)
- Extras: none authorised; do not add purchases to the approval scope
Output format:
1) A day-by-day itinerary outline (bulleted)
2) A component checklist: Flights / Hotels with placeholders for prices and deadlines
3) A short “Acceptance Summary draft” paragraph that states what the client would be authorising to book and the key acknowledgements (availability/price may change until booked; supplier terms govern changes/refunds)
What the adviser must check before using the output
Nowah can structure a planning draft, but supplier details and the client’s actual instruction determine your acceptance record.
Review checklist:
- Match version to reality: Ensure the itinerary you’ll attach to the acceptance request matches the most current plan in Nowah.
- Validate critical booking fields: dates, routing order, traveller count, room occupancy, and baggage assumptions.
- Confirm what is known vs unknown: Don’t let placeholders (prices, deadlines) slip into the final Acceptance Summary.
- Check supplier conditions source: Use the supplier’s terms presented at time of booking/quote; don’t rely on generic assumptions.
- Avoid over-precision: If something is not confirmed (e.g., bed type requests), label it as a request—not a guarantee.
For an overview of what Nowah supports in planning (itineraries, map/timeline views, flight search, hotel search/booking, and eSIM purchasing), refer to Nowah features. Maintain the evidence under your agency’s retention and access process; do not put identity or payment credentials into a general planning prompt.
Use Nowah to research and organise the trip. Use the acceptance record to establish exactly what the client authorised, then compare actual confirmations with that instruction.




