Monitoring and reports

Readreportsanddashboard

Review mission, driver, route, fleet, exception, and proof performance.

Goal

Explain performance reporting.

Who it is for

Operations managers, admins, and dispatch leads.

Expected result

Teams can understand operational performance and identify follow-up actions.

Prerequisites

Completed or active route work

Steps

01

Filter report context

Use branch and date range filters to review the right operating period.

02

Read performance signals

Review status, driver activity, vehicle activity, route performance, and exceptions.

03

Turn reports into action

Use proof gaps, late work, and unassigned work signals to improve the next dispatch cycle.

Field definitions

Total missions
Started missions
Completed missions
Late missions
Delivery time
Routes served
Driver activity
Vehicle activity
Exceptions

Troubleshooting

Reports are empty for the selected range.

Branch filter excludes expected data.

Completed missions are missing proof.

Screenshots to capture

Use anonymized product data. These are screenshot requirements for the final docs pass.

docs-reports-overview.png

Reports overview hero.

docs-reports-filter-branch-range.png

Branch and date filters.

docs-reports-health-grid.png

Health cards.

docs-reports-driver-activity.png

Driver activity chart or list.

docs-reports-route-performance.png

Route performance section.

docs-reports-exceptions.png

Exceptions list.

docs-reports-detail-page.png

Report detail page.

Need to try it with your own route data?

Start with the full dispatch workflow and 200 scheduled order credits.

Start freeBook demo