Frame the case
Register job, stop, route edition, address source and dispatch owner.
Workflow blueprint
Route dispatch software should distinguish a suggested route from a completed stop
A page-specific review aid, not a universal product or compliance claim.
Use the dispatch stop-change board to keep job identity, route suggestion, driver acknowledgement, stop change, proof and customer notice connected for a Mauritius evidence review.
TL;DR — Use the dispatch stop-change board to keep job identity, route suggestion, driver acknowledgement, stop change, proof and customer notice connected for a Mauritius evidence review.
Trace the evidence
Relate driver acknowledgement, access note, resequence, delay and status message.
Review the exception
Keep proof event, customer notice, exception and completion question separate.
Assign the next owner
Assign fleet, safety, privacy, delivery, service and payment owners.
Page-specific decision aid
Dispatch stop-change board
A job, route edition, stop, driver response, access note, proof event, change reason and customer update.
- ✓Route suggestion is not arrival proof
- ✓A stop keeps its response
- ✓Customer notice is not delivery
Scope first
What Codeblix would confirm before implementation
This page is an operational blueprint. The final workflow, screens, permissions and integrations depend on your current process and agreed implementation scope.
- ✓Job and stop identity
- ✓Route and driver response
- ✓Access and proof event
- ✓Dispatch reviewer
Relevant Codeblix foundations
Review the existing product areas that support the proposed workflow.
Use the related planning tools
Run the operational calculation, save the result in the URL and share it with your team.
Map this workflow to your operation
Tell Codeblix how work moves today. We will confirm the practical scope before proposing an implementation.
Discuss your workflow