For advisors and DMCs
How to manage itinerary revisions without losing the thread
Manage itinerary revisions by treating each change as an amendment to one document rather than a new proposal: state what changed, why, and what it costs, keep a single version chain per trip, and confirm in writing which version the client approved. Most disputes between advisors and DMCs come from two parties working off different versions, not from the change itself.
Revisions are the normal case, not the exception
A tailor-made trip of any complexity goes through several rounds before it is confirmed. Three to six is unremarkable, and on a multi-generational family trip it can be far more. Any process that treats a revision as an interruption will be under strain from the first week.
The volume itself is not the problem. The problem is that each round is usually handled as a fresh document, so the history exists only as a sequence of attachments that nobody reads twice.
State the change, not just the new version
The single highest-value habit is writing what changed alongside the revised document. Two or three lines is enough, and it turns a file the recipient must diff by hand into something they can act on in a minute.
It also creates the record. Six weeks later, when someone asks why the Kyoto ryokan was swapped, the answer is attached to the revision that did it rather than somewhere in a thread of forty messages.
Separate the price change from everything else
When a revision moves the price, say what moved it. A new total with no explanation reads as a supplier re-pricing opportunistically, even when it is a genuine consequence of a client request.
Advisors who state the change and its cost separately from the rest of the revision have easier conversations with clients, because the client can see they are paying for something they asked for.
Confirm what was approved
The most expensive failure is not a bad revision. It is a trip that proceeds while the advisor and the DMC each believe a different version is live, which typically surfaces on arrival.
Confirming approval against a specific version, by number or date, costs one line and removes the ambiguity entirely. Where a client approves verbally, the advisor should still record which version they approved.
What to avoid
Some habits look efficient and reliably cause problems later.
- Naming files FINAL, or FINAL_v2, which stops meaning anything after the second round
- Making a change verbally on a call without following it in writing
- Sending a revised proposal with no note of what changed
- Letting a client-requested change and a supplier-initiated change arrive in one undifferentiated update
- Approving a revision without checking whether it affects other suppliers on the same trip
Step by step
- 1
Capture the request in one place
Write down what the client has asked for before acting on it, including anything decided on a call. A revision that starts as an unrecorded conversation has no reliable origin later.
- 2
Amend the existing proposal
Revise the document that exists rather than issuing a new one. The proposal should carry a version identifier so any party can say unambiguously which one they are discussing.
- 3
State what changed and why
List the specific differences alongside the revision, with the reason for each. Two or three lines is enough, and it is what saves the recipient from comparing two documents by hand.
- 4
Show the price effect separately
Where the total moved, say which change moved it and by how much. A price difference presented without a cause reads as opportunistic even when it is not.
- 5
Check the change against the rest of the trip
Before circulating, confirm the revision does not break something held by another supplier, such as a transfer timed to a flight or a deadline in another segment.
- 6
Record the approval against a version
When the client approves, note which version by number or date. This one line is what prevents two parties operating a trip from different documents.
Frequently asked questions
How many revisions is normal on a tailor-made itinerary?
Three to six rounds is unremarkable for a complex trip, and multi-generational or multi-destination itineraries often run to more. The number matters less than whether each round is recorded as an amendment to one proposal or issued as another standalone document.
How should a DMC handle revisions requested by a travel advisor?
Amend the existing proposal rather than reissuing a new one, state explicitly what changed and why, and show any price effect separately from the rest of the update. This gives the advisor something they can pass to a client directly instead of a document they must first compare against the previous one.
What is the most common cause of disputes over itinerary changes?
Two parties working from different versions. The change itself is rarely contentious; the disagreement is about what was current when a decision was made, and it usually surfaces after the client has been quoted or, at worst, after travel has begun.
Should verbal changes be confirmed in writing?
Yes, and promptly. A change agreed on a call and not written down has no version attached to it, so it cannot be traced later. Following a call with two lines summarising what was agreed is the cheapest protection available in this workflow.
How do you keep track of what a client actually approved?
Record approval against a specific version identifier rather than against a date or a conversation. Where the client approves verbally or by a brief email, the advisor should still note which version that approval refers to, since that is the fact in dispute if anything goes wrong.