In case a Task fails to be completed, you can set up a workflow for returning to a specified location (pickup location or a custom location). These options will only apply to Return Tasks.

Setting this up can be done in Configuration ⇒ Issue Options ⇒ Return to a Location.

The Return to a Location section of the Task Issue Workflow gives users flexibility and full control over what happens after a Task cannot be completed.

In case the Failed Task needs to be returned to a specific location you can specify which location. It can either be a Pickup location specified within the Failed Task, the Depot location (you can select any of the existing Depots within eLogii), or an entirely Custom location that you can configure.

Please note that only one custom return location can be set at a time, and you can select only one Depot to be the default return location for Failed Tasks.

In case some processes need to be honored when returning a Task, users can set them up in the Return Actions section. These can either mirror your existing Pickup/Delivery Proof of Delivery actions, you can disable them entirely, or set specific custom return actions unique to Return Tasks. This can be configured in Configuration ⇒ Issue Options ⇒ Actions for return task.

Delivery - This allows delivery POD actions to be set for the returned Tasks. If this option is selected, the Delivery actions configured for the original Task will be copied over onto the Return Task.

Pickup - This allows delivery POD actions to be set for the returned Tasks. If this option is selected, the Pickup actions configured for the original Task will be copied over onto the Return Task. There are two options, the first one will tell eLogii to copy Delivery actions in case there are no pickup actions configured for the Task, while the second option will only copy the pickup actions (if there are no pickup options, then none will be copied over to the Return Task).

Nope - Enabling this option means that the Return Task will not have any required actions at all.

It's also possible to configure custom actions the Driver needs to perform, For example, if a Driver needs to confirm that they are taking the package to the designated return location, and if a person at that location needs to sign and confirm they received the Task - all that can be configured within the return actions.
Essentially. this allows custom Proof of Delivery actions to be set for the return Tasks.

Actions can be set as mandatory which will prevent the Driver from completing the Task unless the mandatory POD requirements have been fulfilled.

Click Save once the actions have been set.

This enables instructions to be presented to the Driver if the Task cannot be completed as the contact is unavailable, notifying them of a safe place to leave the package. You can set the safe place to be either the pickup location or a completely custom location.

Setting this can be done in Configuration ⇒ Task Issue Workflow ⇒ Return to Safe place

Please note that while you can't specifically have the return journey be set as the last Task on the Drivers' list automatically, you can configure where the returned Task should go as well as manually change the order of the Route in the Planning screen