Proof of delivery

Proof of delivery is captured against a task, not against a stop or a trip. That is the fact everything else follows from: a stop with three tasks can require a photo on one, a signature on another and nothing on the third, and a standalone task with no trip at all captures proof the same way a delivery on a busy route does.

The task form asks for a single required proof, or none. The record underneath holds a list, so a task created through the API can require several — and when it does, the driver app steps through them one at a time with a "Proof 1 of 3" counter rather than presenting them all at once.

A free-text notes proof also exists on older tasks. It is no longer offered when you build a task, but tasks that already carry it still behave normally, and drivers can always add notes to a delivery whether or not anything required them.

Completing a task with required proof opens a full-screen capture flow. Each required proof is one step; the driver cannot skip ahead, and cancelling backs out without completing the task. Only when the last step is collected does anything get sent: the photo and signature are uploaded, the PIN is verified, the recipient name and notes are saved, and the task is transitioned to completed.

That order matters when something goes wrong. If the upload fails halfway, the driver gets a retry screen rather than a lost capture, and retrying does not redo the steps that already succeeded — a photo is never uploaded twice and a PIN attempt is never burned twice.

A task refuses to move to completed while any required proof is missing, and the error names which one. The same check also covers required checklist items. There are exactly two ways past it:

• Capture the proof. The normal path.
• Waive the requirement. An admin can waive one specific proof method on one specific task, with a reason. The waiver is recorded on the trip’s timeline as a POD waiver, and only that method is let through.

A method can only be waived if the task actually required it, and the reason is mandatory — a waiver with no explanation is refused. If neither path fits, the honest answer is usually to fail the task with a reason rather than force it through.

For a task on a trip, every proof action writes an event onto that trip’s timeline: a photo uploaded, a signature captured, a PIN verified, a PIN lockout, a requirement waived. That timeline is the record to reach for in a dispute, because it is ordered and attributed rather than reconstructed.

A standalone task has no trip and therefore no timeline. Its proof is still captured and stored exactly the same way — the difference is only where the narrative of the day is kept.