NEMT software for large fleets: many dispatchers, one live board

What changes once a fleet passes 25 vans

At 25 vans, nobody can hold the whole day in their head anymore. Take an example fleet of 40 vans averaging eight trips each: that is about 320 legs a day, plus the calls, changes, and returns that come with them. The work spreads across several people, and problems start in the gaps between them.

Typical symptoms:

• Two people fix the same problem. One dispatcher reassigns a trip while another calls a driver about it.
• Handoffs lose details. The morning desk knows a rider needs a door-to-door escort, and the afternoon desk does not.
• Returns wait too long. A will-call rider sits in a lobby because the person watching returns was also answering intake calls.
• Nobody sees the whole picture. The owner learns about a late pattern from a broker scorecard a month later.
• Credentials slip through. With dozens of drivers, one expired license is easy to miss.

Software for a fleet this size has one main job: let many people work the same day without stepping on each other.

Split the desk by job, and keep one board

Divide dispatch by task. The exact split depends on volume, but these desks cover the main jobs:

The returns desk matters more than it looks. Under MTM Health’s Virginia handbook, the van has 45 minutes from the moment a will-call rider is ready, and three hours from the call for a hospital discharge. A dispatcher who is also taking intake calls will miss those windows on a busy afternoon.

Whatever the split, every desk should work from the same live board. Separate spreadsheets per desk are how two people end up fixing the same trip. Notes about a rider or a trip belong on the trip itself, where the next shift will see them. Our dispatch workflow guide walks through the day desk by desk, and the hiring guide covers staffing each seat.

Add zones only when the service area outgrows one person’s knowledge of the roads. A two-county fleet may run fine with one dispatch desk. A fleet covering a metro area and its rural edges may need a dispatcher who knows each side. A second location follows the same rule: its desk runs its own vans, while the owner and the billing team still see both operations in one place. The guide to opening a second NEMT location covers the rest of that move.

Planning hundreds of trips a day

Building 40 routes by hand takes hours, and the result depends on who built it. At fleet scale, planning works best in a fixed order:

1. Lock what must not move. Standing orders with a regular driver stay put. MTM Health expects the same driver on recurring trips when the schedule permits, and asks you to document any substitute.
2. Place the scarce vehicles first. Wheelchair and stretcher trips go to the vans equipped for them, based on each rider’s level of service.
3. Let the software fill the rest. Automatic planning places the remaining trips around pickup times, appointment times, and where each driver starts.
4. Review before anything changes. A dispatcher checks the proposed plan and applies it.
5. Re-plan when the day changes. A call-out or a cluster of cancellations should trigger a new proposal, not a rebuild from scratch.

Planning also runs on a longer clock than one morning. Under MTM Health’s Virginia process, trips go to eligible providers seven days before the appointment and open to every provider in the area five days out. A trip you cannot cover has to go back to the broker, a turnback, no later than 24 hours before pickup. A large fleet needs to see next week’s coverage, not only tomorrow’s.

Roles, permissions, and a record of every change

Every login in a large fleet should show only what that person’s job requires. HIPAA’s minimum necessary standard asks a covered entity to identify which staff need access to health information and to limit each group’s access to the categories their duties require (45 CFR 164.514(d)).

The HIPAA Security Rule adds standards for the systems themselves:

• One person, one login. Each user needs a unique name or number so their activity can be tracked (45 CFR 164.312(a)(2)(i)). Shared dispatcher logins break this.
• A record of activity. Systems holding health information need audit controls that record and examine what happens in them (45 CFR 164.312(b)).
• Proof of who is signing in. The rule requires procedures to verify that a person seeking access is who they claim to be (45 CFR 164.312(d)).
• Access that ends with the job. Procedures should end a worker’s access when their employment ends (45 CFR 164.308(a)(3)(ii)(C)).

In practice, a dispatcher needs rider names, addresses, and mobility needs, but not invoice totals. A biller needs trip records and rates, but not live driver locations. Drivers need their own manifest and nothing else. Set those roles once, and a new hire gets the right access on day one. The guide to HIPAA compliant NEMT software covers the rest of the rule.

Credentials at fleet scale

The federal minimums apply to every driver, whatever the fleet size. Section 209 of the Consolidated Appropriations Act, 2021 sets four conditions. The company and its drivers stay off federal health care exclusion lists. Each driver is licensed. The company keeps a procedure for drivers who break state drug laws, and it reports its drivers’ histories behind the wheel to the state Medicaid office.

Brokers add their own list. MTM Health’s Virginia handbook wants drivers who are 21 or older and have driven for two years or more. They must meet driving record limits, clear background checks, and finish passenger assistance, HIPAA, and defensive driving training before their first trip. Vehicles are inspected before service and again every six months.

The numbers add up quickly. In an example company of 40 drivers with six dated items each, that is 240 dates to watch, before counting registration, insurance, and inspection dates for every van. The penalty for missing one lands on the company. The same handbook adds two points for every expired credential, the driver’s or the van’s, each time one is used on a trip. Three points suspends a provider from the broker’s trip marketplace. Software for a large fleet should warn before an expiration and stop an expired driver or van from being assigned. For what belongs in each file, use the driver file checklist.

Reports a large fleet should run every week

Brokers score large fleets with numbers, so the fleet should see the same numbers first. Under MTM Health’s Virginia handbook, a pickup is on time if the driver shows up no more than 15 minutes early or late, and the standards are:

Running those weekly, by driver and by payer, turns a scorecard surprise into a Monday fix. Three internal reports round out the picture:

• On-time performance by driver. A fleet average hides the two drivers who cause most late pickups.
• Payer summary. Completed trips, cancellations, billed revenue, and what is still owed, per payer.
• Trip log. Every leg with scheduled and actual times, driver, vehicle, and miles. New York, for example, wants a record for each leg, kept for six years from the payment date, and takes the money back when a record is incomplete.

The NEMT KPIs guide explains how to read each number and what good looks like.

Test software with one of your own days

A sales demo shows a clean sample day. A large fleet should run a real one instead. Pull a recent busy day, remove rider names, and ask each vendor to load it. Then walk through the events that actually cost you time:

• a driver who calls out at 6 a.m. with 10 trips on the manifest,
• a cluster of will-call returns from one hospital in the same hour,
• a same-day discharge that needs a stretcher van,
• a standing order that moves to a new day for one week,
• a new dispatcher who should see trips but not invoices.

Watch how many clicks each fix takes and whether every desk sees the change at once. That tells you more than any feature list.

What to look for in NEMT software for a large fleet

1. One live board for everyone. Changes appear for every dispatcher the moment they happen, with no refresh.
2. Automatic day planning with review. The software proposes the plan, respects locked trips and vehicle equipment, and changes nothing until a dispatcher applies it.
3. Roles you define. Each seat sees what the job needs, and every change is recorded with who made it.
4. Strong sign-in. Individual logins with a second factor or passkeys.
5. Credential tracking with guards. Reminders before expirations and warnings before an expired driver or van is assigned.
6. Broker-ready reports. On-time performance, trip logs, and payer summaries that export as a spreadsheet or PDF.
7. Speed at your size. The board should stay fast with hundreds of trips and dozens of drivers on screen.
8. Pricing that scales predictably. Know what adding ten vans costs before you add them.

Running a large fleet in HealthRide

Several dispatchers can work the HealthRide dispatch board at once, and every change shows up for everyone in real time. With Ryder Go, you plan the whole day in one click. It puts wheelchair, stretcher, and oxygen trips only on vehicles equipped for them and leaves your locked trips where you put them. Each login shows only what that person’s role allows, every change is recorded, and reports cover on-time performance, trip logs, payers, and driver activity.