A custody checkpoint between teams
Shipment handoff checklist for clear custody
Use the handoff to make the next owner, transferred quantity, condition and unresolved exceptions explicit—whether the change is warehouse to carrier, carrier to driver or driver to recipient.
The checklist supports evidence and linked shipment history; it is not a bill of lading or regulatory document by itself.
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
Handoff sequence
Confirm custody before the vehicle or goods move on
A handoff is complete only when both context and exception are visible.
- 01
Identify the shipment
Match the shipment, load, package or stop reference.
- 02
Confirm the parties
Name the releasing and receiving organizations or people.
- 03
Count and inspect
Record quantity, seals or identifiers, condition and any discrepancy.
- 04
Transfer documents and instructions
Keep handling, appointment and proof requirements with the shipment.
- 05
Accept or open an exception
Record time and outcome; do not bury a shortage or damage note in a successful handoff.
Control points
Use one checklist across different custody changes
The fields stay familiar while the operating question changes.
| Handoff | Critical question | Typical exception |
|---|---|---|
| Warehouse to carrier | Is the planned load complete and ready? | Package missing, seal mismatch or late release |
| Carrier to driver | Does the driver have the right goods and instructions? | Wrong vehicle, missing document or capacity issue |
| Driver to recipient | What quantity and condition were accepted? | Short, damaged, refused or unattended delivery |
| Recipient to return carrier | What is being returned and why? | Wrong item, packaging difference or missing authorization |
Audit trail
Make the record useful after the handoff
A signature without context rarely resolves a later dispute.
Stable identifiers
Keep shipment, package, seal and related-order references.
Two moments in time
Record planned handoff and actual acceptance when timing matters.
Exception link
Create an owned case with severity, containment and due date instead of a free-text note.
Rollout decisions
Adapt one custody model to the handoffs your network actually uses
The same App can support several checkpoints, but each checkpoint needs a clear releasing role, receiving role, evidence standard and exception owner.
Warehouse release
Confirm the planned load, package or pallet identifiers, quantity, seals, documents and carrier. A shortage or damaged package should stop clean acceptance and create an accountable exception before departure.
Carrier or driver transfer
Show the new custodian, vehicle or route context, handling instructions and actual transfer time. Keep the previous custodian and any unresolved discrepancy visible after the assignment changes.
Recipient handoff
Connect quantity and condition inspection to recipient acceptance, partial acceptance or refusal. The final delivery event should link to proof and any return, replacement or customer-resolution work instead of hiding it.
Return custody
Preserve the original delivery and authorization while capturing the item, condition, reason and receiving destination. Returned goods need a traceable next owner until receiving or disposition is confirmed.
Rollout decision
Make the next custodian accept a specific condition
A handoff should identify the shipment or packages, transferred quantity, observed condition, releasing party, receiving party and actual time. If either party records a discrepancy, keep custody visible while opening the exact containment and review work. Do not let a generic signature hide a shortage or damaged seal.
Keep the custody event visible in tracking →Define the evidence required at the final handoff →
Questions before rollout
Shipment handoff checklist FAQ
What should a shipment handoff checklist include?
Include shipment and package references, releasing and receiving parties, planned and actual time, quantity, condition, required documents, handling instructions, acceptance and any exception.
Is a handoff checklist the same as proof of delivery?
No. A handoff can occur between warehouse, carrier and driver before final delivery. Proof of delivery records completion at the recipient or agreed destination.
How should a discrepancy be recorded?
Keep expected and transferred quantities, condition evidence, reason, owner and containment together; open an exception rather than completing a clean handoff.
Can the checklist support scans?
Yes, barcode or QR inputs can be configured where scanning helps confirm package or asset identity. Test the exact device and code format.
Who should be able to complete a custody handoff?
Limit completion to the releasing and receiving roles defined by the process, and test their actual permissions. Supervisors should see unresolved discrepancies without turning every handoff into a separate approval.
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.