Proof of delivery: photos, statuses, notes
Where driver evidence lives, how failure reasons work, and the difference between what the office attaches and what the driver captures.
"Where's my package?" stops being a debate when every stop carries its own evidence. In Routerra Teams, proof of delivery is three things together: the status the driver set, the photos and files they captured, and their notes.
Where to find it
Open any stop and check its Attachments panel. Files are grouped by origin, and the grouping matters:
| Group | Who adds it | What it is |
|---|---|---|
| Proof of delivery | The driver, from the app | Delivery evidence: photos of the handoff or drop spot |
| Added by office | The office | Gate codes, entrance photos — drivers see these read-only |
| From address book | Saved on the address | Files that appear on every stop at that location |
Photos preview in a lightbox; PDFs and documents can be downloaded.
Delivered, or not — with a reason
Drivers don't just tick boxes. A successful stop is Delivered, with optional photos and a note. A failed one is skipped with a structured reason — Customer not available, Wrong address, Customer refused, Business closed, Access restricted, or Other reason — plus whatever photos explain it.
Failed stops surface immediately in the dashboard's Needs attention, so the decision (retry, reschedule, refund) happens while the driver is still in the field, not at 6 pm from a spreadsheet.
Offline capture, verified sync
Proof works in dead zones: photos, statuses, and notes are stored on the driver's phone and sync automatically when signal returns. A photo taken in an underground parking garage at 10:03 arrives with its real capture context once the driver resurfaces — nothing is lost, nothing needs re-doing.
Closing the loop with customers
Pair proof with per-stop customer notifications: an email or SMS on Delivered ("left at your door, photo attached to our records") or on Not Delivered ("we couldn't reach you — here's what happens next"). Notification setup has its own guide (coming soon); it uses the same statuses drivers already set, so there's nothing extra to do per delivery.