Delivery Research

Measuring delivery reschedule causes and completion

A method for measuring why cannabis deliveries are rescheduled and whether the new window is actually completed, using one controlled reason field and a thread-level record.

Measuring delivery reschedule causes and completion

Key takeaways

  • Measure the reschedule at the stop level, not the route level, so one delayed stop does not hide the rest.
  • One controlled reason field makes cause patterns comparable across weeks.
  • A reschedule is complete only when the new window is met or the order is formally cancelled.
  • Report customer contact attempts separately from the reschedule decision.

Question and scope

This review asks how a dispensary can measure why cannabis deliveries are rescheduled and whether the new window is actually completed. The unit is one delivery stop that moves from its original window to a later window or another day. The review examines the original window, the reason, the customer contact, the new window, the product hold, and the final order status. It does not measure driver performance or customer satisfaction.

Set the scope to one store, one delivery area, and a fixed period. Record the dispatch rules, the service windows, and the reasons the store allows a reschedule. If the store changed its routing software or added a delivery partner inside the window, separate the periods. A new reason-code list can change the apparent cause mix without changing the underlying operations.

What the sources establish

The Virginia Cannabis Control Authority provides the regulatory setting for licensed delivery and product handling. NIST guidance on incident records supports a consistent timestamp and a named owner for each change. The Federal Trade Commission's consumer-protection guidance supports clear communication about a change to a paid service. None of these sources provides a local reschedule benchmark.

The store therefore needs its own baseline. Public sources can explain why the record should show the original promise, the change, and the customer's confirmation. They cannot show whether a particular reschedule was avoidable. The review should report the local evidence and avoid attributing every delay to the driver or the customer. A baseline from one delivery area is more useful than a rate borrowed from a different route mix.

Definitions and measures

Define a reschedule as a change to the delivery window after the order has been loaded or after the customer has confirmed the original window. Define a completion as a delivery made inside the new window, not merely a later delivery. Define a cancellation as an order closed without delivery and handled under the store's refund or credit rule. Define a contact attempt as a documented call, text, or email to the customer about the change.

Measure the number of stops, the number rescheduled, the number completed in the new window, the number cancelled, and the number still open at the review date. Report the original window, the new window, and the elapsed time between them. Also report the number of contact attempts before the customer confirmed the change. A reschedule without a confirmed contact is a different risk from one the customer accepted.

Sampling and collection

Sample rescheduled stops rather than routes, then collect the order record, the manifest, the dispatch note, the customer communication, and the final delivery status. Include stops that were completed, cancelled, and still open. Stratify by reason, route, and day of week. Record the sampling rule and the observation window before pulling the data. Keep the stop identifier in the table so another analyst can reproduce the selection.

Collect the original window, the time the reschedule was approved, the new window, the driver or vehicle if it changed, and the payment status. If the store uses a delivery partner, collect the partner's status record as well. Mask customer names and addresses in the analysis table. A stop with no reason code is an exception that should be reported, not dropped.

Analysis and reporting

Report the reschedule rate by reason and by route, then show the completion rate for each reason. A high reschedule rate on one route may reflect density or parking, while a high rate across all routes may reflect a notification problem. Show the median and the long tail of the gap between the original and new windows. An average can hide a small number of very long delays.

Inspect the cancelled and still-open stops separately from the completed ones. A reschedule that ends in cancellation is not a successful save, even if the customer was contacted. Report the number of stops where the customer was not reached before the window changed. That count is a service and recordkeeping signal that a simple completion rate will miss.

Coding the reschedule reason

Code the reschedule reason from the dispatch note, not from the customer's later description alone. Use one primary reason and allow a secondary note only when two causes genuinely interacted, such as a vehicle fault during a weather delay. A single primary code keeps the weekly comparison stable. A long free-text field makes two similar events look unrelated.

Check the reason against the time the decision was made. A customer-unavailable code entered before the driver reached the address may actually describe a phone contact failure. A route-delay code entered after the vehicle returned may describe a maintenance issue. The analyst should read the sequence of timestamps before accepting the label at face value. A note written later should be labeled as a reconstruction rather than treated as a live entry.

Comparing routes fairly

Compare reschedule rates across routes with the number of stops and the route length beside each rate. A route with ten stops and one reschedule is not the same as a route with three stops and one reschedule. Report the denominator and the time window so the reader can judge the comparison. A simple percentage without context invites the wrong conclusion.

Check whether the route uses a store vehicle or a delivery partner, because the two have different control points. A partner route may have less flexibility to rebook, while a store route may have more ability to shift a stop to the next day. Report the completion rate by route type. Do not rank a driver on a route that was designed with an unrealistic window.

Limits and sources of error

The order record can show what was promised and what happened, but it cannot prove why a customer was unavailable or whether a road delay was avoidable. A driver's note may be written after the fact and may omit a detail the customer would remember differently. The review should state those limits rather than treating one account as complete. A separate review should test those causes rather than stretching one note beyond its design.

The new window may also be recorded in a different time zone or rounded to the nearest half hour. Keep the timestamp method stable and report any change. If the store uses a delivery partner, the partner's status may update later than the store's own record. Do not compare completion rates across systems without checking how each one defines a delivered order.

Review and next action

Choose one change: add a pre-load confirmation call, require a reason code before the manifest changes, set a minimum rebooking window, or review open reschedules at the end of each day. Assign the owner and the next sample date. Test the change on one route before applying it to the whole delivery area. Write the chosen change into the dispatch checklist so the next shift sees it.

Close the review when the store accepts the result and schedules the next check. Report the remaining uncertainty beside the reschedule counts. The post-load reschedule routine describes the dispatch practice this review measures. Use the result to improve the route and the customer communication, not to rank individual drivers from a single week. Report the remaining uncertainty beside the reschedule counts rather than in a separate memo.

Sources

The sources below support the regulatory, records, and consumer-communication context for this review. Keep the citation list visible beside the analysis table during the review. They do not measure this dispensary, and no source is presented as a local benchmark. Each link should be checked for its date and scope before reuse. The operational finding comes only from the store records described in the method.

This article describes a measurement method rather than legal or compliance advice. Confirm current requirements with the applicable authority and qualified advisers. Keep the local evidence separate from those requirements. Record the review date and the owner who accepted the interpretation. Store the signed scope note with the review file, and give the owner a copy before the next sample begins.

Reviewed by the DispensaryVA editorial team on 2026-11-06.