Documenting client approval before making a booking
Document exactly who approved a travel purchase, which version they saw and what authority they granted, using a practical evidence index and Nowah prompt.

Document approval so another authorised adviser can identify who instructed the purchase, which offer they saw, what action they allowed and which conditions applied. Keep the actual instruction with the exact proposal and supplier evidence. A budget, a favourable comment or a request to investigate is not necessarily authority to commit money.
Nowah can support the planning and component research behind the offer through conversational work, editable day itineraries and flight or hotel searches. Use your agency’s normal records for the approval evidence and payment process. Do not assume a conversation creates an agency permission system or proves that every traveller has agreed to the purchase.
Identify the person and the role giving approval
Record whether the approver is the traveller, a household payer, a corporate booker or another authorised representative. Establish the actual basis of authority through your agency’s process rather than inferring it from who sent the first email.
Develop the exact offer’s travel context in Nowah before requesting a decision. Pair the flight approval summary with a precise approval message so the client can understand the journey attached to the instruction.
Different roles can have different powers. A person may coordinate dates without authority to approve a charge. A finance contact may release a budget while the traveller still needs to confirm an essential arrangement. A group organiser may speak for shared activities but not each household’s room expenditure.
Keep the record proportionate and secure. You need to know which instruction controls the action, not collect unnecessary private details about the organisation or family. If authority is unclear, resolve it before commitment. The fact that someone is copied into a message or uses a company email address does not by itself establish the scope of their approval.
Anchor the instruction to an exact offer
Give the proposal a clear identifier and version. Include the services being approved, travel dates, party and rooming, total currency and price basis, material inclusions and supplier conditions. Keep separately payable charges visible instead of hiding them behind a general estimate.
Preserve the version actually sent. If you later edit a file in place, an approval referring to “the attached proposal” can become difficult to interpret. Your evidence should show the exact offer the client reviewed at the time of the instruction.
Nowah is useful for preparing an understandable approval discussion: the editable route connects the selected services before the client decides on the actual offer and conditions. Review the supported Nowah features.
Separate expenditure limits from service approval
A spending ceiling is a boundary, not a description of what may be bought. Record the actual approved service and action as well as any financial limit. “Up to EUR 3,500” is incomplete if dates, room category, traveller count or non-refundable conditions are still open.
Where the client deliberately grants some flexibility, document it precisely through your actual process. State which changes are permitted and which require another instruction. Do not invent that flexibility after a price changes simply because the revised amount remains below the overall budget.
Payment permission also needs its proper channel. Keep card details, passwords and sensitive financial information out of general approval notes and planning prompts. Reference the approved secure process rather than copying credentials into several records. The purpose of the approval document is to establish the decision, not create a new repository of payment data.
Worked hypothetical example: a corporate booker and three travellers
A fictional corporate contact coordinates three adults travelling to Lisbon for four hotel nights,7–11 June 2027. The actual flight travel dates and individual details are checked separately. The organisation has set a EUR 3,500 budget for the specified services, but the agency still needs the authorised purchase instruction.
Use Nowah to compare the fictional corporate travellers’ route and stay against the booker’s stated requirements. The corporate approval workflow helps keep the service recommendation connected to the appropriate decision-maker.
For this example, assume invented offer figures: flights EUR 450 per person for three, or EUR 1,350; three rooms for four nights at EUR 160 per room per night, or EUR 1,920; and an agency fee of EUR 180. The combined total is EUR 3,450. These are training amounts, not current offers or proof of availability.
The coordinating contact replies, “The plan looks fine.” The adviser checks the recorded authority arrangement and finds that this contact may coordinate the itinerary but must obtain the designated approver’s instruction for purchase. The message is therefore retained as planning feedback, not treated as financial authority.
The designated person receives proposal v 2 with the exact services, total and supplier conditions and gives the required instruction through the agency’s approved process. The adviser records the person, role, version, timestamp and action authorised. The purchase can proceed only while the actual selection still matches that scope and current offer.
If one traveller later needs different dates, that revised service is not covered merely because the overall party budget remains unchanged. The affected offer and authority need review. Nowah may support researching the alternative, but it does not establish the organisation’s approval rules or the result of a supplier transaction.
Copyable approval evidence index
Keep this index with the case, pointing to approved records rather than duplicating sensitive information:
- Trip and component references:
- Proposal identifier, version and issue time:
- Exact documents and conditions supplied:
- Travellers and rooming verified through the secure process:
- Approver, role and basis of authority:
- Actual instruction, channel and timestamp:
- Components and actions authorised:
- Total, currency and any expressly agreed limits:
- Permitted flexibility and stop conditions:
- Payment route reference:
- Adviser’s final offer check:
- Submission result and confirmation references:
Add a short ambiguity check: does the instruction refer to the current version, answer the purchase question and cover the actual amount and conditions? If not, clarify. A polite reply should not be stretched into a meaning the client did not express.
Keep any verbal follow-up documented through the agency’s established process. Do not reconstruct an exact quotation from memory or allow an AI summary to stand in for evidence of what was actually authorised.
Ask for a clear instruction in plain language
State the decision without forcing the client to interpret internal booking terminology. A suitable structure is: “Please confirm whether you authorise the listed components in proposal v 2 at the stated total and conditions. This will permit the specified purchase action; it is not supplier confirmation.”
Make any unresolved issue visible. If the client is choosing only a route direction, label the request accordingly and explain that final offers will follow. Do not mix that question with a payment request that appears to make both decisions at once.
Give the client access to the material conditions in a readable form through your normal process. A short approval sentence is not a reason to omit restrictive terms from the offer. If the deadline is a genuine supplier expiry, identify its actual date, time zone and source. An agency response checkpoint does not preserve inventory.
Copyable Nowah offer-preparation prompt
Help a travel adviser organise a fictional Lisbon proposal for three adults with four hotel nights,7–11 June 2027. Three rooms are required; actual flight travel dates and traveller details are checked separately. Budget EUR 3,500 for the listed services. Produce a checklist of dates, quantities, inclusions, total-price basis and supplier conditions that must be verified before requesting approval. Do not infer corporate authority, available rooms, fares, payment permission or confirmed reservations. Keep planning feedback, budget approval and authority to purchase distinct. No purchase is authorised.
Review the checklist against actual offers and the organisation’s real arrangement. The Nowah features page describes supported planning and booking tasks. Your evidence index records the human instruction that controls the commitment.
Reapprove material changes and uncertain outcomes
If the actual service, dates, essential suitability, total or restrictions change, compare the new offer with the recorded scope. Request the appropriate fresh instruction rather than assuming the earlier approval automatically stretches to the replacement.
If a purchase result is unclear, investigate before submitting again. An approval authorises a defined action; it does not justify duplicate transactions to resolve uncertainty. Record pending, failed and confirmed statuses separately with evidence.
After confirmation, compare what the supplier issued with the approved selection. If there is a discrepancy, assign it and tell the client the actual status. A tidy approval file does not remove the need to reconcile the result.
Make the record usable for cover and review
An authorised colleague should be able to find the current approval without searching every channel. Keep superseded versions identifiable and the final instruction linked to the actual action. Avoid an unlabelled folder of attachments that makes the newest file look authoritative by accident.
Use sample cases to review whether your process distinguishes roles, scope and outcome clearly. Correct recurring ambiguities in the request wording and record structure.
Use Nowah for the planning work and your evidence record for the client’s actual instruction. Clear documentation connects the approved offer to the purchase instead of relying on assumptions about what “looks fine” meant.




