Recipient decision after the stop
Delivery acceptance form for clear decisions
Separate “the driver completed the stop” from “the recipient accepted the goods.” Keep inspected quantity, condition, comments and the next action attached to the shipment.
Use this form when acceptance is a real business decision; a simple doorstep delivery may need only lightweight proof.
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
Two outcomes
Do not let delivery completion overwrite acceptance
The records answer different questions.
Proof of delivery answers
- Did the driver reach the destination?
- What evidence was captured?
- What quantity did the driver report?
- When and where was completion recorded?
Acceptance answers
- What did the recipient inspect?
- What quantity and condition are accepted?
- Is there a shortage, damage or refusal?
- What return, replacement or claim follows?
Decision model
Give partial acceptance a real path
Binary accept/reject forces teams to hide mixed outcomes.
| Outcome | Record | Next step |
|---|---|---|
| Accepted | Accepted quantity and recipient confirmation | Close when proof is complete |
| Partially accepted | Accepted and disputed quantity with reason | Open shortage/damage resolution |
| Conditionally accepted | Condition, reservation and required action | Track corrective action to verification |
| Rejected | Reason, evidence and custody state | Create return pickup or hold instruction |
Follow-through
Connect acceptance to the team that must respond
The form is not finished when the signature is captured.
Customer service
See recipient comments, promise risk and communication owner.
Logistics
See return pickup, redelivery or carrier evidence required.
Quality or supplier team
See condition evidence, lot/item context and disposition when relevant.
Acceptance design
Give every decision enough evidence and a visible consequence
A recipient should understand what is being accepted, while internal teams should immediately see what the decision changes in delivery, return and customer work. Agree who may record the decision, when an office review is required and which downstream record receives the result. That avoids a signature becoming an isolated image with no operational effect.
State the inspection scope
Show the shipment, item or package references, expected quantity and the condition criteria the recipient is being asked to confirm. Do not ask for a generic signature with no clear subject.
Support mixed outcomes
Capture accepted, disputed and rejected quantities separately. Partial acceptance should preserve successful delivery evidence while opening the shortage, damage, replacement or return action for the unresolved portion.
Explain the next step
Tell the recipient and operations team whether the result closes delivery, awaits review, creates a return pickup or requires a corrective action. Avoid a confirmation screen that reveals nothing about follow-up.
Verify conditional closure
When acceptance depends on replacement, documentation or repair, keep the condition open with an owner and due date. Close it only when the agreed action and evidence have been reviewed.
Rollout decision
Keep receipt separate from the claim or replacement decision
The recipient may accept some goods while disputing quantity, condition or documentation. Preserve accepted, disputed and rejected amounts separately, then connect the unresolved portion to return, replacement, claim or corrective work. The acceptance record should show what closes immediately and what still needs a verified follow-up.
Questions before rollout
Delivery acceptance form FAQ
Why separate delivery acceptance from proof of delivery?
Proof records the delivery event and evidence. Acceptance records the recipient’s inspection and decision. They may happen together, but separating them prevents a completed stop from hiding a shortage, damage or refusal.
Can the form record partial acceptance?
Yes. Keep delivered, accepted and disputed quantities separately and require a reason and next action for the difference.
Who should approve a rejected delivery?
That depends on the process. Logistics may own return movement, customer service the promise, and quality or procurement the disposition. Configure an explicit owner and review step.
When is a separate acceptance form unnecessary?
For low-risk deliveries where the required proof itself constitutes acceptance, use a shorter POD flow and avoid duplicate data entry.
What should happen after conditional acceptance?
Create a specific corrective action, owner and due date while preserving the accepted and disputed quantities. Close the condition only after the recipient or authorized reviewer verifies the agreed response.
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.