Proof of delivery

A Delivered tracking event starts Pod Collection. The workflow creates a proof-of-delivery record keyed on the shipment and delivery time, advances the shipment to Delivered and fills actual delivery time only when it is empty. This provides a delivery record for Dispatcher/Ops to complete and review. A Delivered shipment can still have a Pending proof-of-delivery record; arrival and accepted evidence are separate states.

Delivery proof records contain recipient name, recipient signature link, photo link, bill-of-lading image link, delivery notes and exception flag. These fields let the team retain who received the goods and where supporting documents can be found. Choose the document upload and storage connection during setup, then check that the operational reviewer can open the original files.

• Create the event-linked record. Pod Collection keys the record on the shipment and delivery date so a replayed event cannot add another copy of the same delivery evidence. It derives the recipient from the available carrier notes or payload. Dispatcher/Ops must review that value before treating it as confirmed recipient information.
• Complete the evidence. Dispatcher/Ops supplies the missing recipient and document links through authorized record editing. The review uses Pending, Captured and Verified to separate collection from acceptance. Before accepting Captured evidence, open the signature or image and check its shipment identity and delivered quantity.
• Investigate an exception. Exception flag and delivery notes retain damage or shortage context. Disputed is an available proof status. Review the carrier’s supporting information and connect the operational issue through the shipment; Dispatcher/Ops records the corresponding operational follow-up when the receiving evidence identifies a problem.

Choose which delivery documents are required for the pilot’s freight modes and consignees. Decide where the originals remain, who can upload replacements and how a document link is retained when an external store changes access. A photo link with an unreadable target is still incomplete evidence.

Confirm the editor and verifier accounts. Dispatcher/Ops has record management access to proof records. Receiving / Customer is read-only and can inspect the evidence, but leaves the verification decision to Dispatcher/Ops. Agree how customer feedback reaches Dispatcher/Ops during setup and rehearse the handoff. Keep the business’s required verification decision distinct from the workflow that simply creates the Pending record.

Take a delivered pallet shipment with a carrier-provided recipient name and a signed document. Enter the Delivered event, inspect the created proof record and verify actual delivery time. Replay the same event and confirm that the same shipment/date evidence is retained without another proof record or overwritten date.

Dispatcher/Ops opens the document links and checks the recipient and shipment identifiers before changing Pending to Captured. A reviewer then evaluates the captured evidence and records Verified or follows up on a dispute. Rehearse an unreadable signature link and a damage note; neither should be accepted merely because the shipment already reads Delivered. Receiving / Customer should be able to read permitted information while an edit attempt fails.

• POD Capture Worklist — Pending proof records with recipient and document fields ready for completion.
• POD Verification Review — Captured evidence waiting for a reviewer to check the recipient and delivery documents.
• Delivered Shipments — Delivery dates and carrier details for comparing shipment arrival with its proof record.

Rehearse tracking to delivery evidence and review the related freight invoice.