Choose the POD goods condition
Record the delivery outcome used locally and by provider submission. 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.
Where to goPublic POD page → Condition
What you’ll accomplish
Record the delivery outcome used locally and by provider submission. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.
Follow these steps
- Select the condition that matches the observed delivery.
- Add explanatory notes for damaged, short or refused outcomes.
- Submit with signature and snapshot.
Fields and options to review
goodMapped to provider COMPLETED.
damagedMapped to DAMAGED_GOODS.
shortMapped to INCORRECT_GOODS.
refusedMapped to REFUSED.
Rules the system enforces
- Condition mapping affects provider POD status; select accurately.
How to confirm it worked
- 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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.