Find out what changed and who changed it
When work looks different from what the team expected, use the Audit Log to narrow down the record, the time, and the change before deciding what to do next.
When audit history helps
Use the Audit Log to investigate a changed job, an edited stop, or an updated driver record. It gives you a history entry with an entity type, entity ID, action, timestamp, and recorded user ID. Available details may include the changed fields and earlier or later values.
For example, if the office and driver have different expectations about a job, first identify the job and the time of the disagreement. Look for the relevant recorded change, then compare it with the current job before contacting the team.
Recorded event types include job, stop, and driver record creation and updates, plus team deletion. The Audit Log is not a complete history of every Settings edit or every action in RouteIQ. An empty result does not prove that nothing happened.
Use a dispatcher or administrator account for the site. History is scoped to the current site; change sites first if the work belongs to another operation.
Find the relevant events
- Open Settings → Audit Log.
- Set From and To to a useful date and time window. Start wider if the exact time is uncertain.
- Enter an Entity type such as
job,stop, orworker. Driver records useworker. - Enter the exact Entity ID when you have it. Use the record's ID, not its customer name, address, or display label.
- Optionally add an Action, such as
createorupdate, or a User ID if you are investigating a particular recorded actor. - Select Search. Sort by Timestamp to follow the sequence, and use the table's pages to inspect more results.
Text filters match exact values. Leave a field blank to include all its values. If you do not know an action or ID, start with the time window and copy the exact value from a relevant result. Reset clears the filters.
Read the change in context
Open a row's View audit details button in the Details column. The dialog shows the event identity and any payload recorded for that event.
| Detail | What to look for |
|---|---|
| Changes | The fields identified as changed, when a change summary was recorded |
| Previous data | The earlier record snapshot, when available |
| New data | The later record snapshot, when available |
| User ID | The actor ID attached to the event; an absent ID appears as System |
Read the field names alongside their values. A creation event may have new data without a previous snapshot. Some events have no change payload at all. A System label means no user ID was recorded; it does not by itself explain which background process was responsible.
The detail view is an investigation tool. It does not restore old values. If the work needs correcting, open the current job, stop, or driver record and make the appropriate change through its normal workflow.
Finish the investigation
- Confirm that the entity ID belongs to the record you intended to investigate.
- Compare the relevant event with the current record and nearby events. Do not assume one update explains the whole sequence.
- Record the event time, entity ID, action, and relevant fields for the colleague handling the issue. Include the recorded user ID if it helps them identify the actor.
- After any correction, reopen the current record and verify the intended result. If a corresponding audit entry is available, check it too.
When asking for help, describe the expected result and what actually happened. Share only the fields needed to explain the issue; snapshots can contain customer or operational details.
Troubleshooting
No events match
Check the site, widen the time window, and remove one filter at a time. Exact IDs and action names matter. A job's stop has a different entity ID from the job itself.
A settings change is missing
Audit coverage is limited to recorded event types. Check the current setting directly and compare your team's change notes; do not infer that a missing row means the setting was unchanged.
The row exists but its details are blank
If the dialog says no change payload was recorded, use the summary and related records to continue. If loading failed, select Retry; a request failure is different from an event without a payload.
I can see a user ID but not a person's name
The log displays the recorded identifier. Ask an administrator to help identify it if needed, and avoid attributing a change from the ID alone.
For the relationship between the records you are investigating, see Jobs, stops, and routes.