A Research Method for Coding Cannabis Dispensary Incidents by Severity

"The research question is whether severity coding creates a useful comparison without erasing context."

Evidence observation 1

Start with observable facts: event time, location, people or systems affected, immediate controls, interruption, injury report, product impact, and escalation. Then apply a versioned classification rule. “High” should mean the rule says high, not that a manager felt alarmed.

Evidence observation 2

OSHA investigation guidance and NIST incident-response guidance offer different scopes. Virginia CCA material supplies cannabis-specific context. None provides a universal dispensary severity scale, so a local rubric must state its owner, version, and excluded judgments.

Evidence observation 3

A good dashboard reports event count, time to containment, repeat events, open investigations, and severity distribution. Do not compare periods when the rubric, reporting channels, or denominator changed without a version break. Missing reports are not zero incidents.

Evidence observation 4

Near misses deserve a distinct state. Combining near misses with completed harm may hide prevention opportunities; excluding them may hide control weakness. Record whether a severity code was initial, revised, or final and why.

Evidence observation 5

Root-cause language should be evidence-led. A late closeout may correlate with staffing, but a record cannot establish causation without a defined comparison and investigation. Keep causal hypotheses visibly separate from verified observations.

Evidence observation 6

This desk review uses OSHA, NIST, and Virginia regulatory sources. It does not estimate incident rates or decide reportability. Small operators and different store layouts may produce incomparable distributions.

Evidence observation 7

Severity coding helps organize review when facts, rubric, and revisions are visible. It is not a substitute for investigation, required reporting, medical judgment, or accountable operational decisions.

Additional measurement notes

For cannabis dispensary incident severity, the observation unit should be stable before any trend is calculated. A record may represent an attempt, package, request, document, or interval, and those units should not be blended. The operator should state whether duplicates are retained, linked, or excluded and preserve the rule used. That makes a later review reproducible without pretending that a local queue is a representative sample of cannabis businesses.

The evidence also has a time dimension. A same-day count can describe workload or event volume, but it cannot establish a durable rate unless the observation window, open hours, system coverage, and missing periods are known. If a source record was corrected after the event, retain the original value, correction timestamp, and reason. This is analysis hygiene, not proof that the underlying operation performed well.

A responsible finding should name the next decision boundary. Routine records can be summarized; exceptions need an owner, a stopping rule, and a source for the decision. If the evidence is incomplete, “unknown” is more accurate than a favorable assumption. The distinction is especially important in cannabis administration because a customer, product, payment, delivery, or access record may cross several systems and authorities before it is closed.

These limits do not make the research unusable. They make the conclusion narrower and more defensible. A dispensary can use the described fields to compare its own periods, test whether a control operated, and identify records needing review. It should not convert that internal comparison into a public industry statistic, a legal conclusion, or a claim about a vendor, employee, customer, or product without additional evidence.

For an internal repeat measurement, freeze the field definitions before collecting the next sample. Document whether the source is a point-of-sale export, an integration log, a ticket, a scanned document, a meter, or a human observation. Each source has a different failure mode. A missing log event is not the same as a negative event, and a manually corrected record should not silently replace the original. These distinctions let a reviewer challenge the method without having to guess how the number was made.

Comparisons also need a like-for-like boundary. Store hours, product scope, channel, reviewer coverage, and rule version can change the apparent result even when the underlying process is unchanged. Report those changes beside the measure. Where the population is small, show counts and examples of unresolved states rather than relying on a percentage that suggests precision the sample cannot support.

The operational use of this research is therefore diagnostic. It can help an owner decide which evidence to request, which exception to route, and which process boundary needs clarification. It should not be used to rank dispensaries, assign blame, or promise an outcome to a customer or supplier. Those decisions require facts outside the public sources reviewed here and an accountable decision-maker.

Before publishing a local result, have a second reviewer trace a sample from the reported number back to its source record and forward to the stated decision. Resolve disagreements by recording the rule, not by averaging opinions. That modest review step exposes missing identifiers, duplicated events, stale exports, and unsupported causal language. It also keeps the article’s central promise intact: evidence should clarify a cannabis dispensary decision while remaining honest about what the evidence cannot show.

Sources and evidence scope

This article is a bounded desk review for cannabis dispensary administration. The cited sources are public references selected for the specific control question; they are not evidence of a national industry average. Facts from the sources are identified as such, while recommendations and interpretations are analysis. Operators should verify current Virginia requirements and their own license, system, and record boundaries.

Evidence-led conclusion

Severity coding helps organize review when facts, rubric, and revisions are visible. It is not a substitute for investigation, required reporting, medical judgment, or accountable operational decisions.

Public sources

1. [S1] OSHA incident investigation (public source).
2. [S2] NIST incident response (public source).
3. [S3] Virginia CCA laws and regulations (public source).