---
title: "Building a travel booking exception log"
description: "Track booking exceptions with facts, consequence, ownership and closure evidence, using a practical log and a worked supplier-charge discrepancy."
canonical: https://nowah.xyz/blog/travel-agents-building-a-travel-booking-exception-log
lastModified: "2026-11-20T15:07:14.250Z"
---

# Building a travel booking exception log

Track booking exceptions with facts, consequence, ownership and closure evidence, using a practical log and a worked supplier-charge discrepancy.

Use an exception log to record a booking issue that needs a decision outside the normal flow: what happened, what is known, what cannot proceed and who owns the next action. An exception may be an error, an unclear supplier result, a missing requirement or a legitimate client change. Do not label every exception as someone’s failure before checking the evidence.

Nowah can support planning review and relevant flight or hotel research when an exception affects the itinerary. Keep the actual issue, authority and resolution evidence in your agency’s normal operations record. A revised day plan or generated explanation does not resolve a supplier discrepancy by itself.

## Decide what belongs in the log

Record conditions that affect suitability, dates, cost, authority or actual service status and cannot be handled by the ordinary next step. Examples include an unexplained price difference, unresolved occupancy, conflicting dates, a supplier response that differs from approval or an unknown transaction result.

Use the [Nowah](https://app.nowah.xyz) itinerary to locate the travel consequence of an exception before logging its next action. Pair [a logistics review](/blog/travel-agents-reviewing-an-itinerary-for-hidden-logistical-problems) with [the error-review method](/blog/travel-agents-creating-a-travel-agency-error-review-process) so the record describes a specific problem rather than a vague failed stage.

Routine research questions can stay in the planning brief if they do not require exception handling. A preference about dinner style is not the same as an essential room requirement that remains unconfirmed before purchase. Keep the log focused enough that important issues are not buried among every small task.

Define the exception unit. One case may have several issues requiring different owners, such as a hotel amendment and a separate payment-status question. Link them to the same trip without merging them into a single vague “problem booking.” Each entry should identify the actual decision or evidence needed for closure.

## Record observations before explanations

Start with the fact and source: a confirmation shows a different date, an offer excludes a required charge or a submission returned an unclear result. Record when it was observed and by whom. Then list possible explanations separately if they need investigation.

Avoid assigning cause from the first symptom. A mismatch may arise from an old brief, supplier change, copied field or incomplete instruction. A new Nowah output cannot establish why a past record differs or prove what a supplier offered earlier.

Keep original evidence accessible through approved records rather than copying unnecessary sensitive data into the log. Reference the actual offer, client instruction or supplier message. Preserve contradictory evidence until it is resolved. A clear observation lets the next adviser investigate the right issue without inheriting an unsupported conclusion such as “supplier error” or “client changed their mind.”

## Define consequence and the next safe action

State what the issue affects: whether a service meets the brief, whether the client can approve the offer, whether a purchase may proceed or whether a confirmation can be delivered accurately. Use practical impact rather than an unexplained severity score.

Record the stop condition. An unknown transaction result blocks another submission until investigated. A material unapproved condition blocks treating the offer as authorised. A pending supplier clarification may allow other independent research to continue, provided it is labelled appropriately.

Assign an owner and an actual follow-up or update point. Keep supplier deadlines separate from agency checkpoints and include source and time zone where relevant. Do not create an invented expiry simply to make the log look actionable. The useful entry identifies which person will establish which fact and what evidence will permit the next step.

## Worked hypothetical example: an omitted required charge

A fictional couple is considering five hotel nights in Madrid,8–13 October 2027. The proposal presents an invented EUR 1,000 full-stay total for two. The client approves that stated version before purchase. The adviser then sees that the actual example supplier offer also specifies a required EUR 60 charge payable at the property, omitted from the proposal.

The exception is a price-scope discrepancy. The source now shows EUR 1,000 plus EUR 60, or EUR 1,060 combined for the stated hotel arrangement. These are invented training amounts, not current property charges or a statement about local tax rules.

The adviser stops the proposed purchase, records the exact source and checks whether any other required costs were omitted. They do not simply add “local charges may apply” to the old proposal or assume the client’s wider budget authorises the difference.

The revised offer identifies the EUR 60 amount, where it is payable, the corrected total and actual conditions. The appropriate client reviews and instructs on the revised version. The exception entry closes only when the discrepancy has been explained and the required decision and record updates are complete. Actual booking submission and supplier confirmation remain separate stages.

For the hypothetical exception, develop an alternative route or stay in Nowah only after the operational question is clear. The [alternative-scenario workflow](/blog/travel-agents-using-ai-to-prepare-alternative-trip-scenarios) helps separate the possible planning response from the established incident facts.

## Copyable booking exception log

Use one entry per issue in your approved operations system:

- Exception identifier and trip/component reference:
- Date, time and person detecting it:
- Observed fact and original source:
- Current service and transaction status:
- Client authority and relevant proposal version:
- Practical consequence and affected dependencies:
- Unknown facts or possible explanations:
- Stop condition and actions still permitted:
- Owner and next evidence-gathering step:
- Real supplier deadline, if applicable:
- Agency follow-up and client-update point:
- Decision, authority and action taken:
- Resolution evidence and remaining obligations:
- Closure reviewer and linked improvement task:

Keep personal identity and payment details out of general issue descriptions unless the authorised task genuinely needs them. Use secure references to the relevant source instead of pasting sensitive material into a broadly shared log.

Do not overwrite the observation with the eventual explanation. Retain enough sequence to understand what was known when the decision was made. That helps both cover and later process review.

## Keep client communication separate from internal hypotheses

Tell the client the established issue and the next action in clear language. If the cause is still being investigated, say so without presenting speculation as fact or assigning blame prematurely. Avoid unnecessary internal commentary about colleagues or suppliers.

Where the exception changes an offer, present the exact difference and required decision. Where it concerns an unresolved result, distinguish that status from confirmed failure. Do not promise a free correction, refund date or available replacement unless the actual source supports it.

Nowah is useful for exploring the planning response to an exception: an editable route helps show which traveller decisions depend on its resolution. Review the [supported Nowah features](/features).

## Copyable Nowah exception-research prompt

Help a travel adviser identify checks for a fictional hotel price-scope discrepancy. Two adults, five Madrid hotel nights,8–13 October 2027, origin London with flight dates separate. The proposal says EUR 1,000 total, while a supplied supplier note states an additional required EUR 60 payable at the property. List fields to verify: party and stay, charge basis, currency, inclusions, where payment occurs and total presentation. Do not invent local taxes, supplier policy, historical source content or client authority. Keep research and corrected-offer approval separate from actual reservation confirmation.

Review the response against the original offer. The [Nowah features](/features) page describes supported planning and hotel research capabilities. Use those tasks to organise the investigation, while the actual supplier evidence and client instruction determine the correction and next commitment.

## Close the issue with specific evidence

Define the closure condition when the entry is created. “Client informed” may be one action, but it does not necessarily resolve an unapproved price, unknown payment result or mismatched reservation. Close only the issue whose evidence and decision are complete.

If related work remains, assign it as a linked task or separate exception rather than hiding it under a closed status. A corrected proposal can resolve a documentation mismatch while a supplier amendment still awaits confirmation. Keep those stages distinguishable.

Have an authorised reviewer inspect material resolutions where your process requires it. Record what was checked and which current source supports the result. Do not make an entry disappear because it is embarrassing or because a replacement itinerary looks correct. A factual history helps future advisers avoid repeating an action that has already occurred.

## Use patterns to improve the normal workflow

Review recurring categories, unowned entries and passed follow-up points at a suitable interval. Look for missing fields, unclear authority, repeated source confusion or a template that encourages an unsupported status claim.

Separate incident handling from the improvement task. The client may need a correction now, while the agency needs a later change to its checklist or training. Give both an owner without assuming a procedure edit resolves the live case.

Use [Nowah](https://app.nowah.xyz) for planning support and a clear exception log for the operational decision. The entry should show what is known, what is blocked and the evidence that makes the next action appropriate.

## Related guides for travel agents

- [Building a booking reference register for a small agency](/blog/travel-agents-building-a-booking-reference-register-for-a-small-agency)
- [Reconciling itinerary changes with existing reservations](/blog/travel-agents-reconciling-itinerary-changes-with-existing-reservations)
- [Managing travel booking tasks across a small team](/blog/travel-agents-managing-travel-booking-tasks-across-a-small-team)
