Coordinating a Delivery Handoff When the Recipient Cannot Be Reached

Published November 3, 2026

A delivery driver who cannot reach the recipient is not dealing with a simple no-answer call. The order may be in transit, the product may be temperature-sensitive, and the customer may be waiting at a different entrance or using a phone that has lost service. The dispensary needs a routine that protects the product, gives the customer a clear next step, and leaves a record that explains why the handoff did not happen. The store's written delivery policy should be the first reference when the usual contact path does not work.

Define the handoff moment

The handoff begins when the driver arrives at the approved delivery location and attempts contact through the permitted channel. It ends when the product is transferred to the verified recipient or returned through the approved path. Everything between those points should be recorded as a sequence rather than a single status. That distinction helps the store distinguish a late arrival from a failed contact or an identity problem.

Write the approved contact attempts in advance. The driver should know how many attempts to make, how long to wait, and which alternative channel is permitted. The customer should know what to expect if they miss the driver. A routine that depends on the driver's personal phone or an informal text message is difficult to review and may not meet the store's privacy expectations.

Capture the first failed contact

Record the time, the channel, the number or address used, and the result. A call that rings without an answer is different from a number that is disconnected or a recipient who asks the driver to leave the package unattended. Preserve the customer's own words when they are available. The record should not convert a technical failure into a claim about the customer's intent.

If the driver reaches the wrong person, stop and verify before sharing order details. The store's approved identity process applies at the door as well as at the counter. Record that verification was attempted and what happened. Do not leave product with a neighbor or a building employee unless the written delivery policy explicitly allows it and the customer has approved that path.

Use approved alternatives, not improvisation

The alternative may be a second call, a message through the store's approved system, a brief wait, or a return to the store. The driver should not invent a new meeting point or ask the customer to meet at an unapproved location. If the customer requests a change, route the request to the dispatcher or manager who can confirm whether it is permitted. The answer should be recorded with the time and the person who approved it.

Weather, traffic, and building access can complicate the best plan. The routine should say what the driver may do when conditions change and when the decision must go back to the store. A driver who feels pressured to complete the delivery may take a risk that the store would not approve. Give the driver a clear stop condition and a way to reach a human quickly.

Keep the order state honest

Use states that describe what actually happened. An order is not delivered because the driver arrived, and it is not cancelled because one call failed. Possible states include en route, at location, contact attempted, awaiting customer response, return in progress, returned, and closed with a documented outcome. Each state should have an owner and a time. The customer-facing message should match the internal state without exposing details the customer does not need.

If the order will be returned, tell the customer what happens next and who will contact them. If a refund or a reschedule is possible, say that it is under review rather than promising the outcome. The driver may not have the authority to approve a refund, and the customer should not be told otherwise at the door. Consistent language protects the store from a second dispute after the delivery ends.

Return the product through the approved path

The return is part of the delivery record. Record the time the product re-enters the store, the condition check, the person who accepted it, and the package identifiers. If the product cannot be returned to saleable inventory, document the reason and route it to the authorized owner. Do not put a returned package back on the shelf because the seal looks intact. The store's written policy and applicable rules govern that decision.

Reconcile the delivery record with the cash and order records before closing the case. A payment captured for an undelivered order needs a documented next step, even when the resolution is a future delivery. The person closing the case should be able to see the customer communication, the product state, and the financial state together. Otherwise the store may resolve one part and leave another part open.

Record the customer explanation without judging it

Customers may say they were home, that the building intercom was broken, or that they never received a call. Record the explanation as reported and compare it with the attempt log. Do not label the customer as unreliable or the driver as negligent based on one account. The review can identify a pattern across attempts, but the individual case should preserve uncertainty until the evidence supports a conclusion.

Review delivery exceptions weekly

Review a sample of failed handoffs, including cases that were later delivered and cases that ended in a return. Check whether the contact attempts followed policy, whether the customer received a clear next step, whether the product state was accurate, and whether the financial record was reconciled. Look for repeated causes such as a building access problem, a phone-number quality issue, or a scheduling window that is too narrow. The review should record the evidence gap rather than treating a missing note as proof that an attempt did not happen.

Close with a complete customer promise

The final record should show what the customer was told, what the store did with the product, and what happens next. If the case is closed without a delivery, the reason should be visible without exposing unnecessary personal detail. If the customer receives a replacement or a refund, the record should connect that outcome to the original order. The customer should not have to explain the same failed handoff to three different people.

A dependable delivery operation is built on small, unglamorous controls. The driver has a script and a stop condition, the dispatcher has a decision path, the customer has a clear next step, and the store has a record that matches reality. That is what makes a missed handoff a manageable exception instead of a dispute that lingers for weeks. That routine is tested by the exceptions it can explain, not by the smooth deliveries it never has to discuss.

Sources

• Virginia Cannabis Control Authority
• U.S. Small Business Administration, manage your business
• NIST Privacy Framework

Confirm current Virginia requirements and your own written operating procedure before changing a workflow. This guide is operational context rather than legal advice. Keep the approved policy version beside the routine so staff can see which rule applies. Review the routine after any change in the underlying requirement.