Driver onboarding, pay and compliance

Upload a driver compliance document

Follow this guide to add protected evidence to a driver record. 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: Manage complianceModule v2.0.0
Jump to steps
Where to goAdmin Area → Courier & Logistics → Drivers → Open driver → Documents → Upload
Before you start
  • Prepare the correct evidence and expiry details.

What you’ll accomplish

Add protected evidence to a driver record. 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 the driver.
  2. Select the document type.
  3. Select the evidence file.
  4. Enter issue/expiry details where applicable.
  5. Upload.
  6. Verify the document is pending review.

Fields and options to review

Allowed filesPDF, JPG, JPEG, PNG and WebP.
Maximum size8,192 KB.
StorageProtected module upload area rather than a public asset folder.

Rules the system enforces

  • Uploading evidence does not approve it.
  • Use the download endpoint to review protected documents rather than guessing a filesystem URL.

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.