Dispatch a job
Create the assignment, POD and operational side effects atomically.
Exact navigationAdmin Area → Courier & Logistics → Dispatch → Assign
What this guide covers
Create the assignment, POD and operational side effects atomically. 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
- Choose the eligible job, driver and vehicle.
- Review or authorise driver pay.
- Confirm Dispatch.
- Open the job detail.
- Verify assignment response deadline, assigned resources, history and POD.
- Verify optional dispatch email/provider update.
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
- If the required delivery note cannot be created, the assignment transaction is rolled back.
Expected result and verification
- An assignment is created with status dispatched and a 30-minute response due time.
- The job becomes assigned.
- The driver becomes busy and the vehicle assigned.
- Job history and audit records are created.
- A delivery note/POD is created or reused.
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.