Handle an expired driving licence | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/handle-an-expired-driving-licence Publisher: Pixie Technologies LLC Driver onboarding, pay and compliance Handle an expired driving licence Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Prevent dispatch when the driver licence has expired. Audience: Courier operations staff; Permission: Courier: Manage compliance; Module v2.0.0; Where to goAdmin Area → Courier & Logistics → Drivers → Open driver What this guide helps you do Prevent dispatch when the driver licence has expired. 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 after the expiry alert. - Check the driving-licence expiry date. - Mark the driver unavailable if not already blocked. - Request and upload renewed evidence. - Approve the renewed document and recalculate compliance. Fields and options This action uses the values already stored on the selected source record. Review that record before continuing. Rules and limits - An expired licence forces the compliance state to expired. - Dispatch requires a compliant driver. 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 Create a driver record (https://pixiecrm.com/help-centre/create-a-driver-record)Edit a driver safely (https://pixiecrm.com/help-centre/edit-a-driver-safely)Understand driver employment statuses (https://pixiecrm.com/help-centre/understand-driver-employment-statuses)Understand driver availability states (https://pixiecrm.com/help-centre/understand-driver-availability-states)