Guides
NEMT software requirements for the trip's paper trail
A practical guide to NEMT software for trip records, routing, dispatch, payer-specific cash tracking, data exports, and security.
What to take away
- The system's job is to carry one trip from a phone call to a paid invoice without anybody retyping it. Everything else is a feature.
- Four things a spreadsheet cannot do well herehold access notes that improve over time, match a chair to a vehicle, capture times at the door, and age receivables by payer.
- Your payer mix, not your revenue, decides your cash position. Track days to payment separately for each payer or you will be surprised by an average.
- You hold information about people's health appointments and home addresses. That makes security an operating requirement rather than an afterthought.
- Before configuring the system, check the record requirements set by your state Medicaid agency, its broker where applicable, and your contracts.
Owners ask which NEMT software to buy long before they can say what it has to do. The useful order is the reverse: describe the chain a trip travels along, find where information currently gets retyped or lost, and then look at tools.
The chain a trip travels
The chain a trip travels
- Booking: passenger details, access notes
- Authorization: payer requires it
- Assignment: vehicle and driver
- Execution: times captured at each end
- Close-out: record payer requires
- Invoicing
- Remittance and reconciliation
Seven steps. Keep a record at each handoff:
- Book the trip:record the passenger, pickup and drop-off locations, appointment window, and requested service.
- Verify requirements:check the payer, authorization status, medical-necessity requirements, and any required form or service code.
- Assign the trip:match a driver and accessible vehicle to the passenger and trip.
- Record pickup:capture the actual time and any required passenger or representative attestation.
- Track the trip:record mileage or odometer readings and any exceptions, where required.
- Close out service:capture the actual drop-off time, return-trip status, and required attestation.
- Bill and reconcile:submit the claim or invoice, track remittance, and reconcile payment against the trip.
Every retyping is a point where an error enters, and errors at the close-out step are the ones that turn delivered work into unpaid work.
Draw your own chain on one sheet and mark where retyping happens now. That drawing is your requirements document, and it is more useful than any feature list.
For routing, build requirements around each trip's pickup and drop-off locations, appointment window, authorization status, vehicle accessibility and capacity, and return-trip status. Dispatch should help assign compatible trips and sequence them around time windows, then capture actual service times and mileage so you can compare the plan with what happened and spot avoidable empty miles or late arrivals.
Two steps deserve particular attention because they are where money is lost rather than time. Authorization, because a trip run without one that was required is a trip you may never be paid for. And close-out, because a record completed hours later is a record that will disagree with somebody else's account of the same trip.
What a spreadsheet genuinely cannot do
A spreadsheet runs a single vehicle adequately. It fails on four things, and each failure has a cost.
| Function | Why a spreadsheet struggles | What it costs |
|---|
What a spreadsheet cannot do
Spreadsheet
- Access notes
- Nowhere to live
- Vehicle and chair
- No constraint check
- Door times
- Typed later
- Aging by payer
- Rarely maintained
NEMT software
- Access notes
- Per address
- Vehicle and chair
- Matched at assignment
- Door times
- Captured at door
- Aging by payer
- Maintained
Use this function-by-function test to identify where a spreadsheet creates operational risk:
| Function | Why a spreadsheet struggles | What it costs |
|---|---|---|
| Access notes | Instructions can be scattered across files or become outdated between trips. | Disrupted pickups and repeated work to recover or confirm instructions. |
| Chair-to-vehicle matching | A spreadsheet may not reliably flag whether the assigned vehicle fits the passenger's mobility equipment. | A trip that cannot be completed as planned and time spent arranging another vehicle. |
| Times at the door | Actual pickup and drop-off times may be entered later or reconstructed from memory. | Weaker close-out records and billing disputes. |
| Receivables by payer | Payment status can be difficult to connect to each payer and invoice. | Late accounts can be obscured by an overall average, delaying follow-up. |
- Access notes:Keep pickup instructions and building-access details available to the people handling that passenger's trips. Missing or outdated notes can disrupt pickup.
- Chair-to-vehicle matching:Check that the assigned vehicle fits the passenger's mobility equipment before dispatch. A mismatch can make the trip impossible to complete as planned.
- Times at the door:Capture actual service times when the pickup and drop-off happen, rather than reconstructing them later. Delayed entries can weaken close-out records and billing.
- Receivables by payer:Connect invoices and payment status to each payer so overdue accounts are visible. Without that view, a late payer can be obscured by an overall average.
The third of those is the one to solve first, because close-out quality decides both your payment and your defense in an audit.
Choosing without a demonstration script is choosing blind
Do not evaluate on a guided demonstration. Bring your own trips.
Test with your own trips
- Bring one week of real bookings
- Include a will-call return
- Include a chair fitting one vehicle
- Include a cancellation inside your window
- Include a trip that overran
- Enter the data yourself
- Score during the session
Take one week of real bookings, including the awkward ones: a will-call return, a passenger whose chair fits only one vehicle, a cancellation inside your window, and a trip that overran. Ask to enter them and follow each through to an invoice.
You are testing whether the tool handles the hard parts of your week, not the easy ones.
Insist on entering the data yourself rather than watching somebody else do it. The difference between a tool that is usable and a tool that is demonstrable is entirely in who is holding the keyboard.
Score each candidate on the same set of your own trips, and write the scores down during the session rather than afterward. Impressions of software decay within a day, and the vendor's follow-up call is designed to replace them.
Get your data out before you put it in
Ask, before signing anything: can I export my passengers, my trips, my access notes and my invoices in a usable format, such as CSV, whenever I want?
An operation's access notes are years of accumulated knowledge about buildings and people. Losing them at a migration is worse than losing the software. Ask for an export during the trial and look at what actually comes out.
The money side, in the order it bites
Cash, not profit, is what ends small operations in this trade. A few habits matter more than any accounting sophistication.
The money side, in order
- Age receivables by payer, not in total
- Reconcile remittances against trips
- Separate owed from billed
- Keep documents supporting what you billed
The Internal Revenue Service expects businesses to keep documents supporting what they billed. Under 42 CFR 431.107(b), Medicaid provider agreements require providers to keep records that disclose the extent of services furnished and provide information about payments claimed. Requirements vary by program; for example, California's Medi-Cal Provider Manual sets program-specific NEMT requirements. Check the applicable state Medicaid agency provider manual and, where applicable, your broker's contract before configuring the software.
Build the trip record around the payer's requirements. Fields to confirm include the date of service, passenger or member identifier, pickup and drop-off locations, appointment time, authorization number, applicable service or level-of-service code, driver and vehicle IDs, actual pickup and drop-off times, mileage or odometer readings, and any required signature or attestation. Capture the required prior-authorization or medical-necessity form name and number, too; there is no single trip-ticket form or set of codes that applies to every state and payer.
Retention periods for NEMT trip records depend on the state program and broker contract, so confirm the applicable deadline and audit requirements before setting a deletion schedule. Where HIPAA applies, retain documentation required by HIPAA for six years from its creation or last effective date, whichever is later (45 CFR 164.316(b)(2)(i) and 164.530(j)); that is not a universal six-year retention rule for trip records. Keep records available for any open audit or appeal.
The Centers for Medicare and Medicaid Services page on the benefit explains that states administer it. Which bodies set yours is mapped in the licensing and compliance guide.
Security is an operating requirement here
Your records say who is going to dialysis on Tuesdays and where they live alone. That is information worth protecting. The Health Insurance Portability and Accountability Act (HIPAA), including its Privacy, Security, and Breach Notification Rules, may apply if your operation is a covered entity or business associate; applicability depends on your arrangements and contracts, so get advice.
Security as an operating requirement
- Accounts, access, backups
- Plan for a lost phone
- Decide who can see what
- Driver sees today's trips only
- Remove access the same day
- Avoid shared logins
- Note which systems a role touches
The practical side is clear: the NIST small business quick-start guides and CISA resources for small and medium businesses are written for operations this size.
Both start where you should: accounts, access, backups, and what happens when a phone is lost. In a business where dispatch runs on personal phones, that last question is not hypothetical.
Decide who can see what. A driver needs today's trips and the access notes for them. A driver does not need the whole passenger list.
Decide also what happens when somebody leaves. Access removed the same day, shared logins avoided so that removal is possible at all, and a written note of which systems a role touches. Small operations run on shared accounts because it is convenient, and then cannot revoke anything without disrupting everyone.
What the numbers are for
The system exists to answer questions you will actually act on: which accounts run late, which trips consume more time than they were priced for, how long each payer takes, and where the empty miles are.
Those feed the pricing arithmetic in the pricing and profit guide and the evidence you bring to an account review, which is the subject of the sales and proposal guide. If a report cannot change a decision, stop producing it.
Start smaller than you think
A one-vehicle operation with a disciplined paper process and a phone camera for confirmations can produce better records than a three-vehicle operation with software nobody was trained on.
The order that works: fix the process, then choose the tool that supports it, then train properly and check the records for a month. Software adopted to fix a process problem reliably produces the same problem with a subscription attached.
The daily process it has to support is described in the operations and workflow guide. The people who have to use it are in the hiring and training guide, and the vehicles it has to know about in the fleet and premises guide.
Common questions
At what point does a small operation need dedicated software?
Usually when one person can no longer hold the day in their head, which is somewhere around the second or third vehicle. Before that, the constraint is process discipline rather than tooling.
Should billing and dispatch be the same system?
It helps, because the close-out record is the billing record and separating them creates a retyping step. Where they are separate, test the handover with your own awkward trips.
Do I need an accountant?
For the setup, yes, particularly around payer mix and how trips are recognized. Getting the structure right once is cheaper than fixing a year of records.
What is the single most valuable report?
Days to payment by payer, watched monthly. It moves before anything else does and it is the number that predicts a cash problem while there is still time to act.
