Live Itineraries for Travellers and Support Teams

Solution design

The current travel plan has an identifiable version

The itinerary platform records dependencies between booked services and separates draft amendments from the approved travel plan. Supplier confirmations, required traveller acceptance and related adjustments stay attached to each change. Publication creates a recognizable current version for travellers and support. Operations retains the history needed to explain a revision and resolve its effect on connected services.

Booked services, amendments and support conversations share a booking reference. The portal and downloadable itinerary use the same approved information. Operations can see affected services, missing supplier confirmations and important updates the traveller has not yet acknowledged.

• Portal and downloaded plans share an approved version
• Changes expose their effects on other booked services
• Support can distinguish proposed and confirmed arrangements

Business context

A travel operator assembling accommodation, transfers and activities from several suppliers into multi-service itineraries.

Core capability

Software Development

The itinerary remains active after the booking is made

A pickup point changes, an activity moves to a later time or an adviser adds a service. Each update can create a new attachment in a different email thread. The booking may be valid while the traveller and support team are reading different plans. The uncertainty becomes urgent when somebody needs an answer during travel.

The platform treats the itinerary as a published record with a change history. Booked services, proposed amendments and approved traveller instructions occupy distinct states. Staff can see what the traveller currently expects and compare it with supplier confirmations, rather than assuming that the newest document in an inbox represents the agreed trip.

An amendment can reach beyond the item being edited

Each itinerary service has its supplier reference, local time, participants and dependencies. A delayed arrival can affect a transfer and the first activity while leaving accommodation unchanged. A cancellation may remove one traveller from a group service rather than cancel the entire booking. These relationships allow operations to identify the precise arrangements needing review.

Informational corrections and commercial amendments use different approval rules. Clarifying a meeting point is not the same as replacing a paid service. The amendment record identifies the proposed change, its authority, supplier response and any traveller acceptance or payment adjustment required. Staff can review that chain without inferring approval from a modified PDF.

Draft changes do not silently alter the traveller's plan

The booking remains the commercial reference. Its structured itinerary contains scheduled services and the information needed to use them. Publication creates a version identifier, timestamp and summary of meaningful changes. The portal and downloadable documents are generated from that version, so a print layout cannot develop a separate set of dates or instructions.

Supplier messages enter a review queue with source references. Duplicate updates attach to the same amendment rather than producing repeated changes. Service times retain their local timezone and a reference suitable for ordering events across locations. Incomplete supplier information remains pending until operations resolves it; it does not appear as a confirmed instruction.

A saved copy needs a clear relationship to the live plan

The traveller sees the upcoming services, locations, timings and documents needed for each stage. The complete itinerary remains available, with a version marker and last-updated time on both online and downloaded views. Printable information supports limited connectivity, and the help route explains what to do if a saved copy conflicts with a later message.

Notifications describe the change and the action needed. Important instructions can require acknowledgement; a minor wording correction does not carry the same demand. Delivery, opening and acknowledgement remain separate facts. The operating queue can therefore show an urgent unacknowledged update without claiming that sending a message means the traveller has understood it.

The reply starts with the booking history

Support conversations link to the booking and the relevant itinerary version. Staff see approved arrangements, outstanding amendments and earlier commitments before responding. Automated assistance is limited to maintained information and permitted actions. A question about an unconfirmed service or a requested booking change reaches an authorised person with the conversation attached.

Disruption has its own urgency and escalation route. Failed messages, unreachable travellers and unresolved supplier responses stay visible against upcoming services. Travel documents and personal details are limited to the roles that need them. A support agent can explain the plan without broad access to every document collected for every traveller in the booking.

The first itinerary type includes a disrupted journey

The initial release follows one itinerary type through a supplier amendment, approval, publication and traveller acknowledgement. Tests include competing edits, duplicate messages, timezone boundaries, partial group cancellation and a traveller who cannot be reached. The review checks the resulting instructions and the work left in the operations queue, not simply that a notification was generated.

Existing bookings enter only after operations checks their current arrangement against the source records. An old attachment may omit an agreed amendment. Cutover identifies which bookings remain in the earlier process and prevents both systems from sending updates. An outage log preserves manual decisions for review and reconciliation when publication resumes.

The owner of a change is visible

Operations owns service details and supplier confirmations. Advisers handle the commercial consequences of amendments, and support owns traveller questions and disruption reports. Engineering maintains integrations and publication controls. The record identifies whose decision is outstanding, so a proposed change does not sit indefinitely in a shared document that everyone can edit.

Repeated corrections point to maintainable problems. A supplier whose pickup instructions often change needs a better information route. Questions about what a service includes may require a product-content correction before travel begins. Reviews use those patterns to improve the source record and wording, rather than increasing the number of reminders sent to travellers.

The next departure gives an unresolved change its urgency

Reporting follows approved amendments through publication and delivery. Pending supplier confirmations are considered against the affected service time, not just the age of the case. Operations can see which dependency threatens the next stage of travel and whether a traveller still needs to accept or acknowledge an instruction.

Support review includes repeat contact and resolution quality alongside response time. A fast answer from an outdated itinerary creates more work. Version history, approval records and conversation references allow a supervisor to inspect the answer in context and identify whether the source data, handoff or response needs correction.

The choices behind the solution

How the solution is evaluated

These measures define the evaluation criteria for the workflow, its controls and the quality of completed tasks.