Trips
How trips work as operational containers for client travel plans and linked proposals in Ghloria.
Trips
A trip is the operational container for a client's travel plan. It holds the client record, the destination, the dates, and one or more proposals — which are the commercial workspace where pricing, itinerary, and presentation content live.
Use trips to keep all the commercial options for the same client travel plan in one place, even when you are working on multiple versions or alternatives.
Trips vs Proposals
| Trip | Proposal | |
|---|---|---|
| What it is | The operational container for a client trip | The structured commercial offer inside that container |
| Holds | Client, destination, dates, linked proposals | Flights, accommodation, itinerary, budget, presentation content |
| Visibility | Internal — workspace only | Can be shared publicly with the client via a link |
| Count | One trip per client travel request | Many proposals per trip |
A single trip can contain multiple proposals — for example, one budget option and one premium option for the same Japan trip. Each proposal is edited independently, but they all belong to the same trip record.
Creating a Trip
Go to Trips → New Trip
Open Trips in the sidebar and click New Trip, or create a trip directly from a proposal's detail page.
Set the client
Choose an existing client from the search, or enter a new client's name, email, and phone directly from the trip creation form. All proposals inside this trip must belong to the same client.
Add a title (optional)
Give the trip a working title — for example, "Japan Spring 2026" or "Morocco Honeymoon". If left blank, the trip will appear as untitled in the list.
Save and open the trip
After creating the trip, the trip detail page opens. From here you can create proposals, link existing proposals, upload files, and monitor the trip's overall status and value.
Trip Detail Page
The trip detail page shows everything attached to a trip in one place.
Client card — the linked client name, email, and contact. Click the client name to open the full client profile.
Trip summary — destination, start and end dates, status, total value, and proposal count.
Proposals table — all proposals linked to this trip. Each row shows the proposal name, agent, destination, status, last updated date, and value. Click any row to open that proposal.
Files — documents attached to the trip directly, separate from proposal-level files. You can drag and drop files onto the trip detail page to upload them.
Trip Value
The trip total value shown on the trip detail page and in the trips list is the average of all open proposals in the trip. It is labeled Potential trip value while no proposal is closed, and changes to Trip value once at least one linked proposal reaches closed status.
This means the number reflects commercial intent, not a confirmed booking amount, until a proposal is closed.
Linking Proposals to a Trip
You can connect an existing proposal to a trip from two places:
- From the proposal detail page — use the trip assignment card to select an existing trip for the same client or create a new one.
- From the trip detail page — use Link proposals to select from eligible proposals for the same client.
A proposal can only belong to one trip at a time. Reassigning a proposal to a different trip moves it completely — if that leaves the original trip empty, the empty trip is deleted automatically.
Trip Statuses
| Status | Meaning |
|---|---|
| Draft | Trip is being scoped, no active proposals yet |
| Open | Trip is active with at least one open proposal |
| Closed | Trip has been completed or won |
| Cancelled | Trip has been abandoned |
Trip status is derived from the proposals it contains and is managed by the backend. You do not set the trip status manually.
Deleting a Trip
Destructive action
Deleting a trip also deletes every proposal linked to it. This cannot be undone. A confirmation dialog explains this before the action is committed. Trip deletion is only available to Managers and workspace owners.
Starting from a Proposal Instead
If your workflow starts with a proposal rather than a trip, Ghloria handles that too. A proposal created without an explicit trip is automatically placed in a new trip containing only that proposal. You can later assign it to a different trip, merge it with others, or leave it as the sole proposal in its own trip.