Understand driver employment statuses
Apply the supported employment lifecycle consistently.
Exact navigationAdmin Area → Courier & Logistics → Drivers → Open driver
What this guide covers
Apply the supported employment lifecycle consistently. 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
- Open the driver.
- Choose the status that matches the authorised HR/operations decision.
- Save and verify the active driver list.
Fields, choices and supported possibilities
onboardingDriver setup is incomplete or evidence is pending.
activeDriver is employed/engaged and may be operationally eligible.
suspendedDriver must not be dispatched while suspended.
leftDriver is no longer operational.
Code-backed validations and workflow rules
- Dispatch requires an active driver record.
- Employment status and availability are separate controls.
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.