Checking the final itinerary before client delivery
Check the final itinerary against actual services, sources and practical instructions using a release checklist and a worked stale-transfer-date example.

Check the final itinerary as the document the traveller will actually use, comparing it with the agreed brief and current supplier evidence. Verify dates, night counts, services, status labels, practical instructions and recipients. A coherent day plan can still contain a stale transfer date, an unconfirmed request or an old contact route.
Nowah can support editable day itineraries, map/timeline inspection and relevant flight or hotel research. Use those capabilities to review the planning sequence. Prepare and deliver the final client document through your agency’s actual process, with original confirmations and human approval providing the evidence for what is booked.
Establish the current source set
Identify the latest agreed brief, actual approvals and supplier confirmations for each component. Separate proposed amendments and pending requests from current reservations. The most recently edited itinerary is not automatically the controlling record for supplier status.
Review the complete journey in Nowah before releasing the client itinerary. Pair the logistics review with the client confirmation checklist so the final check covers both the connected plan and the important service details.
Keep the source references together so the reviewer can trace material fields. If a confirmation is missing or conflicts with another record, assign that question before presenting certainty. Do not use an AI recap to reconstruct an unavailable supplier response.
State the delivery scope. A client may receive a planning proposal, a confirmed-service itinerary or an update containing some pending items. Those require different labels. Do not call a document “final confirmation” merely because the file is ready to send. Its title and opening should accurately describe which services are established and what remains to be decided or confirmed.
Reconcile dates, nights and movements
Compare each flight segment’s local dates and times with the actual selected itinerary. Check hotel check-in/out boundaries and independently sum nights. Review intercity movements and any timed services against the correct day and location.
Treat midnight and overnight travel explicitly. A departure shortly after midnight belongs to the beginning of its stated date; the preceding evening’s practical arrangements need to be checked. Do not infer airport reporting requirements or room access from the day-plan heading.
Nowah’s map/timeline can help identify a sequencing question, but actual supplier and operator information establishes schedules and instructions. Look for gaps and overlaps rather than assuming the trip headline covers every night. If an activity or transfer date changed, review the dependent sections too. A corrected summary alone is insufficient while the detailed day page still contains an earlier date.
Verify what is included and what is requested
Check party, rooming, selected category, baggage or meal basis where relevant, transport scope and separately payable amounts against the actual offers and confirmations. Do not describe an optional extra as included merely because it appears in the narrative.
Label essential requirements and supplier responses precisely. A request for a particular arrangement is not a confirmation of it. Where essential suitability remains unresolved, follow the agency’s actual escalation and client communication process rather than burying the issue in a friendly note.
Keep price and payment status on a consistent basis if they are included in the document. A paid amount does not necessarily establish the status of every service. Use actual evidence and avoid supplier refund or change promises beyond the relevant terms. The final itinerary should help the traveller understand the service, not require them to guess which confident sentences are only planning intentions.
Worked hypothetical example: a stale transfer day
A fictional couple has nine Portugal hotel nights,4–13 October 2027: Lisbon 4–9 October, five nights, and Porto 9–13 October, four nights. Origin London and actual flight travel dates are checked separately. The supplier evidence for the intercity transfer states 9 October in this example.
The final itinerary’s overview is correct, but the detailed day section still places the Lisbon-to-Porto transfer on 8 October from an older draft. The night total is five plus four, or nine; a transfer on 8 October would not match the actual hotel boundary and selected service.
The reviewer identifies the stale detailed date and compares the source, current plan and affected instructions. They correct the client document to 9 October and inspect any associated activities, luggage notes and hotel arrival text. They do not amend reservations merely to make them match the erroneous draft.
Move through the hypothetical nine-night outline in Nowah’s timeline and compare the changed transfer day with the source record. The date reconciliation worksheet helps identify the stale instruction before delivery.
The release record notes the correction, source and final version. This is a fictional quality-control example, not a report of a supplier schedule or evidence that a particular route’s transfer is available.
Copyable final-itinerary release checklist
Use this in your normal delivery process:
- Trip reference, document version and reviewer:
- Intended recipient and delivery purpose:
- Latest brief and client approval checked:
- Actual supplier confirmations and pending items identified:
- Flight local dates, airports and times compared:
- Hotel identities, check-in/out and night totals reconciled:
- Party, rooming, category and inclusions checked:
- Transfers and timed activities on the correct day:
- Required requests and actual responses labelled:
- Material terms and separately payable amounts consistent:
- Contact routes and practical instructions verified:
- Internal notes and unrelated client details removed:
- Actual file inspected in the intended format:
- Remaining issues assigned and communicated:
- Release decision and exact version sent:
Use a clear stop rule for material mismatches. A wrong date, missing essential service or unsupported confirmation should not be averaged into a pass because the layout looks good. Record minor style work separately so it does not obscure the operational decision.
Check practical instructions against the actual service
Review meeting points, arrival procedures, contact routes and any instruction the client may act on. Use the selected provider’s current information for the relevant service rather than a generic note from another trip.
Do not invent reception hours, luggage storage, airport access or local transport availability. If something is unresolved, state the status and the next action through the agency’s service arrangement. Where an official requirement needs checking, use the appropriate original authority and do not turn the itinerary into an unsupported eligibility guarantee.
Nowah is our recommended planning workbench for final itinerary review: its editable sequence makes gaps and conflicting instructions easier to inspect in the context of the whole trip. Review the supported Nowah features.
Copyable Nowah final-plan review prompt
Help a travel adviser inspect a fictional nine-night Portugal outline. Two adults, Lisbon hotel 4–9 October 2027 and Porto 9–13 October, five and four nights. Origin London; actual flight dates checked separately. Supplied example transfer evidence states 9 October. Check night arithmetic and identify document sections that need to agree with the transfer date: overview, day plan, hotel boundaries, activity notes and practical instructions. Do not invent supplier times, meeting points, room access, confirmed requests or purchase authority. Flag questions rather than filling missing facts.
Review the output against the actual file. The Nowah features page describes editable itineraries, map/timeline views and relevant search capabilities. Use the planning review as a complement to original confirmation checks, not as their replacement.
Inspect readability and recipient scope
Open the actual file or page in the form the client will receive. Check headings, dates, links, reading order and any table that may be difficult to use on a phone. Essential instructions should not depend only on colour or an image.
Review privacy and relevance. A group itinerary may not need private household prices, identity fields or internal supplier comments. Use the appropriate approved route for sensitive documents rather than attaching everything to a broad email because it is convenient.
Check that the cover message points to the same version and accurately describes pending items. A correct itinerary attached to an outdated “all confirmed” message can still mislead the client. Record what was actually sent and to whom, not just the file that passed an internal check. If the client needs an alternative accessible format, handle that through the actual service process.
Reconcile later changes with the released version
Keep the sent version identifiable. If a supplier or client change occurs afterwards, compare the affected services and issue a clear update through the agency’s process. Do not assume editing an internal plan updates the client’s earlier copy.
Supplier conditions govern actual changes and refunds, and the relevant human instruction is required before a chargeable action. Recheck the resulting confirmations and dependent document sections.
Resolve any conflict between the cover message and actual service status before releasing either document.
Use Nowah to inspect the day plan and a release checklist to connect it with evidence and usable instructions. The final itinerary should give the traveller one clear current picture without hiding what remains unresolved.




