Skip to content
  • There are no suggestions because the search field is empty.

Review workforce, booking and alert history reports

Compare planned rosters and reservations with actual driver assignments, journeys and alert context.

Use these reports together when you need to compare planned work with recorded activity:

When was a person scheduled to work?
Rosters

When was a vehicle reserved, and for whom?
Reservations

Who was assigned to a vehicle, for how long and what travel was recorded?
Driver History

What alert occurred, where, and what driver or journey context was available?
Alert History

Before you start

Choose the shortest date range that covers the event under review. Check the account timezone and confirm that you are authorised to view the people, locations, journeys and alerts involved.

These reports answer different questions. Rosters and reservations describe configured plans; Driver History describes recorded vehicle assignments; Alert History describes raised alerts and any linked journey context. A row in one report does not prove that a matching row must exist in another.

Driver assignments can come from the People or Vehicles pages, the Track My Ride app, or a Driver ID keyfob used with compatible hardware. Missing or incorrect assignments affect Driver History and any alert context that depends on the known driver.

Steps

Review planned work and bookings

  1. Open Reports > Rosters.
  2. Select the date range and a person, or choose all people when a fleet-wide review is necessary.
  3. Select Run Report and review Person, Title, Start, End, Repeat and Classification.
  4. Open Reports > Reservations and use the same date range.
  5. Select a vehicle, a person with reservations, or All devices, then run the report.
  6. Review Vehicle, Reserved For, Title, Start, End, Repeat and Classification.

Use these reports to confirm what was configured. To change future roster or reservation records, use the corresponding management page rather than editing an exported report.

Reconstruct driver assignments

  1. Open Reports > Driver History.
  2. Select the date range and vehicles, then select Run Report.
  3. Review the vehicle, registration, driver, login and logoff times, assignment duration, journey count and distance.
Driver History report showing a synthetic vehicle assignment with login duration journey count and distance.
Driver History report showing a synthetic vehicle assignment with login duration journey count and distance.
  1. Compare the assignment period with the expected roster or reservation. An assignment can remain open at the end of the selected period, so check the current vehicle assignment when Logoff is absent.
  2. Investigate gaps or unexpected drivers by checking assignment changes, use of the Track My Ride app and Driver ID events for the same period.

Investigate an alert in context

  1. Open Reports > Alert History.
  2. Choose the date range and vehicles, then run the report.
  3. Find the alert by date, vehicle, driver, location, criteria or event description.
  4. Expand the row to review available journey start, stop, duration, addresses and distance.
Alert History results showing a synthetic speed alert with driver location and journey context.
Alert History results showing a synthetic speed alert with driver location and journey context.
  1. Compare the alert with the source journey, tracker events or Raw GPS data before deciding whether it reflects expected activity, a configuration issue or a tracking problem.

What happens next

Export the filtered result when an authorised reviewer needs a record of the investigation. Keep the report name, date range, timezone and selected people or vehicles with the export so the result can be reproduced.

Correct source records through their owning page. Changing a roster, reservation, person assignment or alert rule affects future behaviour but may not rewrite historical activity that was already recorded.

Troubleshooting

  • A roster or reservation is missing: Confirm the selected person or vehicle, date range and timezone, then check the record on its management calendar.
  • Driver History has no driver: Confirm how the person was assigned and whether the app or Driver ID hardware reported the assignment during the selected period.
  • Journey or distance totals look incomplete: Compare the assignment period with Journeys and Raw GPS data. Location or upload gaps can affect the recorded totals.
  • Alert History has no journey context: Some alerts occur outside a journey or cannot be matched to one. Review the alert time and source tracker data directly.
  • The same event appears different across reports: Confirm that each report uses the same date range, timezone and vehicle or person scope before comparing rows.