The Afternoon Board: How a Dispatcher Runs Three Controls and the Final Plan Is His

Nivio Dispatch computes that plan for him. The Proprietary Algorithm weighs every load and every driver against over 50 rules — hours left, endorsements, commodity restrictions, delivery windows — and returns a plan in under 5 minutes.

What happens next is the point of this post.

---

The plan comes back. Now the dispatcher looks at it.

It is 3:07 p.m. The plan is on the screen.

He sees Marcus flagged for the 340-mile haul. Marcus has been on long runs three days straight. Nothing in the hard rules prevents it — his hours are fine. But the dispatcher knows things the algorithm does not: Marcus mentioned his knee, the long cab time is wearing on him, and if he burns out before Friday the weekend plan falls apart.

That is not a spreadsheet problem. That is judgment. And Nivio Dispatch keeps it squarely with the dispatcher.

He moves Marcus off the long haul and puts him on a shorter regional pull. One drag. The board updates. No phone calls, no rebuilding from scratch.

---

Three controls. Everything before a driver is dispatched.

The dispatcher has three actions available at any point before a load rolls.

Lock. He already promised a specific driver to a customer — a relationship call, not a routing decision. He locks that assignment. Locked loads and drivers stay exactly where he put them. The algorithm does not touch them.

Move. He reassigns any load to any qualified driver. The board shows him what fits — hours remaining, endorsements, location — so the move is informed, not guesswork.

Re-run. He hits re-run. The Proprietary Algorithm re-solves everything that is not locked, in under 5 minutes, around the calls he already made.

The result is not a machine-generated plan with a few manual patches. It is his plan, built on the algorithm's arithmetic.

---

What "re-solve around his calls" actually means

When a dispatcher locks a load or moves a driver and hits re-run, Nivio Dispatch does not start over. It holds every decision he made and re-optimises the remaining open assignments — still weighing all 50-plus rules, still minimising deadhead, still respecting every window and endorsement.

This matters because the alternative is one of two bad outcomes: either the dispatcher accepts a plan he does not trust, or he rebuilds the whole board by hand after every adjustment. Both waste time. Both produce worse plans.

With lock, move, and re-run, he makes a call and the arithmetic catches up to him. The total planning cycle drops from 2 to 3 hours to under 30 minutes. The solver itself accounts for under 5 minutes of that. The rest is exactly what a dispatcher should be doing — reading the board, applying judgment, deciding what rolls.

---

Driver reality is already in the plan

When the plan comes back the first time, it already knows who has hours left, who is due home, and who has been running hard. That context is not a note he added. It is in the plan.

Which means the Marcus situation above is visible before he has to find it. The dispatcher is not auditing the plan for things the algorithm missed. He is applying the knowledge nobody writes down — the customer who needs a particular driver on their site, the driver who cannot run the bridge route on that truck — on top of a plan that already handled the rules.

That is a different afternoon. Not firefighting. Planning.

---

One more thing: it runs beside what you already use

Nivio Dispatch works alongside the TMS and ELD you already run. Nothing gets replaced. The plan it builds feeds into the tools your drivers and customers already see. The dispatcher's board is additive, not a migration.

---

Nivio Dispatch builds the plan. Your dispatcher decides what rolls. See your fleet's plan

---

FAQ

How long does it take Nivio Dispatch to return a plan? The Proprietary Algorithm returns a complete plan — every load, every driver, over 50 rules weighed — in under 5 minutes. The dispatcher then uses the remaining time to apply judgment: locking assignments, moving drivers, and re-running before anything rolls.

What happens to locked assignments when the dispatcher hits re-run? Locked loads and locked drivers stay exactly where the dispatcher placed them. The algorithm re-solves every open assignment around those anchors. Nothing he committed to is moved without his action.

Does Nivio Dispatch replace my dispatcher or reduce headcount? No. The Proprietary Algorithm handles the arithmetic — hours, endorsements, windows, deadhead. The dispatcher keeps every judgment call: which customer gets which driver, who needs a lighter day, what rolls first. The plan is his. Nivio builds it; he decides it.

Will this work with the TMS and ELD we already run? Yes. Nivio Dispatch is additive. It runs alongside your existing TMS and ELD in week one. Nothing gets replaced, and your dispatcher does not have to learn a new system of record.

How much time does the dispatcher actually save? By hand, building tomorrow's plan takes 2 to 3 hours every afternoon. With Nivio Dispatch, the full cycle — including the dispatcher's own adjustments — runs under 30 minutes. The solver itself is under 5. That is roughly 90 to 150 minutes returned to the dispatcher every day.