Understand the 30-minute assignment response window
Use the dispatch response due time as an operational control.
Exact navigationAdmin Area → Courier & Logistics → Jobs → Open assigned job
What this guide covers
Use the dispatch response due time as an operational control. 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 the assignment.
- Review dispatched time and response due time.
- Follow the organisation’s escalation process if no response is recorded by the deadline.
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
- The assignment response due value is set 30 minutes after dispatch.
- The module does not justify silently changing the job state without the supported status action.
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.