# A Day with Your Fleet Bring tracking, reports, and service records together for the work ahead. Last updated: . ## Review a Delivery Vehicle's Working Day Start with the vehicle's last update time, then open its journeys for the relevant date. Compare completed trips with the planned deliveries, and inspect playback where timing or route details need explanation. Use a current-trip sharing link for a customer who needs progress visibility during an active delivery. At the end of the day, export **Trip history** or **Vehicle usage** for the same vehicle and dates. Treat this as recorded vehicle activity: it does not establish proof of delivery or explain every stop without supporting operational records. ## Investigate Fuel Use and Idling Run **Fuel consumption** for a consistent period and check coverage before comparing vehicles. Review **Fuel by journey** for the trips contributing usable readings, then compare **Idling periods** and journey distances for the same period. For example, a higher litre total may simply reflect more distance travelled. Compare L/100 km only where both distance and fuel are available, and consider load, traffic, route, and installation quality before drawing conclusions. Recorded idle time can identify activity to review, but it does not measure the cause of every fuel difference. ## Plan Maintenance Across Several Vehicles Use **Outstanding maintenance** with a future date range to see scheduled work, then widen the start date to include older overdue items. Open each vehicle's service record to check the work required and mileage threshold. After servicing, complete the record with the actual cost, odometer, notes, and receipts. Use **Completed maintenance** to confirm service history and **Maintenance costs** to review recorded expenditure. A service without a recorded cost does not represent a free service; complete the missing entry before relying on expenditure totals. ## Review Driver Safety Events Choose a common period for **Speeding events** and **Harsh driving events**, then inspect the relevant journeys. Confirm the driver assignment and device reporting context before discussing an event. Several alerts may come from one episode, and vehicles with different reporting coverage may not be directly comparable. Use the findings to identify trips that need review and to check whether the configured behaviour thresholds are appropriate. An alert count alone does not explain road conditions or assign responsibility. ## Related Guides - [Drivers, Assignments, and Journeys](/docs/drivers) - [Create and Manage Geofences](/docs/geofences) - [Maintenance and Service Scheduling](/docs/maintenance) - [All customer guides](/docs)