These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Travel Expense Optimizer
- Features
- Trip bookings
Trip bookings
Carry each trip from request through hold and confirmation to completion, with the supplier units it reserves.
OverviewCompleted Bookings×
Travel Expense Optimizer · Trip bookings
New
Completed Bookings
Bookings
| Record number | Subject | Customer name | Counterparty | Quoted amount USD | Starts at | |
|---|---|---|---|---|---|---|
| BKN-22404 | Completed bkn-247 | Customer 139 | RSR-3402 | 950 | 22 Oct | |
| BKN-71618 | Completed bkn-401 | Customer 945 | RSR-3675 | 750 | 06 Oct | |
| BKN-28492 | Completed bkn-690 | Customer 553 | RSR-6722 | 720 | 06 Oct | |
| BKN-72335 | Completed bkn-883 | Customer 300 | RSR-7949 | 780 | 21 Oct | |
| BKN-51275 | Completed bkn-508 | Customer 429 | RSR-6280 | 700 | 16 Oct |
6 of 6 records
Completed bkn-247Bookings · BKN-22404
Customer nameCustomer 139
CounterpartyRSR-3402
Quoted amount USD950
Starts at22 Oct
Completed at15 Oct
What you can do
One record for the whole trip
A booking is one trip for one traveler or client: a record number, a subject such as “Chicago customer visit”, the traveler’s name, start and end dates, the quoted amount in US dollars, the supplier and the coordinator who owns it. It moves through Requested, Held, Confirmed, In Progress and Completed, or ends as Cancelled or no show. Every change raises the booking’s revision, so approvals and payments always refer to the version they saw.
When a fare is approved, the coordinator places a hold with the supplier. The hold expires if it is not confirmed in time. Reserved resource lines record what is claimed against the supplier’s capacity: the resource, the units reserved, any buffer time before and after, and the confirmation date once the supplier confirms.
How the work is organized
- Request first. Every trip starts as Requested with dates, traveler, quoted amount and supplier, before any fare is booked.
- Hold, then confirm. An approved trip is Held with its reserved units. It becomes Confirmed only when verified payment evidence exists.
- Travel and close. The trip moves In Progress when travel starts and Completed when it ends, with the completion date recorded.
What to agree during setup
Agree how subjects are written so the board reads well: purpose, then destination. Agree how long a hold may stay open before it expires, by supplier type. Agree what reserved units mean for each supplier, such as seats for a flight or rooms for a hotel. Decide who owns a trip when the requesting coordinator is away. Agree how far ahead trips should be requested.
Check the handoff on an actual case
A coordinator records a booking for a sales engineer: Chicago customer visit, March 10 to 13, quoted at 1,450 USD with the hotel group HG-CHI. The fare option is approved the same day. The coordinator holds three room nights; the reserved line shows one room for three nights against the hotel’s allocation, and the hold expires in 24 hours.
The card payment is captured that afternoon and the booking moves to Confirmed, with the supplier’s confirmation date on the reserved line. On March 10 the trip moves In Progress and on March 13 it is Completed. If the payment had not arrived before the hold expired, the room would have been released and the coordinator would have placed a new hold.
What your team sees
- Trip Calendar — Held, confirmed and in-progress trips by start and end date, with traveler and supplier.
- My Bookings — The signed-in coordinator’s own trips with dates, quoted amount, revision and status.
- Reserved Resources — Reserved units, capacity and confirmation dates by booking and supplier.
Follow the work through
- Request to approved fare: Request the trip and approve its fare.
- Hold to confirmed booking: Hold, pay and confirm.
- Cancellation and no-show: Cancel or close a trip that did not happen.
Plan the rollout with your coordinators.
What it keeps track of
Data model- Bookings
- Travel booking records with lifecycle, quoted amount and counterparty.
- Booking resources
- Reserved resource lines attached to a booking parent.
- Resources
- Eligible travel suppliers and service resources used as booking counterparties.
- Team members
- Authenticated platform identities with an active membership in a travel organization.
Who uses it
Permissions- Travel Coordinator
- Requests, holds, confirms and closes trips.
- Travel Manager
- Watches the board and the calendar.
- Payments Analyst
- Reads bookings when checking payment events.
- Admin
- Corrects records and access.
Set up Travel Expense Optimizer your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.