Use the Courier audit trail

Trace who changed an operational record and what changed.

What this guide covers

Trace who changed an operational record and what changed. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.

Exact step-by-step process

1. Open the relevant driver, vehicle, customer, job, delivery note, finance or integration record.
2. Review its history or audit context.
3. Match action, entity, record ID, staff identity, before/after values and timestamp.
4. Use the audit entry together with the source record and any notification or sync log.

Fields, choices and supported possibilities

This action uses the values already stored on the selected source record. Review that record before continuing.

Code-backed validations and workflow rules

• Secrets are redacted before audit payloads are stored.
• Audit evidence supplements rather than replaces the authoritative operational record.

Expected result and verification

• The source record, status/history and any downstream notification, provider, POD or finance record should agree after the action.

Security, audit and operational checks

• Use the exact record and least-privilege role before changing any state.
• Verify the saved record after every action; a browser message alone is not evidence that every downstream step completed.
• Use protected document and image routes rather than exposing server filesystem paths.
• Keep customer, driver, provider, financial and credential data within the authorised workflow.
• For provider, finance, employment, transport and compliance decisions, follow the organisation’s authorised professional process.

Related Courier guides