Customer Operations Research
Studying Customer Wait Time at Dispensary Intake
A study design for measuring the wait between a dispensary customer's arrival and the start of service, separating check-in, verification, queue, and handoff.
Key takeaways
- Measure arrival, check-in, verification, service start, and outcome separately.
- Report walkouts as an outcome, not as a missing timestamp.
- Keep the queue length and open station count beside each wait interval.
- Compare the same stages before and after one intake change.
Question and scope
This study asks how long a dispensary customer waits between arrival and the start of service, and where that time is spent. The unit is one customer visit tied to one arrival and one service start. The review separates check-in, identity and age verification, queue time, and handoff to the sales floor. It does not judge the quality of the product advice or the customer's purchase decision.
Set the scope to one store and a fixed period. Record the intake process, the verification method, the staffing model, and the service types included. If the store changes its check-in system or its queue layout during the window, separate the periods. A layout change can alter the wait more than a change in staff behavior. Name the busiest and quietest periods before sampling.
What the sources establish
The Virginia Cannabis Control Authority sets the licensed retail context for intake and identity verification but does not publish a local wait benchmark. NIST privacy guidance is relevant because the intake record contains identity and age information. GAO data-reliability guidance describes how to assess timestamps created for operations. The sources support a process review, not a customer-satisfaction score.
The sources do not establish an acceptable wait time or prove that a shorter wait improves the customer's experience. A fast intake can still feel rushed, and a longer wait can be handled well with clear communication. The study therefore measures the stages and the information given to the customer, not only the elapsed minutes. The customer's stated wait experience should be recorded separately from the timestamps.
Definitions and measures
Define arrival as the time the customer enters the queue or checks in. Define check-in as the completion of the store's initial intake step. Define verification as the completion of the identity and age check required by the store. Define service start as the time a budtender begins the customer interaction. Define outcome as a completed sale, a walkout, or a referral.
Measure the interval between arrival and check-in, check-in and verification, verification and service start, and service start and outcome. Record the queue length at arrival and the number of open service stations. Report the median, the interquartile range, and the longest waits. Keep the visit type and the customer's stated need beside each interval.
Record the number of customers ahead in the queue at arrival and the number of open service stations, because the same wait can mean different things under different load. A five-minute wait with one station open is not the same as a five-minute wait with four stations idle. The analysis should keep the load beside the interval. The load should be recorded at the same moment as the arrival, not estimated later.
Sampling and collection
Sample visits rather than customers. A customer may visit more than once with different needs. Include pickup customers, walk-in customers, and customers who arrived during a shift change. Record the time, the station count, and the staff role. A sample drawn only from quiet periods will understate the wait that most customers experience.
Collect the check-in log, the queue record, the verification timestamp, and the service-start record. Mask identity details that are not needed for the analysis. If a timestamp is missing, keep the visit and record the gap. Dropping the least documented visits would make the wait look shorter than it was.
Include visits during a shift change and during the last hour before closing, because those periods can produce a wait that an ordinary sample misses. Record the station count and the handoff time. The customer experience at closing deserves the same review as the midday rush. The closing period should be sampled deliberately rather than left to chance.
Calculating wait time
Calculate the total wait and each stage separately. A long verification step and a long queue after verification need different fixes. Report the share of the total spent in each stage. Do not combine the stages into one average without showing the components. A single number can hide the bottleneck.
Report the customers who left before service separately from those who waited. A walkout is an outcome, not a missing data point. If the store records a reason, keep it in the customer's words. Compare the walkout rate with the wait distribution to see whether long waits cluster around the same periods.
Report the visits that required a second verification step separately, because a repeat check can look like a queue delay when it is actually a document problem. The customer's experience still includes the extra time, but the fix belongs with the verification process. The report should name the cause rather than only the minutes. The extra verification should be attributed to the document process, not the queue.
Separating cause from delay
Classify each long wait by stage and cause. A delay may come from a verification question, a queue surge, a staffing gap, a system outage, or a customer who needed more time. These causes require different fixes. A single wait percentage cannot tell the manager whether to add a station, change the check-in form, or adjust the schedule.
Review a small number of long waits in detail. Look for a customer who was checked in but not verified, verified but not assigned, or assigned but not served. Check whether the customer was told about the wait and whether the estimate was updated. Do not infer that the staff ignored the customer from a timestamp alone.
Check whether the customer was given a wait estimate and whether it was updated when the queue changed. A long wait with clear information is different from a long silence. The record should capture the message and the time it was given, not only the arrival and service timestamps. A wait message that was never updated should count as a communication gap.
Analysis and reporting
Report the number of visits, the share served within the store's stated wait goal, the median and tail of each stage, and the walkout rate. Break the results down by visit type, time of day, and station count. Report the visits with a missing timestamp separately. A completion rate that excludes them is not a full picture.
Compare the results with the store's own prior period rather than an external benchmark. If the store changes its intake form or its queue layout, keep the definitions stable and use a comparable visit mix. A before-and-after comparison is more credible when the sample size and the exceptions are visible. The report should name the uncertainty beside the result.
Limits and next action
The study cannot prove that a particular wait caused a walkout or that the customer's experience was fully captured by timestamps. It also cannot explain why a customer left without telling the store. A missing timestamp may mean the step happened elsewhere. The analysis should distinguish a documentation gap from a process delay.
Choose one change and assign an owner. The change might be a separate verification station, a clearer wait message, or a queue check at shift change. Set a repeat sample date and keep the definitions stable. A useful result is an intake pathway that the next busy period can follow without rebuilding the routine.
Keep the intake definitions beside the check-in station so a new employee can record the same events. Review them after a layout or system change. A wait study is only repeatable when the next person can apply the same rules. The definitions should be dated so a later review can tell which version was used.
Sources
The sources below support the operational, privacy, and consumer-protection context for this review. They do not measure this store, and no source is presented as a local benchmark. Check each link 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.
Reviewed by the DispensaryVA editorial team on 2026-11-08.