1. Last-mile Delivery Platform
  2. Features
  3. Delivery and custody
Feature · Delivery and custody

Delivery and custody

Record recipient handover and keep a human decision between submission and completion.

OverviewEvidence Attachments
Last-mile Delivery Platform · Delivery and custody

Evidence Attachments

Record attachments

New
ParentTitleEvidence typeVisibilityUploaded atUploaded by
LDS-99524Internal ra-592ET-646Internal12 Oct
LDS-17311Shared ra-228ET-415Shared08 Oct
LDS-74803Internal ra-939ET-857Internal12 Oct
LDS-89805Shared ra-484ET-119Shared27 Oct
LDS-31145Internal ra-978ET-382Internal17 Oct
6 of 6 records
Internal ra-592Record attachments · RA-89371
Internal
ParentLDS-99524
Evidence typeET-646
Uploaded at12 Oct
Example screen with sample data

What you can do

Close a stop with evidence

A delivery stop belongs to a load and an organization. It can name the driver and recipient, package count, address, handover time and proof reference. A signature file or delivery photo can add evidence. Its status distinguishes draft, submitted, approved, rejected and completed work. The receiving handoff is a decision point: submission places the record before a human reviewer, and approval or rejection is recorded separately from a driver’s completion claim.

The ordered load stops provide the trip context. Before a delivery is closed, the team checks the unique earliest visit and verifies that its arrival and departure were recorded. The completed delivery stop then connects the recipient handover with the parent load. A load’s actual delivery time lets Dispatcher compare the result with the original promise.

How the work is organized

  • Submit. Driver records the recipient and custody details before seeking a decision.
  • Decide. Warehouse Handoff Reviewer checks the handover and records approval or rejection.
  • Complete. Driver records handover time and at least one proof source for a completed stop.

What to agree during setup

Define what a valid proof reference means and when a signature or photo is appropriate. Agree who can see internal evidence and who may receive shared attachments. Set a rule for recording recipient exceptions, such as refusal or a different person accepting the goods, in the handover record and reviewer reason. The person who reviews custody should know whether package count is reconciled against the dispatch record.

Agree how to correct a rejected handoff. A revised stop should be resubmitted for a new decision rather than silently treated as approved. Decide whether a late delivery requires a separate exception review and who enters the final actual delivery time on the load. These responsibilities prevent a proof file from being mistaken for an authorized closeout.

Check the handoff on an actual case

A driver arrives at the final address with several packages. They record the recipient, handover time and a proof reference, then submit the stop. Warehouse Handoff Reviewer checks the load, package count and custody evidence. If the handoff is accepted, the reviewer approves it and records the decision time. The completion check confirms handover time, proof and the unique earliest load stop’s visit times. Dispatcher then checks the load’s actual delivery time before closing the load.

Try the same case without a handover time or with no proof reference, signature or photo. The stop should remain open for correction. Try submitting a record with an unclear recipient; the reviewer can reject it with a reason. The team can then ask for corrected evidence while preserving the prior decision.

What your team sees

  • Custody Board by Status — Delivery stops grouped by their handoff status.
  • Loading Handoffs Default List — Submitted handoffs for the human reviewer.
  • Evidence Attachments — Files linked to the parent load with visibility and evidence type.

Follow the work through

Read stop to proof and delivery to review. The data model shows where the evidence remains attached.

What it keeps track of

Data model
Delivery stops
Delivery stop records supporting the complete-a-delivery-stop operation with proof and recipient exception evidence
Load stops
Ordered pickup and delivery stops within a load with appointment windows
Loads
Freight loads from pickup to delivery with promised windows, freight value and lifecycle
Record attachments
Evidence files attached to loads with visibility and evidence type
Review decisions
Independent approval, rejection or return decisions on a source revision

Who uses it

Permissions
Driver
Records the handover.
Warehouse Handoff Reviewer
Approves or rejects custody.
Dispatcher
Checks load closure.
Operations Reviewer
Investigates disputed evidence.

Set up Last-mile Delivery Platform your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started