Skip to main content

PDF formats of an itinerary

This article outlines the available PDF formats for itineraries each designed for specific documentation needs.

Updated over a month ago

In managing itineraries, having the right format for documentation is essential for clarity and convenience. This article explores the four different PDF formats available for itineraries. Each format serves a unique purpose, catering to different needs and ensuring that important information is presented effectively.

Below is an overview of each format and how it can be used to enhance itinerary management:

  • Draft PDF

  • Voucher PDF

  • Trip Summary PDF

  • Condensed PDF


Draft PDF

The Draft PDF provides an overview of the itinerary, including data about the trip, bookings and accommodation.

Important note: The bookings are listed by execution date and time.

Note: Pricing information for each booking is not included.

This format includes the itinerary's creation date, Trip ID, itinerary name, and the ITINERARY INFO section. Additionally, it features the ITINERARY SCHEDULE.

The ITINERARY INFO displays the following basic details:

  • GUEST: Name of the Trip Leader

  • FROM: Arrival date

  • TO: Departure date

  • GUESTS: Number of guests

  • NIGHTS: Number of nights

It also includes the company's welcome message, along with any additional information included in the Info section of the Guest app, which is retrieved from the Guest App Configuration (found in the left-hand menu under More > Guest Facing > Guest App > Home).

Additionally, it provides details on the company's support hours, also sourced from the Guest App Configuration (found in the left-hand menu under More > Guest Facing > Guest App > Support).

Each booking section includes the following details:

  • Booking ID: The unique identifier for the booking, along with the name of the product booked.

  • Execution DATE and TIME: The scheduled date and time of the booking.

  • SELECTIONS & ADDONS: Participants and quantities, along with the pricing name and any selected addons.

  • Additional Information: Details such as the group (subservice), number of passengers/luggage, and the selected resource (if applicable).


Voucher PDF

The Voucher PDF provides an overview of the itinerary, including data about the trip, bookings and accommodation.

This format includes the same information as the Draft PDF, with an added note indicating that it can be used as a voucher: "Can be used as voucher. Show this at time of service."

Important note: The bookings are listed by execution date and time.

Note: Pricing information for each booking is not included.


Trip Summary PDF

The Trip Summary PDF offers a comprehensive overview of the entire itinerary, including travel dates, duration of stay and key details. It highlights the main aspects of the trip for easy reference.

Important note: The bookings are listed by creation date.

Note: Pricing information for each booking is included.

This format includes the itinerary's creation date, Trip ID, itinerary name, and the ITINERARY INFO section, as well as the ITINERARY SUMMARY.

The ITINERARY INFO displays the following basic details:

  • GUEST: Name of the Trip Leader

  • FROM: Arrival date

  • TO: Departure date

  • GUESTS: Number of guests

  • NIGHTS: Number of nights

It also includes the company's welcome message, along with any additional information included in the Info section of the Guest app, which is retrieved from the Guest App Configuration (found in the left-hand menu under More > Guest Facing > Guest App > Home).

Additionally, it provides details on the company's support hours, also sourced from the Guest App Configuration (found in the left-hand menu under More > Guest Facing > Guest App > Support).

The ITINERARY SUMMARY displays the Total Itinerary Cost, along with the bookings associated with the itinerary, organized by product type (Experiences, Restaurants, Transfers, Rentals, Services, Accommodation).

Each booking includes the following details:

  • Booking ID: The unique identifier for the booking, along with the name of the product booked.

  • Session(s): Provides details about the booked session, such as the execution date and time, duration and the number of passengers or luggage, if applicable.

  • Selections & Addons: Outlines pricing selections and addons chosen.

  • Amount: Specifies the number of participants or quantity for each pricing selection and addon.

  • Total: Presents the overall total cost for the booking, including all selections and addons.


Condensed PDF

The Condensed PDF offers a streamlined, chronological list of all bookings, providing basic information and the status of each reservation for quick reference.

Important note: The bookings are listed by execution date and time.

Note: Pricing information for each booking is not included.

This format includes the itinerary's creation date, Trip ID, itinerary name, and the ITINERARY INFO section. Additionally, it features the BOOKINGS section.

The ITINERARY INFO displays the following basic details:

  • GUEST: Name of the Trip Leader

  • FROM: Arrival date

  • TO: Departure date

  • GUESTS: Number of guests

  • NIGHTS: Number of nights

It also includes the company's welcome message, along with any additional information included in the Info section of the Guest app, which is retrieved from the Guest App Configuration (found in the left-hand menu under More > Guest Facing > Guest App > Home).

Additionally, it provides details on the company's support hours, also sourced from the Guest App Configuration (found in the left-hand menu under More > Guest Facing > Guest App > Support).

The BOOKINGS section provides a list of the bookings included in the itinerary, organized by their execution date and time.

Each booking includes the following details:

  • Booking: The name of the product booked.

  • ID: The booking ID.

  • Date: The execution date of the booking.

  • Time: The execution time of the booking.

  • Participants: The number of participants.

  • Status: The current status of the booking.



​

Did this answer your question?