How to use this list
Every demo looks smooth because vendors rehearse the happy path. Your job is to steer the session toward your hard days: the dialysis standing order that changes, the 2 p.m. will-call surge, the claim a broker rejected. Ask the presenter to perform tasks live in the product rather than describe them, and bring a few of your real (anonymized) scenarios.
Send your top questions ahead of time so the vendor brings the right people, and take notes on what you saw done versus what you were told is possible. "On the roadmap" means "does not exist today."
Scheduling and recurring trips
Recurring riders are the backbone of most NEMT books of business, so scheduling questions come first.
- 1. Show me how you create a dialysis standing order for Monday-Wednesday-Friday with a will-call return — and then skip one occurrence for a holiday. This reveals whether recurring trips are a real feature or a copy-paste workaround.
- 2. What happens to future occurrences when the linked authorization expires? You are checking whether the system prevents unbillable phantom trips or silently keeps generating them.
- 3. How do I import a broker trip file, and what happens when today's file conflicts with trips already scheduled? Reconciliation, not import, is the hard part.
Dispatch and day-of changes
The dispatch board is where your team lives all day, so make the vendor drive it under realistic pressure.
- 4. A rider cancels at 6:45 a.m. and a will-call return pops up at 1 p.m. — walk me through handling both. Watch how many clicks and screens it takes.
- 5. How does a dispatcher see which trips are at risk of running late right now? Look for live status and exception flags, not a static list.
- 6. Can I reassign a trip mid-route, and how does the driver get and acknowledge the change? Unacknowledged changes are how riders get stranded.
Routing and optimization
Optimization claims are easy to make and hard to verify, so ask for specifics with your constraints.
- 7. What constraints does the optimizer actually enforce — wheelchair capacity per vehicle, securement and load times, ride-time limits, driver shifts? Ask to see each one configured.
- 8. Can it re-optimize mid-day after cancellations and add-ons without scrambling trips already in progress? Day-of re-planning is where many tools fall short.
- 9. How does it handle rider-vehicle matching, like a power chair that only two of my vans can carry? Generic routing engines usually cannot.
Driver app
A driver app your drivers will not use produces no data, so evaluate it from the driver's seat.
- 10. Show me a full trip from the driver's view — statuses, navigation, signature capture, and a trip note. Count the taps; drivers will.
- 11. What happens when the driver loses cell coverage mid-trip? You want offline capture that syncs later, not lost timestamps.
- 12. Can drivers see only their own manifest, and can I control what rider information they see? This is both a privacy and a simplicity question.
Billing and claims
Billing is where software pays for itself or quietly costs you. Bring the name of every broker and payer you bill.
- 13. Which of my specific brokers and payers do you support for claim submission today, and in what format? Get names, not "most major brokers."
- 14. Show me the workflow when a claim is denied — how do I see why, fix it, and resubmit? Denial rework is the daily reality of NEMT billing.
- 15. How does the system stop a trip with missing documentation — no drop-off timestamp, no signature — from being billed? Prevention beats clawbacks.
Integrations and data migration
You are not starting from zero — riders, standing orders, and history live somewhere today.
- 16. How do you migrate my existing riders, standing orders, and driver records, and who does the work? Ask what a typical migration timeline looked like for a fleet your size.
- 17. What broker portals, clearinghouses, or hardware (tablets, telematics) do you integrate with out of the box? "We have an API" is not an integration.
- 18. Can I export all of my data — trips, claims, GPS history — in a standard format if I ever leave? Data portability is leverage you negotiate before signing.
Reporting
Reports are how you run the business and answer brokers, so test them against questions you actually get asked.
- 19. Show me on-time performance by driver, by broker, and by day — filtered live, not a canned screenshot. Broker scorecards depend on this.
- 20. Can I reproduce the documentation for one billed trip from six months ago in under five minutes? That is the audit-readiness test.
- 21. Can I build or schedule custom reports myself, or does every new report go through the vendor? Vendor-only reporting becomes a bottleneck.
Security and compliance
You handle protected health information, so security answers should be specific and in writing.
- 22. Will you sign a Business Associate Agreement, and how is rider data encrypted in transit and at rest? A HIPAA-serious vendor answers this without flinching.
- 23. How do role-based permissions and audit logs work — can I see who viewed or edited a trip record? Also ask how credential expirations (licenses, inspections) are tracked and alerted.
Pricing, contract, implementation, and support
Total cost and go-live experience vary more between vendors than feature lists do, so pin both down before you leave the call.
- 24. What is the all-in cost for my fleet size — including implementation, training, per-driver or per-vehicle fees, SMS or mapping usage charges, and support tiers — and what is the contract term and exit clause? Ask for it in writing.
- 25. Walk me through implementation week by week: who trains my dispatchers and drivers, how long until my first fully live day, and what support do I get at 6 a.m. when something breaks? Ask to speak to a reference customer of similar size.
After the demo: scoring and next steps
Score each vendor on the same questions within a day of the demo, while details are fresh, and mark each answer as demonstrated, claimed, or roadmap. Shortlist two vendors and ask each for a trial or sandbox with a slice of your real trip data — an afternoon of your dispatcher clicking through actual work reveals more than three demos.
If you want to see how Axen answers this list, its team runs demos against exactly these scenarios — bring your hardest day.
Related resources
Frequently asked questions
How long should an NEMT software demo take?
Plan for 60–90 minutes to cover scheduling, dispatch, driver app, and billing with live scenarios. If a vendor cannot show your key workflows in that time, schedule a focused follow-up rather than accepting a description.
Who should attend an NEMT software demo?
At minimum the owner or manager, a senior dispatcher, and whoever handles billing. Each sees different failure modes — dispatchers catch clunky day-of workflows, billers catch claim and denial gaps that owners miss.
What is the biggest red flag in a software demo?
Answers that describe instead of demonstrate. If the presenter cannot perform a standing-order change, a mid-day reassignment, or a denial rework live in the product, assume the workflow is weaker than claimed.
Should I ask for a trial before buying NEMT software?
Yes, or at least a sandbox loaded with a sample of your own trips. Hands-on time with real data exposes usability and data-fit issues that no demo will, and serious vendors accommodate it.