top of page

The Dispatcher Approved the Plan. Then the Order Changed

Writer: Charles Weber
Charles Weber
13 hours ago
2 min read

A dispatcher reviews tomorrow’s loads in the afternoon. An hour later, a customer moves a delivery and the plant needs the first truck for another job. The recommendation that looked sensible at three can send the crew in the wrong direction at four. When the manager looks back the next morning, a username in the log will tell them who approved the change. They still need to know which version of the order the dispatcher saw.


Adam Gardner of Command Alkon against a softly blurred concrete dispatch office
Adam Gardner, vice president and global product manager at Command Alkon. “It won’t ‘keep its eye on’ anything it’s ever been asked about.”

A Fresh Answer Takes a Fresh Question


In written comments to The Supply Chainer, Adam Gardner, vice president and global product manager at Command Alkon, described what happens when someone asks Command Intelligence about a dispatch plan. “It won’t ‘keep its eye on’ anything it’s ever been asked about,” he said. If the dispatcher asks again after a change, Gardner said, the system answers against the new data. His description leaves a practical question for the shift: what prompts the dispatcher to ask again?


Gardner said a person still approves a change and that the system records who made it. An AI-assisted change and a manual change can both end up under the dispatcher’s username. That answers the question of who signed off. Gardner’s response did not establish whether the log also retains the earlier recommendation or the order details it used. A manager investigating a missed delivery would have a reason to ask for both.


The Approval Is Only Half the Record


“Human oversight requires more than an approval button,” Prof. Shlomit Yanisky-Ravid wrote in a previous Supply Chainer opinion column on AI compliance. A dispatch screen makes that point tangible. If a delivery window moved after a recommendation was generated, the person approving it needs to see the change and have time to reconsider. An approval tied to a username cannot show whether that happened.


A revised plan can be correct on the dispatcher’s screen and still reach the loading crew too late. Suppose a concrete delivery moves after the plant has started batching the original load. The dispatcher now needs to confirm what the plant has already done before assigning that truck elsewhere. Put a step in the workflow that shows whether batching has started and asks the plant to acknowledge the change. The revised schedule is ready to use once the people who have to act on it know which load goes next.


The gap shows up when the dispatcher hands over to the next shift. If the successor can see the revised order but cannot see why the first truck was reassigned, they may spend the morning reconstructing yesterday’s decision. The person who approved it may already be off shift. An approval log earns its keep when the second dispatcher can answer the customer without calling the first one at home.

Join Our Newsletter

And get the latest news from The Supply Chainer directly to your email

Thanks for submitting!

The Supply Chainer's editorial team of experienced writers, editors and industry experts collaborates to produce high-quality content that tackles the dynamic challenges of the global supply chain landscape. We are dedicated to building a vibrant community of supply chain professionals while promoting knowledge sharing and industry innovation. ​ We don’t maintain social media accounts as a matter of principle. To find our editorials on social search: "The Supply Chainer"

Dark futuristic robot banner with CaPow logo.png

​

​​

The Supply Chainer© 2016 Watermark Publishers Group, Inc.  All Rights Reserved. 1209 Orange St. Wilmington, DE 19801, USA

​

bottom of page