NEMT EVV Compliance: What Every Provider Needs to Know in 2026

NEMT EVV compliance means capturing six specific data points electronically on every completed trip — service type, patient identity, date, location, caregiver identity, and exact start/end times — as required by the 21st Century Cures Act and, in most states, extended to non-emergency medical transportation by Medicaid managed care programs. Miss any of those six, and the trip can't be billed. This guide walks through what EVV actually requires, whether it applies to your state, and how to build it into your daily operations without adding another manual task to your dispatcher's plate.

What Is EVV in NEMT?

Electronic Visit Verification, or EVV, is a digital system that records proof a Medicaid-funded trip actually happened — who was transported, where, when, and by whom — instead of relying on paper trip logs that can be filled out days later, or not at all. EVV was created under Section 12006(a) of the 21st Century Cures Act, originally aimed at personal care and home health visits, but most state Medicaid programs have since extended the same verification standard to non-emergency medical transportation trips, because the underlying fraud and documentation risks are identical. For NEMT operators specifically, this means the trip record itself becomes the proof of service. If that record is incomplete, generic, or reconstructed from memory at the end of a shift, it doesn't count — no matter how good your service actually was.

Why EVV Compliance Matters for NEMT Providers

EVV isn't a nice-to-have documentation habit — it's tied directly to whether Medicaid pays you at all. States that require EVV treat it as a condition of clean claim submission: a trip without a compliant EVV record is treated the same as a trip that never happened, which means the claim is denied, not delayed. Beyond the individual claim, EVV data discrepancies are one of the audit triggers state Medicaid programs and brokers actively screen for. A pattern of missing or inconsistent EVV records doesn't just cost you that trip's reimbursement — it puts your broader broker contract and Medicaid enrollment status under review, the same credentialing standing covered in our guide on how to get more NEMT trips from brokers.

The 6 Data Points Every EVV Record Must Capture

A compliant electronic visit verification NEMT record needs to document all six of the following, captured at the time of service rather than reconstructed afterward:

• Type of service performed (trip/transport type)
• Individual receiving the service (patient identity)
• Date of the service
• Location where the service was delivered (pickup and drop-off)
• Identity of the driver/caregiver providing the service
• Exact start time and end time of the visit

Some states and brokers layer on additional requirements beyond these six — vehicle ID, odometer readings, or full GPS route data rather than just start/end points. The federal floor is six data points; your state or broker contract may ask for more, so it's worth confirming the specific fields required through your state Medicaid portal.

NEMT EVV Requirements by State: How Vendor Models Work

Because EVV rollout was left to individual states, there's no single national EVV system — instead, most states fall into one of three vendor models:

• State-mandated model: The state selects one EVV vendor, and every provider must use it. No alternative systems are permitted.
• Open vendor model: The state provides a free vendor option, but providers can use a different EVV system at their own expense, as long as it integrates with the state's data aggregator.
• Provider choice model: Providers select their own EVV solution, which must be verified to submit data correctly to the state's designated aggregator.

For example, Arizona and Indiana both use Sandata as their state-designated data aggregator under an open vendor model, meaning providers can use third-party software as long as it feeds data into Sandata correctly. Requirements — and enforcement intensity — vary meaningfully by state and continue to change, so the most reliable step is confirming your specific state's current model directly through your state Medicaid agency or your broker before assuming your software is compliant.

What Happens When EVV Data Is Missing or Incomplete?

The immediate consequence of an EVV gap is a denied claim — most states treat non-compliant EVV data as an automatic rejection, not a request for follow-up documentation. But the real cost compounds from there. Denied claims slow cash flow, incomplete EVV records are a specific audit trigger state Medicaid programs and brokers screen for, and a pattern of EVV discrepancies can jeopardize your broker credentialing and Medicaid enrollment status entirely. This is the core reason EVV claim denials in NEMT operations tend to be a symptom of a bigger operational gap — usually a driver logging trip details after the fact from memory, rather than the system capturing them automatically in real time.

NEMT EVV Compliance Checklist

Use this as a working checklist to evaluate whether your current process is actually audit-ready, not just "mostly fine":

• Every completed trip captures all 6 required EVV data points automatically, not manually
• Location data is GPS-verified at pickup and drop-off, not self-reported
• Driver identity is tied to each trip electronically (not a shared login or paper sign-in)
• Start/end times are timestamped at the moment of service, not entered later
• EVV records are retained for the length your state requires (commonly several years)
• You've confirmed your specific state's EVV vendor model and data aggregator
• Your dispatch software's EVV output has been checked against your state's exact required fields, not just the federal minimum six

Manual EVV Tracking vs. Software-Captured EVV

Providers still relying on paper manifests or a driver texting in trip details are effectively trying to reconstruct EVV data after the fact — which is exactly the pattern state auditors flag. Manual entry introduces timing gaps, inconsistent signatures, and mileage figures that don't match GPS reality, all of which read as red flags rather than routine paperwork. Software-captured EVV closes that gap by recording each of the six required fields the moment a driver's status changes — arriving, transporting, completed — rather than depending on someone remembering to fill in a form later that day.

How ZeitRide Handles NEMT EVV Software Requirements

The ZeitRide Driver app captures GPS location, timestamps, and digital signatures automatically as part of the normal dispatch workflow — so EVV compliance isn't a separate task your drivers have to remember, it's a byproduct of doing the trip the way the app is already built to run. That data flows straight into dispatch and billing, which means the documentation an auditor or broker asks for is already sitting there, timestamped, instead of something your team has to reconstruct after the fact. If you're currently piecing together EVV compliance from paper logs, spreadsheets, or a mix of tools, it's worth seeing how that looks running on your own trips rather than a generic demo — book a 15-minute demo and bring a real route.

Frequently Asked Questions

If EVV compliance currently depends on a driver remembering to fill something in, that's the gap worth closing before it costs you a claim. See how ZeitRide captures EVV data automatically on every trip — bring one of your own routes to the demo and we'll show you the exact workflow. If you're also weighing this against overall software cost, our NEMT Software Pricing Complete Guide breaks down what's typically included versus billed as an add-on.