Handling Medicaid broker trip offers: acceptance, assignment and reconciliation

The trip offer for tomorrow’s 7:15 a.m. dialysis pickup lands in the broker portal at 9:40 the night before, sitting next to four other offers that arrived in the same batch. The decline window closes in twenty minutes. Accept it and you have committed a vehicle and driver to a fixed pickup window tomorrow morning, on a route you have not built yet. Ignore it and the offer expires, goes back into the pool, and a competing provider three counties over probably picks it up instead. Whoever is running your board at 9:40 that night decides tomorrow’s on-time percentage before a single van has moved.

That moment — offer in, decision made, clock already running — repeats dozens of times a day for a working NEMT fleet, and it is the least talked-about part of running a Medicaid broker contract. Everyone plans for the pickup and the paperwork. Fewer providers plan for the mechanics in between: how offers actually reach you, what happens the instant you accept one, how a same-day change gets folded into a board that is already built, and how you find out at the end of the day whether the broker actually paid you what the offer said it would.

How the trip offer actually shows up

Every broker runs trip distribution through a portal or an API feed into your scheduling software, and the shape of that feed matters more than most providers realize. Some brokers push a batch the night before — the next day’s standing orders and newly booked trips arriving together around a set time. Others trickle offers through the day as members book, cancel, or reschedule with the call center. A provider running contracts with more than one broker is watching two different rhythms at once, one predictable and one not.

Each offer carries the same core data regardless of which broker sent it: pickup address, appointment time, requested pickup window, level of service — ambulatory, wheelchair, stretcher — and the mileage-based or flat rate the broker is offering for the leg. That last field is the one providers skim past and later regret not checking, because the rate on the offer is the rate you are agreeing to when you accept, not a number you get to renegotiate after the trip runs.

The accept-or-decline window is where the day gets decided

Decline windows are short by design, sometimes closing in minutes, more often within an hour or two, and brokers do not extend them for a busy Tuesday. An offer left sitting until the window closes does not stay open. It expires, drops back into the broker’s assignment pool, and gets pushed to another contracted provider in your service area. Let that happen often enough on a given lane and the broker’s system quietly starts routing that lane’s trips past you first.

The harder discipline is accepting only what you can actually staff. Grabbing every offer that lands looks good on a weekly trip count and terrible on the no-show line, because an accepted trip your board cannot cover by pickup time becomes a provider no-show — the metric that actually damages your standing with the broker. The desk working the offer queue needs a live read on tomorrow’s open driver hours and vehicle slots before it clicks accept, not just an eye on the countdown clock.

• Accepting a trip when no vehicle of the right class is actually free at that hour
• Declining a trip reflexively because the pickup window looks tight, when it was workable
• Sitting on an offer while a decision gets debated, until the window closes on its own

Turning an accepted offer into a driver assignment

Accepting the offer is the easy click. Turning it into an assignment that actually runs is the dispatch work the broker’s software does not do for you. The trip has to be matched to a driver with the right vehicle class free at that hour, slotted into a route that does not deadhead the vehicle across town between pickups, and, where the geography allows, clustered with other confirmed trips heading the same direction so one van is not running near-empty.

Standing orders make this easier because the pattern repeats — the same dialysis run, the same three mornings, the same driver if you can hold continuity, which patients and facilities both notice and appreciate. New same-day offers are harder, because they land on a board that is already built and have to be threaded into open slots without bumping a trip you already promised. A desk that treats assignment as an afterthought once the offer is accepted ends up with a trip count on paper that does not match a workable route sheet.

Same-day changes and will-call do not wait for a quiet moment

Accepting the offer is not the end of that trip’s story. Appointments run long or get moved up, members cancel from the clinic parking lot, facilities add urgent same-day trips, and a return leg booked as will-call reactivates the moment a patient is discharged and calls ready. Every one of those events has to reach whoever owns the board, get checked against the vehicle actually assigned, and, if the change breaks the existing assignment, get reassigned before the new window closes.

This is where an accepted offer can quietly turn into a no-show that was entirely avoidable. A pickup time that moved up thirty minutes and never made it from the phone call to the route sheet is a driver arriving to an empty room. The gap there is not the broker’s system and it is not the driver. It is whoever is supposed to be watching the board between the moment the offer was accepted and the moment the vehicle actually rolls.

End-of-day reconciliation: matching the trip log to the remittance

Somewhere after the last van clocks off, the day’s real accounting starts, and it looks nothing like the offer queue. The job is to line up three things: the trips the broker offered, the trips you actually completed and logged, and the rate the broker eventually pays for each one. When all three agree, reconciliation is a formality. When they do not, the gap is where revenue quietly disappears.

Mismatches are routine, not exceptional, and they cluster into a few familiar shapes:

• A trip paid at a lower mileage tier than the offer specified, because the logged mileage did not match what the broker’s system calculated for the run
• A completed trip that never shows up on the remittance at all, dropped somewhere between your log and the broker’s payment batch
• An accepted trip marked as a no-show in the broker’s system despite being completed, because the completion was never confirmed back through the portal
• A same-day change that was actually run correctly but billed against the original, pre-change trip details

Building a desk that can run the whole cycle

None of these mismatches get caught by accident. They get caught by someone comparing the day’s trip log against the remittance line by line, on a set schedule, rather than assuming the broker’s payment automatically matches what was offered. A provider that skips this step is trusting the broker’s accounting to correct itself, which it generally does not do without a dispute filed on your side.

Offer acceptance, driver assignment, same-day changes, and reconciliation are one continuous job, not four separate ones, and treating them as separate is where providers lose money and standing at the same time. The dispatcher deciding whether to accept an offer needs to know what the board can staff. The person assigning drivers needs the accepted offer’s real details, not a summary. The desk fielding a 2 p.m. schedule change needs to update the same board the morning assignments live on. And reconciliation only works if the trip log it is checked against was kept accurately all day.

Most providers build for the acceptance-to-assignment half of this cycle and never staff the reconciliation half, which is why aging discrepancies pile up quietly instead of getting caught the week they happen. Pull last month’s remittance against your own trip log for a single broker and see how many lines fail to match. That gap — not the trips you turned down, not the ones you missed — is usually the larger and more fixable number.

Common questions