← Resources

Free Tool

Build a leased-travel policy your booking engine can execute.

The Leased Travel Policy Builder is a free, no-account tool that runs entirely in your browser. It turns leased-travel rules into a structured, machine-readable JSON policy — the deterministic input a booking engine uses to decide who flies, who waits, and who is offloaded when a flight is full.

It is built for organisations that operate their own aircraft, vessels, or vehicles, where the seat has no price, so fairness, quotas, and seat allocation are the whole problem — workforce aviation logistics, FIFO rotations, and marine crew change in oil and gas, LNG, mining, and remote field operations, where different travel groups compete for the same scarce capacity.

Open the policy builder Go straight to the wizard →

Why it's different

Priority replaces price.

A commercial travel policy uses money to balance supply and demand — budgets, cabin class, fares. Leased aircraft, vessels, and vehicles have no fare, so the policy itself has to do that job: a priority matrix, quotas, seat allocation, booking windows, and who gets offloaded when a flight is full.

That is why self-service booking works differently here. A traveller can book their own seat, but what they may book is decided by the travel group they belong to — its priority, its quota, its booking window — while operations keep schedule management over the routes and capacity. This tool is where those rules get written down precisely enough for an engine to execute them.

From rules to a decision

One JSON file.
No guessing at booking time.

The policy you build is the single source of truth. It maps once into a deterministic policy engine that decides allow or deny against live state — quota used, bans, the manifest — with no AI guessing at booking time. The same file authors a plain-English document, so when a booking is denied, the booker is told why. The JSON is, in effect, an operational ontology — the contract between natural-language policy and executable logic. New to the terms? The glossary defines priority matrix, quotas, displacement, and the rest.

Policy Builder wizard matrix · quotas · windows · penalties BUILDS · NO AI POLICY JSON single source of truth MAPS ONCE AUTHORS ONCE Deterministic policy engine rules compiled from the JSON · no per-booking AI live state: quota used · bans · manifest Policy document / PDF human-readable · authored from the same file Allow / Deny deterministic · auditable Plain-English explanation why a booking was denied ON DENY
The wizard builds the policy JSON with no AI. From that one file, the engine decides allow or deny deterministically and a human-readable document explains any denial. A short explainer of how the booking step works is on this video.

Live Demonstration

Watch the rules decide.

A 19-seat aircraft, simulated booking demand, and a real allocation engine running in your browser — the same pattern of deterministic rules the platform executes. Requests arrive; a priority matrix, quotas, and displacement rules decide who flies; penalty points punish the no-show and go-show automation refills the seat before departure. Flip the policy off and watch what first-come-first-served costs.

Dependant travel appears twice, deliberately. Dependant (quota) is a union-agreed entitlement — so much travel for families, agreed and protected, because entitlements an organisation honours are what keep its airfields open. Dependant (subsidised) is standby economics — leftover seats sold at low cost, adding goodwill while recovering real money on capacity that would otherwise fly empty.

Simulated demand · real rules · runs entirely in your browser — no AI, nothing uploaded.

The Aircraft · 19 seats

0%
Utilisation at departure
0/0
Rotation crew aboard
0/0
No-show seats recovered

Decision Log

Structured output

A machine-readable JSON policy

Priority matrix, per-rule quotas, booking windows, seat allocation, salary-group entitlements, penalties, and offload rules — captured as one structured file rather than prose a person has to interpret.

Deterministic by design

Exact, auditable, debuggable

The JSON maps once into a deterministic policy engine. Allow or deny is decided against live state, with no AI guessing at booking time, so every decision can be audited and reproduced.

Explainable denials

Plain-English reasons, from the same file

A human-readable policy document is authored from the same JSON, so when a booking is denied the booker is told why — in plain English, not an error code.

Free and private

No account, nothing uploaded

The builder is free and runs in your browser. There is no sign-up, and the policy you build is not uploaded. It reflects the policy logic UnityTrip runs in production.

Air, Sea, and Road

Aircraft, vessels, and vehicles — one policy model.

The published schema governs air, maritime, and vehicle modes in the same document, because a rotation rarely uses only one. A crew member reaching an offshore facility may take a chartered flight, a crew boat, and a bus, and each leg is rationed by the same priority matrix rather than by three separate systems.

Marine operations get first-class treatment rather than an aviation model bent to fit: quota timeframes include per-sailing and per-peak-sailing caps, and rules can be scoped to peak or off-peak sail periods — because in a rotational marine operation, peak-period capacity is the scarcest resource there is. That vocabulary is in the schema, not in a roadmap.

Try it now

Turn your leased-travel rules into a policy your booking engine can execute — in your browser, for free.

Open the policy builder See the rule engine →

FAQ

Common questions

What's in a leased travel policy?

A priority matrix that sets which passenger types and trip reasons get which priority, per-rule quotas and booking windows, seat allocation, salary-group access entitlements, penalties, and displacement or offload rules. A commercial travel policy needs none of these, because commercial travel uses price to manage demand.

How do I write a leased travel policy?

Work through it in the order the model needs. Describe the operation and its site types. List the transport modes the policy governs — air, maritime, vehicle. Define the passenger types, the travel groups they sit in, and the trip reasons, since business, leave, medical, and compassionate travel are funded and rationed differently. Then build the priority matrix: ordered rules mapping passenger types, trip reasons, and modes to a priority, each rule carrying its own quotas and booking windows. Add salary-group entitlements, which govern access rather than quantity. Set penalties for no-shows and the fairness rules that decide displacement when a departure is oversubscribed. From schema version 1.1, each rule declares its channel, and from 1.2 every trip reason declares its own — because reason-to-channel mapping is per-organisation policy, not doctrine. Reference defaults: business-funded reasons map to approved; everything else — private, subsidised, and medical — to unapproved, with medical deliberately unlimited so nothing impedes organising a medevac. Rules that mix channels do not validate. The builder checks the result for contradictions and exports it as JSON. Most operations already hold all of this in prose across several documents; the work is making it precise enough to execute.

Does it cover marine crew change and vessels?

Yes, as a first-class mode rather than an aviation model adapted to fit. The schema governs air, maritime, and vehicle transport in one policy document, quota timeframes include per-sailing and per-peak-sailing caps, and rules can be scoped to peak or off-peak sail periods — because peak-period capacity is the scarcest resource in a rotational marine operation. A crew-change journey that combines a chartered flight, a crew boat, and ground transport is rationed by one priority matrix rather than three disconnected systems.

How is this different from a commercial travel policy?

A commercial policy manages demand with money. Leased aircraft, vessels, and vehicles have no fare, so the policy has to allocate scarce seats fairly on its own. Priority replaces price.

What does the tool produce?

A structured JSON policy, built entirely in your browser. It feeds a deterministic booking engine, and a human-readable policy document can be produced from the same file.

How do I use the JSON file?

It becomes one document in your client-managed policy import — alongside the policy PDFs and procedure documents you already hold — with one distinction: it is the pre-deconflicted, machine-precise one. The built-in consistency checker means it enters the knowledge base free of the contradictions that make outcomes contradictory, and the import pipeline recognises it and routes it to the deterministic policy engine the booking engine consumes, while the same content grounds the assistant's answers. The document conforms to the published JSON Schema. A short explainer of how that booking works is on this video.

Can the output be used with something other than UnityTrip?

Yes. The output conforms to a JSON Schema published openly, so the policy is yours in a portable, documented format and any engine capable of reading it can act on it. The schema is also the shortest way to check what UnityTrip's model actually contains before talking to anyone — it is the platform thesis made inspectable rather than described.

Is it free?

Yes. It is free and needs no account, and nothing is uploaded — the policy is built in your browser.