How to Choose NEMT Software: A Buyer's Checklist for 2026
To choose NEMT software, start with your own numbers: trips per day, vehicles, service levels, payers, and how trips arrive. Shortlist tools that cover scheduling, dispatch, a driver app, and billing in one system. Run each demo on a real day of your trips, get a signed business associate agreement, confirm you can export your data, and compare the full monthly cost for your fleet.
On this page
Start with your own operation
Every vendor demos a perfect day. Your own numbers keep the demo honest, so write them down before the first call. They also tell you which features matter and which ones you would pay for and never use.
| Write down | Why it matters |
|---|---|
| Trips per day, per vehicle, and on your busiest day | Sets the load the software must handle and your cost per trip |
| Vehicles by type: sedan, wheelchair van, stretcher | Drives the matching rules the software has to enforce |
| Payers and their share of trips: each broker, facility, and private pay | Tells you which billing and export formats you need |
| How trips arrive: broker portal, phone, fax, facility email | Shows how much intake work the software must remove |
| Share of standing orders and will-calls | Recurring and will-call handling become must-haves |
| Staff: dispatchers, billers, drivers, and the languages drivers speak | Sets user counts and driver app requirements |
| Your three worst recurring problems | These become your demo test cases |
If you are still on paper or a spreadsheet, the spreadsheet vs software guide helps you put a number on what the current setup costs. If you are new to the category, what NEMT software does explains each part.
The capabilities to require
These are the parts a working NEMT operation touches every day. For each one, the right column is the test to run during the demo.
| Capability | What good looks like | Test it in the demo |
|---|---|---|
| Scheduling | Round trips, recurring series, will-call returns, pickup time worked back from the appointment time | Book a Monday, Wednesday, Friday dialysis series, then move one Wednesday without touching the rest |
| Dispatch board | The whole day on one screen, assignment by drag and drop, warnings for mismatches | Try to put a wheelchair rider on a sedan and see what happens |
| Automatic planning | Plans the whole day, respects equipment, time windows, and locked trips, shows the plan before applying it | Run it on one of your real days and ask what it could not place and why |
| Driver app | iOS and Android, status taps, signatures, works without signal, opens navigation | Hand the phone to one of your drivers for ten minutes |
| Live map | Every vehicle’s position and status, early warning when a trip will run late | Ask how far ahead it flags a late pickup |
| Billing | Rates per payer, mileage, invoices, payment tracking, accounting export | Bill last month’s trips for one facility |
| Reports | On-time performance, trip log with actual times and miles, payer summary | Export a week’s trip log and check it against what your broker asks for |
| Compliance | Reminders before licenses, training, and inspections expire | Ask what happens when you assign a driver with an expired credential |
| Access control | A login per person, permissions by role, an activity record | Ask to see what a driver login can and cannot open |
Automatic planning deserves extra time in the demo, because it decides how many trips each van can carry. The route optimization guide explains what a good optimizer weighs and how to judge its plans.
The records your software has to produce
Payers audit trip records, so the software has to capture them while the day runs, not rebuild them afterward. CareOregon’s transportation provider manual (February 2024) is a useful benchmark. It sets a minimum record for every trip: member name, pickup location, scheduled and actual pickup times, destination, appointment time, drop-off time, mode of transport, provider and driver names, date, authorization or trip number, trip cost, mileage, and the vehicle’s ID or plate. It requires providers to keep that documentation for at least six years.
During the demo, have the vendor show three things for one completed leg:
- Where each of those fields is stored.
- How the driver’s taps fill in the actual times and the signature.
- How the trip log exports for an auditor, as a spreadsheet and as a printable file.
Get the answers in writing. The documentation requirements guide covers the records payers commonly ask for.
How to run a demo that tells you something
A scripted demo shows the product. A demo on your own trips shows whether it fits. Run it this way:
- Send a real day ahead of time. Pick 20 to 30 trips from a normal weekday. Strip names, member IDs, and phone numbers, and swap home addresses for a nearby cross street, so you share as little patient data as possible before an agreement is in place.
- Ask them to build your day live. Not a demo account. Your trips, your vehicles, your drivers’ shifts.
- Throw the usual curveballs. A driver calls out at 6:45 AM. A will-call comes in at 1:40 PM. A rider is a no-show. A hospital discharge gets added at noon. A wheelchair rider was booked as ambulatory.
- Watch the driver side. Status taps, signature capture, and what happens with no signal in a parking garage.
- Bill the day. Price the trips at your payers’ rates and produce the invoice or export.
- Export everything. Riders, trips, invoices. You want to know now that your data can come out in a standard format.
- Call support. During your busiest hour, not theirs.
- Talk to a customer your size. Ask how the first month went, who loaded their riders and recurring rides, and how drivers were trained.
Score each vendor on the same sheet. A simple 1 to 5 score for each row of the capability table, weighted by your three worst problems, beats a gut feeling after three demos that blur together.
HIPAA, security, and your data
Your rider list is patient information, so the vendor relationship is regulated. Four checks:
- Business associate agreement. HIPAA defines a business associate as a person or company that creates, receives, maintains, or transmits protected health information on behalf of a covered entity (45 CFR 160.103). A dispatch system that stores your riders’ names, addresses, and trip details fits that definition. The agreement must cover the terms in 45 CFR 164.504(e), including breach reporting and returning or destroying data at the end.
- Logins and activity records. The HIPAA Security Rule requires unique user identification and audit controls that record activity in systems holding electronic health information (45 CFR 164.312). One shared dispatch login fails the first test.
- Record keeping. Medicaid provider agreements require you to keep the records needed to show the extent of services you furnished and to produce them on request (42 CFR 431.107). Your state and broker contracts set how long. Ask how long the vendor keeps trip records and how you get them out.
- Export on exit. Get the export formats and the exit process in the contract, not in a sales email.
Pricing and contract terms
Most published NEMT software prices are per vehicle per month. Others charge a flat base plus a per-trip fee, price by fleet-size tier, or quote on request, and some add setup, onboarding, or add-on fees. The NEMT software pricing comparison lists published prices, so this section covers the math.
Here is a worked example with illustrative prices that are not any vendor’s. A 10-van fleet runs 8 legs per van on 22 working days, or 1,760 legs a month.
| Model | Illustrative price | Monthly cost | Cost per leg |
|---|---|---|---|
| Per vehicle | $75 per vehicle | $750 | $0.43 |
| Per trip | $0.45 per leg | $792 | $0.45 |
| Per vehicle plus setup | $75 per vehicle plus $1,200 setup spread over 12 months | $850 | $0.48 |
At these prices the two main models cost the same at about 167 legs per van a month ($75 ÷ $0.45), or roughly 7.6 legs a day over 22 working days. Busier vans favor per-vehicle pricing, and per-trip pricing costs more as each van does more work. Setup fees matter most if you might leave in the first year.
Before you sign, check the contract for:
- Term length, automatic renewal, and the cancellation notice period
- Limits on price increases at renewal
- What counts as a billable vehicle or user
- Fees for implementation, training, text messages, and extra modules
- Who loads your existing riders, places, and recurring rides, and what it costs
- Data export on exit, in writing
- Support hours that match your operating hours
Red flags
- The vendor will not run the demo on your own trips.
- You must sign a long contract before you have run a real day on the product.
- Your data cannot be exported in a standard format.
- There is no business associate agreement, or it arrives after signing.
- The price you will actually pay is not in writing before you sign.
For a shortlist of platforms with published prices, start with the best NEMT software roundup, then use this checklist on the two or three that fit.
How HealthRide approaches it
HealthRide keeps scheduling, the dispatch board, the driver app for iOS and Android, the live map, invoicing, and reports in one system. Ryder Go plans and assigns the whole day in one click, and you can review each plan before it applies. Pricing is $59 per vehicle per month, month-to-month, with no setup fees. Patient information is encrypted and protected, your team only sees what their role allows, and we sign business associate agreements with our providers.
Frequently asked questions
- How much time should I plan for moving to a new system?
- Plan the move around your data, not a fixed number of days. Riders, addresses, standing orders, rates, and drivers have to come across cleanly, and every driver needs the new app installed and tested. Running both systems side by side for a few days before cutover is the safest way to do it.
- Should dispatch and billing be in the same system?
- Yes, when you can get both done well in one product. A completed leg then carries its actual times, miles, and signature straight onto the invoice. Split systems mean someone re-types or re-imports trips every week, and that is where billing errors and missed trips creep in.
- Do I need route optimization with a small fleet?
- Not on day one. With two or three vans, an experienced dispatcher can plan a day by hand. The value grows with each added vehicle, service level, and same-day change, because the number of possible plans grows much faster than the fleet. Test it on a real day of your trips before you pay extra for it.
- Can I just use my broker's portal instead of buying software?
- Only if all your work comes from one broker and you never need to plan across it. A broker portal shows the trips that broker assigned to you. It does not plan your drivers' days, carry facility or private-pay work, or bill other payers. With two brokers you have two portals and no single view of your fleet.
- What should a business associate agreement with a software vendor include?
- Under 45 CFR 164.504(e), it must limit how the vendor uses your patients' information, require safeguards, require the vendor to report breaches to you, bind any subcontractors to the same terms, and require the vendor to return or destroy the data when the contract ends if that is feasible. Ask for the agreement before you sign the order.
- Is per-vehicle or per-trip pricing cheaper?
- It depends on how busy each vehicle is. Per-vehicle pricing gets cheaper per trip as each van runs more trips, while per-trip pricing grows with every ride. Work out the monthly bill both ways using your real trip counts before comparing vendors.