> ## Documentation Index
> Fetch the complete documentation index at: https://help.odia.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Confirmed Journeys

> Confirmed trips are managed in the same Journey workspace, not in a separate itinerary screen.

## What Are Confirmed Journeys?

A Confirmed Journey is a trip that has moved from sales into operations. It uses the same Journey you built and published earlier.

Confirmed Journeys are where you manage:

* Supplier details
* Purchase orders
* Service statuses
* Traveller assignments
* Files, tickets, and vouchers
* Tasks and communications
* Invoices
* Public link updates

**To confirm a Journey,** set its status to **Confirmed**. A short confirmation dialog appears — confirming marks the Journey as confirmed and publishes its latest version. You can keep editing and publish again afterwards.

<Note>
  Confirming a Journey doesn't lock it — you can keep editing services and pricing, and publish again whenever the public link should show your changes. The one difference: on a confirmed Journey, services can be **cancelled** rather than deleted, so you keep an accurate operational record.
</Note>

## Finding Confirmed Journeys

Go to **Journeys** and select the **Confirmed** view.

You can filter by date, owner, and status, and search by title or traveller-facing headline.

## Working In A Confirmed Journey

Open the Journey and use the main tabs:

| Tab                 | Purpose                                                                         |
| ------------------- | ------------------------------------------------------------------------------- |
| **Areas**           | Manage destinations and the area timeline                                       |
| **Journey Builder** | Manage services, content cards, and trip or day summaries in board or list view |
| **Travelers**       | Manage travellers and service assignments                                       |
| **Pricing**         | Review revenue, cost, margin, and commission                                    |
| **Invoicing**       | Create and manage invoices                                                      |
| **Tasks**           | Track operational work                                                          |
| **Communications**  | Review related emails and messages for this Journey                             |

## Adding Or Editing Services

Use the **Journey Builder**:

<Steps>
  <Step title="Add a service">
    Click the **+** button on the correct day and choose a service from the Library.
  </Step>

  <Step title="Edit service details">
    Open the service to update dates, times, supplier, contact, travellers, files, pricing, and notes.
  </Step>

  <Step title="Save">
    Click **Save Changes** when the save bar appears.
  </Step>

  <Step title="Publish when needed">
    If the change should be visible to the traveller or agent, publish again.
  </Step>
</Steps>

## Purchase Orders

Before sending a purchase order:

1. Add the supplier
2. Add the supplier contact if needed
3. Complete mandatory PO fields
4. Preview the email
5. Send it from the connected inbox

The message is stored on the service so the team can review the communication history.

## Public Link

Confirmed Journeys use the same public Journey link. You can also download it as a PDF: open the web Journey, select the **three-line icon** in the top-right corner, toggle **Photos** and **Branding**, then select **Download PDF**. Anyone with the public link can do the same.

<Warning>
  If you see **Unpublished changes**, the public link is not showing the latest saved work yet. Publish again when the client or travel agent should see it.
</Warning>

Examples that usually need publishing:

* New or removed service
* New pickup time, address, or description
* Uploaded voucher or traveller-facing file
* Updated display settings
* Changed public layout

Master data changes, such as editing a supplier profile or CRM contact, are managed separately in the CRM and may appear wherever that master data is used.