Submit a signed POD
Commit the local proof, close the job where eligible and trigger downstream actions.
Exact navigationPublic POD page → Submit
What this guide covers
Commit the local proof, close the job where eligible and trigger downstream actions. 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
- Verify signer, signature, snapshot, condition and notes.
- Submit.
- Confirm signed time.
- Open the staff job and verify completion, released resources, history, audit, invoice/journal and provider submission status.
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 submission is accepted only while the note is open and unexpired.
Expected result and verification
- Delivery note becomes signed.
- Signer, IP (max 64), user agent (max 500), timestamps, paths and hashes are stored.
- The job is completed if it is not already closed and evidence satisfies the model.
- Resources are released and accounting/provider workflows run.
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.