1. Travel Expense Optimizer
  2. Features
  3. Fare comparison
Feature · Fare comparison

Fare comparison

Gather fare and route options for each trip, each quoted on a date under a named policy version, and submit the preferred one for review.

OverviewPending Review
Travel Expense Optimizer · Fare comparison

Pending Review

Approval conditions

New
ParentRouteQuoted atFare USDPolicy versionRevision
BKN-98904RTE-56213 Oct480Rev A130
BKN-80096RTE-14913 Oct940Rev B830
BKN-94433RTE-91521 Oct590Rev C450
BKN-82311RTE-78826 Oct250Rev D700
BKN-90163RTE-78911 Oct420Rev E710
6 of 6 records
RTE-562Travel options · TO-59321
ParentBKN-98904
Quoted at13 Oct
Fare USD480
Policy versionRev A
Revision130
Example screen with sample data

What you can do

Compare before you choose

For each trip the coordinator gathers the realistic options: the direct flight and the one-stop, the preferred hotel and the one next to the client’s office, the train and the plane. Each option records its route, the date it was quoted, the fare in US dollars and the travel policy version it was checked against. Options sit under the booking, so the approver sees every alternative the coordinator considered alongside the chosen one.

Options start as Draft. The coordinator submits the preferred option for review with supporting evidence, such as a screenshot of the fare search. Route, quote date, fare and policy version are checked against that evidence, and the submitted version is frozen. An approved option is still only a quote: the supplier’s own confirmation is needed before anything is booked.

How the work is organized

  • Several options per trip. Record each realistic alternative with route, quote date and fare.
  • Policy version on every option. The option names the policy version that applied when it was quoted, so a later policy change does not rewrite past decisions.
  • Submit one, keep the rest. The preferred option is submitted for review. The others stay on the trip as the comparison.

What to agree during setup

Agree how many options a coordinator should gather for each trip type, for example three for flights over 500 USD. Agree how policy versions are named, such as “Travel Policy 2026.1”. Agree what evidence must back a submitted option, and how long a quote stays valid before it must be refreshed. Agree how routes are written, for example origin, destination and connection.

Check the handoff on an actual case

A consultant needs to fly from Boston to Denver for a client workshop on April 8. The coordinator records three options: a nonstop at 612 USD, a one-stop via Chicago at 438 USD and a nonstop the evening before at 455 USD, all quoted on March 20 under policy 2026.1. Policy allows the lowest logical fare within two hours of the preferred time.

The coordinator submits the evening-before nonstop, attaching the fare search. The approver compares it with the other two options on the trip and approves it: it is within policy and avoids an early-morning connection. The nonstop on the day stays on record as the option not chosen.

What your team sees

  • Fare Comparison — All options for each trip with route, quote date, fare, policy version and status.
  • Approved Options — Options approved for booking, with fare, policy version and decision date.

Follow the work through

Review the data model before importing open trips.

What it keeps track of

Data model
Travel options
Fare and route options submitted for independent review before selection.
Bookings
Travel booking records with lifecycle, quoted amount and counterparty.
Record attachments
Uploaded evidence files attached to a booking parent.

Who uses it

Permissions
Travel Coordinator
Gathers and submits options.
Travel Approver
Reviews submitted options.
Travel Manager
Reads the comparison to tune the policy.
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.

How to get started