The route builder started as a power tool. Select technicians, click auto-build, get routes. But it assumed you already knew the workflow. A wizard emerged from the question: what does a solo operator need versus a team manager?
A mode picker at the start: "Build a Route" for a single technician with a single dropdown, or "Build Daily Routes" for multiple techs with a MultiSelect. The picker shows the unrouted order count and team size — context before commitment. Back button returns to the mode picker. Simple navigation for a tool that handles complex decisions.
The auto-build algorithm gained a priority pass. Orders where the assigned assistant matches a technician get routed to that tech first. Remaining orders split geographically. In single-tech mode, pre-assigned orders sort to the top with a green left border — visual confirmation that the system respected what the operator already decided.
Unrouted markers on the map now show a green "Add to Route" popup button when routes have been built. One click adds the order to the first available planning route. Hovering over an unrouted order in the sidebar lights up its map marker — 1.5x scale, green fill, glowing ring shadow. The connection between list and map becomes physical.
Road-following polylines replaced straight lines between stops. A decoder utility handles Google's encoded polyline format. The renderer tries three tiers: full route polyline first, then per-leg polylines, then straight-line fallback. Routes on the map now follow actual roads — turns, curves, highways — instead of cutting through buildings and lakes in a straight line from A to B.