UnityTrip vs Nomadis.

Nomadis, in its own words

Nomadis positions itself as a "leading cloud software platform for workforce logistics" — an integrated suite covering workforce management (demand forecasting, crew rotations with complex patterns, staffing requirements), travel management (bookings generated automatically from work schedules, across commercial and charter transport, with GDS integration), charter management with departure control and manifesting, camp and accommodation management with automated housekeeping, compliance validation before travel, and safety features including mustering and a real-time people locator. It serves mining, energy and resources, construction, healthcare, and government, in English, French, and Spanish.

That is a serious, mature platform with two decades of production behind it — and of every product in this field, it automates the movement half of rotational travel most completely: the roster fires the booking, and no human intervenes.

The difference is what counts as the hard problem

For Nomadis, the hard problem is scheduling: get the right people to the right site on the right rotation, with compliance validated and a bed waiting. For UnityTrip, the hard problem starts where the schedule ends: the seat has no fare, so policy has to do the job price does everywhere else — a priority matrix, quotas, booking windows, and penalty points rationing scarce seats among competing claims, executed by a deterministic engine over an event-sourced record that makes every decision reproducible.

No-shows illustrate the philosophies exactly. Nomadis tracks no-shows for contractor chargebacks — cost recovery after the fact. UnityTrip treats a no-show as a seat to refill: penalties discourage it, and go-show automation offers the freed seat to a waiting traveller minutes before departure — recovering the seat in the moment rather than the cost afterwards.

The same difference runs through the money. In UnityTrip, budget approval runs in the booking flow, expense claims live in the same platform, and for business bookings no payment executes without an approved claim number — travel spend reaches finance as governed data. This is the tenth of the ten evaluation questions — does the platform govern the money as well as the movement — and it is the question this comparison turns on.

What UnityTrip puts on the table

• Policy as the economic instrument — priority, quotas, booking windows, and penalty points allocating seats that have no fare, executed deterministically and published as a JSON Schema.
• Go-show automation — freed seats refilled before departure, contributing to no-shows down by roughly half and utilisation lifted from a ~40% industry average to around 90%.
• The money loop closed — budget approval in the booking flow, expense claims in the same platform, no payment for business bookings without an approved claim number, and bidirectional SAP integration in production.
• Published depth — the API and ontology reference, the platform thesis, and measured outcomes stated plainly rather than implied.
• Cloud-marketplace procurement — transactable on the Microsoft Azure Marketplace, billed through your existing Microsoft agreement.

Where Nomadis is strong

Honest scorekeeping: twenty-plus years in production, the most complete roster-to-booking automation in the field, camp operations with housekeeping workflows, mustering and people-location for emergencies, a healthcare vertical, and trilingual delivery are real advantages. An organisation whose binding problem is workforce scheduling and camp operations may reasonably anchor there. UnityTrip's answer is the same as everywhere else in the stack: integration rather than replacement — rosters and HR systems plug in beneath the policy layer, and UnityTrip governs the travel they generate.

Choosing between them? The ten evaluation questions separate the architectures — put them to every vendor, including us.

Common questions