Interpret Courier job-flow counts
Understand how the dashboard groups jobs by their saved lifecycle state.
Exact navigationAdmin Area → Courier & Logistics → Dashboard
What this guide covers
Understand how the dashboard groups jobs by their saved lifecycle state. 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 Dashboard.
- Compare draft, available, quoted, assigned, accepted, collection, delivery, completed and cancelled counts.
- Open Jobs with the matching filter for the underlying records.
Fields, choices and supported possibilities
Pre-dispatchdraft, available, quoted
Assigned flowassigned, accepted, en_route_collection, collected, en_route_delivery
Closed flowcompleted, cancelled
Code-backed validations and workflow rules
- Counts do not override transition rules.
- A completed count requires locally retained POD evidence; an external completion alone does not satisfy this rule.
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.