Managing Recurring Trips in NEMT: Standing Orders Done Right

How to build standing orders that run themselves, handle exceptions cleanly, and keep recurring trips aligned with broker authorizations.

Updated July 12, 2026 · Axen Editorial Team

Why recurring trips are the backbone of NEMT revenue

Dialysis riders travel three times a week, often for years. Therapy patients, adult day program participants, and behavioral health clients follow similarly predictable schedules. For many NEMT providers, these recurring riders account for the majority of trip volume and the most stable share of revenue.

Predictability is the operational advantage. A dialysis standing order that runs Monday, Wednesday, and Friday at the same clinic lets you plan vehicles, driver shifts, and multi-loads weeks in advance instead of reacting trip by trip. Providers that treat recurring trips as one-off bookings give up that advantage and re-do the same scheduling work every week.

Building a standing order correctly the first time

A standing order is a template that generates individual trips on a schedule. The template should capture everything a dispatcher would otherwise have to look up: pickup and drop-off addresses, appointment time, mobility type, escort or attendant needs, door-through-door instructions, and the funding source or broker authorization behind the trip.

Set an explicit end date tied to the authorization period rather than letting the series run indefinitely. Open-ended series are how providers end up dispatching trips that no payer will reimburse.

Handling exceptions: holidays, schedule changes, hospitalizations

Exceptions are where standing orders break down. Dialysis clinics shift schedules around holidays, riders change treatment days, and a hospitalization can suspend a series for weeks. Your process needs a way to skip, move, or pause individual occurrences without rebuilding the whole series.

The dangerous shortcut is deleting the series and recreating it, because history and authorization links get lost. Instead, edit at the right level: change one occurrence for a one-time move, and change the template for a permanent shift like a new clinic time. Keep a note on every exception so billing staff can explain gaps later.

Keeping series in sync with broker authorizations

Most recurring Medicaid trips run under an authorization with a defined trip count or date range, and brokers reauthorize on their own cycles. Requirements and formats vary by state and by broker, so confirm the rules for each contract you hold rather than assuming one process applies everywhere.

Build a review step ahead of every authorization expiration: is the reauthorization in hand, has the trip count changed, and does the broker trip file still match your series? When a broker sends updated standing-order files, reconcile them against your active series line by line instead of assuming nothing moved.

Avoiding phantom trips that cause billing errors

A phantom trip is an occurrence your system generated that never should have run or never actually ran: the rider was hospitalized, the clinic was closed, or the series should have ended with the authorization. If phantom trips reach billing, they become denials at best and payback demands or audit findings at worst.

The defense is closing the loop on every generated occurrence. Each trip should end the day with a definitive status — completed with timestamps, canceled with a reason, or rider no-show — and anything still open at end of day should be investigated before claims go out. Software that ties driver status updates to each occurrence, the way Axen links the driver app to scheduled trips, makes this reconciliation routine instead of detective work.

Managing the return leg and will-call riders

The return leg of a recurring trip is often less predictable than the outbound. Dialysis treatment can run long, and some programs release riders on a will-call basis. Decide per series whether the return is firmly scheduled or will-call, and staff your dispatch accordingly during peak return windows.

For will-call returns, track the request time and the pickup time separately. That record protects you when a rider or facility disputes a long wait, and it shows brokers your actual response performance.

A weekly hygiene routine for standing orders

Recurring trip data decays quietly: riders move, clinics change hours, authorizations renew with different terms. A short weekly review keeps the series inventory clean and prevents small errors from compounding across dozens of future occurrences.

Related resources

Frequently asked questions

What is a standing order in NEMT?

A standing order is a recurring trip arrangement — for example, dialysis transport every Monday, Wednesday, and Friday — set up once and generating individual trips on a schedule until it ends or the authorization expires.

How do brokers handle recurring trip authorizations?

It varies by state and broker. Some authorize a date range, some a trip count, and reauthorization cycles differ. Always confirm the process with each broker you contract with and track expiration dates in your scheduling system.

What causes phantom trips in NEMT billing?

Common causes are series that keep generating trips after a rider was hospitalized or an authorization ended, and occurrences that were never given a final status. Reconciling every generated trip daily before billing prevents most of them.

Should I delete a standing order when a rider is hospitalized?

Usually no. Pause or skip occurrences instead, so the series history, notes, and authorization links stay intact and you can resume cleanly when the rider returns to treatment.