Generate a failed delivery report
Filter Upper's Route Plan Detailed Report by Stop Status to see only failed stops, review the reason for each, and export the list as CSV or XLS for analysis.
When a delivery doesn't get made, the Route Plan Detailed Report is where you find out which stop it was, who attempted it, and why it failed. The report has one row per stop, so you can filter it down to just the failed stops, read the reason on each, and export the list for follow-up.
Your workspace may label deliveries as services and drivers as technicians. If so, you'll see wording like "Service" and "Technician Name" in place of the delivery and driver labels used below.
Why this matters
Every failed stop is a customer who didn't get their order and a delivery that has to be reattempted. Reviewing the reasons over time tells you whether the cause is bad addresses, time windows that no longer fit, or something on the route — and each of those has a different fix.
Generate the report
Go to Track > Analytics in the left sidebar.
Open the View by dropdown and choose Route Plan Detailed Report.
Open the Filter panel (the filter icon at the top right) and set what you want to see:
- Date Range — the period to review (defaults to the last 7 days)
- Stop Status — choose Fail to see only the stops that didn't get delivered
- Drivers — optionally narrow to one driver
- Select Route Plan — optionally narrow to a specific route
Then choose Apply.
Review the filtered table. The columns most useful for a failed-delivery review are Stop Status, Reason, Notes From Driver, Arrive At, Stop Address, and Driver Name.
If you don't see a column you need, open Customize Columns (the grid icon at the top right), check the columns you want in the Edit Column window, drag to reorder, and choose Done. Your column choices are saved for this report.
Key columns for failed-delivery analysis
| Column | What it shows |
|---|---|
| Stop Address | Where the failed stop was |
| Stop Status | The outcome recorded for the stop |
| Reason | Why the delivery failed |
| Notes From Driver | The driver's own explanation |
| Arrive At | When the driver arrived |
| Driver Name | Who attempted the stop |
Export for follow-up
To share the failed-stop list or analyze it in a spreadsheet, select Export at the top right.
In the Export window, confirm or change the Export File Name.
Pick a Format — CSV or XLS.
On the Fields tabs, keep Default to use the report's standard columns, or switch to Custom to choose exactly which fields to include and in what order.
Optionally tick Send e-mail when Export is complete., then choose Start Export.
The filters you apply on screen carry through to the export, so set your Stop Status and Date Range before you export.
Common scenarios
- Monthly failure review — Set the Date Range to the month and Stop Status to Fail, then export and group the rows by Reason in a spreadsheet to find the most common cause.
- Problem addresses — Export failed stops over a longer period and group by Stop Address. Addresses that fail repeatedly usually need updated access notes on the contact record.
- Driver check — Filter to one driver over the last month. If their share of failed stops is well above the team's, look at their route load and the failure reasons before drawing conclusions.
Troubleshooting
If something still doesn't look right, contact support@upperinc.com.
Related
Generate a driver activity report
Build a complete driver activity report in Upper by combining the Driver Timesheet Report for hours worked with the Route Plan Detailed Report for delivery activity.
Generate a proof of delivery report
Proof of delivery data lives in Upper's Route Plan Detailed Report. Add the POD columns in Analytics, then export the report as CSV or XLS.