Fleet and vehicle compliance

Create a vehicle record

Follow this guide to add a fleet asset with capacity, ownership, allocation and compliance dates. 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: CreateModule v2.0.0
Jump to steps
Where to goAdmin Area → Courier & Logistics → Vehicles → Add Vehicle

What you’ll accomplish

Add a fleet asset with capacity, ownership, allocation and compliance dates. 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 Vehicles and select Add Vehicle.
  2. Enter registration, make, model and descriptive details.
  3. Select vehicle type and ownership.
  4. Assign a default driver only when appropriate.
  5. Enter payload, cubic capacity, fuel and odometer details.
  6. Enter MOT, tax, insurance and other monitored dates.
  7. Save and verify availability/compliance.

Fields and options to review

RegistrationNormalised to uppercase with spaces removed.
Ownershipcompany, driver, leased or hired.
Availabilityavailable, assigned, maintenance or unavailable.
Compliancecompliant, pending, action_required or expired.
External referencesOperator licence, Courier Exchange and telematics identifiers where used.

Rules the system enforces

  • Use the actual registration as the unique operational identifier.
  • Dispatch still checks the current availability and compliance state.

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.