Task Priority

Learn how to define task's importance

Written by eLogii
Updated yesterday

When creating a Task you have the option of defining its importance in the Advanced section of the Task form.

Depending on what you select, eLogii will take this information into consideration when optimizing and creating Routes.

If the priority is set to high, the optimization will ensure that the Task is assigned and of greater importance than other Tasks; and if it's set to low it will first consider other Tasks and fit it only if there is room.

Other than selecting the Task priority from the drop down menu, there is also the option of adding a number ranging from 1 to 100 to define the importance with 1 being of lowest and 100 of highest importance. By default, Normal priority is 0, while the values go up by 25 for each next selected option.

Alternatively, you can also define the Task priority after the task has been created by navigating to Tasks โ‡’ Task Profile โ‡’ Task Priority.

Click Save once the priority has been added.

Please note that other factors come into play during optimization such as Vehicle capacity, Driver schedule, Task time windows, and other constraints, which may sometimes result in the Task priority not being met as expected. This means that Tasks will not be optimized regardless of their priority over others if including them would mean breaking set constraints.

Another thing that's important to note is that priority doesn't necessarily impact the order of Task execution and we recommend utilizing the Task Execution order feature to determine the exact order of a Task in a route.

๐Ÿ’กPro tip - Automatically setting the priority based on Driver skill

If you would like to automatically attribute a priority value to Tasks based on a specific Driver skill, you can accomplish that via Task rules. Set the source field as skills and define the desired skill you wish to trigger the automation, and in the target field select priority and enter the value you wish attributed to the Tasks that contain the defined skill.

The same logic can be applied to any other entity you would like to use as a trigger for the priority change, so if skills are not something you utilize, you can choose any other Task element to trigger the Priority change.

Did this answer your question?