Rail Policies

Rail policies control how Juno supports train travel during rail beta. Rail beta does not include rail search or fully in-product ticketing. Instead, Juno helps guests and coordinators choose rail as a travel method and issues a rail virtual card for payment. When travel-agent assistance is available for your organization, Juno can also provide the reference details needed to complete rail booking by phone.

When a travel policy has no rail policy configured, Rail is not available for invites that use that policy.

During rail beta, only Maximum price is enforced. Highest travel class and Booking window are stored and shown as guidance, but they are not enforced, flagged, blocked, or routed to approval.

Maximum Price

Set the maximum amount Juno covers for rail. This value becomes the spend limit on the rail virtual card issued for the invite.

The maximum price is evaluated against the total rail purchase price, including taxes and fees. Juno does not add a buffer or multiplier to the configured amount.

If you leave the default value in place, Juno uses a $1,000 maximum.

Limit Increase Requests

Choose what happens when the rail card limit is not high enough for the guest’s rail purchase.

Setting	Behavior
Allow limit increase requests	Guests can request a higher rail card limit. The request is routed to the travel policy approver. The card limit is raised only if the approver approves the request.
Block (hard cap)	Guests cannot request an increase. Any amount above the maximum is not covered by the rail card.

Use Allow limit increase requests when rail prices vary by route or timing and you want approvers to make exceptions. Use Block (hard cap) when the maximum should be a strict spending limit.

Highest Travel Class

Select the highest rail class guests should book, such as Coach, Business, or First. During rail beta, this is display-only guidance. It does not prevent a guest from purchasing a higher class, and it does not create an approval request.

Booking Window

Set how many days in advance guests should book rail. During rail beta, this is display-only guidance. It does not prevent late bookings or create approval requests.

Use 0 when you do not want to show an advance-booking expectation.

Default Rail Locations

Default rail locations are saved office locations where qualifying invites should default to both Air and Rail as travel methods.

Rail defaults on only when all of the following are true:

The invite uses a travel policy with a rail policy configured
The selected event location is a saved office location
That saved office location is listed in Default rail locations
Rail beta is enabled for your organization

For all other locations, Juno defaults to Air only. Coordinators can still adjust the travel methods while creating the invite.

Default rail locations only affect the initial travel method selection. They do not make Rail available unless the resolved travel policy includes a rail policy and rail beta is enabled.

When Approval Is Required

Rail beta does not evaluate train search results or rail ticket details against policy. The rail approval surface is for rail card limit increase requests.

If Allow limit increase requests is enabled and a guest requests more funds, the request is routed to the policy approver. The approver can approve or reject the increase from the approvals workflow. If the request is approved, the guest’s rail card limit is raised to the approved amount.

If Block (hard cap) is enabled, guests cannot request a limit increase.

Travel-Agent Support

Rail travel-agent assistance depends on your organization’s Juno configuration. If it is available, guests and coordinators can use the reference details Juno provides to call and complete the rail booking over the phone.

If travel-agent assistance is not available for your organization, rail booking uses self-booking by default. The guest or coordinator receives a single-use rail virtual card, books directly with their preferred rail provider, and uploads the receipt for confirmation.

Work with your Customer Success Manager or the Juno team if you need help enabling or confirming rail travel-agent support for your organization.

Best Practices

Set a realistic card limit — Base the maximum price on expected total rail fares, including taxes and fees.
Use limit requests for variable routes — Allow requests when rail prices fluctuate or when last-minute bookings are common.
Treat class and window settings as guidance — Do not rely on them for enforcement during rail beta.
Confirm agent support before promising it — Work with your Customer Success Manager or the Juno team if your program expects guests to book rail by phone.
Use saved office locations deliberately — Add only locations where rail is a common alternative to flying.

Policy Selection Rules — Automatically assign travel policies based on traveler attributes
Managing Invites — Review rail card limit increase requests from the guest invite dashboard
Rail Booking — Understand what guests see when Rail is available