# How to Choose NEMT Software in 2027: A Buyer's Checklist

Canonical URL: https://nemtguide.com/guides/how-to-choose-nemt-software/ · Updated 2026-09-28

To choose NEMT software, start with what your brokers and state require: how trips reach you, the GPS, times, and signatures each one wants back, and the claim format each payer takes. Then make sure the vendor signs a HIPAA business associate agreement, lets you export all your records, answers support during your service hours, and prices in a way you can predict.

- Write down what each broker and your state require before any demo. Their GPS, trip log, and claim rules decide which software can work for you.
- Any vendor that stores or sends rider information for you must sign a HIPAA business associate agreement first. HHS says it may not lock you out of your records, even in a payment dispute.
- Keep trip records reachable for years. MTM Health's standard agreement requires 10 years, and plan audit rights can last 10 years after a contract ends.
- Judge any AI feature on a day of your own trips. Ask for six months of release notes, and confirm your agreement covers any outside AI service that sees rider information.
- Compare the full price at your fleet size and at twice that size, including setup, broker connections, and extra logins.

NEMT software runs your whole day: trips in, driver schedules, the driver app, trip records, and claims out. A poor fit costs you in denied claims and hours of retyping. This checklist helps you compare vendors on what matters to a small NEMT company, and it starts with the rules your payers already set.

## Start with what your brokers and state require

Your brokers and your state decide much of what the software must do. Before you book a demo, write down how each payer sends trips and what it wants back. Four published examples show how much they differ:

| Payer | How trips reach you | What must come back |
|---|---|---|
| MTM Health, Virginia (handbook approved August 10, 2026) | Trip manifests in MTM's provider portal, or sent straight to your own routing software by an API connection | Vehicle location tracking on for the whole ride, from MTM's free driver app or compatible software connected by API. An electronic trip log with the trip ID, scheduled and actual pickup times, departure and arrival times, and the member's signature. |
| Medical Answering Services, New York (since April 3, 2023) | Trip invoices from the state's broker | The starting point, end point, and every GPS point along the trip. GPS that does not match the pickup, drop-off, or miles on the invoice blocks the prior authorization the claim needs. |
| Arizona fee-for-service (manual revised July 31, 2026) | Rides you schedule and bill to AHCCCS directly | Only the state's own Daily Trip Report, on paper or a tablet. Electronic copies go in as PDF files, never HTML or Excel. Electronic claims carry the full pickup and drop-off addresses. |
| MediTrans, Louisiana (September 2026) | Trip offers in its provider portal | En route, arrived, and completed status in the portal, no-shows with a time stamp, and trip documentation within 24 hours of the trip |

Some brokers keep most of the work in their own portals. Verida, for example, describes a secure provider portal for trip manifests, claims, reports, and forms, with automated trip documentation and electronic claims.

Three things follow from this. First, a broker connection is not a yes or no question: ask which of your brokers the software connects to, and what moves each way. MTM's Virginia handbook says it connects with over 20 outside applications, so ask for yours by name. Second, the driver app must produce the exact records each payer checks. Third, some payers need their own paper form or portal no matter what software you use.

In New York, a billing or routing company working for you must register with the broker and get a data key for each client, and billing companies must enroll with New York Medicaid as a service bureau. The broker's network manual (October 1, 2023) also warns that routing data that does not show the driver's actual location and time will be treated as possible fraud and reported to the state. Ask any vendor for New York trips whether it is already registered.

For how trips come out of broker portals, see NEMT broker trip imports. For what each record must hold, see [NEMT trip documentation requirements](https://nemtguide.com/guides/nemt-trip-documentation/).

## The buyer's checklist

Use this list in every demo. Ask the vendor to show each item on screen with a real trip, not describe it.

### Trips in

- **Broker connections.** Trips import from each of your brokers, with changes and cancellations updating on their own. Ask how often the connection checks for changes.
- **The full manifest.** MTM's Virginia manifests carry the trip ID, member name and phone, pickup and appointment addresses and times, the doctor's name and phone, mode and level of assistance, any escort, and the member's weight with mobility devices. Every field should come through, with nothing retyped.
- **Facility and private pay trips.** You can enter your own trips next to broker trips, with standing orders for repeat riders such as dialysis.

### Scheduling and dispatch

- **Level of service matching.** A wheelchair trip cannot land on a sedan by mistake.
- **Conflict warnings.** MTM's Virginia handbook tracks overlapping claims, meaning one driver in two vehicles or two drivers in one vehicle at the same time, with a standard of under 0.99 percent. The software should flag these before a claim goes out.
- **Automatic assignment you can check.** If the software builds or suggests routes on its own, a dispatcher can review and change each assignment before it reaches drivers, and every trip still matches its level of service.
- **Will-calls and same-day changes.** Dispatch can place a return the moment the rider calls. See [NEMT dispatch](https://nemtguide.com/guides/nemt-dispatch/) and [NEMT scheduling](https://nemtguide.com/guides/nemt-scheduling/).

### The driver app

- **Status taps with time and GPS.** En route, arrived, picked up, and dropped off, each saved with the time and location.
- **A GPS trail, not just start and end points.** New York requires every coordinate along the trip.
- **Works with no signal.** It keeps recording in a dead zone and uploads later. New York's broker says GPS data can be sent during or after a trip when a problem outside your control got in the way.
- **Real signatures.** On a tablet, Arizona wants a signature drawn with a pen or fingertip, or a fingerprint when the rider cannot sign. A typed name does not count for the rider or the driver, and a driver's initials or stamp does not either.
- **No-shows with proof.** A time stamp and location for every no-show.
- **Safe phone use.** MTM's Virginia handbook says drivers should never use a mobile device while driving, except a Bluetooth headset. Ask how the app handles that.

See NEMT driver app and NEMT GPS tracking for more.

### Billing

- **Broker claims that sync, or a clean upload.** In MTM Health's Rhode Island program (handbook updated July 1, 2026), trip logs and signatures from its driver app or approved routing software sync to its portal. Companies without either upload claims on MTM's spreadsheet template, unchanged, with each signature as a separate file. MTM still tells providers to check every synced trip before submitting.
- **State Medicaid formats.** The HIPAA standard electronic transactions: the 837 professional claim (version 5010, ASC X12N 005010X222), the 835 remittance (005010X221), and the 270/271 eligibility check (005010X279).
- **Filing deadlines on every trip.** MTM's standard agreement gives 90 days unless the state or plan sets another limit, its Virginia handbook gives 6 months, and MediTrans gives 365 days.
- **Checks before a claim goes out.** The software flags any trip missing a field your payer requires, such as the actual pickup time or member signature MTM's Virginia handbook lists, so you fix it before a denial.
- **Denials and appeals.** Denied claims show the reason and the appeal deadline, such as the 365 days MTM's Virginia handbook allows.
- **Payments matched to trips.** Each payment and remittance links back to its trip, so you can see what is still unpaid.

See [how to bill NEMT brokers](https://nemtguide.com/guides/how-to-bill-nemt-brokers/) and [how to bill Medicaid for NEMT](https://nemtguide.com/guides/how-to-bill-medicaid-for-nemt/).

### Records and security

- **Records for as long as you need them.** MTM's standard agreement, in the January 1, 2023 version Pennsylvania posts, requires full records for 10 years. When a Medicaid health plan hands its rides to a broker, federal rules let the state, CMS, the HHS Inspector General, and the Comptroller General audit the records and computer systems of the broker and of its contractors, which includes you. That right lasts 10 years from the end of the contract period or the last audit, whichever is later ([42 CFR 438.230](https://www.ecfr.gov/current/title-42/section-438.230)).
- **One login per person.** Unique user identification is a required HIPAA safeguard ([45 CFR 164.312](https://www.ecfr.gov/current/title-45/section-164.312)).
- **A record of who did what.** Audit controls that record activity are required too.
- **Automatic logoff and encryption.** Both are addressable safeguards under today's rule. You use them where reasonable and appropriate, or document why not and use an equal alternative where reasonable ([45 CFR 164.306(d)](https://www.ecfr.gov/current/title-45/section-164.306)).
- **Backups and recovery.** A data backup plan and a disaster recovery plan are required parts of your contingency plan ([45 CFR 164.308](https://www.ecfr.gov/current/title-45/section-164.308)).

A change may be coming. HHS proposed on January 6, 2025 to require encryption of electronic health information at rest and in transit, and multi-factor login (90 FR 898). The latest federal regulatory agenda lists it as a long-term action, with the final rule planned for July 2027. As of September 28, 2026, it is not final, so ask vendors whether they already offer both.

## The HIPAA business associate agreement

When your company is covered by HIPAA, a software vendor that creates, receives, keeps, or sends rider health information for you is your business associate under [45 CFR 160.103](https://www.ecfr.gov/current/title-45/section-160.103). If a broker made you its business associate, your vendor is your subcontractor, and you need the same written assurances from it before it touches rider data ([45 CFR 164.502(e)](https://www.ecfr.gov/current/title-45/section-164.502)). HHS says this holds even for a cloud service that stores only encrypted data and has no key to read it.

Under [45 CFR 164.504(e)](https://www.ecfr.gov/current/title-45/section-164.504), the agreement must require the vendor to:

1. Use and share the information only as the agreement allows.
2. Use safeguards, including the Security Rule for electronic information.
3. Report any use or sharing the agreement does not allow, including breaches.
4. Bind its own subcontractors to the same terms.
5. Make information available for riders' access, amendment, and accounting requests.
6. Follow the Privacy Rule for any of your Privacy Rule duties it carries out.
7. Open its records to HHS.
8. Return or destroy the information when the agreement ends, where feasible.

It must also let you end the agreement if the vendor breaks a material term. After discovering a breach, a business associate must notify its client without unreasonable delay, and no later than 60 calendar days ([45 CFR 164.410](https://www.ecfr.gov/current/title-45/section-164.410)). Your broker may want to hear sooner, so ask the vendor to match your broker's deadline in writing.

HHS's cloud guidance also lists what a service agreement can cover: system availability, backup and data recovery, how data comes back to you when service ends, who is responsible for security, and limits on use and retention. HHS says HIPAA does not require a cloud vendor to let you audit it, but you can ask for documentation of its safeguards or audits in the agreement.

See business associate agreement, the business associate agreement checklist, and [HIPAA for NEMT providers](https://nemtguide.com/guides/hipaa-for-nemt/).

## Who owns your records, and how you get them out

Your trip logs, signatures, and GPS trails back up every claim you have been paid for. You need them for audits long after you stop using a vendor.

HHS guidance says what a business associate cannot do. It may not block its client's access to the health information it holds. HHS's example is a health records software developer that activates a "kill switch" to settle a payment dispute, which it calls an impermissible use. When the agreement ends and it calls for the information to be returned, the vendor must return it in a format that keeps it accessible and usable (HHS OCR FAQ 2074, reviewed January 9, 2023).

Put the details in the contract before you sign:

| Question | What a good answer looks like |
|---|---|
| What can I export? | Every trip, status time, GPS trail, signature, no-show, driver and vehicle file, claim, and payment |
| In what format? | Spreadsheet files for data, and PDF or image files for signed trip logs |
| How often, and at what cost? | Any time, from your own login, at no extra charge |
| What happens when I cancel? | A full export, then deletion within a stated number of days, with written proof of destruction |
| Can you cut off access over a billing dispute? | No, and the agreement says so |

The guide to switching NEMT software walks through a move from one system to another.

## How NEMT software is priced

Vendors use a handful of pricing models. None is better in every case. What matters is the total cost at your size and the size you plan to reach.

| Pricing model | What you pay for | Question to ask |
|---|---|---|
| Per vehicle | Each van in service, monthly | Do spare or out-of-service vans count? |
| Per driver | Each driver with app access | Do part-time and on-call drivers count? |
| Per user login | Each dispatcher, biller, and driver login | Is there a cap, and what does one more cost? |
| Per trip | Each completed trip, or each trip imported | Do canceled trips and no-shows count? |
| Flat tiers | A monthly price up to a limit | What happens when you pass the limit? |

Watch the add-ons: setup and training, data migration, each broker connection, text message reminders, payment processing for private pay riders, and exports. Price per user can tempt a company to share logins. HIPAA requires each person to have their own, so count every user honestly.

Read the contract terms as closely as the price: the length, any auto-renewal, the notice needed to cancel, limits on price increases, and what happens to your data at the end. Then compare vendors on the total for 12 months and for the full contract. See NEMT software cost.

## Support, training, and backup plans

Broker work starts early and runs into the weekend. MediTrans's Louisiana dispatch line, for example, opens at 5:00 a.m. Central time on weekdays and 6:00 a.m. on Saturdays, as of September 2026. Ask when the vendor's support answers, by phone or only by chat, how fast it responds, and who fixes a broken broker connection.

Plan for the day the system is down. HIPAA requires your own contingency plan, including a data backup plan, a disaster recovery plan, and an emergency mode plan that keeps critical work going while protecting rider data ([45 CFR 164.308(a)(7)](https://www.ecfr.gov/current/title-45/section-164.308)). MTM Health's Rhode Island handbook tells every driver to keep paper copies of approved trip logs as a backup, even with an app. Keep a printed copy of the next day's schedule too. Arizona, for one, accepts its Daily Trip Report on paper in blue or black ink.

Ask how the vendor sets you up: who loads your drivers, vehicles, standing orders, and rates, and how long training takes for dispatchers and drivers.

## How AI is changing NEMT software

An AI label in NEMT software can cover several kinds of work. Each one should save your office time without breaking a payer rule.

| AI feature | What it does | What to check |
|---|---|---|
| Automatic trip assignment and routing | Builds or suggests each driver's day from trip times, addresses, and vehicle types | Every trip keeps its level of service, and a dispatcher can change any assignment |
| Reading trip requests | Turns broker files and emailed requests into trips on your schedule | Every manifest field comes through, and anything it cannot read goes to a person |
| Live arrival estimates | Predicts when each van will reach each pickup | The estimate never replaces the GPS trail and status times payers check |
| Rider calls and texts | Answers routine questions, such as when the van will arrive | Anything the broker must approve goes to the broker |
| Claim checks | Flags a trip missing a required field before the claim goes out | It checks against each payer's own list |

### Why it matters to a small company

These features aim at the numbers brokers score. MTM Health's Virginia handbook (approved August 10, 2026) sets on-time performance above 95 percent, vendor no-shows under 0.25 percent, and denied claims under 0.29 percent. Missing them can bring a performance improvement plan, liquidated damages, or removal from the network. MediTrans in Louisiana asks for 95 percent on time or better and provider-caused no-shows under 1 percent, as of September 2026.

For a company with a few vans, the gain to look for is fewer office hours per trip: less time building tomorrow's schedule, answering "where is my ride" calls, and fixing rejected claims. Measure those hours, your late pickups, and your denied claims during a trial rather than trusting a sales figure.

Your contracts and state rules still apply to every trip the software touches. New York's broker treats routing data that does not show the driver's actual location and time as possible fraud, so a planned route never stands in for the real GPS trail. When a New York rider asks at the last minute to be picked up somewhere else, the broker tells the transportation company to send the rider to the broker for the change. MediTrans says not to reroute without its dispatch approval. An assistant that answers riders has to pass these requests on, not approve them.

### How to tell current technology from a label

Payer rules keep changing. New York's GPS trail rule took effect April 3, 2023. Arizona began requiring pickup and drop-off addresses on NEMT claims on November 1, 2022, and it revised its transportation billing chapter twice in 2026. Software has to keep up with each change, so favor a product that is still being improved. These tests show the difference:

1. **Run the demo on a day of your own trips.** A prepared sample day shows little. Real trips carry rider health information, so sign the business associate agreement before you share them.
2. **Ask for the release notes from the last six months.** Regular, dated updates show a product that is still being built. Ask what the vendor changed after the last broker rule change you had to follow.
3. **Ask who approves AI changes.** A dispatcher should be able to review automatic assignments and schedule changes before they reach drivers. You should be able to turn each AI feature off.
4. **Ask what each AI feature costs.** Find out whether it is included in your price or billed extra, and how: per trip, per message, or per month.

### Rider information and outside AI services

Some AI features send trip details to an outside AI service to do their work. HHS says a subcontractor that creates, receives, keeps, or sends health information for a business associate is a business associate too. Your vendor needs a written agreement with that service, with the same limits your own agreement sets, before it passes rider information on ([45 CFR 164.502(e)](https://www.ecfr.gov/current/title-45/section-164.502) and [164.308(b)](https://www.ecfr.gov/current/title-45/section-164.308)).

Ask the vendor which outside services see rider information, whether its business associate agreements cover them, and whether those services may keep or reuse your data. Then check that the answers match the business associate agreement you sign, covered in the section above.

### The AI label can be marketing

The Federal Trade Commission holds AI claims to the same laws as any other claim. On September 25, 2024, it announced Operation AI Comply, five law enforcement actions against companies that used AI hype or sold AI tools that could deceive. The FTC said there is no AI exemption from the laws on the books. Treat an AI feature like any other sales promise: see it work on your own trips, and put anything you pay for in the contract.

## Questions to ask in every demo

1. Which of my brokers do you connect with today? Can I speak with a company that uses that connection?
2. Show me a trip coming in from my broker, then changed and canceled by the broker. What happens on the driver's phone?
3. Turn off the phone's signal and run a trip. Does the app keep recording, and does it upload later?
4. Show me the finished trip record a broker or auditor will see, with times, GPS, and signature.
5. Will you sign a business associate agreement before I load rider data? Can I see it now?
6. Does every user get a unique login? Can I turn on two-step login?
7. Can I see who viewed or changed a trip, and when?
8. How do I export all my data, including signatures and GPS trails? What does it cost?
9. What happens to my data if I cancel, and will you certify that you deleted it?
10. Which claim formats do you produce for my state and each broker?
11. How do you track filing deadlines and denied claims?
12. What are your support hours, and how do I reach a person before my first pickup?
13. What is my full price today, and at twice my fleet? What add-ons are extra?
14. How long is the contract, does it renew on its own, and how much notice do I give to cancel?
15. When a broker changes its rules, such as a new GPS requirement, how fast do you update?
16. Which features use AI? Does any outside AI service see rider information, can a dispatcher review or turn off each feature, and what does it cost?

## A simple way to compare vendors

Score two or three vendors side by side. Any "no" in the first four rows rules a vendor out.

| Check | Vendor A | Vendor B | Vendor C |
|---|---|---|---|
| Meets every broker's and state's trip record rules | | | |
| Signs a business associate agreement | | | |
| Full data export at any time | | | |
| One login per person | | | |
| Broker trip import, 1 to 5 | | | |
| Scheduling and dispatch, 1 to 5 | | | |
| Driver app, 1 to 5 | | | |
| Billing and claim formats, 1 to 5 | | | |
| Support hours and response, 1 to 5 | | | |
| Total cost for the full contract | | | |

If you can, run a trial with a week of real trips before you sign. If you still run on paper and spreadsheets, NEMT spreadsheet vs software helps you decide when the switch pays. For a plain explanation of each tool, see [what NEMT software is](https://nemtguide.com/guides/what-is-nemt-software/).

## Frequently asked questions

### What should NEMT software do?

It should take in trips from each broker and facility, help you build each driver's day, give drivers an app that records times, GPS, and signatures, and turn completed trips into claims in the format each payer takes. It should also keep your records, protect rider information under HIPAA, and let you export everything. Your brokers' and state's rules set the minimum.

### Do I need NEMT software if my broker has a free app?

Not always. MTM Health's Virginia handbook says its free driver app meets its location tracking rule, and New York's broker points companies to a free GPS app that meets the state's minimum. A small company with one broker can start that way. Software earns its cost when you serve several brokers, facilities, and private pay riders and want one schedule and one set of records.

### Does NEMT software need to be HIPAA compliant?

Yes, if it holds rider information for a company covered by HIPAA or working as a broker's business associate. A vendor that creates, receives, keeps, or sends protected health information for you is then a business associate and must sign a business associate agreement. HHS says that is true even for a cloud service that stores only encrypted data and has no key to read it. Get the signed agreement before you load any rider names.

### Can I switch NEMT software later?

Yes, if you plan for it when you buy. Confirm in the contract that you can export all trips, signatures, GPS trails, driver and vehicle files, and claims in a usable format. HHS says a business associate must return health information when the agreement ends, where the agreement calls for it, in a format that keeps it usable. Also check the notice period and any auto-renewal.

### How is NEMT software priced?

Common models charge per vehicle, per driver, per user login, per trip, or a flat monthly tier, with add-ons such as setup, broker connections, and text messages. Compare the total cost over the whole contract at your current fleet and at the size you plan to reach. Count every dispatcher, biller, and driver who needs a login, because HIPAA requires one per person.

### Should I pick NEMT software with AI features?

Pick software first for how well it meets your brokers' and state's rules, then judge each AI feature on a day of your own trips. Useful ones cut office time on scheduling, rider calls, and claim fixes, which feed the on-time, no-show, and denial rates brokers score. Make sure a dispatcher can review or turn off each one, and that your business associate agreement covers any outside AI service that sees rider information.

### Which claim formats should the software support?

The ones your payers take. Brokers such as MTM Health and MediTrans take claims in their own portals, synced from a driver app or connected software or uploaded as a file. State Medicaid programs take electronic claims in the HIPAA standard 837 professional format, version 5010, and send payment details back as an 835 remittance. Arizona fee-for-service also requires its own Daily Trip Report with each claim, sent as a PDF or on paper. Ask the vendor to show each one.

## Official resources

- [HHS OCR: Sample business associate agreement provisions](https://www.hhs.gov/hipaa/for-professionals/covered-entities/sample-business-associate-agreement-provisions/index.html)
- [HHS OCR: Guidance on HIPAA and cloud computing](https://www.hhs.gov/hipaa/for-professionals/special-topics/health-information-technology/cloud-computing/index.html)
- [HHS OCR: HIPAA for professionals](https://www.hhs.gov/hipaa/for-professionals/index.html)
- [HHS and ASTP: Security Risk Assessment Tool for small providers](https://healthit.gov/privacy-security/security-risk-assessment-tool/)
- [eCFR: 45 CFR 164.312, Technical safeguards](https://www.ecfr.gov/current/title-45/section-164.312)
- [eCFR: 45 CFR 164.504(e), What a business associate agreement must say](https://www.ecfr.gov/current/title-45/section-164.504)