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 and travel groups compete for the same capacity.
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.
A traveller books their own seat; what they may book is decided by their travel group's priority, quota and booking window. This tool is where those rules are written precisely enough for an engine to execute.
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.
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: Dependant (quota) is an agreed entitlement, protected within its quota; Dependant (subsidised) is standby, boarding only on seats that would otherwise fly empty.
Simulated demand · real rules · runs entirely in your browser — no AI, nothing uploaded.
The Aircraft · 19 seats
Decision Log
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.
Quota time frames are per year, per week, per day, per sector and per peak sailing, and rules can be scoped to a peak or off-peak sail period, because peak-period capacity is what a marine rotation runs short of. 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.
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. Each rule and each trip reason declares its channel, 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. The schema governs air, maritime and vehicle transport in one policy document; quota time frames are per year, per week, per day, per sector and per peak sailing, and rules can be scoped to a peak or off-peak sail period. A crew-change journey of a chartered flight, a crew boat and ground transport is rationed by one priority matrix.
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 machine-precise one, checked for contradictions before it enters. The import pipeline routes it to the deterministic policy engine, and the same content grounds the AI travel assistant's answers. The document conforms to the published JSON Schema. The schema is the published subset of a larger production model that evolves continually. Once a policy is built, the Policy Simulator runs bookings through it and shows which rule decided each one.
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 a way to check what UnityTrip's model 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.