Skip to main content

Configuring Public Transport Rules

Updated over 2 months ago

This article outlines how to configure public transport rules in Trip Scheduler. These rules allow your organization to set limits for walking distance, transfers, age, or appointment types. When a trip request violates a rule, the system provides a warning to help users make informed choices without blocking the booking. “Arrive By” routing ensures accurate transit options for future scheduled trips, allowing flexible and consistent application of your policies.

1. Accessing Public Transport Rules

  1. Navigate to Settings → Configuration → Eligibility Criteria.

  2. Note the following rules (do not reword):

    1. Rules are checked in real-time during trip creation

    2. Violations trigger advisory warnings but don't block bookings

    3. Leave parameters blank to ignore specific rules

    4. Rules apply to all members in your organization


2. Configurable Criteria for Public Transportation

On the Eligibility Criteria page, configure the following rules exactly as described:

  • Max Walking Distance to Pickup
    Warn users if walking distance to the pickup location exceeds this value.

  • Max Walking Distance from Drop-off
    Warn users if walking distance from the drop-off location exceeds this value.

  • Max Number of Transfers
    Warn users if the route requires more transfers than this value.

  • Minimum Eligible Age
    Warn users if the member is younger than this age.

  • Maximum Eligible Age
    Warn users if the member is older than this age.

  • Ineligible Appointment Reasons
    Members with these appointment reasons are not eligible for public transportation.

  • Max Trip Duration
    Warn users if the trip duration exceeds this value.


3. Applying and Updating Rules

  • Enter values in the fields to enforce the rule.

  • Leave fields blank if you want the system to ignore that rule.

  • Changes are applied to all members in your organization immediately.

  • Warnings will display during trip creation whenever a rule is violated, but bookings are not blocked.


Did this answer your question?