Track vehicle MOT expiry
Maintain the monitored MOT date and act before it expires.
Exact navigationAdmin Area → Courier & Logistics → Vehicles → Open vehicle → Compliance
What this guide covers
Maintain the monitored MOT date and act before it expires. 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 vehicle.
- Enter or verify the MOT expiry date.
- Save the vehicle.
- Review Compliance alerts and renew the evidence before expiry.
Fields, choices and supported possibilities
mot_expirySaved date used by vehicle compliance monitoring and automation.
Code-backed validations and workflow rules
- When the monitored MOT date is in the past, automation can mark the vehicle expired and unavailable.
- A future date alone does not prove the evidence is valid; retain and verify the source document through the organisation’s process.
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.