Handle a vehicle compliance expiry
Remove an expired vehicle from dispatch and restore it after renewal.
Exact navigationAdmin Area → Courier & Logistics → Compliance → Vehicle alerts
What this guide covers
Remove an expired vehicle from dispatch and restore it after renewal. 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
- Open the alert.
- Open the vehicle and identify the expired monitored field.
- Set maintenance/unavailable if required.
- Renew and verify the source evidence.
- Update the expiry date.
- Save and confirm compliance and availability.
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
- Automation may set compliance to expired and availability to unavailable when a monitored date passes.
- Do not manually mark compliant until the verified dates support it.
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.