Nivio Dispatch plans and optimizes an entire bulk fleet shift — every load, every driver — in under 30 minutes, on top of the TMS a fleet already runs. Every empty mile it removes is diesel and parts never paid for. What follows is what sits behind that.
What a bulk shift plan actually has to satisfy
A bulk shift plan is not a list of assignments. It is a set of constraints that all have to hold at once before a single driver rolls.
- Hours of service. A driver with four hours left cannot take a nine-hour run. Federal, not optional.
- Weight grades and bridge limits. Not every driver is certified for every commodity, and not every lane clears at full gross.
- Permit corridors. Requirements attach to specific routes, not to the load in general.
- Tanker equipment type. A driver cleared for pneumatic does not automatically move to a liquid tanker.
- Time windows. Origin and destination both have to fit inside the driver's available clock.
- Customer rules. Dedicated lanes, preferred drivers and site-access restrictions sit on top of all of it.
Generic scheduling software handles one or two of those adequately. Bulk operations carry all of them, simultaneously, across every load and every driver on the board. That is the point where generic tools stop being useful.
How the plan gets built
Loads come in. Drivers' hours are known. The board has to be filled before the morning run.
Nivio Dispatch takes that board and runs it through a Proprietary Algorithm weighing over 50 rules — hours of service, commodity type, weight grades, bridge laws, permit corridors, tanker equipment restrictions, time windows, customer preferences. The solver returns a complete plan in under 30 minutes: which driver takes which load, sequenced across the board, every constraint already satisfied. Not one route at a time. The whole shift, at once.
The algorithm handles the arithmetic. The dispatcher keeps the judgement.
The dispatcher reviews every assignment and approves what rolls. That distinction matters: a plan that arrives without dispatcher review is a plan that creates problems at 5 a.m. Nivio is built so the dispatcher stays in control of the board.
Where it sits relative to the TMS
Nivio Dispatch does not replace McLeod, TMW, Samsara or Motive. It runs beside them.
Loads and drivers come in by spreadsheet or by hand. Integration with an existing TMS comes later, at the fleet's pace, and is never a condition of getting started. Nothing in the current stack gets removed — no data migration, no retraining on a new system of record.
| Layer | What it owns |
|---|---|
| TMS (McLeod, TMW, Samsara, Motive) | Load lifecycle — booking, billing, compliance |
| Nivio Dispatch | The planning problem — which driver, which load, whole shift |
What the removed empty miles are worth
Bulk fleets not running Nivio sit at about 38% loaded. Fleets running Nivio sit at about 47%. That nine-point gap is mostly empty miles — diesel burned driving to a load rather than with one.
$4,720 per truck, per year. Modelled at a conservative 6% mileage reduction, counting fuel and maintenance only — no revenue uplift, no incremental load count. Those are the shipped defaults on our own calculator — 60,000 miles per truck a year, 4.5 mpg, $5.00 diesel, $0.20 a mile in maintenance — so the number is reproducible in one click.
Nivio is priced at $2.00 to $3.00 per driver per day, by fleet size and term, with no overages. At the 51–200-driver month-to-month rate of $2.75, that is about $1,000 per driver a year — against about $4,720 per truck a year in modelled fuel and maintenance savings. The 6% mileage reduction sits deliberately below the floor of what fleets running Nivio have measured, not at the ceiling.
Running it against a real day
Send one day of actual dispatch — the loads and the drivers, on a template Nivio provides. That day gets run through Nivio Dispatch and returned as a head-to-head comparison within 24 hours, at no cost. That is a fleet's own number, on its own data, before committing to anything.
Questions fleets ask
Does Nivio Dispatch replace our TMS?
No. It runs beside McLeod, TMW, Samsara, Motive and other TMS platforms. The TMS manages the load lifecycle. Nivio solves the planning problem the TMS was never built for: which driver takes which load, across every constraint, for the whole shift.
How does the plan get into Nivio if we are not integrated yet?
Loads and drivers come in by spreadsheet or by hand entry on a template Nivio provides. Integration comes later, at the fleet's pace, and is never a condition of starting.
What rules does the algorithm actually weigh?
Over 50, covering hours of service, commodity type, weight grades, bridge laws, permit corridors, tanker equipment restrictions, time windows and customer-specific rules. The plan returned is one a dispatcher can run, not a theoretical optimum that ignores operating reality.
How long does the solver take?
The solver returns a complete shift plan in under 30 minutes. The dispatcher then reviews and approves every assignment before anything rolls.
Is the $4,720 per truck figure guaranteed?
No. It is modelled at a conservative 6% mileage cut, fuel and maintenance only, on the same defaults our home-page calculator ships with — 60,000 miles per truck a year, 4.5 mpg, $5.00 diesel, $0.20 a mile in maintenance. Run those numbers yourself and you land on the same figure. It is a reproducible estimate, not a guarantee. A fleet's number varies with its miles, its fuel cost and its current loaded percentage, which is exactly why the head-to-head comparison comes before any commitment.
Run one day of your board through it
Send a single day of loads and drivers. Get back a head-to-head against what your dispatcher built, on your own data, within 24 hours.
Get the comparison →