The morning starts from a proposed plan
A manufacturing and logistics operation. Name withheld.
Dispatch was a blank sheet every morning. Routes and assignments were built by hand, shift by shift. The plan lived in a spreadsheet and in one person’s head. A late order rewrote the board. The next shift started over.
What was deployed
Mapped the dispatch workflow: orders, constraints, who is allowed to override, and what “on time” means on their floor and on their lanes.
Deployed an ops agent that proposes assignments and routes from the live book.
Dispatchers approve the plan and handle the exceptions. The agent does not send a truck or move a work order on its own.
What changed
proposed each morning; people approve the exceptions
The morning starts from a proposed plan. People spend the shift on exceptions, not on rebuilding the board from zero. We do not publish miles saved, a percent on time, or a dollar figure. Those are measured on the client’s baseline, and they are not on this page.
No. The agent proposes the plan. Dispatchers approve it and handle the exceptions.
A miles or overtime figure that we did not measure with the client would be fiction. This page stops at the process return: a proposed plan, and people on the exceptions.
Start with the workflow.
Week 1 is a mapping of one workflow. If you already know the system and want a read on the shape, ask for an architecture review.