Preparation: work from one shared route list
Daily work starts with an agreed list of routes, stops and items. After import, check identifiers, addresses and missing information. E-route uses consistent route data for preparation and subsequent feedback, so errors in the source data should be resolved before handover.
Ready for handover is not the same as handed over
The preparation team indicates what is available. The digital handover already records what was actually handed over and who accepted it. Separating the two states helps to interpret the shortage: an item that has not been prepared requires a different measure than a discrepancy indicated at handover.
The driver sees the assigned task
The proprietary Android application connects to the central process with the routes, stops and items assigned to the driver. The field feedback must belong to the given stop or item. The photo and the related event data can help clarify it later; which evidence should be recorded is determined by the organizational process.
Offline data capture and the central status
With a changing network connection, field recording and the appearance of central data are not necessarily the same time. Due to the synchronization planned for offline work, it is worth investigating separately the disconnection and return of the connection during the introduction test. The customer service interpretation must also clarify which feedback has already been received by the center.
Exception: the stop cannot be closed according to the plan
Illustrative situation: the driver notices a discrepancy when handing over. Instead of a mere failed status, the necessary reason and the person responsible for the next step must also be defined. Returns, partial fulfillment and new negotiation can be different tasks. The event history helps you separate what actually happened and what still requires action.
Completion and later retrieval
Customer service can interpret the delivery status together with the delivery note and related documents. Common identifiers and system connections must be agreed upon during introduction. On a test day, you examine the entire process: import, preparation, handover, field feedback and closing. The exact range of functions is determined by the chosen version and the implementation plan.