Suspend or offboard a driver
Remove operational eligibility while retaining history.
Exact navigationAdmin Area → Courier & Logistics → Drivers → Open driver
What this guide covers
Remove operational eligibility while retaining history. 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
- Check for active assignments.
- Complete, cancel or reassign work through the supported job workflow.
- Set employment status to suspended or left.
- Set availability to unavailable/offline as appropriate.
- Save and verify the driver no longer appears as dispatch eligible.
Fields, choices and supported possibilities
This action uses the values already stored on the selected source record. Review that record before continuing.
Code-backed validations and workflow rules
- Do not soft-delete a driver merely to offboard them.
- Historic assignments, PODs and finance records should retain their link.
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.