When should a NEMT company outsource? The 50-trips-a-day rule

Every growing NEMT company hits the same wall, and almost nobody sees it from the front. From the owner’s chair the business looks fine — vans are full, the broker keeps sending trips, revenue is up. Then the quarterly report shows on-time percentage drifting down, a facility that used to call weekly goes quiet, and the owner realizes they have answered the will-call line personally every afternoon for a month. The wall is not a revenue problem. It is a coordination problem, and it arrives on a schedule.

At TransportBPO we onboard NEMT providers at every size, and we see where the wall sits often enough to have turned it into an internal rule of thumb: around 50 trips a day, owner-run dispatch breaks. That is our number from our own accounts — not an industry statistic — and this piece explains the reasoning behind it, plus the earlier trigger signals that usually mean the wall is closer than the trip count suggests.

What is the 50-trips-a-day rule?

It is the heuristic we use internally when a NEMT provider asks whether they are ready to outsource: at roughly 50 trips a day, a fleet needs a dedicated, always-on dispatch function — and duct-taping it out of the owner’s phone and a part-timer stops working. Below that, a capable owner-dispatcher can usually hold the board. Above it, something structural has to change, whether that is hiring a dispatch team or outsourcing the desk.

The number is deliberately a rule of thumb, not a law. A fleet running 40 trips heavy on will-call returns and three broker portals hits the wall earlier; a fleet running 55 clean standing orders on one contract might coast a little past it. But when providers come to us describing missed returns and sliding on-time numbers, their trip count is nearly always in that neighborhood — which is why we ask about daily trips before anything else.

Why does dispatch break around 50 trips?

Because trips are not the unit of dispatch work — touches are. A single NEMT round trip generates an entry, a confirmation, a manifest slot, a possible schedule change, a will-call ready-call, an assignment, and a completion confirmation back through the portal. Call it five to eight touches per trip on an ordinary day. At 50 trips you are near 300 touches, arriving from before dawn to mid-evening, with the afternoon will-call block landing in unpredictable clusters.

One good dispatcher can hold a surprising amount of that — until the touches collide. Two ready-calls during a broker adjustment while a driver reports a wheelchair lift fault: each is routine alone, and together one of them slips. At 50 trips a day those collisions stop being occasional, and the failures land on the metrics brokers grade hardest — return-window compliance and no-shows. The owner absorbs it for a while by working the phone at night. That is not a system; it is a countdown.

What are the trigger signals before you hit 50?

The trip count is the lagging indicator. These are the leading ones we hear on first calls with NEMT owners, and any two of them together usually means the wall is already in view:

• Will-call returns are slipping — patients waiting long after calling ready, because afternoon reactivations pile onto a desk already dispatching live trips.
• Your on-time percentage is drifting down in the broker’s own report, quarter over quarter, without any single obvious failure to blame.
• The owner is the after-hours desk — dawn schedule changes and evening confirmations run through your personal phone, and a vacation would be an operational event.
• One dispatcher is a single point of failure — a sick day means the owner covers, and nobody else can confirm standing orders or work the portal.
• Broker offers are expiring unworked — evening and dawn batches close before anyone with board knowledge can accept, and volume quietly routes to competitors.
• Paperwork is backing up — eligibility checks skipped, completions unconfirmed in the portal, remittances unreconciled for weeks.

What should a NEMT company outsource first?

The hours, not the whole desk. Almost every provider’s failures cluster in the same places: the pre-dawn block that feeds dialysis mornings, the will-call afternoons, and evening and weekend coverage. Outsourcing those hours to a desk that works inside your software fixes the metrics that are actually bleeding while your day operation stays exactly as it is. It is also the cheapest way to test whether outsourcing suits you at all.

If dispatch is holding but your evenings are gone, start with the back office instead — trip entry, eligibility checks, portal confirmations and reconciliation support through a virtual assistant. And if the honest problem is that you are under 20 trips a day and cash is tight, the answer may be to not outsource yet: at that size an organized owner with good software usually is the most cost-effective dispatch desk available.

How do you make the switch without dropping trips?

Run it as an overlap, not a cutover. A competent provider trains its agents inside your dispatch software on your live account while your existing desk still runs the board, then takes over the target hours once the agents have shadowed real shifts — standing orders, will-call procedure, your broker’s portal rhythm. Your patients and facilities should notice nothing except that the phone gets answered faster.

The commercial terms should let you test cheaply. TransportBPO runs month-to-month with no setup fees and the first week free, which exists precisely so a skeptical owner can hand over the will-call afternoons for a week and judge the desk on the broker’s own numbers. Whoever you use, hold them to that standard: if the on-time and return-window metrics do not move, the outsourcing is not working — whatever the sales deck says.

Common questions