Understand driver availability states
Use availability independently from employment status.
Exact navigationAdmin Area → Courier & Logistics → Drivers → Open driver
What this guide covers
Use availability independently from employment status. 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.
- Select the current availability.
- Save.
- Confirm the dispatch list reflects the change.
Fields, choices and supported possibilities
availableMay be considered for dispatch if all other checks pass.
busyCurrently allocated or otherwise unavailable.
offlineNot presently accepting work.
unavailableExplicitly unavailable.
Code-backed validations and workflow rules
- A successful assignment changes the driver to busy.
- Completion or cancellation releases the assigned driver back to available.
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.