Driver onboarding, pay and compliance

Understand driver onboarding progress

Follow this guide to use the percentage as a code-backed readiness indicator. 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: ViewModule v2.0.0
Jump to steps
Where to goAdmin Area → Courier & Logistics → Drivers → Open driver

What you’ll accomplish

Use the percentage as a code-backed readiness indicator. 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. Check onboarding progress together with compliance status.
  3. Go to Documents to identify missing or non-qualifying evidence.

Fields and options to review

This action uses the values already stored on the selected source record. Review that record before continuing.

Rules the system enforces

  • New drivers begin at 20%.
  • Progress increases from qualifying required evidence; 100% aligns with a complete compliant set.
  • Do not use the percentage alone as dispatch approval.

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.