- Owner
- Delivery Operations Manager
- Effective date
- September 15, 2026
- Review cycle
- Every 12 months
1.Purpose
To complete the final delivery stop safely and consistently, giving customers a good handoff experience while capturing the documentation needed to close out the delivery.
2.Scope
Applies to the driver's actions at each delivery stop, from arrival to departure. Route planning and dispatch tracking are covered by separate SOPs.
Definitions
- Delivery window
- The time range promised to the customer for their delivery to arrive.
- Contactless delivery
- A delivery method where the driver leaves the package without requiring an in-person signature or handoff.
- Failed delivery attempt
- A delivery stop where the package could not be delivered, such as no one available to receive it or an inaccessible address.
- Redelivery
- A scheduled second attempt to deliver a package after a failed first attempt.
3.Responsibilities
- Driver
- Navigates to each stop, completes the handoff or contactless delivery, and captures proof of delivery.
- Delivery Operations Manager
- Sets delivery standards, reviews exception patterns, and approves redelivery scheduling.
- Customer Service Representative
- Handles customer inquiries about delivery status and coordinates redelivery or pickup arrangements.
- Dispatcher
- Monitors delivery progress against windows and reassigns stops when a driver falls behind.
RACI matrix
| Activity | Driver | Delivery Operations Manager | Customer Service Representative | Dispatcher |
|---|---|---|---|---|
| Arrive and park safely at the stop | R/A | A | - | I |
| Complete customer handoff | R/A | A | - | - |
| Handle a failed delivery attempt | R | A | C | C |
| Schedule redelivery | I | A | R | C |
| Respond to customer delivery inquiry | C | A | R | I |
R = Responsible, A = Accountable, C = Consulted, I = Informed
4.Materials and PPE
Materials, tools and systems
- โDelivery app or handheld scanner
- โPackage manifest for the route
- โPhoto capture device for proof of delivery
- โDoor tag or attempted-delivery notice
- โHand truck or dolly
- โCustomer signature pad or app
Personal protective equipment
- โSafety shoes
- โHigh-visibility vest in loading areas
- โWeather-appropriate outerwear
5.Procedure
- 5.1
Confirm the next stop details
DriverBefore leaving the previous stop, check the app or manifest for the next address, delivery window, package count and any customer instructions or access codes.
- 5.2
Park safely at the delivery location
DriverPark in a legal, safe location as close to the delivery point as possible, using hazard lights if needed, and set the parking brake before leaving the vehicle.
- 5.3
Locate and verify the address
DriverConfirm the unit or suite number matches the delivery address before approaching, especially at multi-unit buildings, to avoid delivering to the wrong door.
Checkpoint: The address and unit number are visually confirmed against the package label before the package leaves the vehicle.
- 5.4
Attempt customer contact if required
DriverFor deliveries requiring a signature or age verification, knock or ring the doorbell and wait a reasonable time for a response before considering the attempt failed.
- 5.5
Complete the handoff or contactless delivery
DriverFor an in-person handoff, verify the recipient if required and capture a signature; for contactless delivery, place the package in a safe, dry, hidden-from-street location per the customer's instructions.
Warning: Never leave a package in a location that blocks an exit, ramp, or is clearly visible and accessible from the street when a hidden option is available.
- 5.6
Capture proof of delivery
DriverTake a clear photo showing the package at the delivery location and the address or unit number visible in frame, and confirm it uploads successfully before leaving.
Checkpoint: A proof-of-delivery photo or signature is captured and confirmed uploaded before the driver leaves the stop.
- 5.7
Mark the stop complete
DriverMark the delivery as complete in the app with the timestamp, method (handoff, contactless, or locker) and any delivery notes.
- 5.8
Handle a failed delivery attempt
DriverIf no one is available for a required handoff or the location is inaccessible, leave a door tag or notice with instructions, mark the attempt as failed with a reason, and photograph the location.
- 5.9
Report an access or safety issue
DriverReport a locked gate, aggressive animal, unsafe property condition or other access barrier to dispatch immediately so future attempts can be planned around it.
Warning: Never enter a property past a closed gate, fence or posted warning, or attempt to distract or approach an animal to complete a delivery.
- 5.10
Schedule a redelivery
Customer Service RepresentativeFor a failed attempt, schedule a redelivery date with the customer or confirm the pickup location option, and update the delivery record with the new plan.
- 5.11
Respond to a delivery status inquiry
Customer Service RepresentativeWhen a customer contacts support about a delivery, check the app for the delivery timestamp, photo and driver notes before responding with accurate status.
- 5.12
Review delivery exception trends
Delivery Operations ManagerReview failed delivery attempts and customer complaints weekly by area or building to identify recurring access issues and adjust delivery instructions.
6.Quality checks
- โEvery completed stop has a proof-of-delivery photo or signature confirmed uploaded.
- โAddress and unit number are verified against the package label before dropping off.
- โFailed delivery attempts include a documented reason and a photo of the location.
- โRedelivery is scheduled within the customer's expected timeframe.
7.Records
- โProof-of-delivery photos and signatures
- โFailed delivery attempt log
- โRedelivery scheduling records
- โDelivery exception trend report
8.KPIs
- โFirst-attempt delivery success rate
- โPercentage of stops with confirmed proof of delivery
- โAverage time per stop
- โCustomer complaints per thousand deliveries
9.Common mistakes
- โLeaving a contactless delivery in plain view of the street when a hidden spot was available.
- โMarking a stop complete before the proof-of-delivery photo finishes uploading.
- โDelivering to the wrong unit at a multi-unit address without checking the label.
- โNot documenting the reason for a failed delivery attempt.
10.Revision history
| Revision | Date | Description | Reviewed by |
|---|---|---|---|
| 1.0 | September 15, 2026 | Initial release | Ilia Pirozhenko |
This is a template. Adapt it to your organization, equipment and local regulations before use.