The Planned vs. Actual report compares your planned routes with what happened in the field. You can use it to review planned and actual route details side by side. In this article, you’ll learn how the report works, how to customize the information it shows, and how to export the report.
| Who can use this feature | |
|---|---|
| Pro and Custom plans | |
| All users | |
| All regions | |
What is the Planned vs. Actual report?
The Planned vs. Actual report is an analytics report that compares planned routes with their actual results side by side.
The report updates in real time and can be run for any past date range.
Accessing the report
To get to the Planned vs Actual report:
- Go to the “Analytics” tab
- Choose “Planned vs. Actual” from the left menu
- Adjust the time range to find the routes you want to compare
You can only select up to 30 days at a time.
Report layout
The Planned vs. Actual report compares planned route details with what happened during route execution. The report is organized by driver route and order stop sequence.
Driver route summary
Routes are grouped by driver and shown in chronological order for the selected date range.
Each route summary shows:
- Driver name
- Day of the week
- Route date
- Number of successfully completed orders compared with the total number assigned to the driver
Order information
The first column in the report shows a summary of order information including:
- Order ID
- Order Type
- Location Name
- Location Address
You can double click on the order to get more order details.
Planned vs. actual columns
The table is divided into two column groups: “Planned” and “Actual.” Use these columns to compare the optimized route with what happened during route execution.
You can compare:
- Stop order
- Timing
- Location
These comparisons can help you understand differences between the plan and what happened in the field.
You can also export the report.
| Field | Meaning |
|---|---|
| Planned Stop Number | The planned stop number. |
| Actual Stop Number |
The stop number when the order was actually performed. If allowed, drivers can perform stop numbers out of sequence. |
| Planned Start Date | The date the order was planned to be serviced. |
| Actual Start Date | The date when the order was actually serviced. |
| Scheduled At | The planned start time of the order. |
| Actual Start Time | The time when the driver actually started service on the order. |
| Planned Duration | The proposed duration for the order shown in minutes. You can also export this in seconds. |
| Actual Duration |
The actual duration of the order. When drivers use the driver app to start/stop service, the actual duration is calculated and sent to the dispatcher. Durations less than 1 minute will appear as 0, unless exported in seconds. |
| Status |
This is the order status which is the result of the service and can be any of the following:
“-” means no status was recorded by the driver or the dispatcher. This will show as “Scheduled” in the plan. |
| Distance to Location at Actual Start |
Shows the distance between the planned order location pin and where the driver was when the order was actually started. This is helpful in verifying driver position and pin location accuracy. This is available for both manual starts and geofencing auto-starts. |
| Actual Start Latitude & Longitude | Shows the exact position of the driver when the order was actually started. These are two separate columns that are only available in the report export. |
| Distance to Location at Actual End |
Shows the distance between the planned order location pin and where the driver was when the order was actually completed. This is helpful in verifying driver position and pin location accuracy. This is available for both manual completions and geofencing auto-completions. |
| Actual End Latitude & Longitude | Shows the exact position of the driver when the order was actually completed. These are two separate columns that are only available in the report export. |
| Started by | Shows if the driver started the order, or if it was started automatically by geofencing. |
| Completed by | Shows if the driver completed the order, or if it was completed automatically by geofencing. |
| POD Exceptions | Indicates whether any issues occurred during barcode scanning. |
| When you export the report, you can include additional details about orders, drivers, and vehicles for deeper analysis. |
Customizing and exporting the report
This report can be customized and exported to Excel. To do this:
- Go to the “Analytics” tab
- Choose “Planned vs. Actual” from the left menu
- Adjust the time range to find the routes you want to export
- Click “Export” in the top left corner of the table
- Choose the columns you want to export
- Click "Export"
| Customizing the report: You can also select 80+ other columns to add to this report when you click "Export" or edit the columns. |
Learn more about customizing and exporting Planned vs Actual reports here.