Every Rule in Your Dispatcher's Head — In the Plan Before the Afternoon Runs

Those rules are not details — they are the whole job. Nivio Dispatch is a Proprietary Algorithm built for bulk fleets. It holds every one of them, plans every load and every driver for the full shift, and returns a plan the dispatcher can act on in under 30 minutes. The solver itself runs in seconds. The dispatcher still decides what rolls. The arithmetic is already done.

Here is what that looks like in practice.

---

A driver's clock runs out at 4:15 p.m. — the plan already knows.

A driver does not run out of hours at a convenient time. At 4:15 p.m., one of yours hits his 14-hour duty limit. Another is three hours into an 11-hour drive window. A third needs his 30-minute break before he can touch the next load. A fourth is at hour 67 of his 70-hour cycle and needs to come home clean.

Most tools see a fleet. Nivio Dispatch sees each driver's clock individually — duty time remaining, drive time remaining, break status, cycle hours. Every assignment clears all four before it goes on the board. No driver gets a load they cannot legally finish.

---

One driver holds the tanker endorsement — the load finds him.

One driver in your fleet holds the tanker endorsement. One holds hazmat. Two are on a customer's approved-driver list. A food-grade load cannot go to a driver whose last haul was chemicals.

These are not exceptions your dispatcher remembers to check. They are constraints the plan solves around. Every assignment clears the endorsement requirement and the customer rule before it lands. The right driver for the load is matched first. Everything else builds from there.

---

The rack opens at 7 a.m. — one delayed gate does not move everything behind it.

The rack opens at 7 a.m. and closes at 3 p.m. A terminal has a 45-minute load time. A customer appointment has a 30-minute detention window before the charges start.

Nivio Dispatch chains loads so a driver drops near the next pickup, building buffer time into each leg. One delayed gate stays contained. The plan accounts for appointment windows, terminal hours, load and unload times, and detention exposure — so the schedule you send out at the end of the afternoon is still the schedule that runs the next day.

---

Aged loads surface. Recurring hauls schedule themselves. Promised loads stay locked.

Three types of loads live outside the normal priority queue.

Aged loads have been sitting. They move up the order before the customer calls to ask why. The plan surfaces them first, not after the phone rings.

Recurring hauls — the same lane, same customer, same day of the week — schedule themselves. Your dispatcher does not rebuild them from scratch every afternoon.

Locked loads are promises already made. A driver is committed to a haul. The plan locks that assignment and re-solves everything else around it. Nothing moves what was promised.

---

The dispatcher still owns the board

Nivio Dispatch works alongside the TMS and ELD your fleet already runs — McLeod, TMW, Samsara, Motive. Nothing gets replaced. When the plan comes back, the dispatcher reviews it, locks anything that needs to stay, moves what he wants to move, and re-runs. The solver returns a revised plan in seconds.

The full planning cycle drops from 2 to 3 hours a day to under 30 minutes. The time left over is not time saved on a spreadsheet. It is time spent making real decisions — the ones that actually require a dispatcher.

The founder of Nivio ran a 100-truck bulk fleet for ten years before writing a line of code. The rules Nivio Dispatch holds are the rules he held. Every one of them is in the plan because every one of them cost him something when they were not.

---

FAQ

Does Nivio Dispatch replace the dispatcher's judgment? No. The Proprietary Algorithm computes the assignments; the dispatcher reviews, adjusts, locks or re-runs before anything is sent to a driver. The dispatcher controls what rolls. Nivio handles the arithmetic so that control is spent on real decisions, not on checking hours-of-service math by hand.

How does Nivio Dispatch handle a driver who needs a 30-minute break mid-shift? Hours of service are read per driver, not per fleet. The constraint solver tracks duty time, drive time, break status, and cycle hours individually. If a 30-minute break is required before a driver can legally take the next load, the plan accounts for that gap rather than assigning the load as if it does not exist.

What happens if a customer only allows specific named drivers? Customer-approved driver lists are a constraint the plan respects. Every assignment clears the customer rule before it lands on the board. A load goes to an approved driver, or it does not go at all — the plan flags the constraint rather than silently assigning a driver the customer will reject.

Will Nivio Dispatch work with the TMS and ELD we already run? Yes. Nivio Dispatch runs alongside your existing tools — it does not replace them. It is additive from week one. Your dispatchers keep their current system; Nivio layers on top and feeds them a plan they can act on rather than a starting point they have to rebuild.

How does Nivio Dispatch handle a load that is already promised to a specific driver? That assignment is locked. The solver treats it as fixed and re-solves every other load around it. A promised haul stays with the driver it was promised to — nothing the algorithm computes can move it.