Every afternoon, from 3 to 7, your dispatcher hand-builds tomorrow's plan — matching every available driver to every load, around hours of service, time windows, and customer rules. Nivio Dispatch does it in under 30 minutes. Same drivers, same loads, a better plan. The first optimization algorithm built for bulk trucking dispatch.
Simulated solve. Drivers, loads and lanes are representative bulk operations; the figures are modelled from the algorithm against real fleet data, not customer results.
Keep your TMS and ELD. Nivio works with both.
Nivio builds the optimized dispatch plan for your fleet.
Connects to your stack
Your dispatcher knows the drivers and lanes better than any software will. What nobody can do in an afternoon is check every constraint, requirement and mileage pairing for 200 loads against 70 clocks — which is why fleets planning by hand lose 60 to 70% of their miles to deadhead.
Here is one afternoon shrunk to five drivers and fifteen loads — — ways to run it — so build the board yourself, then hand the same fifteen to Nivio. Give each driver three loads, and keep every one of them inside their clock.
Run the same 5 drivers and 15 loads
261 weekdays and 104 weekend days, with half the desk covering Saturdays and Sundays — 313 planning days a year each. A full-time year is 2,080 hours.
The afternoon plan isn't one decision — it's hundreds of rules held in one person's head. Here's what the Proprietary Algorithm weighs on every load, so the plan that comes back is one you can actually run.
Nivio Dispatch is a cloud application your dispatcher signs into — a board they build the shift on, not a black box that mails them a file. Loads and drivers come in, the optimized plan comes back on a map, and every load on it can still be locked, moved or run a second way before a single driver is dispatched.
The algorithm does the arithmetic nobody can do by hand. The dispatcher keeps the judgement no algorithm has.
Illustrative — the planning screen, simplified.
Every one of these is a decision your dispatcher makes and the software respects. Nivio never sends a load anywhere your dispatcher didn’t approve.
Loads and drivers import from the Excel file you already keep, or come straight out of your TMS over the API. When the plan is set it leaves the same way — an export, or assignments pushed back to the TMS, so drivers are dispatched from the system they were always dispatched from.
Plan by operating area, by commodity, by day crew and night crew — however the business is actually split. You set the shape of the shift; the algorithm optimizes inside your structure rather than around it.
Every driver’s day drawn end to end. A dispatcher reads a shift the way they read a road, so a pairing that looks wrong can be checked on the screen instead of taken on faith.
Lock a load to the driver it has to go to. Swap another between drivers because you know something the data doesn’t — a customer, a truck, a driver who needs to be home tonight. Nivio re-solves around every call you make.
Solve for the fewest empty miles, then again for the most loads per driver, and set the two boards side by side. You are not guessing which objective was the right one — you are reading the difference.
Loaded-mile percentage, deadhead, utilization and revenue per truck — for the shift you just built and every shift behind it. What used to be an argument at month end is a number on the screen.
You already pay for deadhead. It never shows up as its own line — it is spread across the fuel bill and the maintenance schedule, so it gets paid every month without anyone deciding to.
Nivio takes the empty miles out of the plan and the cost leaves with them — diesel that isn’t burned, tread and brakes that aren’t replaced.
Set your own fleet below. Every dollar here is cost you stop paying, not revenue we’re promising you’ll win.
The default sits at 6% on purpose — low enough that your own deadhead audit should beat it. Move it to whatever your numbers support.
What this deliberately leaves out: revenue from freed capacity, driver-hours recovered, reduced overtime, and anything to do with EBITDA. Those are real and they are usually larger than the number above — but they depend on whether you can sell the freed capacity, and that isn’t ours to promise. Everything here is cost you stop paying.
Nivio’s algorithm is available as a direct API call. Optimized boards are requested and returned inside the TMS your dispatchers already work in.
// a load, as the API actually takes it { "id": 151355, "commodity": "CHEMICALS", "revenue": 412.00, "revenueType": "FIXED", "urgencyLevel": "HIGH", // HIGH | MEDIUM | LOW "autoHaul": true, // → marked high-urgency "daysSinceCalledIn": 3, // older ⇒ earlier in the shift "pickup": { "name": "Northern Refinery", "availableFrom": "06:00", "availableTo": "18:00", "onSiteTime": "PT45M", "driverSkills": ["H2S"], "truckRequirements": ["VACUUM"], "dryHaul": true }, "stops": [{ "name": "WASH RACK", "onSiteTime": "PT30M" }] } // GET /solver/{jobId}/explain { "hardConstraints": [], "mediumConstraints": [{ "constraintName": "Minimize Unassigned Loads", "constraintWeight": -1, "violations": [{ "description": "Total of 2 Loads left unassigned.", "scoreImpact": -2 }] }], "softConstraints": [{ "constraintName": "Driver Shift Duration Balance", "constraintWeight": -1000 }] }
Send us one day of your actual dispatch — the loads and the drivers, on a template we give you. We solve the same day and hand back the comparison: total miles, deadhead, loaded percentage, and what the gap is worth over a year.
No integration to see it. Loads and drivers come in by spreadsheet or by hand. Connecting your TMS and ELD is there when you want it, never a condition of getting the numbers. Priced per driver, per day — $2.00 to $3.00 by fleet size and term, no overages — and you only pay for drivers Nivio actually plans.
Your first 14 days are free. Tell us what you want to see and we set the account up on your own loads and drivers. Nothing to cancel — billing starts only when you say so.