Understand driver employment statuses
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Apply the supported employment lifecycle consistently.
Where to goAdmin Area → Courier & Logistics → Drivers → Open driver
What this guide helps you do
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.
Follow these steps
- Go to the driver.
- Select the status that matches the authorised HR/operations decision.
- Save and verify the active driver list.
Fields and options
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.
Rules and limits
- Dispatch requires an active driver record.
- Employment status and availability are separate controls.
Check 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.
Related guides
Was this guide useful?Your response is stored only in this browser.