Compliance workspaces and alerts

Review vehicle compliance alerts

Identify fleet records with expiring or expired monitored dates.

Audience: Courier operations staffPermission: Courier: Manage complianceModule v2.0.0
Exact navigationAdmin Area → Courier & Logistics → Compliance → Vehicles

What this guide covers

Identify fleet records with expiring or expired monitored dates. 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. Filter vehicle alerts.
  2. Open the vehicle.
  3. Review MOT, tax, insurance, hire-and-reward and goods-in-transit dates.
  4. Renew and update verified dates.
  5. Confirm availability/compliance.

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

  • Use the supported screen and permission; do not bypass validation or edit database records directly.

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.
Do not bypass the code flowDo not force database values, invent a status, mark a job completed without signed POD evidence, or expose encrypted credentials to make a screen appear successful.