Dispatch a job

Follow this guide to create the assignment, POD and operational side effects atomically. 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

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.

Follow these steps

1. Select the eligible job, driver and vehicle.
2. Check or authorise driver pay.
3. Verify Dispatch.
4. Go to the job detail.
5. Check assignment response deadline, assigned resources, history and POD.
6. Check optional dispatch email/provider update.

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

• If the required delivery note cannot be created, the assignment transaction is rolled back.

How to confirm it worked

• 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.

Continue with related guidance