Skip to content
Back to Blog

Travel agent resources8 min read

Creating a travel itinerary revision log

Keep itinerary changes traceable with a revision log, clear approval states and a Nowah workflow for checking updated plans.

Editorial illustration of travel-planning work: creating a travel itinerary revision log

Create a travel itinerary revision log as a single running table (one line per change) that records what changed, why, when, and what you’re waiting on. Keep it separate from your client-facing itinerary and update it whenever any quoted element moves—dates, routing, flights, hotels, transfers, activities, or traveller details.

This guide gives you a clean structure you can implement immediately, a worked fictional example, and a practical workflow that uses Nowah for the planning surface while your log remains the authoritative record.

What an itinerary revision log does for quoting and proposals

A revision log is an internal control that helps you run a smoother quote-and-proposal cycle.

Use it to:

  • Spot missed changes when multiple moving parts update (supplier availability, client preferences, routing shifts).
  • Keep approvals tidy so you don’t progress based on assumptions.
  • Support handovers if another adviser needs to pick up the file.
  • Limit avoidable rework by making each change explicit (old → new), rather than rewriting drafts from memory.

The minimum viable log: nine fields to capture every time

If your log becomes too complicated, it won’t get used. Start with these fields; they cover the operational “must-haves” without turning into a second proposal document.

Record the reason and scope before editing the Nowah itinerary. The quote version-control guide helps connect that change to the correct proposal.

Field

What to record

Why it matters

Rev ID

REV-001, REV-002…

Lets you reference a specific change unambiguously

Logged date/time + zone

When you recorded it

Reconstructs the timeline during follow-up

Trip reference

Internal trip/file ID

Prevents cross-trip confusion

Snapshot label

Draft A / Draft B (simple)

Ties changes to the draft you updated

Change area

Flight / hotel / transfer / activity / traveller details

Makes scanning fast

Old detail

The detail being replaced

Stops “we always meant…” disputes

New detail

The replacement

Shows the exact delta

Reason

Short code + plain note

Standardises entries and improves reporting

Approval status

Pending / Approved + where recorded

Keeps you aligned with client sign-off expectations

Add two optional fields when you’re ready:

  • Commercial impact (neutral): “re-price required”, “supplier terms to re-check”, “deposit amount may change by supplier”. Avoid guarantees.
  • Next action + owner: “Confirm room needs (A. Smith)”, “Re-check flights (J. Patel)”.

Reason codes that keep your log consistent

Reason codes make your log readable at speed. Use a small list and keep notes short.

  • CR — Client request (direct traveller instruction)
  • SA — Supplier availability/terms change (inventory, schedule, conditions)
  • PC — Price change since last check
  • AR — Adviser recommendation accepted
  • EC — Error correction (internal)
  • SC — Scope change (dates/routing/party/room needs)
  • OT — Other (explain in one sentence)

How to write each revision line (so it’s actually useful)

A strong log line is “atomic”: one change, one reason, one approval state.

Describe what changed in the Nowah day plan and why the client needs to decide. The itinerary update email guide supports a concise explanation.

Write each entry so someone unfamiliar with the trip can answer:

  1. What exactly changed? (old → new)
  2. Why did it change? (reason code)
  3. Is it approved? (and where is that approval captured)
  4. What must happen next?

Practical rules:

  • Split combined requests. If the client changes a hotel and adds an activity, that’s two lines.
  • Don’t hide uncertainty. If something is proposed but not confirmed, write “proposed” in the New detail and keep Approval as Pending.
  • Don’t rewrite history. If you refine a change later, add a new line rather than editing the old line into a new reality.

Worked fictional example: “Trip JPN-CHEN-2027”

Scenario (hypothetical): Family of four (2 adults, children aged 8 and 12). Target travel window: 10–22 March 2027, with 12 nights and 13 destination days. Routing: Tokyo → Hakone → Kyoto → Osaka. You’re in planning and quoting mode; nothing is paid until the client approves and you are ready to transact under supplier terms.

For the fictional Japan revisions, compare each Nowah route against the dated log. The multi-city planning guide helps review the effect of each hotel move.

1) Build the initial structure in Nowah

Start by using Nowah to generate a paced, coherent day-by-day plan you can refine. This is where Nowah is especially valuable: it helps you get to an editable itinerary draft quickly, then you apply professional judgement and supplier checks.

Copyable Nowah prompt (fictional brief):

“Create a 13-day, 12-night Japan itinerary for a family of 4 (2 adults, children aged 8 and 12). Route: Tokyo (4 nights), Hakone (2), Kyoto (4), Osaka (2). Arrival 10 March and departure 22 March 2027. Provide a day-by-day outline with a balanced pace for kids (no starts before 08:00). Clearly mark transfer days. Suggest family-suitable hotel types (not brand-dependent). Flag elements that typically require advance booking. Use a simple structure: morning / afternoon / evening.”

What you check before you treat the draft as usable:

  • Transfer days aren’t overloaded.
  • Distances and timing are plausible (no “teleporting”).
  • Any “advance booking” flags make sense (and you’ll verify specifics later).
  • The plan matches the brief’s pace and family needs.

Log line:

Rev ID

Logged date/time + zone

Trip ref

Snapshot

Area

Old detail

New detail

Reason

Approval

Next action

REV-001

2026-11-19 09:10 UTC

JPN-CHEN-2027

Draft A

Whole itinerary

—

Initial itinerary draft created in Nowah

OT: baseline from brief

Internal draft, not client approval

Prepare client draft in agency tool

2) Client requests two changes

Client requests: (a) include a Ghibli-themed activity in Tokyo, (b) prefer a ryokan-style stay in Hakone.

Split these into two log entries:

Rev ID

Logged date/time + zone

Trip ref

Snapshot

Area

Old detail

New detail

Reason

Approval

Next action

REV-002

2026-11-20 10:05 UTC

JPN-CHEN-2027

Draft B

Tokyo activity

Day 3 afternoon: general museum time

Day 3 afternoon: Ghibli-themed option (to validate availability)

CR: client preference

Preference approved (email 20 Nov); booking pending

Research options + constraints

REV-003

2026-11-20 10:07 UTC

JPN-CHEN-2027

Draft B

Hakone lodging type

Family hotel-type stay

Ryokan-style stay, family-appropriate

CR: accommodation style

Style approved (email 20 Nov); booking pending

Shortlist ryokan-type options

3) Supplier availability forces an alternative

Your checks show the first Tokyo option can’t be secured in the requested window. You propose an alternative that still meets the theme and fits the day’s geography.

Rev ID

Logged date/time + zone

Trip ref

Snapshot

Area

Old detail

New detail

Reason

Approval

Next action

REV-004

2026-11-21 16:20 UTC

JPN-CHEN-2027

Draft C

Tokyo activity

Ghibli-themed option #1

Proposed themed alternative #2, availability to recheck

SA: first option unavailable

Direction approved (email 21 Nov); booking pending

Update itinerary text + check timing

4) Scope changes: extra traveller for part of the trip

Client adds: “A grandparent may join for Kyoto only.” That impacts rooming and pacing. Keep it clearly bounded.

Rev ID

Logged date/time + zone

Trip ref

Snapshot

Area

Old detail

New detail

Reason

Approval

Next action

REV-005

2026-11-22 09:40 UTC

JPN-CHEN-2027

Draft D

Travellers

2 adults + 2 kids

+1 adult (Kyoto segment only, tentative)

SC: party change

Pending

Confirm Kyoto dates + room needs

5) Use Nowah to re-draft after multiple edits

Once several edits stack up, use Nowah again to regenerate a coherent itinerary narrative so you’re not patching text endlessly.

Copyable Nowah revision prompt:

“Revise the 13-day, 12-night Japan family itinerary from the current draft: (1) research a themed alternative for Tokyo on Day 3 afternoon, without assuming tickets exist, (2) change Hakone to a ryokan-style family-appropriate stay, and (3) add a tentative extra adult joining for Kyoto only—highlight rooming/pacing implications. Output an updated day-by-day plan and explicitly list what changed.”

How you review the output against your log:

  • Confirm each approved revision (REV-002/003/004) appears once and only once.
  • Confirm tentative items (REV-005) are still labelled tentative.
  • Check for new additions that were never requested; if you adopt them, log them as new revisions.

Nowah’s editable itinerary structure and map/timeline views (see /features) are useful here because you can stress-test pacing after changes—then document each accepted change in your log.

Copy/paste revision log template (agent-ready)

Put this in a spreadsheet or document table. Keep it simple enough that you can update it between supplier checks.

TRIP ITINERARY REVISION LOG
Trip reference:
Lead adviser:
Created date:

| Rev ID | Logged date/time + zone | Snapshot label | Change area | Old detail | New detail | Reason (code: note) | Approval status (pending/approved + source) | Commercial impact (neutral) | Next action + owner |
|--------|------------------|----------------|-------------|------------|------------|---------------------|--------------------------------------------|----------------------------|---------------------|
| REV-001|                  |                |             |            |            |                     |                                            |                            |                     |

If you want a quick standard list for “Change area”, use: Traveller details, Dates, Routing, Flights, Hotels, Transfers, Ground transport, Activities, Other.

Approval micro-script (built for clean logging)

Use a consistent message whenever a change affects cost, supplier terms, or the on-the-ground experience. This is not a software feature—just an agency script that makes your Approval column easy to complete.

Copyable text:

“Confirming the change for Trip [REF]:

  • Change area: [Flights/Hotel/etc.]
  • From: [old detail]
  • To: [new detail]
  • Notes/assumptions: [one line]

Reply ‘Approved’ to proceed with updating the itinerary/quote. This approves updating the planning version only. Before any booking or payment, we will send the exact selected offer, total and supplier conditions for separate approval. Supplier terms govern bookings, changes and refunds.”

When the client replies, update the log: Approved (email YYYY-MM-DD HH:MM) or your internal equivalent.

A lightweight review routine to keep logs healthy

Review pending changes at a cadence suited to each file. A weekly review does not replace action before an earlier supplier deadline. Filter for pending decisions, assign an owner and due time, and distinguish permission to research from authority to book. Add a time zone to every deadline and timestamp so another adviser can interpret it. A clear itinerary revision log makes proposed changes and unanswered approvals visible—especially when you pair the log with Nowah as your planning workspace.

Build your next draft itinerary in Nowah at Open Nowah, and review trip-planning capabilities on /features.

Share this article