How to write a seat allocation policy for leased aircraft

A commercial seat is rationed by its fare: when demand exceeds supply, the price rises and demand falls away. A seat on an aircraft your organisation owns, leases, or charters has no fare — the aircraft is paid for whether or not anyone boards — so price cannot ration it. Something else has to. That something is the seat allocation policy, and it is the part of a travel policy that generic templates leave out entirely, because generic corporate travel has never needed it.

There are only three ways scarce travel gets rationed: price (commercial — the fare gatekeeps), authority (business travel — an approver holding delegated financial authority says yes or no), and entitlement (the rules grant the seat, sanctions protect the rules, and there is no approval step). A seat allocation policy is the entitlement mechanism written down. Priority replaces price: when the fare cannot decide, the policy has to say precisely what does.

Start with the test, not the content source

The classic mistake is to organise the policy around where the seat comes from — leased versus commercial, this charter desk versus that booking tool. Content source is just a property of a booking. What the policy actually turns on is a single test: is the trip approved? Business travel is approved, through 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.

Every element below belongs to one channel or the other. Priority, quotas, and booking windows are the machinery of the private channel, where nobody approves and the rules decide. Policies written around content source instead of the test are why the categories that straddle the seam — rest-and-recuperation travel, dependants' travel — become unmanageable. Write the policy around the test and they become ordinary rules. The full model is set out on the workforce aviation logistics page.

The seven elements of an executable seat allocation policy

Each element below corresponds to a field in the published leased-travel-policy schema, and the free Leased Travel Policy Builder walks through them in this order. A policy that has all seven can be executed by a booking engine; a policy missing any of them is enforced by whoever is on shift.

1. Passenger types and trip reasons — with the channel each reason implies. Define who can travel (rotational staff, contractors, management, dependants, visitors) and why (rotation, business, leave, medical, compassionate, subsidised). From schema version 1.2 every trip reason declares its own channel, because which reasons require an authority is per-organisation policy, not doctrine. The reference defaults: business-funded reasons map to approved; everything else — private, subsidised, and medical — maps to unapproved. Medical sits in the unapproved channel deliberately, with unlimited quota, so nothing impedes organising a medevac.
2. The priority matrix. An ordered set of rules mapping passenger types, trip reasons, and transport modes to a priority level, so competing requests for the same seat rank the same way every time. Crew due on rotation outrank visitors; a medical case outranks both. Each rule carries its own quotas and booking windows, and rules that mix channels do not validate — the schema refuses them, which is the thesis expressed as a validator.
3. Quotas, with the right timeframes. A quota caps how much a person, group, or trip reason can book within a period. Match the period to how the capacity is actually contended: the schema supports quotas per year, per week, per day, per sector, and per peak sailing, and a rule can carry more than one, because an annual quota alone lets a whole year's entitlement be spent in the peak month. Keep two dependant concepts separate: a dependant quota (how many trips) and a dependant subsidy (who pays) are different rules, both valuable, and conflating them is a reliable way to lose the confidence of the workforce and its representatives.
4. Booking windows. The period before departure in which a given traveller or trip type is allowed to book. Windows stage demand so a late request cannot displace an earlier entitled one, and protect seats for the movements the flight exists for. A rotation crew's window opens earliest; a visitor's opens last.
5. Displacement, with key-person separation. The rule that decides who is removed from a full flight so a higher-priority traveller can board — deterministic, with the reason recorded and a waitlist that puts the displaced traveller first onto the next departure. Pair it with a separation rule: two key personnel on the same aircraft is a tail-case error an audit will not forgive.
6. No-show penalties and go-show rules. Penalty points scaled to departure proximity discourage no-shows without blocking essential travel — repeated no-shows suspend the booker, not the traveller, so a colleague can still book on their behalf. Go-show automation refills a freed seat minutes before departure. The economics are covered in a separate guide.
7. Salary-group access entitlements. A privilege such as cabin, route, or accommodation tier granted on grade or band. Entitlements govern access; quotas govern quantity. Keep them in separate rules so neither silently overrides the other.

Write it so the engine can refuse

A seat allocation policy is only as good as its enforcement, and enforcement is only reliable when the policy exists as data. In prose, "management may travel business class on long sectors" is a negotiation; as a rule with a passenger type, a mode, a sector length, and an entitlement, it is a decision the engine makes identically for every request and can reproduce a year later with the rule that decided it attached. The test of a well-written policy is that a deterministic engine can say no to it — and that when it does, the reason is plain English rather than a support ticket.

Two properties follow. Contradictions must be caught when the policy is written, not when a traveller is standing at a counter: the Builder checks a policy for conflicting rules before it exports, and the schema rejects rules that mix channels. And clauses that are inherently human judgement — compassionate grounds, manager discretion — should be flagged and routed to an approver with the source clause attached, not silently dropped or improvised by whoever is on shift. A visible gap is a better failure mode than a hidden one.

A worked allocation

Picture a nineteen-seat aircraft on a rotation day with more requests than seats: crew due on and off rotation, a handful of leave travellers, dependants on quota, a contractor, a visitor, and one medical case. A first-come-first-served list boards whoever booked earliest and typically strands part of the rotation crew the flight exists for, then flies the no-show seats empty. Under a priority matrix the medical case boards unconditionally, rotation crew fill their seats, leave travel and dependants board within their quotas, the visitor waits, and a no-show minutes before departure triggers a penalty and a go-show refill from the waitlist. The Policy Builder page runs exactly this scenario live in the browser — simulated demand, real rules, no AI — so the difference between the two allocations can be watched rather than argued.

The mistakes that make a policy unenforceable

• Organising by content source. Leased versus commercial is a property, not a channel. Organise by the approval test.
• Treating subsidised travel as approved. A subsidy is money, not an approval step. Subsidised travel is private travel and belongs beside quota.
• Conflating dependant quota with dependant subsidy. Two rules, two meanings, both defended fiercely by the people they cover.
• Defaulting to first-come-first-served. It is not a fairness rule; it is the absence of one.
• Annual-only quotas. They permit a year's entitlement to be spent in the one month everyone wants.
• Flat no-show penalties. A no-show the night before costs the operation a seat; one a month out costs nothing. Scale penalties to departure proximity.
• Making medical travel wait for approval. Nothing should impede organising a medevac. Put medical in the auto-approved channel with unlimited quota unless your organisation has decided otherwise, and decide it explicitly.
• Keeping the policy in prose only. A policy that exists only as a document is enforced by people. Express it in a machine-readable form the engine executes and the audit can replay.

Common questions

What is a seat allocation policy?

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. It replaces price with entitlement: a priority matrix ranks passenger types and trip reasons, quotas cap how often a seat can be used, booking windows stage demand, displacement rules decide who waits when a flight is full, and penalties and go-show rules protect the rules and refill freed seats. Written well, it is a document a booking engine can execute deterministically.

How do you allocate seats fairly on a leased aircraft?

By entitlement rather than by queue or by rank alone. Fairness comes from stating the rules in advance and applying them identically every time: a priority matrix that ranks passenger types and trip reasons, quotas that stop any one group monopolising capacity, booking windows that stop late requests displacing earlier entitled ones, and displacement rules with a recorded reason when someone has to wait. First-come-first-served is not fair on a leased aircraft; it rewards whoever books earliest and typically strands the rotation crew the flight exists for.

What is a priority matrix in a travel policy?

An ordered set of rules mapping passenger types, trip reasons, and transport modes to a priority level, so a booking engine can rank competing requests for the same seat consistently. Each rule carries its own quotas and booking windows. The matrix is the core of a leased travel policy because it is the mechanism that replaces price. The glossary defines it alongside the related terms.

How should travel quotas be set — per year, per week, or per sector?

Match the timeframe to how the capacity is actually contended. An annual quota alone lets a whole year's entitlement be spent in the peak month, so the published policy schema supports quotas per year, per week, per day, per sector, and per peak sailing, and a single rule can carry more than one. Quotas cap quantity; salary-group entitlements govern access, such as cabin or mode, and the two should not be confused.

What is displacement in seat allocation?

Displacement, or offload, is the rule that decides who is removed from a full flight or vessel so a higher-priority traveller can board, turning an overbooked asset into a fair, auditable decision rather than an argument at the gate. A good displacement rule is deterministic, records the reason, and pairs with a waitlist so the displaced traveller is first onto the next departure.

Should medical travel need approval in a seat allocation policy?

In the reference model, no. Medical travel sits in the auto-approved channel deliberately, with unlimited quota, so nothing impedes organising a medevac — and in practice it has not been abused. Which trip reasons require an authority is itself an organisational choice, configured per tenant: the test is universal; the mapping is policy.

How is a seat allocation policy enforced?

At the point of booking, by a deterministic policy engine that executes the policy as data — the same inputs give the same answer every time, with the rule that decided it attached. A policy that lives only in prose is enforced by whoever is on shift; a policy expressed in a machine-readable form, validated against a published schema, is enforced identically for every request and can be audited a year later. See how the rule engine works.

Is there a tool or template for writing a leased aircraft seat allocation policy?

Yes. The free Leased Travel Policy Builder walks through passenger types, trip reasons, the priority matrix, quotas, booking windows, entitlements, and penalties, checks the result for contradictions, and exports JSON conforming to the published schema — no account required. The corporate travel policy template carries the surrounding policy sections.

Go deeper

• The Leased Travel Policy Builder — write the seven elements as an executable policy in about five minutes, and watch the allocation demonstrator run.
• What a corporate travel policy should include — the ten elements of the surrounding policy this one sits inside.
• What is workforce aviation logistics? — the two channels, the single test, and the two chokepoints that enforce the model.
• No-shows, go-shows, and the cost of empty seats — the economics of penalties, quotas, and go-show automation.
• Leased-fleet utilisation benchmarks — why fleets run near a ~40% average and what policy-governed allocation achieves.
• The glossary — priority matrix, quota, booking window, displacement, go-show, and the rest, defined.