Every service stop routed by rule, one loop a week

The problem

A case came in, someone looked at a map, guessed a day, and called a driver. Drivers made solo runs across the same area on different days. Straight-line distance stood in for drive time, so a day that looked fine on the screen fell apart on the road.

What we built

Each service area gets one set day a week. When a case becomes a job, the engine checks the address is in range, offers the zone day or an expedite date, assigns a driver already nearby or the day's primary driver, and checks capacity warehouse to stops to warehouse. Over cap, the job overflows to a teammate. If every driver is full, it goes to a manual-review queue that keeps posting until a dispatcher clears it.

Customers can pick their own day from a private link; the self-scheduling portal is its own use case.

Nightly, Sunday through Thursday, the optimizer re-sequences the next day's stops on real drive times, rebalances between drivers, and posts each route to the team chat in driven order. Dispatchers can move a date and watch the job re-route itself, override an out-of-range address with the true drive time shown, or change a zone's coverage in configuration without a release.