Jobs, stops, dispatch and status control

Understand the complete job-status matrix

Apply only model-authorised transitions.

Audience: Courier operations staffPermission: Courier: EditModule v2.0.0
Exact navigationAdmin Area → Courier & Logistics → Jobs → Open job → Change Status

What this guide covers

Apply only model-authorised transitions. 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

  1. Open Admin Area → Courier & Logistics → Jobs → Open job → Change Status.
  2. Review the source record and choose the supported action.
  3. Save or submit once, then reopen the record and verify the result.

Fields, choices and supported possibilities

draftavailable, cancelled
availablequoted, assigned, cancelled
quotedassigned, cancelled
assignedaccepted, cancelled
accepteden_route_collection, cancelled
en_route_collectioncollected, cancelled
collecteden_route_delivery, cancelled
en_route_deliverycompleted, cancelled
completedno next state
cancelleddraft

Code-backed validations and workflow rules

  • Invalid transitions are rejected.
  • Assigned and later operational states require a linked driver.
  • Completed requires signed POD and snapshot.

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.