Fleet and vehicle compliance

Understand vehicle availability states

Control operational allocation independently from compliance. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.

Audience: Courier operations staffPermission: Courier: EditModule v2.0.0
Jump to steps
Where to goAdmin Area → Courier & Logistics → Vehicles → Open vehicle

What you’ll accomplish

Control operational allocation independently from compliance. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.

Follow these steps

  1. Go to Admin Area → Courier & Logistics → Vehicles → Open vehicle.
  2. Check the source record and choose the supported action.
  3. Save or submit once, then reopen the record and verify the result.

Fields and options to review

availableMay be selected for dispatch if compliant.
assignedCurrently allocated to a job.
maintenanceUnavailable because maintenance is required or in progress.
unavailableExplicitly blocked from dispatch.

Rules the system enforces

  • Assignment changes availability to assigned.
  • Job completion or cancellation releases the vehicle to available.
  • Expired compliance automation can set unavailable.

How to confirm it worked

  • 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.