PROOF / COD GUIDE
Proof of delivery and COD tracking for courier teams
A delivery is not fully closed when a driver reaches the address. The team may still need proof, an exception decision, a customer update or a cash handoff. A shared operational view makes those next steps easier to see.
Capture proof where the stop happens
Proof of delivery should be connected to the package and route context. The approved Dispatchly scope includes proof of delivery; confirm the exact driver workflow and the photo or signature surfaces for your operation.
Make failed stops actionable
When a delivery cannot be completed, keep the reason and next action visible. Customer problem tracking helps the dispatcher distinguish a reattempt, an address correction, an access issue or another operational question.
Keep COD in the closeout conversation
COD tracking gives the owner a place to review cash-related handoffs alongside the delivery work. It should be part of the route and closeout rhythm, not a separate list that is checked only after the day is over.
Use margin to understand the job
Margin per delivery helps compare what a delivery creates with what it costs to run. Keep any example values fictional and treat the calculation as a decision aid, not a guaranteed savings claim.
Confirm the evidence you need
Before a rollout, agree which proof, customer problem, COD and role states matter to the team. Start with one route, test the handoffs, and then decide whether the workflow is ready to expand.
See the workflow on one route.
Dispatchly is early-access software for small courier fleets. Bring one route or one operational problem.
Bring us your route