Submit a signed POD

Commit the local proof, close the job where eligible and trigger downstream actions. 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.

What you’ll accomplish

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.

Follow these steps

1. Check signer, signature, snapshot, condition and notes.
2. Submit.
3. Verify signed time.
4. Go to the staff job and verify completion, released resources, history, audit, invoice/journal and provider submission status.

Fields and options to review

This action uses the values already stored on the selected source record. Review that record before continuing.

Rules the system enforces

• The submission is accepted only while the note is open and unexpired.

How to confirm it worked

• 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.

Continue with related guidance