A route planner can propose a shorter journey without knowing every operational constraint. A vehicle may have a delivery sequence, an unavailable loading bay or a customer commitment that changes the decision. Route-change software should therefore separate the proposed plan, the approved plan and the route the driver has acknowledged.
The workflow matters most when a change occurs after dispatch. At that point, a mathematically attractive alternative can disrupt work already under way. Make the remaining stops, current vehicle state and reason for the proposed change visible before asking anyone to approve it.
Capture constraints as data
List the constraints your operation actually uses: capacity, delivery windows, required stops, restricted vehicle routes and shift availability. Assign an owner who can maintain each rule. Do not hard-code assumptions from one dispatcher into an optimization model and treat them as permanent policy.
Google OR-Tools routing guidance explains routing models and constraints. Openrouteservice's routing options illustrate options for route restrictions. Neither source establishes that a proposed route is operationally suitable for a specific business; the application must combine route data with its own approved rules.
Worked example: a blocked delivery stop
Imagine a hypothetical distributor with six deliveries assigned to a van. The third customer reports that its loading area will be unavailable for an hour. The planner suggests visiting stop four first, then returning to stop three.
The change request shows the old and proposed sequences, estimated arrival differences and the affected customer windows. The dispatcher checks whether the revised sequence is compatible with the vehicle's load and the remaining commitments. If one delivery requires an arrangement not modeled in the planner, that exception stays visible in the decision record.
Approval creates a new route version. The driver's application receives the version and requests acknowledgment. Until that acknowledgment arrives, the control room should not assume the new sequence is in effect. If the driver is offline, the workflow exposes the uncertainty and supports the operation's agreed communication fallback.
Separate proposals from commands
A planner may generate several alternatives while a dispatcher reviews the first one. Tie the approval to a specific route version and set of stops. If a delivery is canceled or vehicle location changes materially, recheck the proposal rather than apply stale approval to a changed plan.
Require a reason for manual overrides. Record who approved the change and when it became effective. Avoid allowing an optimization job to overwrite the approved sequence merely because it has produced a newer result.
Design the driver's experience
Show the change clearly: which stop is next, what changed and whether the old instruction has been replaced. A small notification alone is insufficient when the driver could continue following a downloaded route. Avoid interface patterns that require distracting interaction while driving; review them with operational and safety stakeholders.
Capture acknowledgment, rejection and inability to comply as different responses. If the driver reports that the route is unsuitable, send the issue back to dispatch. Preserve the message and route version so the subsequent review can reconstruct what was communicated.
Evaluate the complete operational cycle
Test a proposed change while the device is offline, two dispatchers approving competing versions, a stop being canceled during review and an external mapping outage. Confirm that only the current approved route can be issued as the active instruction.
Measure unresolved change requests, acknowledgment delay and repeated overrides by reason. These reveal missing constraints and communication problems that distance savings alone would overlook. A reliable route-change workflow gives optimization a controlled place in operations, with accountable decisions and an honest view of execution.
Primary references
Related reading
Design dispatch approvals and reliable integration with our business systems service.