Audit Trail

Immutable GPS proof for every completed trip

With Audit Trail , The Fleet Owner can generate GPS-verified trip records so they can prove service was delivered — resulting in audits resolved in hours.

The Problem

The Core Problem
Operators who cannot provide GPS-verified trip proof face the same audit outcomes as fraudulent operators including denied claims and potential recoupment.
The Scenario
A state Medicaid auditor requests documentation for 200 trips performed over the past 18 months.
Why It's Urgent
The auditor wants GPS-verified proof that each trip happened including pickup coordinates, dropoff coordinates, and timestamps that match the billed events.
Without MediRoutes
The operator has paper signature sheets (some missing), no GPS records, and must reconstruct evidence from driver memory and printed schedules. The audit takes weeks and results in partial recoupment because documentation is incomplete.
With MediRoutes
The operator exports a ServiceProof GPS™ report for all 200 trips in 15 minutes. Each record includes GPS coordinates, breadcrumb trail, timestamps, and signatures. The audit closes in days.

Who This Helps

The Fleet Owner
knows their drivers are doing the right thing but has no way to prove it if an auditor or broker questions a trip. The burden of proof falls on the operator. Frustrated by the idea of being treated like a fraudulent provider simply because documentation is missing.
Frustrations
  • Cannot tell which runs are profitable until month-end
  • Losing money on certain broker contracts unknowingly
  • Audit exposure from incomplete documentation
Pain Points
  • Razor-thin margins with no per-trip visibility
  • Scaling requires proportionally more staff
Ideal Workflow
See real-time margin per trip, auto-enforce contract rules, pass audits with GPS-verified records
The Broker Compliance Officer
has to manually investigate disputed trips because providers cannot provide GPS verification. ServiceProof GPSu2122 resolves disputes in minutes instead of weeks.
Frustrations
  • Providers submit incomplete trip data
  • Missing GPS, signatures, and wrong timestamps
  • Manual review bottlenecks payment for everyone
Pain Points
  • Cannot verify service was actually delivered
  • Compliance review is entirely manual
Ideal Workflow
Receive clean claims with GPS proof, auto-validate before payment, resolve disputes in minutes

How It Works

Each step shows what happens when things go right — and what MediRoutes does when they don't.

Start / End
Process Step
Decision Point

Common Questions

Pickup GPS coordinates with timestamp, all breadcrumb trail points between pickup and dropoff, dropoff GPS coordinates with timestamp, patient signature image, driver signature image if required, and calculated actual distance vs. billed distance.
GPS coordinates are captured by the device at the moment of the event and transmitted directly to MediRoutes servers. They cannot be manually edited after the fact. Any attempt to create a record without actual GPS data generates a flag.
Operational trip data is retained for 3 years by default. Billing records are retained for 7 years. Retention periods are configurable to match state Medicaid audit windows, some of which extend to 10 years.
In NEMT Command Central, GPS data is proxied from the TNC provider's API and stored in the same format. The source is noted as TNC-provided rather than Driver App.
The billing module supports bulk export filtered by date range, funding source, driver, or vehicle in PDF or CSV format.
The driver marks the actual dropoff location in the app. If the billed dropoff address differs from the GPS dropoff coordinate, ClaimLocku2122 flags it before billing so it can be documented.