1
Open reports.
Open reports.
Reports and billing
Review driver performance
Use reports to review driver activity, route performance, mission status, exceptions, and delivery history.
A manager wants to understand how the delivery day performed and identify follow-up actions.
Difficulty: Beginner
Time: 10-15 minutes
Steps
2
Select branch and date range.
Select branch and date range.
3
Review top-level delivery summary.
Review top-level delivery summary.
4
Check mission status breakdown.
Check mission status breakdown.
5
Review driver activity.
Review driver activity.
6
Review route performance.
Review route performance.
7
Look for exceptions, failed missions, late work, or missing proof.
Look for exceptions, failed missions, late work, or missing proof.
8
Use findings for tomorrow's planning.
Use findings for tomorrow's planning.
Prerequisites
Completed or active route work exists.
Completed or active route work exists.
User has reporting permissions.
User has reporting permissions.
Branch/date range is known.
Branch/date range is known.
Common mistakes
Wrong date range selected.
Wrong date range selected.
No completed work exists yet.
No completed work exists yet.
User lacks reporting permission.
User lacks reporting permission.
Proof gaps are confused with photo/signature requirements.
Proof gaps are confused with photo/signature requirements.
What you will do
Open reports or dashboard.
Open reports or dashboard.
Filter by branch and date range.
Filter by branch and date range.
Review mission totals and statuses.
Review mission totals and statuses.
Review driver activity.
Review driver activity.
Review route performance.
Review route performance.
Review exceptions or proof gaps.
Review exceptions or proof gaps.
Decide next operational actions.
Decide next operational actions.
Related links
Docs
Read reports and dashboard
Docs
Verify proof of delivery
Feature
Reports and analytics
Feature
Proof of delivery
Track each step in your next run
Start with the current Rouptimize workflow and bring your dispatch, drivers, proof, and reporting into one operating system.