Understand dispatch eligibility checks
Troubleshoot why a driver, vehicle or job cannot be assigned.
Exact navigationAdmin Area → Courier & Logistics → Dispatch
What this guide covers
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.
Exact step-by-step process
- Open each source record.
- Correct the exact failed field/state.
- Return to Dispatch and select the records again.
Fields, choices and supported possibilities
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.
Code-backed validations and workflow rules
- Do not bypass an eligibility failure by editing database values directly.
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.