Electronic proof tied to the shipment record
Proof of delivery form for every outcome
Capture the minimum evidence needed to confirm what arrived, who accepted it and what must happen next—without forcing every delivery into a successful outcome.
The mobile view uses a phone presentation and supports configurable evidence fields, including barcode or QR-code inputs when required.
Free for up to five users. No credit card required.
Adapt fields, workflows, and dashboards without code. Explore 1,000+ app templates and use cases
Evidence design
Require proof according to the service—not one oversized form
Collect only the evidence needed to confirm completion or support a dispute.
| Evidence | Use it when | What it proves |
|---|---|---|
| Recipient name and signature | Named acceptance is required | Who accepted the delivery |
| Photo | Condition or placement matters | What was delivered or where it was left |
| Barcode or QR scan | Package/item identity must be checked | Which coded unit was handled |
| Timestamp and location | Stop timing or place is material | When and where completion was recorded |
| Quantity note | Partial delivery is possible | What was received versus expected |
Outcome path
Let the form end in more than “delivered”
The evidence should drive the correct next record.
- 01
Accepted
Required proof is complete and the recipient accepts the delivery.
- 02
Partial
Retain delivered quantity and open the remaining-quantity decision.
- 03
Exception review
Damage, shortage, missing proof or a disputed outcome requires office review.
- 04
Refused
Record the reason and evidence, then create or link the return movement.
Usability
Keep the mobile completion path short
Field order is part of data quality.
Show shipment context first
Driver and recipient should see the reference and location they are confirming.
Put required proof together
Place signature, photo, scan and quantity in the natural completion sequence.
Expose exceptions early
A driver should not fake a successful completion to reach a damage or refusal field.
Control before rollout
Make the proof useful without turning the stop into paperwork
Pilot the form with the people who will complete and investigate it. The fastest proof flow still needs enough context to withstand a quantity, condition or recipient dispute.
Define evidence by service
Document which delivery types require a signature, photo, barcode or QR scan, location, recipient name or quantity note. Avoid forcing low-risk stops to collect evidence that no downstream team uses.
Test accepted and failed outcomes
Run a clean completion, partial quantity, refused delivery, damaged condition, missing proof and offline or weak-network case. Each outcome should open the correct next action rather than falling back to free text.
Separate capture from acceptance
Let the driver submit field evidence while an authorized recipient or office role records acceptance where that distinction matters. Do not imply that a completed stop automatically closes a commercial dispute.
Retain the audit trail
Keep the original capture time, submitter, shipment reference and evidence. Corrections should be attributable and connected to the disputed record instead of silently replacing what was first submitted.
Rollout decision
Set evidence and retention rules before field rollout
Choose signature, photo, scan, location and recipient details according to the service promise and privacy need. Define who can view, correct and retain each item. Then test a clean delivery, partial quantity, refusal, offline interruption and disputed proof on the actual phone and network conditions used by drivers.
Questions before rollout
Proof of delivery form FAQ
What belongs on a proof of delivery form?
Include shipment reference, recipient, delivery location, delivered time, delivered quantity and the required evidence such as signature, photo, barcode/QR scan or note. Add an acceptance or exception outcome.
Is a signature always required?
No. The correct proof depends on service, contract, risk and privacy requirements. Some deliveries use photo, scan, geolocation or a recipient name instead.
Can the form handle partial delivery?
Yes. Keep expected and delivered quantities separate, retain evidence and open the remaining-quantity or return decision rather than marking the whole shipment complete.
Does Jodoo support mobile evidence capture?
The web App can present mobile forms and image upload, and configured workflows can use barcode or QR inputs. Test the target device, camera permissions, code format, network and retention requirements.
How should proof changes be audited?
Retain the original shipment and stop reference, capture time, submitter and evidence, then record any correction as a visible follow-up rather than silently replacing disputed proof.
Inspect the working product
Open the populated App behind this page
Review connected records, operating views, a real exception workflow and representative normal, at-risk, failed and completed delivery states.