Glossary
Owned, leased, and chartered travel runs on terms that commercial travel never needs — because the seat has no price. These are the concepts that decide who flies, who waits, and who is offloaded when an asset is full.
A leased travel policy is the set of rules that decides who travels on transport an organisation owns, leases, or charters, when seats are limited and there is no fare to ration them. Where a commercial travel policy uses budgets and cabin class to manage demand, a leased travel policy uses priority, quotas, and seat allocation, because the seat itself has no price.
You can build one with the free Leased Travel Policy Builder.
Operational travel is travel that is core to running the business — moving crews, rotations, and field staff to sites — rather than occasional point-to-point business trips. It typically combines owned, leased, and commercial transport across air, sea, and land, and is planned around rosters and operations rather than individual choice.
Priority replaces price is the principle behind leased and owned transport policy: because the seat has no fare, money cannot balance supply and demand, so the policy allocates scarce seats by priority instead. Passenger type, trip reason, and entitlements decide who flies, who waits, and who is offloaded when a flight is full.
When demand exceeds seats, something has to say no. There are three mechanisms: price, authority, and entitlement. Commercial travel rations by price — the fare is the gatekeeper. Business travel rations by authority — an approver holding delegated financial authority says yes or no to each request. Entitlement travel rations by quota — the rules grant the seat, sanctions protect the rules, and there is no approval step. Priority replaces price is the entitlement instance of the general law: when price cannot ration, something else must.
Channel names are arbitrary; the mechanism defines the channel. A subsidised booking with no approval step behaves as entitlement travel whichever budget funds it — a channel is what it does. Most corporate travel software models price and a thin layer of authority; modelling entitlement is what a leased travel policy requires, and it is the part inherited from airline staff-travel systems.
A claim is the authoritative approval for travel and access to money. A request is not a booking — approval turns one into the other, as a quote becomes a sale — and in the business channel the approval a request must hold is a claim. Many bookings can attach to one claim, and claim revisions and approvals track the journey rather than a single moment.
The claim is where the two gates meet: bookings attach to it on the demand side, and on the supply side no content provider is paid without an approved claim number. Claims post to the organisation's finance system, which is what makes travel spend visible, governed, and reconcilable end to end.
The claim is a business-channel object. Private-channel requests become bookings with no claim at all — the quota is the approval, and no company money moves, so there is nothing for a claim to authorise. That is deliberate: most travellers in a rotational operation move through the private channel, so most travellers get the simplest and quickest booking experience the platform can offer — governance carried by the quota, invisible at the moment of booking.
Travel arranged outside an organisation's automated booking systems — by email, phone, spreadsheet, or a locally invented workflow — and reconciled by hand afterwards. In the travel industry the online/offline split is usually read as a maturity measure: the more bookings go through the tool, the better the programme.
In workforce operations the offline share carries a different meaning. It is not evidence of a backward organisation or reluctant travellers; it is evidence that the installed software does not model the enterprise. Generic travel systems impose a standardised flow — search, policy, approve, book, expense — while a workforce operation runs on entitlement, roster, transport capacity, priority, quota, and displacement. Those rules are not configuration options around a booking workflow; they are the business. When the system cannot represent them, the organisation does not stop operating — it builds an offline process around the system, and every manual workaround marks a requirement the software could not absorb.
Offline work is therefore the market signal for workforce aviation logistics: it maps exactly where the modelling gap sits. The remedy is to express those requirements as a configured model executed by a deterministic policy engine, so the offline fragments become governed bookings behind the two gates — nothing moves without a booking number, and nothing is paid without a claim number.
The rotation of a vessel's crew between shore and ship: crew signing off are moved home and their reliefs moved aboard — typically a flight to the port, a crew boat or helicopter to the vessel, and ground transport at either end. In workforce aviation logistics it is the marine rotation: a fixed sailing with a fixed number of seats, rationed by priority and quota rather than by fare. The governed version is set out on the crew change logistics page.
A named window in a vessel operation's calendar — a rotation cycle, a season, or a holiday period — against which quotas and booking rules are scoped. The published policy schema labels sail periods so that quotas can apply per sailing and per peak sailing rather than only per year, and rules can be scoped to peak or off-peak periods.
A sailing during a period the operation has defined as peak — end-of-rotation and holiday sailings, where demand concentrates. Because peak-period capacity is the scarcest resource in a rotational marine operation, quotas can cap bookings per peak sailing, and the operation defines what counts as peak in its own policy rather than inheriting a fixed calendar.
A wet lease provides an aircraft together with crew, maintenance, and insurance; a dry lease provides the aircraft only, with the operator supplying its own crew. Both arrangements put the cost of the seat on the organisation, which is why utilisation and fair allocation matter as much as the booking itself.
A priority matrix maps each passenger type and trip reason to a priority level, so a booking engine can rank competing requests for the same seat consistently and transparently. It is the core of a leased travel policy: the table that turns "who matters most on this route" into a rule a machine can apply.
Seat allocation is the rule that ties travel groups to the trips and routes they are permitted to book, reserving capacity for the movements that matter most. It prevents lower-priority demand from consuming seats that essential operations will need.
A quota is a cap on how much a person, group, or trip reason can book within a period, used to share limited capacity fairly rather than first-come, first-served. Quotas typically reset on a fixed cycle, and excess quota can sometimes be lent to a colleague who needs to travel.
A booking window is the period before departure in which a given traveller or trip type is allowed to book, used to stage demand and protect seats for higher-priority movements until closer to the date.
A salary-group access entitlement grants a travel privilege — such as a cabin, route, or accommodation tier — based on an employee's grade or band, rather than on price. It encodes who is entitled to what, so the booking engine does not have to interpret it case by case.
Displacement, or offload, is the rule that decides who is removed from a full flight or vessel so a higher-priority traveller can board. A clear displacement rule turns an overbooked asset into a fair, auditable decision rather than a dispute at the gate.
A sector restriction controls movement over specific legs or routes so that essential personnel can travel without being blocked, balancing operational continuity against capacity limits. It is common where a single leg is the bottleneck for an entire site's staffing.
A no-show is a booked traveller who does not present for departure. On owned or leased transport it is a direct loss: the seat is paid for whether or not it is used, and it was denied to someone else who could have travelled. See also no-shows, go-shows, and the cost of empty seats.
A go-show is a prepared traveller who takes a seat freed up by a cancellation or no-show, often minutes before departure. Go-shows convert capacity that would have flown empty into a completed trip, and depend on the system knowing the instant a seat opens.
Penalty points are a score applied for no-shows, late cancellations, or changes, scaled by how close to departure they occur, so that a last-minute no-show costs more than an early cancellation and disruptive behaviour carries proportionate consequences.
A ban temporarily suspends a booker after repeated penalties, but still allows another traveller to book on their behalf — so essential travel continues while the behaviour is corrected. This differs from a hard block, which stops the travel outright and can strand someone who genuinely needs to move.
Asset utilisation is the share of available seats or capacity that is actually used. Because the cost of a leased aircraft, vessel, or vehicle is committed regardless of occupancy, raising utilisation — for example from a roughly 40% industry average toward 90% — directly recovers money already spent. The figures and the levers behind them are set out in the leased fleet travel benchmarks.
A deterministic policy engine applies a policy to a booking request and returns the same allow-or-deny decision every time for the same inputs, with no AI guessing at booking time. Because it is deterministic, every decision can be audited, reproduced, and explained in plain English.
A machine-readable policy expresses travel rules as structured data, such as JSON, rather than prose, so a booking engine can execute them directly and a human-readable document can be generated from the same file. It removes the gap between a policy that is written and a policy that is enforced.
An operational ontology is a structured, machine-readable model of an operation — its passenger types, trip reasons, assets, entitlements, and rules — that a policy engine can execute directly. It is the contract between natural-language policy and executable logic: people write the policy in documents; the ontology makes it computable, and every decision made against it can be traced back to the rule that caused it. This makes UnityTrip ontology-first rather than inventory-first: where conventional travel systems model trips and seats, the ontology models workers, entitlements, rotations, assets, and rules — and bookings are projections of it, executed deterministically over an event-sourced record. The free Leased Travel Policy Builder produces one.
An event stream is the ordered, immutable record of everything that happens in a system — every booking, change, approval, and claim captured as an event at the moment it occurs. Downstream processes react in real time rather than on a batch cycle, and the stream doubles as a complete audit trail of the operation.
A manifest is the live list of who is booked on a specific service. A booking engine checks each request against the manifest and current state — quota used, active bans, seats remaining — before allowing or denying a booking.
A booking engine is the system that takes a travel request and confirms or refuses it against availability and policy. For owned and leased transport it must also account for the organisation's own assets, not only commercial inventory, which is the part conventional travel systems treat as out of scope.
FIFO, or fly-in fly-out, is a workforce model in which staff are flown to a remote site for a set rotation and home again. FIFO travel is schedule-driven, repetitive, and tightly tied to rosters, so a single missed connection can leave a shift uncovered.
Rotational travel follows a fixed roster of work and leave, so bookings are predictable but unforgiving. The system has to align travel to the roster and recover quickly when weather, delays, or operational changes break the plan.
Workforce aviation logistics is 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 and go-show handling, and cost attribution for seats that carry no fare. The category answers to many names: FIFO travel, FIFO workforce logistics, camp and crew logistics, rotational travel, personnel logistics, people logistics, human logistics, crew change, and workforce airlift — the travel half of workforce logistics. Its closest established ancestor is the airline staff-travel system — entitlements, standby, and quotas — generalised to any organisation's own transport.
Zero-dollar travel is travel with no fare and no employee reimbursement: the organisation allocates a seat on transport it already pays for, and the traveller never incurs an expense. Because spend cannot ration demand, control shifts from reimbursement to entitlement — priority, quotas, booking windows, and penalties — and because the seat is valued at zero, this travel appears in no conventional spend report until service fails. The Travel Spend Diagnostic measures how much of it an organisation carries.
Duty of care is an organisation's obligation to protect the safety of travelling staff. It depends on knowing where people are in real time and being able to reach them, which requires an accurate, current view of every itinerary across all transport modes.
Journey management is the practice of assessing and controlling the risk of a specific trip in advance — route, timing, and precautions — common in energy, mining, and humanitarian operations where a journey can carry real safety risk.
Put the terms to work
Turn priority, quotas, and seat allocation into a structured policy a booking engine can execute — free, in your browser.