Round Audit – URBANTZ | SUPPORT

The Round Audit tab is meant to help you quickly detect any possible issues within a selected round.

The point of this screen is not to show all the information about the round and its tasks, but rather to show the minimum amount of information that will help you determine the problem.

We therefore rely on colors to highlight any deviations from the plan.

The color depends on the severity of the deviation and will be explained in detail in this doc.

The Round Audit tab consists of two sections:

Round Summary
Timeline

This is visible in the following image:

Round Summary

Round Summary contains general information about the round. There are 5 color-coded cards that show planned value plus the deviation for the following parameters:

distance
duration
service time
travel time

Distance: The below screenshot depicts that the planned distance for this round was 11.1 km, but the actual round was 1.4 km longer.

If the card color is orange, then the deviation from the planned value is between 30% and 60%.

If the card color is red then the deviation is greater than 60%.

We also show the total number of tasks that have any kind of issue in the 'Total Issues' card.

The below card shows that out of 45 tasks in the round 23 tasks have an issue.

We consider a task to have an issue if any of the following is met:

task failed
task delivered outside of the time window
real service time is more than 30% different than planned
Bad customer review (1-3 stars)
Delivery forced
Delivery completed at the wrong location

Above those cards, you can see additional details:

Number of mobile devices used during the execution of the round
Percentage of the round distance for which we have the GPS location of the driver
Indication if the round was optimized automatically or manually. If the round is created by the Round Editor or if 'On Fly' was used or if the driver changed the round in the mobile app we will consider that a manual optimization.

Timeline

The Timeline section shows in chronological order what went wrong in a round.

There are 3 important columns (from left to right):

the order in which tasks were executed
the circles containing information about the deviations
the time windows with extra information

The order of execution column

On the left of the Timeline section, you can observe the order in which tasks are executed.

The number in the box indicates the planned sequence of the task. The tasks are ordered by their real completion time. If a task is delivered when it was not its turn, you will see the circular arrows next to its number:

Between the tasks you can see the planned distance and planned travel time:

If the sequence is not respected, then the planned distance and travel time will not be available:

The task box itself can have 3 colors:

green - successful delivery and no highlighted issues
white - successful delivery with some highlighted issues
red - failed delivery

The circles column

Next to the column that shows the order of tasks you have a column of color-coded circles that show any deviations.

Here we list all possible circles and their meaning:

Clock icon: Round start delayed or early for a certain number of minutes:

Red: if the delay is more than 30 minutes

Orange: if the delay is between 15 and 30 minutes or if the round started more than 15 minutes early.

For all the following circles, the color is orange if the deviation is between 30% and 60% from what is planned, and red if the deviation is greater than 60%.

Hand icon: Real service time longer or shorter than planned with a certain number of minutes:

Car icon: Real distance or real travel time longer or shorter than planned with a certain number of kilometers or minutes:

The time windows column

The right column in the timeline shows time windows and relevant events on horizontal timelines.

The Timeline starts with the information about the round start. You can see the times of the following:

Planned round start - when was the round planned to start
Actual start - when the driver taps Start round in the mobile app
Driver departure - when we detect that the driver left the hub

Actual start and driver departure can be color-coded. Similar to the circle for the late or early start of the round, they will be red if the delay is more than 30 minutes, and orange if the delay is between 15 and 30 minutes or if they are more than 15 minutes early.

Then we show the time window for each task with relevant events on the timeline. This will look similar to the depiction below:

This means that the time window is between 06:00-08:00, the planned ETA is 07:21 and the task actually was successfully delivered at 07:07.

If a task is delivered outside of the time window, you'll see:

Orange is used if the delay is lower than the lower boundary and red if the delay is greater than the lower boundary. Note: The lower boundary is configurable in Administration > Platform > General.

If the delivery fails then you will see:

If the Onsite feature is activated, you will see when the driver indicated that he is on site:

Icons for onsite, successful, and failed deliveries can have an extra icon on top which indicates that these actions didn't happen at the location where they were supposed to.

"At the right location"
"Not at the right location"
	Successful delivery but not at the right location	Failed delivery but not at the right location	Forced onsite (i.e. onsite but not at the right location)