Understand dispatch eligibility checks | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/understand-dispatch-eligibility-checks Publisher: Pixie Technologies LLC Jobs, stops, dispatch and status control Understand dispatch eligibility checks Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Use this guide to diagnose and resolve why a driver, vehicle or job cannot be assigned. Audience: Courier operations staff; Permission: Courier: Dispatch; Module v2.0.0; Where to goAdmin Area → Courier & Logistics → Dispatch What this guide helps you do Troubleshoot why a driver, vehicle or job cannot be assigned. 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 each source record. - Correct the exact failed field/state. - Return to Dispatch and select the records again. Fields and options JobActive, unassigned, status draft/available/quoted, receiver name, valid receiver email, agreed revenue > 0. DriverActive record, employment active, availability available, compliance compliant, valid email. VehicleActive record, availability available, compliance compliant. Rules and limits - Do not bypass an eligibility failure by editing database values directly. 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 courier job (https://pixiecrm.com/help-centre/create-a-courier-job)Edit a draft or pre-dispatch job (https://pixiecrm.com/help-centre/edit-a-draft-or-pre-dispatch-job)Understand job sources and external references (https://pixiecrm.com/help-centre/understand-job-sources-and-external-references)Enter collection and delivery addresses (https://pixiecrm.com/help-centre/enter-collection-and-delivery-addresses)