Capture proof of delivery

Note

Your operator decides what proof each stop needs — you don't choose the capture types that show up. This article covers everything you might be asked for; any single stop usually only asks for a couple of these.

Most stops ask you to prove the work happened before you can complete them. What that proof looks like is set by your operator, stop by stop — the app simply shows you what a given stop needs, and your job is to capture it. This article walks through each kind of proof you might see, the two situations that change what's required on the fly, and how a capture gets saved once you've made it.

Photo

Tap Take Photo to open the camera and capture the package — either at pickup, to confirm what you're taking, or at drop-off, to confirm what you left. You can retake it before confirming if it doesn't come out clearly. Once it's accepted, you'll see a confirmation that the photo was captured.

Signature

Tap Signature to bring up a signing pad, and hand your phone to whoever's dropping off or receiving the package. The screen has a Sign here hint over the pad. Once a signature is drawn, confirm it to attach it to the stop.

Barcode scan

If a stop asks for a scan, open the scanner and point your camera at the item's barcode. A successful scan matches that item to what's expected at the stop and marks it handled — this usually happens alongside checking items off the item list, not as a separate step on its own.

Notes

Tap Notes any time you want to leave a written comment about a stop — this field is always there, whether or not the stop requires one. Use it to record anything worth flagging: something unusual about the drop-off, a detail for your operator, or context for a customer's request.

ID or age check

Some stops involve something age-restricted, and the app will ask you to confirm the recipient's identity before you can complete the delivery. You'll be walked through checking their ID and confirming their date of birth. You can't complete the stop until this check is done.

Parking bay or check-in

At stops that ask for it, you'll see a field asking you to log where you've parked — usually a parking spot or bay number. Enter it before moving on; some stops won't let you continue until you have.

Two situations that change what's required

Two things you might do at a drop-off shift what proof gets asked for, on the fly:

• Leave unattended — if no one's available to receive the package, check Leave unattended and pick a reason. Doing this makes the app require a delivery photo, as proof the package was left safely. This option isn't available at stops that require you to hand the package to someone in person.
• Other recipient — if you're handing the package to someone other than the named recipient, check Other recipient and enter their name. Doing this makes the app require an ID check on whoever actually took it, even if the stop wouldn't otherwise have asked for one.

Both are still proof of delivery — they just change what the app asks for based on how the drop-off actually went, rather than what was planned ahead of time.

How a capture gets saved

Once you've made a capture — a photo, a signature, a scan, a note, or a completed ID check — it's attached to that stop automatically; you don't need to do anything else with it. If you're offline when you capture something, it's held on your device and uploaded as soon as you're back online, so you can keep working through your stops without a connection.

Every piece of required proof has to be captured before Complete unlocks for that stop — see Run a stop, pickup to drop-off for how completion works, and Proof of delivery reference for a quick lookup of every capture type and when it's required.

Nash dispatches the work; the proof you capture confirms what you and your operator's fleet actually did in the field.