Intake, scheduling, dispatch, driver app, compliance, rating and billing — everything a NEMT fleet needs. Plus the six things the incumbents leave you to work out in a spreadsheet.
Payer policy inheritance, driver skill vectors, crew-based dispatch, effective-dated rates and telemetry on every status change. Where this market has already worked something out, we kept it.
Unassigned queue on the left, a crew timeline on the right, live counters across the top. Drag a trip onto a crew and conflicts are checked before it lands.
Organisation default, payer override, trip override — with the UI always showing which level a value came from. Every contract quirk becomes configuration, not a code branch.
Timestamp, GPS, phone odometer and keyed odometer at every transition, written immutably, with derived per-segment miles and durations. Enough to survive a recoupment without arguing.
Revenue figures in this category are gross, so an owner cannot see cost per trip, margin per payer, or which contract is quietly losing money. Routely models driver pay, payroll burden, fuel and vehicle wear, a share of the day's fixed cost and overhead — and puts margin next to revenue on every trip, payer, driver and vehicle view.
Most NEMT systems cover intake, dispatch and invoicing. These are the places we went further, because each one is work an operator is otherwise doing by hand.
Driver pay and burden, fuel and vehicle wear, a share of the day’s fixed cost and overhead — modelled on every trip. Margin sits next to revenue on every trip, payer, driver, vehicle and invoice.
Every assignment shows what it cost, which constraint bound it, and what came second. Trips it could not place get a constraint report naming the reason. Pin, re-run, revert.
Unassigned inside cutoff. Driver not started. Stuck in status. GPS gone dark. A run projected to miss its appointment window. A trip priced below cost.
Ingest the broker’s payment file, match it line by line against the trip ledger, and work only the exceptions — underpaid, denied, unmatched — with the reason code attached.
Timestamp, GPS, phone odometer and keyed odometer at each status change, written immutably, with derived per-segment miles and durations.
A documented REST API and HMAC-signed webhooks, an exportable audit log, and time-boxed support access instead of standing vendor accounts in your tenant.
No tiers, no feature gates, no setup fee, no contract. Reconciliation, the API, payroll and multi-entity are not upsells — feature-gated pricing in this market reads as a trap to owner-operators, and it is.
The whole product from a single vehicle. Email support.
The same product at a lower rate once you run six or more vehicles.
For operators running twenty or more vehicles. Priority support and hands-on onboarding.
Bring one week of trips. We will show you cost per trip, margin per payer and the deadhead ratio you are carrying — before you commit to anything.