Workforce Aviation Logistics
The logistics of flying your own workforce.
Workforce aviation logistics is the discipline of moving a workforce on aircraft an organisation owns, leases or charters: scheduled private inventory, seats allocated by entitlement rather than price, no-show penalties and go-show automation, and costs posted to finance for seats that carry no fare.
It is not crew rostering and it is not conventional corporate travel. It sits between the two, which is why it is routinely misfiled as one or the other.
One Phrase, Two Categories
Opposite sides of the aircraft door.
The Other Meaning
Aviation workforce management
Crew pairing, rostering, fatigue and legality checking: software for the people who operate aircraft. This is the established airline category, and the one a search for aviation workforce software usually finds.
This Page
Workforce aviation logistics
Moving the people who ride them: engineers, operators, contractors and rotational staff travelling as passengers on the organisation's own aircraft, with entitlement, quotas, penalties and finance posting governing every seat. This is what UnityTrip does.
What the Category Requires
When the seat has no fare, policy is the price.
Scheduled private inventory
Wet-leased and dry-leased aircraft flown on the operation's schedule, with commercial legs in the same booking and one PNR across the whole rotation.
Entitlement, not price
A priority matrix, per-rule quotas and booking windows ration scarce seats deterministically: the same request gets the same answer, with the rule attached.
No-shows and go-shows
Penalty points scaled to departure proximity change behaviour; go-show automation refills a freed seat minutes before departure. No-shows fall by half; utilisation climbs from a 40% industry average to 90%. Basis at benchmarks.
Zero-dollar travel
No fare and no employee reimbursement, so the travel appears in no conventional spend report. Governance happens at booking, or not at all.
Finance posting
Budget approval under delegation of financial authority in the booking flow, and journeys posted to the ERP. For business bookings, no payment without an approved claim number.
Duty of care
One live record of who is aboard what, where: the charter leg, the commercial connection and the accommodation at the end of them.
The common workaround is a stack: a corporate booking tool for the commercial legs, an aviation operations system for the aircraft, and spreadsheets for the allocation between them. It fails at the seam: no shared record, no policy across it, and no answer when finance asks what the fareless seats cost. The spreadsheets are the signal. A workforce operation runs on entitlement, roster, transport capacity, priority, quota and displacement; those rules are the business, not configuration options around a booking workflow, and when the installed software cannot model them the operation builds an offline process around it. Offline travel is the map of the modelling gap. Converting it into governed, configured rules is what this category exists to do. Definitions for every term are in the glossary; the levers and figures in the utilisation benchmarks.
The Thesis
Two channels. Two chokepoints. Approved, or not.
Workforce aviation logistics runs on two channels, separated by a single test: is the trip approved? Business travel is approved: budget approval under delegation of financial authority. Private travel is not approved, and is therefore governed by quota and sanctions. Subsidised travel is still private travel that does not get approved. The channel names are arbitrary; the test is not. "Not approved" never means denied. Private travel is auto-approved, in the precise sense that no approver intervenes: quota, entitlement or the traveller's own payment says yes, deterministically. A person says yes only where delegation of financial authority requires one. Medical travel sits in this channel deliberately, with unlimited quota, so nothing impedes organising a medevac. Which reasons require an authority is an organisational choice, configured per tenant. The test is universal; the mapping is policy.
The classic mistake is to organise the model around content source: commercial versus leased, this booking tool versus that charter desk. Content source is a property; approved or not approved is the only distinction the model turns on. Policies written around content source are why the categories that straddle the seam, rest-and-recuperation travel and dependants' travel, become unmanageable: they look like exceptions in a source-shaped taxonomy, and they are ordinary citizens of a mechanism-shaped one. It took eighteen years to see that clearly.
Two chokepoints enforce the model and together prevent leakage: no traveller can consume a travel service without a platform-issued booking number, and no content provider is paid without an approved claim number. One gate on the demand side, one on the supply side. A request is not a booking; approval turns one into the other, and many bookings can attach to one claim. The claim is a business-channel object: private-channel requests become bookings with no claim at all, because the quota is the approval and no company money moves, which is why most travellers in a rotational operation get the simplest booking experience. Friction is derived rather than imposed: medical travel is frictionless because safety outranks process, private travel because no company money moves, and business travel carries the claim machinery because company money does. On a seat with no fare the money has already moved with the lease, and the claim is still required: the approval is an appointed officer's authority under delegation of financial authority, not a payment. The model is enforced, not merely stated: the published policy schema, version 1.2, encodes the two channels, the test itself a constant in the schema, and a rule declared approved that carries a quota does not validate.
Names
What this discipline is called elsewhere.
The same work carries different names by region and industry. Each emphasises one part of it; none of them changes the two channels or the two chokepoints.
| Term | Where it is used | What it emphasises |
|---|---|---|
| FIFO travel | Australia (Western Australian resources) and Canada (Alberta oil sands, mine sites, construction) | Scheduled rotations flown between home and site |
| Camp and crew logistics | North America (mining, oil and gas, workforce housing) | Travel and camp accommodation managed as one job |
| Crew logistics, crew travel | UK North Sea and North American offshore energy | Moving crews to and from offshore assets, end to end |
| Field crew travel | United States (construction, fibre, pipeline, utilities and energy contractors) | Tracking and lodging mobile crews |
| Rotational workforce travel, rotational travel | UK and global travel management; Africa and the Middle East | The rotation cycle itself: who is on, who is off, and when |
| Personnel logistics | Offshore oil and gas (Norway, Qatar, Canada East) | Personnel on and off installations, with persons-on-board tracking |
| People logistics | Australia (Perth) and enterprise logistics vendors | Moving people with the discipline applied to freight |
| Human logistics | Canada (Quebec) | Travel, camp and rosters treated as one problem |
| Workforce logistics | Canada (Alberta) and Australia (Perth), energy and resources | The supply-chain framing of workforce movement |
| Crew change | International shipping and offshore oil and gas | The timed handover of one crew for another, by air, sea and road |
| DIDO, BIBO | Australia (Queensland coal, NSW Hunter Valley; enterprise agreements) | Drive-in drive-out and bus-in bus-out: the road versions of FIFO |
| Workforce mobilisation, mobilisation and demobilisation | Australia and global energy staffing | Moving a project workforce to site at the start and home at the end |
| Remote workforce travel | Canada (Alberta) | Travel plus accommodation for remote sites |
Each term is defined in the glossary. The FIFO page covers the Australian and Canadian form; the crew change page covers the marine form.
Boundaries
What UnityTrip is, and is not.
These are the boundaries, each with the page that holds it.
UnityTrip is
- Workforce movement on aircraft, vessels and vehicles the organisation owns, leases or charters, alongside commercial travel and accommodation, in one record.
- Policy-driven allocation of seats that carry no fare: priority, quotas, booking windows, penalties and go-show automation, because spend cannot ration what has no price.
- One operational model across booking, approvals, exceptions, claims and the posting to finance, held by two chokepoints: no travel without a booking number, and for business bookings no payment without an approved claim number.
- A way to hold an organisation's own rules as configuration, instead of in spreadsheets, email and custom code.
UnityTrip is not
- A generic corporate booking and expense product. For conventional commercial travel those tools remain the right choice; UnityTrip sits beside them as the child system for the legs they cannot book.
- Crew rostering or flight-operations software. Those manage the people who operate the aircraft; UnityTrip moves the people who ride in it, so an operation can run both.
- A replacement for a travel management company. It is a content source inside the TMC's service, not a rival to it.
- An architecture looking for a problem. The platform is built to outlast its first vertical and the company is travel-first; the architecture is the answer to this operating problem before it is anything else.
Common Questions
What is workforce aviation logistics?
The discipline of moving a workforce on aircraft an organisation owns, leases, or charters: scheduled private inventory, seat allocation under entitlement and quota rules, no-show penalties and go-show automation, zero-dollar travel with no fare and no employee reimbursement, and cost attribution to finance for seats that carry no fare. It is the travel half of workforce logistics, and its closest established ancestor is the airline staff-travel system — entitlements, standby, and quotas — generalised to any organisation's own transport.
What are the two channels of workforce aviation logistics?
Business travel and private travel, separated by a single test: is the trip approved? Business travel is approved, under delegation of financial authority, and carries a claim number. Private travel is not approved and is governed by quota and sanctions; leave and dependants' travel are private, and subsidised travel is still private travel that does not get approved. "Not approved" never means denied: quota, entitlement or the traveller's own payment says yes, and a person says yes only where delegation of financial authority requires one. Medical travel sits in the auto-approved channel deliberately, with unlimited quota, so nothing impedes organising a medevac. Which trip reasons require an authority is configured per organisation. The test is universal; the mapping is policy. Travel content source is a property, not a channel. Two chokepoints enforce the model: no traveller can consume a travel service without a platform-issued booking number, and no content provider is paid without an approved claim number. Both channels run under one policy layer, and the published policy schema, version 1.2, will not validate a rule declared approved that carries a quota.
How is workforce aviation logistics different from airline crew management or rostering software?
They are opposite sides of the aircraft door. Crew management software, the category of crew pairing, rostering, fatigue and legality checking, manages the people who operate aircraft. Workforce aviation logistics moves the people who ride them: engineers, operators, contractors and rotational staff travelling as passengers on the organisation's own aircraft. A search for aviation workforce software usually returns crew-rostering vendors; that is the other meaning. UnityTrip does not replace a crew management system; an operation can run both. One schedules the aircraft and its crew, the other allocates and accounts for every passenger seat.
How is workforce aviation logistics different from corporate travel and expense software?
Corporate travel and expense platforms model one thing: fares purchased from third parties, controlled by spend. In workforce aviation logistics the seat has no fare — the aircraft is paid for whether or not anyone boards — so spend cannot ration demand and policy has to: priority, quotas, booking windows, and penalties. Conventional travel platforms have no concept of an organisation's own aircraft flying half-empty and no mechanism to fill it.
What software do FIFO and energy operators use for flights on owned or leased aircraft?
Historically, spreadsheets and manual coordination — the bulk of rotational logistics was judged too complex to automate. Purpose-built platforms now manage it: one booking and one PNR across charter and commercial legs, a deterministic policy engine for priority, quotas, and booking windows, no-show penalties with go-show automation, and posting to the ERP. UnityTrip is built for this category — policy-governed allocation lifts leased-fleet seat utilisation from a 40% industry average to 90% and cuts no-shows by half. Basis at benchmarks. Ten evaluation questions are in the buyer's guide.
Is workforce aviation logistics the same as personnel logistics or people logistics?
They overlap but are not the same. Personnel logistics, people logistics and human logistics are the labels vendors use for the operational half of this work: rosters triggering bookings, charter flights, camps, manifests, mustering. Workforce aviation logistics covers that and the governing half: policy as the economic instrument, go-show automation refilling freed seats, and the finance loop from budget approval in the booking flow to the approved claim number. The vendors behind those labels are compared one by one: Nomadis, IBS iLogistics, Uplift, and the camp-and-crew platforms.
What is UnityTrip not?
Not a generic corporate booking and expense product, not crew rostering or flight-operations software, not a replacement for a travel management company, and not an architecture looking for a problem. Each boundary, with the page that holds it, is set out above.
See It Running
One booking, one PNR, one policy layer, in production in energy and resources.