What Is a Geofence in NEMT? Automatic Arrivals, Trip Proof, and GPS Limits

A driver who taps “arrived” from the corner, or forgets to tap at all, leaves a trip record that does not match the drive. A geofence takes that tap off the driver’s hands. It is simple in idea and easy to get wrong in practice. In New York, the GPS data behind it decides whether a trip gets its prior authorization.

How a geofence works on a NEMT trip

A geofence is a boundary drawn around a point on a map, usually a circle around the pickup or drop-off address. The driver’s phone or the vehicle’s tracking unit reports its GPS position at regular intervals. When the position crosses the boundary, the app records an event with the time and the coordinates.

On one trip leg, that looks like this:

Trip event	Can a geofence mark it?	What else records it
En route to the pickup	No. The trip starts when the driver or dispatch starts it.	Driver tap or dispatch assignment
Arrived at pickup	Yes, when the van enters the pickup boundary	Manual tap as a backup
Rider on board	No. Leaving the boundary shows the van left, not who is inside.	Driver tap and the rider’s signature
Arrived at drop-off	Yes, when the van enters the drop-off boundary	Manual tap as a backup
Rider dropped off	Partly. The van is there, but the rider leaving is a separate event.	Driver tap, signature where required
Rider no-show	Partly. It shows the arrival time and how long the van stayed.	The driver’s note, calls to the rider, and dispatch contact

Between the events, the app keeps the GPS trail, the string of time-stamped points that shows the route and the miles. New York calls it breadcrumb data. For the wider picture of tracking rules, see NEMT GPS tracking.

What brokers and states ask for

Most of the rules below do not name geofences. They require the GPS data and trip events a geofence produces. As of September 2026:

Program	What it requires	Date
New York Medicaid	Every trip’s start point, end point, and all GPS coordinates along the way. Every event, from en route to trip complete, must be recorded in real time by manual entry or by technology such as geofencing. GPS that does not match the pickup, drop-off, and miles on the trip invoice stops the prior authorization. The Department of Health sets how close is a match.	Required since April 3, 2023. MAS notice February 3, 2023. Policy manual effective August 25, 2023.
MTM Health standard agreement	Working vehicle location tracking on an internet-connected device that sends, in real time, the vehicle’s location, trip events, and member signatures. MTM’s app meets it, or another routing system if MTM approves its data connection.	January 1, 2023 version Pennsylvania posts, section 4.B
MTM Health, Virginia	Tracking active for the full ride to capture arrivals, pickups, the ride, and drop-offs. Graded on more than 90.01 percent of trips tracked, plus a check comparing each trip’s recorded minutes with its miles.	Handbook approved August 10, 2026
Montana Medicaid	Under the new broker, Modivcare, transportation providers get a digital app for ride tracking and appointment confirmation through geofencing. Members claiming mileage can use a member app that captures geocoordinates, time, mileage, and provider signatures.	DPHHS overview, July 2026. Full go-live October 1, 2026.
Colorado Medicaid	The state must adopt rules requiring providers, the broker, or both to use a digital dispatch system that automatically records pickup and drop-off addresses, GPS coordinates, pickup and drop-off times, routes, miles, and the driver and vehicle. Fleets of more than five vehicles also need two-way dash cameras that capture pickups and drop-offs.	HB26-1328, effective July 1, 2026
Kentucky Medicaid	Regional brokers must make sure every NEMT vehicle has a GPS device showing its precise location whenever it is carrying out NEMT, at the broker’s cost. The rule does not cover NEMT run by the health plans.	HB 2, Acts chapter 179, enacted April 14, 2026

If your broker’s manual does not mention GPS or geofences, ask in writing what location data it wants and in what format. Colorado’s camera rule is covered in Colorado’s NEMT law on video cameras.

What geofence data proves, and what it does not

GPS data is strong evidence about the vehicle and weak evidence about the rider. Federal auditors have drawn the same line.

HHS OIG’s Massachusetts audit (A-01-19-00004, January 2021) found trip records missing details such as pickup and drop-off addresses, dates, and driver names, so auditors could not verify that the rides happened. It named GPS as a control that could confirm riders were taken to the right destination. As a separate control, it named proof that the rider was in the vehicle, such as signing a transportation log or a date-stamped photo of the rider’s ID. OIG’s New York City audit (A-02-21-01001, September 2022) asked the state to make sure providers do not bill for a ride on a date when the rider received no Medicaid-covered service. In its response, the state said GPS data would make trip start and end times and locations trackable.

Question in a review	Does geofence data answer it?	The record that closes it
Was the van at the pickup, and when?	Yes, within GPS accuracy	The arrival event and the trail
Did the driver wait the full no-show time?	Mostly: it shows how long the van stayed	The driver’s note and call log
How far did the van drive with the rider?	Yes, from the trail	Odometer readings where your state requires them
Was the rider in the van?	No	The rider’s signature or other proof your program accepts
Did the rider have a covered appointment?	No	The authorization, and the facility’s confirmation where required
Which driver and vehicle ran it?	Only if each device is tied to one driver and one van	The manifest and your driver and vehicle files

Keep all of it together. See NEMT trip documentation and NEMT broker audits.

Why geofence arrivals go wrong

GPS.gov says GPS-enabled smartphones are typically accurate to within 4.9 meters, or 16 feet, under open sky. Accuracy gets worse near buildings, bridges, and trees, and signals bounce off walls. GPS.gov adds that the hardware is often fine and the map is the problem: badly drawn maps, mislabeled businesses, and missing roads or buildings.

For a NEMT trip, that shows up in a few ways:

• Big campuses. A hospital’s address may map to one point while the rider waits at a different entrance. The geofence fires at the wrong door, or not at all.
• Tall buildings and garages. The signal weakens or bounces, so arrivals log late or early.
• Rural addresses. Some homes have no street address a map can find. CMS notes that drivers can use GPS coordinates to find a location and figure mileage where there is no street address (SMD 23-006).
• Dead zones and dead batteries. New York’s broker accepts GPS information during or after the trip when something outside your control blocked it, and expects that to be rare.
• Boundaries that are too big. An arrival that logs a block away makes the van look early and the wait look long.

Setting up geofences that hold up

1. Read your broker’s GPS rule first. Know what events it wants, in what format, and whether it wants its own app or accepts yours. See what a NEMT driver app should do.
2. Put the pin on the door. Save the entrance each rider actually uses, such as the dialysis unit door, not the campus address.
3. Test each regular stop. Drive in once and check that the arrival logs at the door, not down the street.
4. Keep a manual tap as the backup. Tell drivers to tap when the geofence misses, and to add a note saying why.
5. Tie each device to one driver and one van. Your trail is only useful if it shows who drove and in which vehicle.
6. Check mismatches before you bill. Look each day for trips with no arrival, times that do not fit the miles, or a trail that ends before the drop-off.
7. Protect the data. HIPAA’s de-identification rule counts street addresses and their equivalent geocodes as identifiers (45 CFR 164.514). Limit who can see trip trails. See HIPAA for NEMT providers.

Minnesota’s 2026 session law, chapter 121, article 10, adds nonemergency medical transportation to the services its electronic visit verification law covers. Starting January 1, 2027, or on federal approval if that comes later, enrolled NEMT providers must meet that law’s requirements. EVV records much the same who, where, and when. See EVV for NEMT. Driver notice and consent rules for tracking are covered in the GPS tracking guide.