Recurring trip series
Build standing orders for dialysis, therapy, and adult day program riders once, then manage exceptions instead of re-entering trips every week.
Trip scheduling
NEMT Scheduling Software
Most NEMT problems start at scheduling: a missed recurring trip, a wheelchair rider booked on the wrong vehicle, a return leg nobody entered. Axen captures the details that matter at intake so dispatch, drivers, and billing inherit a plan that actually works.
Scheduling built for medical transportation
Pickup windows & appointment times
Schedule around the appointment, not just the pickup—so the plan protects arrival times payers and facilities actually measure.
Mobility & service-level matching
Record wheelchair, stretcher, oxygen, and escort requirements on the trip so only compatible vehicles and drivers are assigned.
Broker and CSV trip imports
Bring trips in from broker files or spreadsheets instead of retyping them, and catch conflicts before the day starts.
Will-call returns
Hold return legs until the rider is ready, then activate and assign them without disrupting the rest of the schedule.
Conflict-aware scheduling
See capacity, driver availability, and timing conflicts while building the schedule—not after riders are already waiting.
What good NEMT scheduling looks like in practice
A dialysis rider needs three trips a week at 5:45 AM with a wheelchair-accessible van and a return that depends on how treatment goes. A one-time hospital discharge arrives mid-afternoon with two hours' notice. A broker file lands with forty trips for tomorrow. Good scheduling software absorbs all three without a dispatcher rebuilding the day by hand.
In Axen, each trip carries its pickup window, appointment time, service level, mobility equipment, escort needs, and payer context from intake onward. That single record flows to route optimization, the driver app, and billing—so nothing gets re-typed and nothing gets lost between systems.
Questions to ask before you buy
- How are recurring series edited—one occurrence, future occurrences, or the whole series?
- What happens to downstream routes when a scheduled trip changes?
- How are will-call returns held and activated?
- Can the scheduler see vehicle capacity and driver availability while booking?
- How do broker trips enter the system, and how are duplicates caught?
For a full evaluation framework, read our guide on how to choose NEMT software and managing recurring trips.
Frequently asked questions
What is NEMT scheduling software?
NEMT scheduling software manages the intake and planning of medical transportation trips: recurring series, one-time rides, pickup windows, mobility requirements, and return legs. It feeds dispatch and routing so the planned day is feasible before vehicles roll.
How is scheduling different from dispatch?
Scheduling is the planning layer—building trips and assigning them to the right day and constraints. Dispatch is the live layer—managing those trips as the day changes. Axen connects both so schedule data carries through to real-time operations.
Can Axen handle standing orders for dialysis riders?
Yes. Recurring trip series are a core workflow. You create the pattern once and manage holiday skips, time changes, and cancellations as exceptions.
Can we import trips from a broker?
Axen supports connected data workflows and imports. Available broker connections depend on your source systems and are confirmed during discovery.
See scheduling and dispatch working together
Bring a sample of your own trip patterns and we'll walk through them live.
Schedule a demo