Fleet and vehicle compliance

Edit a vehicle record

Update fleet details while preserving job history.

Audience: Courier operations staffPermission: Courier: EditModule v2.0.0
Exact navigationAdmin Area → Courier & Logistics → Vehicles → Open vehicle → Edit

What this guide covers

Update fleet details while preserving job history. 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 vehicle.
  2. Update verified specifications, ownership, assignment or compliance dates.
  3. Save.
  4. Reopen and confirm availability and compliance state.

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

  • Registration is normalised on save.
  • Expired monitored dates can be processed by automation and make the vehicle unavailable.

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.