How to Keep Client Itinerary Versions Consistent

By the TripTended team

An advisor can be editing a new itinerary while the client is still reading the previous published version. A supplier update, a saved draft and a client decision may each refer to a different point in the trip’s history. Before sharing an update, identify which version each record belongs to and compare the details that changed.

This guide helps travel advisors make a version review for one client itinerary. Use it with your current trip records and normal publishing tools. The output is a clear record of what is being edited, what is currently available to the client, what they approved and which differences still need action.

1. Identify the versions you are comparing

Open the working draft, the current client-facing page and the relevant client decision. Keep their references separate. A recently saved draft is evidence of editing; it does not, by itself, establish which page the client can see.

Record these four references before changing anything:

Use the version identifiers your system provides. If you maintain a worksheet, give each item a reference and link it to the original record. Do not use a filename such as “final-latest” as your only evidence of which version was published or approved.

2. Compare changed facts before editing the page

Start with the latest information you have checked. Compare it with both the working draft and the current client-facing version. Note the source and the exact fields affected: a local date or time, room description, service scope, meeting detail, price or condition.

Use a difference record like this:

The bracketed values are placeholders. Keep a reported change separate from a verified result. If a supplier message is unclear, preserve both statements and resolve the question before presenting the new value as confirmed. The supplier confirmation guide explains how to check the applicable arrangement.

Decide whether the difference changes the agreed trip or only corrects its presentation. A new service, supplement or material change may require a new client decision through your normal workflow. Keep that review connected to the applicable quote and scope; an earlier approval does not authorize different content. Follow the client change workflow when that is the task you need to complete.

3. Review the draft against the current evidence

Update the affected content and then look for repeated values elsewhere in the itinerary. A revised pickup time in a day entry can still conflict with the trip summary or meeting instructions. Check the introduction, service details, option summaries and any repeated terms that concern the change.

Use the source references to explain why each correction was made. Preserve earlier published versions and decisions so that another advisor can trace the sequence. Do not rewrite an old approval record to make it appear to cover the edited draft.

If the records changed after you began editing, reopen the comparison using the new evidence. If your software reports an out-of-date draft or a version conflict, read the current records before retrying. Refreshing a draft is a way to obtain current context; it is not a substitute for checking the content again.

4. Check the intended version before publishing

Preview the saved draft in the form the client is meant to receive. Review its purpose, service scope and important dates, times and terms. Confirm that you are publishing the intended draft and that the required business decisions and checks apply to it.

Keep proposal review and final delivery distinct. Publishing a proposal gives the client something to consider; publication is not their approval. A final itinerary should reflect the applicable approved scope and checked arrangements. Publishing it does not verify supplier acceptance, payment or the whole trip’s readiness.

Record the version you intended to publish. If the action fails, or the result is uncertain, check the active client-facing version before announcing an update. A saved draft or a publish request is not evidence that the client page changed. Retry through your tool’s recovery process after checking its result; keep the previous published reference in the review record.

5. Verify the page the client actually receives

After a successful update, open the current client-facing page through the normal client-view workflow. Check its version reference where available and the changed content itself. A newly copied link is not enough: read the relevant field and check the neighboring summary or instruction that might still contain the old value.

Use this small completion record:

• Version made available: [published reference and time].
• Content checked: [changed fields and review result].
• Decision reference: [applicable approval, or a required decision still pending].
• Client follow-up: [what was communicated, when and by whom].
• Unresolved item: [specific gap, owner and next action, or none after review].

Sending an update does not prove that the client read or approved it. Keep those results distinct. A downloaded PDF, printed copy or earlier attachment also needs its own follow-up: making a new online version available does not change the copy already in someone’s possession. Identify the version being replaced when you send an updated document.

Worked example: a corrected draft is still unpublished

This is a fictional version review, not a real trip, supplier result or TripTended test. The times and references illustrate the comparison only.

Input: Client-facing itinerary F4 lists a transfer at 15:00. A later supplier response has been checked and confirms 16:00 for the applicable service. Working draft D5 now says 16:00, but no new version has been made available to the client. Any client review required by the change is recorded separately.

Review output:

If publication fails, F4 remains the reference you need to check; do not tell the client that D5 is live. After the update is verified, record the newly available version and communicate the correction through your normal channel. Keep F4, the source response and the applicable decision in the history.

When to repeat the comparison

Repeat the affected checks when new supplier information arrives, the client chooses a revised scope, someone changes the draft during your review, or the active client-facing version changes. If an earlier version is restored, compare its contents with the current arrangements before treating it as suitable for the trip. Restoring content does not reverse an external booking or payment.

For preparing an itinerary entry from a checked source, use the booking-confirmation-to-itinerary guide. For the checks across the whole trip, use the trip-delivery workflow.

Explore TripTended · Review current plans

Prepared with AI assistance using TripTended’s documented version and business-state boundaries. The method describes advisor review in existing tools; it does not claim automatic publication, client approval, supplier booking, payment or Trip Ready. Advisors remain responsible for checking sources and what clients receive.