Suspend or offboard a driver

Remove operational eligibility while retaining history. 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.

What you’ll accomplish

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.

Follow these steps

1. Check for active assignments.
2. Complete, cancel or reassign work through the supported job workflow.
3. Set employment status to suspended or left.
4. Set availability to unavailable/offline as appropriate.
5. Save and verify the driver no longer appears as dispatch eligible.

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

• Do not soft-delete a driver merely to offboard them.
• Historic assignments, PODs and finance records should retain their link.

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.

Continue with related guidance