One PNR, or two systems with a shared screen?
A rotation is one journey — a commercial leg, a charter leg, a bus, a room. Ask whether charter and commercial content genuinely share one booking record and one policy engine, or whether two systems are stitched together at the interface. The difference decides how disruption recovery, duty of care, and spend reporting behave.
UnityTrip runs one booking engine, one PNR, and one policy layer across owned, wet-leased, dry-leased, and commercial content.
A policy engine, or a manifest tool?
Recording who is on the aircraft is table stakes. Ask what happens when demand exceeds seats: is there a priority matrix, quotas, booking windows, penalty logic, and displacement rules — enforced deterministically, with an explanation when the answer is no — or a coordinator resolving it by email?
UnityTrip's rule engine executes an operational ontology: allocation decided identically every time, auditable, and explainable in plain English. The free Policy Builder shows the model.
Does spend post to finance, or export to a spreadsheet?
Travel that never reaches the ERP never reaches budget control. Ask whether the platform posts to your finance system bidirectionally, enforces budget approval at the point of booking, and accounts for leased travel — which most spend reports value at zero because the seat has no fare.
UnityTrip runs bidirectional SAP integration in production and enforces budget approval in the booking flow. The Travel Spend Diagnostic measures how much of your spend currently bypasses it.
What happens at twenty times normal load?
Look-to-book surges correlate exactly with disruption: a cyclone closes a site and every affected worker searches at once. A platform's worst load day is your worst operational day. Ask what the architecture actually is — and read the vendor's engineering job advertisements to find out what their system is made of.
UnityTrip is event-sourced and natively distributed, designed to absorb surges of 10 to 1000 times normal activity. See the architecture.
What is the measured utilisation outcome?
Every vendor claims efficiency. Ask for a published, quantified before-and-after on seat utilisation and no-shows — and for the methodology behind it.
UnityTrip publishes its production numbers: ~40% industry-average utilisation lifted above 90%, no-shows down roughly half. See the benchmarks, with methodology, reusable with attribution.
Can it see a rogue identity inside a trusted network?
Perimeter security assumes the threat is outside. A misconfigured script — or, increasingly, a misbehaving AI agent — inside a client's trusted network forces a perimeter-only architecture into a bad choice: block all the client's traffic, or stay open and degrade. Ask how the platform identifies and isolates a single identity in real time.
UnityTrip has done this in production: per-identity observability down to the email address, with the offender isolated and the client unblocked.
Can procurement buy it the way they already buy cloud?
Enterprise procurement is part of the total cost. Ask whether the platform is transactable through a cloud marketplace where your commercial terms, security review, and billing relationship already exist.
UnityTrip is available on the Microsoft Azure Marketplace.
Does it work where travel is booked offline?
In many operating markets, hotels are arranged by email and flights by phone. Ask whether the platform can bring offline bookings under policy governance, or whether it assumes every booking starts in its own interface.
UnityTrip runs in production in exactly these markets: roughly 80% of one client's travel logistics — previously considered too complex to automate — now runs as policy-governed workflow, offline flows included.
How does accommodation join the policy?
For remote operations the bed is as contended as the seat. Ask whether camp and guesthouse accommodation is governed by the same policy engine as transport — same priority, same quotas, same audit trail — or managed in a parallel system with its own rules.
UnityTrip integrates Elina PMS so rooms are booked within the same policy layer as seats. See partners and integrations.
A note on vocabulary: this category answers to different names in different markets — FIFO travel in Australia, camp and crew logistics or rotational workforce travel in North America, rotational travel in Africa and the Middle East. The questions are the same everywhere. For the rotation-specific detail, see FIFO travel management.