Flight Policies

Flight policies control cabin access, seat attributes, and booking requirements for air travel. These settings help travelers book appropriate flights while maintaining cost control and compliance.

Cabin Requirements

Configure approval and blocking rules for each cabin class. Each cabin (Economy, Premium Economy, Business, First Class) can have different requirements based on your organization’s travel standards.

Approval Requirements

Determine when travelers need approval before booking specific cabin classes:

Always

Always requires approval regardless of cost or circumstances. Use for cabin classes that need explicit permission.

Best for:

• Business class for standard employees
• First class for all travelers
• Strict cost control policies

Never

Never requires approval, so travelers can book freely. This provides maximum flexibility for approved cabin classes.

Best for:

• Economy class for all travelers
• Premium Economy for executives
• Pre-approved cabin upgrades

Above Threshold

Requires approval when flight cost exceeds a specific dollar amount. This balances flexibility with cost control.

Configuration:

• Threshold Amount - Dollar limit for automatic approval
• Currency - USD, EUR, etc.

Best for:

• Premium Economy with cost limits
• Business class for long-haul flights only
• Executive travel with budget constraints

Above LLF (Lowest Logical Fare)

Requires approval when flight cost exceeds the Lowest Logical Fare by a specified amount or percentage. This ensures cost-effective booking while allowing flexibility.

Configuration:

• LLF Threshold - Dollar amount or percentage above LLF
• LLF Definition - Reference to your organization’s LLF rules

A Luxury LLF definition uses the lowest qualifying Business fare as its benchmark. If no Business fare qualifies, Juno uses the lowest qualifying First fare instead. Business remains the benchmark even when a First fare is less expensive. The LLF definition’s stop, layover, and red-eye settings determine which fares qualify.

Best for:

• Premium cabins when cost-justified
• Flexible booking with cost accountability
• Market-rate based approvals

With Conditions

Conditional approval based on custom field values (e.g., executive level, travel distance, trip purpose) or on the cabin being booked.

Configuration:

• Conditions - Custom field logic for approval requirements
• Field Examples - Role, department, travel duration, destination, cabin class

The Cabin Class condition matches the cabin the traveler is booking — Economy, Premium Economy, Business, or First. It appears only on the Luxury rule, which covers both Business and First, so a single Luxury rule can treat the two differently: require approval when Cabin Class equals First, while Business stays bookable without approval.

Rules that govern one cabin don’t offer Cabin Class. There the cabin is already fixed, so the condition could only ever always match or never match.

Best for:

• Role-based cabin access
• International vs. domestic rules
• Event-specific accommodations
• Requiring approval for First but not Business under one Luxury rule

Block Requirements

Determine when specific cabin classes are unavailable to travelers:

Always

Always blocked - travelers cannot book this cabin class under any circumstances.

Best for:

• First class restrictions
• Cost control enforcement
• Policy compliance

Never

Never blocked - cabin class is always available (subject to approval requirements).

Best for:

• Approved cabin classes
• Executive travel flexibility
• Emergency booking situations

Above Threshold

Blocked when flight cost exceeds a specific dollar amount. Higher costs require alternatives.

Above LLF

Blocked when flight cost exceeds the Lowest Logical Fare by specified thresholds.

With Conditions

Conditionally blocked based on custom field logic. Cabin Class is available here too, on the Luxury rule — for example, block First outright while leaving Business bookable.

Refundable Fares

Use Refundable fares to require approval for a non-refundable itinerary when a comparable, fully refundable alternative is available within your additional-cost allowance.

From Admin → Settings → Travel policies, open a policy and select Flights. Edit Refundable fares in its own section, separately from Cabins. Saving either section preserves the other section’s settings.

If an existing policy has no configured allowance, this rule is off and stays off when you reopen the editor. Opening or saving other settings does not enable it.

Enable Require approval when a refundable alternative is within the allowance, then set Maximum extra cost per journey direction and its currency. Enabling an unconfigured rule starts the allowance at USD 75 per direction: USD 75 for a one-way trip or USD 150 for a complete round trip. New policies also start with this allowance. Juno compares total prices including taxes and fees, per traveler. An alternative exactly at the allowance qualifies. A saved zero allowance keeps the rule enabled; it is not the same as turning the rule off.

After saving, review the Flights overview to confirm the allowance, currency, and per-direction amount, or that the rule is off.

The alternative must be fully refundable without a cancellation penalty, match the route, travel date, trip type, and cabin, and meet all other applicable policy requirements. Different airlines or departure times can qualify. Fares with unknown refundability or cancellation penalties do not qualify as fully refundable alternatives.

This rule marks the non-refundable itinerary as requiring approval but keeps it visible, selectable, and bookable through the applicable approval flow. Juno does not automatically select or book the refundable alternative. For round trips, the final comparison waits until both directions are selected.

Policy variants can inherit or override the allowance. If you enable coordinator trip exceptions for Refundable fares, coordinators can set an allowance for one trip even when none is inherited, increase or decrease the amount, change the currency, turn the allowance off, or revert the trip-specific allowance.

Turning the allowance off stops the refundable-alternative approval comparison for that trip. Reverting removes the trip-specific allowance and restores the inherited policy setting, which may be enabled or off. Other policy requirements still apply.

Seat Attributes

Control flight features and set traveler preferences for booking options.

Refundable Tickets

Allowed Options:

• Yes - Refundable tickets available
• No - Nonrefundable tickets only

Preferred Setting:

• Yes - Prioritize refundable options
• No - Prioritize nonrefundable options

Use Cases:

• Flexible schedules benefit from refundable tickets
• Cost-conscious policies prefer nonrefundable
• Executive travel needs maximum flexibility

Changeable Tickets

Allowed Options:

• Free - Free change tickets available
• Paid - Paid change tickets allowed
• Not Allowed - No changeable tickets

Preferred Setting:

• Free - Prioritize free change options
• Paid - Accept paid changes when necessary
• Not Allowed - Avoid changeable tickets

Use Cases:

• Uncertain schedules benefit from free changes
• Budget policies limit change flexibility
• Fixed schedules don’t require changes

Carry-on Bag

Allowed Options:

• Yes - Carry-on bags included/available
• No - No carry-on bags

Preferred Setting:

• Yes - Include carry-on bags
• No - Skip carry-on bags

Use Cases:

• Short trips may not require carry-on
• Business travel typically needs carry-on
• Ultra-low-cost carrier policies

Checked Bags

Allowed Options:

• 0 - No checked bags
• 1 - One checked bag
• 2 - Two checked bags

Preferred Setting:

• 0, 1, or 2 - Preferred number of checked bags

Use Cases:

• Short trips: 0 bags
• Standard business travel: 1 bag
• Extended travel: 2 bags
• Equipment transportation needs

Seat Selection

Allowed Options:

• Included - Seat selection included in fare
• Paid - Paid seat selection available
• Not Available - Random seat assignment

Preferred Setting:

• Included - Prefer included seat selection
• Paid - Accept paid seat selection
• Not Available - Accept random assignment

Use Cases:

• Premium fares include seat selection
• Budget policies use random assignment
• Accessibility needs require specific seats

Boarding Priority

Allowed Options:

• Standard - Standard boarding process
• Priority - Priority/early boarding

Preferred Setting:

• Standard - Standard boarding preference
• Priority - Priority boarding preference

Use Cases:

• Executive travel benefits from priority boarding
• Carry-on restrictions may require early boarding
• Cost control policies use standard boarding

Flight Search Options

Control advanced flight search capabilities that affect how the booking engine searches for and displays flight options to travelers.

Split-Ticket Search

Split-ticket search allows the booking engine to combine one-way tickets from different airlines into a single itinerary. When enabled, travelers can see additional flight options that combine one-way tickets from different airlines. This can unlock more itinerary choices at lower initial prices. However, these may lead to higher change fees and additional unused tickets if plans change.

Configuration:

• Enabled - Travelers see additional flight options combining one-way tickets from different airlines
• Disabled - Only round-trip or same-airline itineraries shown

How It Works:

When enabled, the flight search engine will:

1. Search for one-way flights independently for outbound and return segments
2. Identify combinations from different airlines that create viable itineraries
3. Display these split-ticket options alongside traditional round-trip fares
4. Clearly indicate when an itinerary uses tickets from multiple airlines

Use Cases:

Enable split-ticket search when:

• Cost savings are a priority over simplicity
• Your organization values having more itinerary choices
• Travelers are comfortable managing tickets from different airlines
• You want to access ultra-low-cost carriers for one leg while using major carriers for another

Disable split-ticket search when:

• Simplicity and ease of management are priorities
• You prefer single-airline itineraries for easier rebooking during disruptions
• Travelers prefer unified airline experiences (lounges, loyalty programs, baggage policies)
• Your travel policy requires same-airline bookings

Considerations:

Best Practices:

1. Set Clear Expectations - Educate travelers about split-ticket itinerary implications
2. Review Policies - Ensure your disruption policy accounts for multi-airline itineraries
3. Monitor Feedback - Track traveler satisfaction with split-ticket bookings
4. Consider Routes - Some routes benefit more from split-ticketing than others

Different Return Destination

Different Return Destination controls whether — and under what conditions — a traveler can book a trip that returns to a different city than they departed from, for example flying out of San Francisco but flying home from Boston. This is a common request for travelers attending multi-stop trips or events that end somewhere other than where they started. New policies permit different return destinations by default (both requirements set to Never); tighten either requirement to add oversight or restrictions.

You configure two independent requirements, the same way cabin rules work:

Require approval to book:

• Never - A different return destination never requires approval on its own.
• A return to a different city - Any return that lands in a different city than the origin routes the booking for approval.
• A return to a different country - Only a return that lands in a different country routes the booking for approval.

Block the ability to book:

• Never - Nothing is blocked; the approval requirement above governs.
• A return to a different city - Travelers cannot book any return to a different city, so they always fly home to their departure city.
• A return to a different country - Travelers cannot book a return to a different country, but a domestic different-city return is still allowed (subject to the approval requirement).

How It Works:

Requirements are enforced throughout booking, not just hidden in the trip-type selector:

1. At return-location selection, the guest or coordinator sees an inline error and cannot submit a blocked return, or a “will require approval” notice for a return that only needs approval.
2. Flight search rejects a blocked return before search results are shown.
3. Approval evaluation routes an approval-required return for review, or blocks a blocked return, at checkout as a final safeguard.

Use Cases:

• Allow freely - Set both requirements to Never so travelers can book any return city without approval.
• Allow with oversight - Leave Block as Never and set Require approval to “A return to a different city” so open-jaw trips are permitted but reviewed.
• Domestic only - Block “A return to a different country” to keep returns in-country while allowing different domestic cities.
• Disallow entirely - Block “A return to a different city” so travelers always fly home to their departure city.

Considerations:

When you allow returns to a different city (Block is not set to “A return to a different city”), the Uber policy also offers the return-airport pickup location, so a traveler can be picked up at the different airport they fly into. See Uber Policy.

Configuration Examples

Standard Employee Policy

Cabin Requirements:

• Economy: Never require approval, never blocked
• Premium Economy: Always require approval, never blocked
• Business: Always require approval, above $1000 threshold blocked
• First: Always require approval, always blocked

Seat Attributes:

• Refundable: No preferred, Yes/No allowed
• Changeable: Paid preferred, Free/Paid allowed
• Carry-on: Yes preferred, Yes allowed
• Checked Bags: 1 preferred, 0/1 allowed
• Seat Selection: Not Available preferred, all allowed
• Boarding: Standard preferred, Standard allowed

Flight Search Options:

• Split-Ticket Search: Enabled (to maximize cost savings)

Event Timing Buffer:

• Outbound: Show warning, 3 hours fixed buffer
• Return: Show warning, 3 hours fixed buffer

Executive Policy

Cabin Requirements:

• Economy: Never require approval, never blocked
• Premium Economy: Never require approval, never blocked
• Business: Above LLF +$500 require approval, never blocked
• First: Always require approval, above LLF +$2000 blocked

Seat Attributes:

• Refundable: Yes preferred, Yes/No allowed
• Changeable: Free preferred, all allowed
• Carry-on: Yes preferred, Yes allowed
• Checked Bags: 2 preferred, 1/2 allowed
• Seat Selection: Included preferred, all allowed
• Boarding: Priority preferred, all allowed

Flight Search Options:

• Split-Ticket Search: Disabled (prefer single-airline experience)

Event Timing Buffer:

• Outbound: Require approval, smart travel time (90 min airport buffer)
• Return: Require approval, smart travel time (120 min airport buffer)

International Travel Policy

Cabin Requirements:

• Economy: Never require approval, never blocked
• Premium Economy: Never require approval, never blocked
• Business: With Conditions (flight >8 hours), above $3000 blocked
• First: Always require approval, always blocked

Seat Attributes:

• Refundable: Yes preferred, Yes/No allowed
• Changeable: Free preferred, all allowed
• Carry-on: Yes preferred, Yes allowed
• Checked Bags: 2 preferred, 1/2 allowed
• Seat Selection: Included preferred, all allowed
• Boarding: Priority preferred, all allowed

Flight Search Options:

• Split-Ticket Search: Enabled (to maximize route options for international travel)

Event Timing Buffer:

• Outbound: Block booking, 8 hours fixed buffer (customs and jet lag)
• Return: Require approval, 5 hours fixed buffer (post-event networking)

Event Timing Buffer Policy

Control when travelers must arrive before events start and when they can depart after events end. This ensures travelers have adequate time to reach event venues and handle post-event logistics.

From Admin → Settings → Travel policies, open a policy and select Flights → Event timing to edit arrival and departure buffers and event-overlap rules. Advance booking window and Last flight option of the day have separate editors on the Flights tab.

If the policy has no saved Event timing configuration, configure and save Event timing before editing advance-booking or last-flight rules. Those editors provide Go to Event timing to help you complete this prerequisite; opening an editor alone does not enable timing rules.

Buffer Calculation Modes

Choose how the system calculates required buffer time between flight arrival/departure and event start/end:

Fixed Hours

Set a fixed time buffer in hours between flight times and event times. This provides consistent, predictable requirements.

Configuration:

• Buffer Hours - Number of hours required (e.g., 3, 5, 8)

Best for:

• Simple, consistent policies across all destinations
• Organizations without complex travel time considerations
• Predictable buffer requirements

Example: Require travelers to arrive 5 hours before event start time, regardless of venue location.

Smart Travel Time

Calculate buffer dynamically using real-time travel time from airport to event venue, plus airport processing time. Uses Google Maps Distance Matrix API with live traffic data.

Configuration:

• Airport Buffer Minutes - Time needed for baggage claim, customs, and airport exit (e.g., 60-120 minutes)
• Additional Buffer - Extra time beyond travel time + airport buffer (optional)

How It Works:

When enabled, the system:

1. Calculates real-time driving time from arrival airport to event venue
2. Adds configured airport buffer (baggage claim, customs, airport exit)
3. Compares flight arrival/departure time against required buffer
4. Displays travel time estimates and requirements in flight search

Best for:

• Events with specific venue locations
• Organizations prioritizing precise time management
• Destinations with variable traffic patterns
• International travel with customs considerations

Requirements:

• Event must have venue coordinates (latitude/longitude)
• Falls back to 3-hour fixed buffer if coordinates unavailable

Example: For an event at a downtown convention center, the system calculates 45 minutes driving time + 60 minutes airport buffer, requiring flights arrive at least 1 hour 45 minutes before event start.

Enforcement Levels

Configure how the system handles flights that don’t meet buffer requirements:

Show Warning

Display a warning to travelers about insufficient buffer time, but allow booking without approval. Use when you want to inform travelers but trust their judgment.

Best for:

• Flexible policies that defer to traveler discretion
• Experienced travelers who understand timing risks
• Organizations prioritizing autonomy

Block Booking

Prevent travelers from booking flights that don’t meet buffer requirements. The flight option is unavailable and cannot be selected.

Best for:

• Strict timing requirements
• High-stakes events where late arrival is unacceptable
• Risk mitigation policies

Require Approval

Allow travelers to select flights that don’t meet buffer requirements, but require coordinator approval before booking.

Best for:

• Balancing flexibility with oversight
• Policies requiring case-by-case review
• Allowing exceptions with accountability

Outbound vs. Return Configuration

Configure buffer policies separately for outbound flights (arriving before event) and return flights (departing after event):

Outbound Flight Buffer

Controls when travelers must arrive relative to event start time. Ensures adequate time to travel from airport to venue.

Common Settings:

• Short local events: 3-hour fixed buffer
• International events: 8-hour fixed buffer (customs, jet lag)
• Events with venues: Smart travel time + 90 minutes airport buffer

Return Flight Buffer

Controls when travelers can depart relative to event end time. Ensures travelers attend full event and have time to reach airport.

Common Settings:

• Standard events: 3-hour fixed buffer
• Events with networking: 4-6 hour fixed buffer (post-event activities)
• Events with venues: Smart travel time + 2 hours (pack, checkout, travel)

Flight Search Integration

When travelers search for flights, the event timing buffer policy:

1. Evaluates each flight against outbound and return buffer requirements
2. Displays visual indicators (warning badges, approval required badges, blocked status)
3. Shows travel time estimates in tooltips when smart travel time mode is enabled
4. Explains buffer requirements so travelers understand timing constraints

Travelers see clear feedback about which flights comply with policy and why certain flights require approval or are blocked.

Approval Flow Integration

When flights violate event timing buffer policy and require approval:

1. Approval alert displays specific timing violation details
2. Shows required vs. actual buffer in minutes for both outbound and return
3. Indicates travel time calculations when smart travel time mode is used
4. Approvers see full context to make informed decisions

This helps approvers quickly understand why the flight needs review and make appropriate decisions based on specific circumstances.

Last Flight Option of the Day

Use Last flight option of the day to discourage travelers from choosing the latest departure available for their route and date. Juno compares only the priced flight options returned in the current search, not the airline’s complete published schedule.

On the policy’s Flights tab, edit Last flight option of the day. If prompted, use Go to Event timing to configure and save Event timing first, then return to this section.

Choose an action and the flight directions it applies to:

• Off: Do not flag the latest option.
• Show a warning: Recommend that the traveler choose an earlier flight while keeping the latest option bookable.
• Require approval: Keep the latest option selectable, but route the booking for approval.
• Apply to: Enforce the action for outbound flights, return flights, or both.

If multiple options tie for the latest departure time, Juno flags each of them. A search with only one flight option does not provide enough options for comparison, so Juno does not flag it.

Advance Booking Window

On the policy’s Flights tab, edit Advance booking window to require flights to be booked a set number of days before the trip’s first departure. If prompted, use Go to Event timing to configure and save Event timing first, then return to this section. Turn on Require flights to be booked in advance, then configure:

• Minimum days before departure: how far ahead a flight must be booked (for example, 14 or 30 days). Measured from the moment of booking to the first departure; a booking exactly at the boundary is in policy.
• Minimum hours for last-minute trips (optional): when a trip is created fewer than the minimum days before departure, require this many hours instead. Leave it empty to always require the minimum days.
• Enforcement: show a warning or require approval to book.

Flights departing fewer than the required number of days away are labeled Booking too close to departure in search results. With approval enforcement, the traveler can still select the flight and it files a Request to Book; the approval shows how far ahead the flight was booked and what the policy required. Travel policy variants can add, change, or turn off the window for specific clients. In a variant, use Add a change to select Event timing, Advance booking window, or Last flight option of the day separately. These three sections share the Event timing coordinator exception permission.

Best Practices

Cabin Configuration

1. Start Conservative - Begin with restrictive policies and loosen as needed
2. Use Thresholds Wisely - Set realistic dollar amounts based on route analysis
3. Consider Route Length - Different rules for domestic vs. international flights
4. Monitor Compliance - Track approval rates and policy violations

Seat Attributes

1. Align with Expense Policy - Ensure travel and expense policies are consistent
2. Consider Traveler Needs - Balance cost control with traveler experience
3. Test Booking Flows - Verify policies work as expected in booking scenarios
4. Regular Review - Update preferences based on airline product changes

Policy Testing

1. Use Test Bookings - Validate policy behavior before deployment
2. Check Edge Cases - Test unusual routes and scenarios
3. Verify Integrations - Ensure policies work with expense management
4. Monitor Feedback - Collect traveler feedback on policy effectiveness

Event Timing Buffer

1. Start with warnings - Use “Show warning” enforcement initially to gauge traveler behavior
2. Consider event types - Professional conferences may need less buffer than client meetings
3. Test smart travel time - Verify venue coordinates are accurate before enforcing travel time mode
4. Account for traffic - Choose Heavy traffic for destinations where drive times are unpredictable
5. Set reasonable buffers - Balance risk mitigation with flight availability
6. Different outbound/return rules - Arriving late is often worse than leaving early; enforce accordingly

Related Features

• Lowest Logical Fares - Market-based cost control thresholds
• Custom Fields - Create fields for conditional flight policies
• Policy Selection Rules - Assign different flight policies by traveler type
• Expense Policies - Align post-travel expense rules with booking policies