Shuttle Scheduling Software: The Definitive Guide for Passenger Transportation Operators

# Shuttle Scheduling Software: The Definitive Guide for Passenger Transportation Operators If you run a shuttle, NEMT, limo, or airport‑transfer service, you already know that moving people safely and on time is only half the battle. The other half is coordinating vehicles, drivers, reservations, and ever‑changing passenger demands without letting details slip through the cracks. That’s where **shuttle scheduling software** becomes a cornerstone of modern operations. In this guide we’ll walk through what the technology does, why it matters, how to implement it effectively, common mistakes to steer clear of, and how to evaluate options so you can choose a solution that fits your unique workflow. --- ## What Is Shuttle Scheduling Software? At its core, shuttle scheduling software is a digital platform that automates the creation, adjustment, and communication of vehicle and driver schedules. Unlike generic calendar tools, it is built around the specific realities of passenger transportation: - **Time‑window constraints** – passengers often need pick‑up or drop‑off within a narrow band (e.g., airport arrivals, medical appointments). - **Vehicle capacity & type** – shuttles vary from 8‑seat vans to 50‑seat coaches; limos and NEMT vehicles may have special equipment. - **Driver qualifications & hours‑of‑service rules** – certifications, break requirements, and maximum drive time must be respected. - **Reservation changes** – last‑minute cancellations, additions, or re‑routes happen frequently. - **Real‑time visibility** – dispatchers and drivers need instant updates when a trip shifts. By centralizing these variables, the software turns a manual, error‑prone process into a repeatable workflow that can scale as your fleet grows. --- ## Why Shuttle Scheduling Software Matters for Your Fleet Investing in a purpose‑built scheduling system does more than replace a spreadsheet. It addresses several operational pain points that directly affect service quality and cost effectiveness: ### 1. Reduces Manual Errors When schedules are created by hand or in disconnected documents, double‑bookings, missed pickups, or incorrect vehicle assignments become common. A scheduling engine validates each entry against rules (capacity, driver eligibility, time windows) before it is saved, dramatically lowering the chance of human error. ### 2. Improves Driver Utilization Drivers are a significant cost center. By optimizing routes and minimizing deadhead miles, the software helps you keep vehicles moving with passengers rather than idling. Better utilization translates into fewer vehicles needed to meet the same demand, which can lower fuel consumption and wear‑and‑tear. ### 3. Enhances Customer Experience Passengers appreciate reliable pickup times and clear communication. When the system automatically sends SMS or email confirmations, reminders, and real‑time ETAs, you reduce anxiety and build trust. Satisfied riders are more likely to become repeat customers and refer others. ### 4. Provides Actionable Insights Modern platforms capture data on every trip: scheduled vs. actual times, delays, cancellations, and driver performance. Reporting dashboards let you spot trends—such as a recurring bottleneck at a particular airport terminal—and adjust staffing or routes proactively. ### 5. Supports Scalability As you add vehicles, expand service areas, or take on new contract types (e.g., corporate shuttles vs. NEMT), the software adapts without requiring a complete overhaul of your scheduling process. --- ## Core Capabilities to Look For Not all scheduling tools are created equal. When evaluating options, focus on features that directly support the nuances of passenger transportation. Below is a checklist of capabilities that tend to deliver the most tangible benefits. ### Vehicle & Driver Management - **Fleet profile editor** – store vehicle type, capacity, accessibility features, and maintenance schedules. - **Driver qualification matrix** – track licenses, certifications (e.g., CPR, NEMT training), and availability. - **Hours‑of‑service compliance** – automatic warnings when a driver approaches legal limits. ### Reservation Intake & Modification - **Multi‑channel booking** – web portal, phone API, or integration with third‑party reservation systems. - **Real‑time availability view** – instantly see which vehicles/drivers are free for a requested window. - **Drag‑and‑drop rescheduling** – adjust trips on the fly while the system re‑validates constraints. ### Route Optimization & Dispatch - **Automated route generation** – create optimal pick‑up/drop‑off sequences based on time windows and traffic forecasts. - **Live map dashboard** – monitor vehicle locations, ETA updates, and delays. - **Dynamic re‑routing** – automatically suggest alternate paths when traffic incidents arise. ### Communication & Notification - **Automated passenger alerts** – SMS/WhatsApp/email for booking confirmation, driver arrival, and changes. - **Driver mobile app** – push notifications for trip details, route changes, and ability to confirm completion. - **Dispatcher console** – quick‑send messages to individuals or groups without leaving the platform. ### Reporting & Analytics - **Trip performance metrics** – on‑time percentage, average wait time, miles per passenger. - **Utilization reports** – vehicle occupancy, driver idle time, fuel usage trends. - **Export options** – CSV or PDF for accounting, invoicing, or regulatory submissions. ### Integration Flexibility - **API access** – connect to billing software, GPS telematics, or electronic health record systems (for NEMT). - **Pre‑built connectors** – popular accounting or CRM tools reduce manual data entry. - **Single sign‑on (SSO)** – simplify user management for larger teams. When you map these features against your current pain points, you’ll quickly see which vendors address the most critical gaps. --- ## Step‑by‑Step Implementation Guide Adopting new software can feel daunting, but a structured rollout minimizes disruption and accelerates adoption. Below is a practical roadmap you can tailor to your organization’s size and complexity. ### Phase 1: Preparation & Goal Setting 1. **Stakeholder workshop** – gather input from dispatchers, drivers, managers, and IT. List the top three scheduling challenges you aim to solve. 2. **Define success metrics** – decide what you’ll measure after go‑live (e.g., reduction in manual schedule edits, improvement in on‑time performance, decrease in driver overtime). 3. **Data audit** – export existing schedules, vehicle lists, driver rosters, and reservation histories. Clean duplicates and standardize formats (CSV works well for most imports). ### Phase 2: Vendor Selection & Contracting 4. **Shortlist providers** – use the capability checklist above to score each option. Request demos that focus on your specific workflow (e.g., NEMT trip chaining). 5. **Reference checks** – ask for contacts at similar‑sized operators; inquire about implementation length and support responsiveness. 6. **Contract review** – pay attention to service level agreements (SLAs) for uptime, data ownership, and exit clauses. ### Phase 3: Configuration & Integration 7. **Import master data** – load vehicle profiles, driver qualifications, and service zones into the system. 8. **Set business rules** – define time‑window tolerances, maximum ride length, required break intervals, and vehicle‑type restrictions. 9. **Configure integrations** – connect to your GPS provider for live tracking, and to your invoicing system for automatic trip billing. 10. **Build notification templates** – craft SMS/email messages that reflect your brand tone and include necessary details (pickup point, contact number). ### Phase 4: Pilot Testing 11. **Select a pilot route or service line** – start with a low‑volume, predictable segment (e.g., a hotel‑airport shuttle). 12. **Run parallel schedules** – operate the new system alongside your existing process for one to two weeks. 13. **Collect feedback** – hold daily debriefs with dispatchers and drivers; note any usability hiccups or rule mismatches. 14. **Iterate** – adjust configurations based on pilot insights before scaling. ### Phase 5: Organization‑Wide Rollout 15. **Training sessions** – provide role‑based workshops: dispatchers learn the console, drivers get hands‑on with the mobile app, managers review reporting dashboards. 16. **Go‑live communication** – inform passengers about any changes to booking confirmation methods or notification channels. 17. **Monitor cutover** – have a support champion on‑site for the first 48 hours to address questions quickly. 18. **Post‑go‑live review** – after one month, compare actual metrics against the goals set in Phase 1; refine rules or training as needed. ### Phase 6: Continuous Improvement 19. **Regular data review** – schedule a monthly analytics meeting to spot trends (e.g., increasing cancellations on certain days). 20. **System updates** – stay current with vendor releases; test new features in a sandbox before deploying to production. 21. **Feedback loop** – maintain an open channel for drivers and dispatchers to suggest enhancements; prioritize those that align with operational goals. Following these steps helps ensure that the technology serves your people rather than the other way around. --- ## Common Mistakes and How to Avoid Them Even with a solid plan, certain pitfalls can erode the expected benefits. Being aware of them ahead of time lets you put safeguards in place. ### Mistake 1: Over‑Customizing Early It’s tempting to tweak every rule to match legacy processes exactly. However, excessive customization can create fragility—each change adds complexity and may conflict with future software updates. **Avoidance:** Start with the vendor’s recommended best practices. Implement only those adjustments that solve a proven pain point, and document why each change was made. ### Mistake 2: Ignoring Driver Input Drivers are the frontline users of the mobile app. If the interface feels cumbersome or requires too many taps, they may resort to paper logs or manual calls, defeating the purpose of automation. **Avoidance:** Involve drivers in usability testing during the pilot. Prioritize features like voice‑enabled trip confirmation or one‑tap ETA updates if they reduce friction. ### Mistake 3: Underestimating Change Management Technology adoption fails when people feel the change is imposed without explanation. Skepticism can lead to workarounds that dilute data quality. **Avoidance:** Communicate the “why” behind the rollout early and often. Highlight personal benefits—such as less time spent on phone coordination and more predictable shift endings. Recognize early adopters publicly to reinforce positive behavior. ### Mistake 4: Skipping Data Validation Garbage in, garbage out. If imported vehicle capacities or driver availability contain errors, the scheduler will generate infeasible trips that cause delays or compliance violations. **Avoidance:** Run data‑quality scripts before import (e.g., ensure no vehicle is listed with a capacity of zero, verify that driver license expiration dates are in the future). Conduct a dry‑run of the scheduler with a small dataset to catch logic errors. ### Mistake 5: Failing to Plan for Exceptions Real‑world operations inevitably encounter edge cases—sudden road closures, weather events, or a passenger needing wheelchair assistance at the last minute. A rigid system that cannot accommodate exceptions will force manual overrides, eroding trust. **Avoidance:** Define clear exception handling procedures within the software (e.g., a “manual override” button that requires dispatcher approval and logs the reason). Train staff on when and how to use these tools, and review override logs regularly to identify patterns that may warrant rule adjustments. By anticipating these issues, you can design rollout safeguards that keep the project on track and preserve the confidence of your team. --- ## Comparison Checklist: Evaluating Shuttle Scheduling Software When you sit down with vendors, having a side‑by‑side comparison sheet makes it easier to see where each solution shines or falls short. Below is a detailed checklist you can print or copy into a spreadsheet. | Category | Feature | Why It Matters | Evaluation Notes (Vendor A / B / C) | |----------|---------|----------------|-------------------------------------| | **Fleet & Driver Master Data** | Unlimited vehicle profiles | Supports growth and diverse fleets | | | | Driver qualification tracking | Ensures compliance and proper assignment | | | | Hours‑of‑service alerts | Prevents violations and fatigue | | | **Reservation Handling** | Web‑based self‑service portal | Reduces call‑center load | | | | API for third‑party bookings | Enables partnership with hotels, hospitals, etc. | | | | Real‑time availability view | Cuts double‑booking risk | | | **Scheduling Engine** | Constraint‑based optimization | Generates feasible, efficient routes | | | | Drag‑and‑drop rescheduling | Allows rapid adjustments | | | | Automatic re‑optimization after change | Keeps schedule valid without manual rework | | | **Dispatch & Mobile** | Live GPS tracking map | Provides situational awareness | | | | Driver app with push notifications | Delivers trip details instantly | | | | Two‑way messaging (driver ↔ dispatcher) | Handles on‑the‑fly issues | | | **Communication** | Automated passenger SMS/email | Improves passenger experience | | | | Branded notification templates | Maintains professional image | | | | Multilingual support | Serves diverse rider base | | | **Reporting & Analytics** | On‑time performance dashboard | Core service metric | | | | Vehicle utilization reports | Drives cost effectiveness | | | | Export to CSV/PDF | Facilitates billing and audits | | | **Integrations** | Pre‑built GPS telematics connector | Eliminates manual data entry | | | | Accounting software sync (e.g., QuickBooks) | Streamlines invoicing | | | | NEMT‑specific EHR/HL7 link (if applicable) | Meets regulatory data flow | | | **Support & Training** | 24/7 technical support | Critical for operations that run outside business hours | | | | Online knowledge base | Empowers self‑service troubleshooting | | | | Role‑based training materials | Shortens ramp‑up time | | | **Pricing & Contract** | Transparent subscription model | Avoids surprise fees | | | | Implementation services included | Reduces hidden costs | | | | Data portability clause | Protects your information if you switch vendors | | **How to use the checklist:** 1. Assign a weight to each category based on your operational priorities (e.g., if compliance is paramount, give “Hours‑of‑service alerts” a higher weight). 2. Score each vendor on a scale of 1‑5 for every feature. 3. Multiply the score by the weight and sum to obtain a total rating. 4. Review the qualitative notes—sometimes a lower‑scoring vendor excels in an area that is a deal‑breaker for you (e.g., superb NEMT EHR integration). This structured approach transforms a gut feeling into a defensible decision backed by evidence. --- ## Edge Cases and Special Scenarios Passenger transportation is rarely uniform. Certain service models introduce unique scheduling challenges that merit special attention. Below we outline a few common edge cases and how a robust scheduling platform can address them. ### 1. Mixed‑Fleet Operations (Shuttle + Limo + NEMT) Different vehicle types have distinct constraints: limos may require a chauffeur license, NEMT vans need wheelchair lifts, and shuttles often have fixed routes. **Solution:** Use a hierarchical vehicle‑type classification where each class inherits base rules (e.g., maximum daily drive time) and adds type‑specific attributes (e.g., lift availability). The scheduler then matches reservation requirements to the appropriate class automatically. ### 2. Time‑Sensitive Medical Appointments (NEMT) Patients may have strict arrival windows (e.g., must be at dialysis center by 09:00 ± 5 minutes). Missing the window can cause clinical repercussions. **Solution:** Enable “hard window” mode for specific appointment types. The optimizer treats any schedule that places the patient outside the window as infeasible and will either suggest an alternative vehicle/driver or flag the trip for manual review. ### 3. Multi‑Leg Corporate Shuttles A corporate client may request a morning pickup at several office locations, a midday drop‑off at a conference center, and an evening return—all with different passenger groups. **Solution:** Allow reservation grouping. The system can treat the series of legs as a single “trip itinerary” while still tracking individual passenger manifests for each segment. This simplifies billing (one invoice per itinerary) and provides clear visibility for drivers. ### 4. Ad‑Hoc Event Transport (Concerts, Sports) Demand spikes unpredictably; you may need to augment your regular fleet with temporary vehicles or subcontracted operators. **Solution:** Maintain a “contingent fleet” pool in the software where you can upload temporary vehicle details on the fly. The scheduler can then draw from both owned and contingent pools, applying the same rule set to ensure compliance. ### 5. Regulatory Reporting Requirements Some jurisdictions mandate daily logs of vehicle miles, passenger counts, and driver hours for audit purposes. **Solution:** Activate automated export features that generate the required CSV or XML files at the end of each shift. Verify that the data fields align with the regulator’s schema; many platforms offer configurable templates for this purpose. ### 6. Language Accessibility for Riders In regions with sizable non‑English speaking populations, passengers may not understand English notifications. **Solution:** Configure multilingual notification templates. The system can pull the passenger’s preferred language from their profile and send SMS/email accordingly. ### 7. Emergency Situations (Severe Weather, Road Closures) When a major highway shuts down, you need to reroute many vehicles simultaneously without overwhelming dispatchers. **Solution:** Use the “mass re‑route” function: select affected trips, apply a constraint (e.g., avoid a specific road segment), and let the optimizer propose new routes in bulk. Review the suggestions, approve, and push updates to drivers in one go. By recognizing these scenarios ahead of time and confirming that your chosen software can handle them, you reduce the likelihood of being caught off‑guard when reality deviates from the textbook schedule. --- ## Frequently Asked Questions **Q1: Do I need to replace my existing reservation system to use shuttle scheduling software?** Not necessarily. Many platforms offer APIs or import/export tools that let them work alongside your current booking engine. You can keep the front‑end where passengers make reservations and let the scheduling software handle the back‑end optimization and dispatch. **Q2: How long does a typical implementation take?** Timeline varies with fleet size and complexity. A small operator with fewer than ten vehicles might go live in four to six weeks, while a larger, multi‑service organization could require eight to twelve weeks, especially if deep integrations with GPS or billing systems are needed. **Q3: What kind of training is required for drivers?** Most driver apps are designed for simplicity—often just a few screens showing the next trip, route map, and a button to confirm completion. A hands‑on session of 30‑45 minutes, plus a quick reference guide, is usually sufficient for drivers to become comfortable. **Q4: Can the software help with fuel cost reduction?** Indirectly, yes. By minimizing deadhead miles and optimizing stop sequences, the platform reduces the total distance vehicles travel without passengers. Lower mileage translates into less fuel consumed, though actual savings depend on baseline efficiency and how aggressively you pursue route improvements. **Q5: Is my data safe in the cloud?** Reputable vendors employ industry‑standard encryption (both at rest and in transit), regular security audits, and role‑based access controls. When evaluating a provider, ask about their data‑center certifications (e.g., ISO 27001, SOC 2) and request a copy of their security whitepaper. **Q6: What if I need to add a new vehicle type mid‑year?** Adding a new vehicle class is typically a matter of editing the fleet profile: specify capacity, special equipment, and any associated driver qualifications. The scheduler will immediately consider the new type when generating future trips. **Q7: How do I measure ROI after implementation?** Compare pre‑ and post‑implementation metrics such as: average schedule creation time per dispatcher, percentage of trips arriving within the promised window, total vehicle miles per passenger, and overtime hours logged by drivers. Qualitative gains—like fewer passenger complaints or easier compliance reporting—also contribute to overall value. **Q8: Can the software support recurring contracts (e.g., a daily university shuttle)?** Yes. Most systems let you define recurring trip patterns with adjustable start/end dates, which automatically populate the schedule each day. Changes to the pattern (e.g., a holiday shutdown) can be applied globally with a few clicks. **Q9: What happens if the internet goes down at the dispatch center?** Many platforms offer an offline mode for the driver mobile app, allowing drivers to view their assigned trips and capture completion data locally. Once connectivity resumes, the app syncs with the server. Dispatchers may rely on a secondary connection (e.g., cellular hotspot) for critical real‑time adjustments. **Q10: Is it worth paying extra for AI‑powered optimization?** AI can improve solution quality when dealing with highly complex constraints (e.g., time windows that overlap tightly across many trips). However, a well‑tuned rule‑based optimizer often delivers sufficient results for most shuttle and NEMT operations. Evaluate whether the added cost translates into measurable gains in your specific context before committing to AI features. --- ## Advanced Implementation Walkthrough: From Data Migration to Go‑Live This section adds a detailed, step‑by‑step walkthrough that expands on the earlier phases, focusing on practical actions you can take today. ### 1. Data Cleansing Workshop - Gather a cross‑functional team (dispatch, operations, IT). - Export current master data (vehicles, drivers, service zones) to a spreadsheet. - Identify duplicate entries, outdated driver certifications, and vehicles marked as inactive but still listed. - Create a “clean‑master” file that will serve as the import source. ### 2. Rule‑Building Sprint - List all operational constraints (e.g., max 10‑hour shift, mandatory 30‑minute break after 4 hours, wheelchair‑lift requirement for NEMT trips). - Translate each constraint into a rule within the software’s rule engine. - Test each rule with a single‑trip scenario to confirm the system blocks invalid entries. ### 3. Integration Prototyping - Set up a sandbox environment provided by the vendor. - Connect your GPS telematics feed using the vendor’s API key; verify that latitude/longitude updates appear in the live map within 30 seconds. - Link your invoicing system via a webhook; send a test trip completion and ensure an invoice draft is generated. ### 4. User‑Role Configuration - Create role‑based access profiles: Dispatcher (full schedule edit, override rights), Driver (view assigned trips, confirm completion, send ETA), Manager (view reports, adjust rules, export data). - Assign existing staff to the appropriate profiles and have them log in to verify menu visibility. ### 5. End‑to‑End Dry Run - Pick a realistic day of operations (e.g., a weekday with mixed airport shuttles and NEMT appointments). - Load the day’s reservations into the system. - Run the optimizer and review the generated schedule for conflicts. - Dispatch the schedule to drivers via the mobile app and simulate trip start/completion. - Check that notifications (SMS, email) are triggered at the correct moments. ### 6. Go‑Live Checklist - [ ] All master data imported and validated. - [ ] Business rules active and tested. - [ ] Integrations functioning in production mode. - [ ] Notification templates approved and branded. - [ ] Training completed for all user roles. - [ ] Support contact list shared with the team. - [ ] Fallback procedure (offline mode, hotspot) documented. Following this walkthrough helps you move from theory to a live, reliable scheduling environment with confidence. --- ## Vendor Comparison Checklist (Markdown) You can copy the table below into your own markdown file or spreadsheet to score each option side‑by‑side. | Category | Feature | Importance (1‑5) | Vendor A Score | Vendor B Score | Vendor C Score | Weighted Total (A) | Weighted Total (B) | Weighted Total (C) | |----------|---------|------------------|----------------|----------------|----------------|--------------------|--------------------|--------------------| | Fleet & Driver | Unlimited vehicle profiles | 4 | | | | | | | | Fleet & Driver | Driver qualification matrix | 5 | | | | | | | | Fleet & Driver | Hours‑of‑service alerts | 5 | | | | | | | | Reservation | Web self‑service portal | 3 | | | | | | | | Reservation | Third‑party API | 4 | | | | | | | | Reservation | Real‑time availability | 5 | | | | | | | | Scheduling Engine | Constraint‑based optimizer | 5 | | | | | | | | Scheduling Engine | Drag‑and‑drop rescheduling | 4 | | | | | | | | Scheduling Engine | Auto‑re‑optimize after change | 4 | | | | | | | | Dispatch & Mobile | Live GPS map | 5 | | | | | | | | Dispatch & Mobile | Driver app with push notes | 4 | | | | | | | | Dispatch & Mobile | Two‑way messaging | 4 | | | | | | | | Communication | Automated passenger alerts | 5 | | | | | | | | Communication | Branded templates | 3 | | | | | | | | Communication | Multilingual support | 3 | | | | | | | | Reporting | On‑time dashboard | 5 | | | | | | | | Reporting | Utilization reports | 4 | | | | | | | | Reporting | CSV/PDF export | 4 | | | | | | | | Integrations | GPS telematics connector | 4 | | | | | | | | Integrations | Accounting sync (QuickBooks) | 3 | | | | | | | | Integrations | NEMT EHR/HL7 link | 2* | | | | | | | | Support | 24/7 tech support | 4 | | | | | | | | Support | Knowledge base | 3 | | | | | | | | Support | Role‑based training | 4 | | | | | | | | Pricing | Transparent subscription | 4 | | | | | | | | Pricing | Implementation services inc. | 3 | | | | | | | | Pricing | Data portability clause | 4 | | | | | | | \*Only relevant if you provide NEMT services; otherwise set importance to 0. After filling in scores, multiply each score by its importance weight, sum across rows, and compare the totals. The highest weighted total indicates the best overall fit for your weighted priorities. --- ## Real‑World Scenarios ### Scenario A: Hotel‑Airport Shuttle with Fluctuating Flight Times A boutique hotel runs a 12‑seat shuttle to the nearest airport. Flight arrivals vary by ±20 minutes, and the hotel wants to minimize guest wait time while avoiding empty runs. **How the software helps:** - Import the hotel’s flight feed via API; the system treats each arrival as a time‑window request. - The optimizer clusters arrivals into efficient pickup windows, reducing deadhead miles. - Drivers receive push notifications with updated ETAs as flight status changes, allowing them to adjust arrival at the curb. - After each trip, the system logs actual vs. scheduled times, giving the hotel data to negotiate better curb access with the airport authority. ### Scenario B: NEMT Provider Servicing Dialysis Centers A regional NEMT company transports patients to three dialysis centers. Each patient must arrive within a 10‑minute window of their appointment start time. **How the software helps:** - Enable “hard window” mode for dialysis appointments; the scheduler flags any assignment that would place a patient outside the window. - The driver qualification matrix ensures only vehicles with wheelchair lifts and staff with CPR certification are assigned. - Real‑time GPS tracking lets dispatchers see if a vehicle is stuck in traffic and proactively reassign another vehicle if needed. - At day’s end, the export function creates a CSV file matching the state’s Medicaid reporting schema, simplifying reimbursement. ### Scenario C: Limo Fleet for Corporate Events A limo company provides transportation for a multi‑day conference with shifting attendee lists and varying vehicle stretch lengths (from 4‑seat sedans to 8‑seat stretch SUVs). **How the software helps:** - Reservation grouping treats each attendee’s round‑trip as a single itinerary, even though legs may use different vehicle types. - The fleet profile editor stores each limo’s passenger count, amenities (bar, privacy partition), and chauffeur license requirements. - When a last‑minute change occurs, the drag‑and‑drop interface lets the dispatcher reassign a vehicle while the system instantly checks chauffeur eligibility and vehicle availability. - Post‑event, utilization reports show which vehicle classes were under‑used, informing future fleet right‑sizing decisions. --- ## Deep‑Dive Edge‑Case Guidance ### Managing Mixed‑Fuel Fleets (Electric, Hybrid, Gasoline) If your operation includes electric vans alongside traditional fuel vehicles, you must account for charging times and range limits. **Steps to configure:** 1. Add a “fuel type” attribute to each vehicle profile. 2. Create a rule that prevents scheduling an electric vehicle for a trip whose estimated mileage exceeds 80 % of its rated range. 3. Set up a charging‑station resource calendar; the optimizer can insert a charging block as a pseudo‑trip when needed. 4. Notify drivers via the app when a charging stop is required, showing the nearest station and estimated charge time. ## Helpful Resources - Learn more about [how Passenger Transportation Pro works](https://passengertransportationpro.com) and what it does. - Browse the full [feature overview](https://passengertransportationpro.com/features) for details. - Read more guides on the [Passenger Transportation Pro blog](https://passengertransportationpro.com/blog).