Compliance + ops deep-dive
Cannabis surveillance — retention monitoring and incident timelines
Two surveillance problems sit on top of every cannabis dispensary. First: nobody actually knows their camera system’s retention is meeting WAC 314-55-083 until inspection day, when the answer matters most. Second: when something goes wrong on the floor, finding the moment in the footage is a 4-hour scrub. Both are solvable with structure, not vigilance.
Why surveillance gets neglected — until it’s urgent
Cannabis surveillance is a compliance requirement that doesn’t produce daily friction until something fails. WAC 314-55-083 (Washington), §1 CCR 212-3 R 3-110 (Colorado), Title 4 §15049 (California) — every state has a retention rule. Every state assumes the operator is checking. Most operators check retroactively, when a customer complaint or WSLCB inspection forces the issue.
- Retention monitoring is silent until it isn’t. A camera goes offline; nobody notices until the WSLCB asks for footage from 23 days ago.
- Incident review is reactive. A variance over your threshold means somebody looks at footage. The lookup is a manual scrub through the relevant timeframe — guess + scroll + repeat.
- Spreadsheet tracking — most operators have a tab in a master spreadsheet listing each camera + its expected retention + when it was last verified. Updated when remembered, which means “monthly if you’re lucky.”
- Inspection-prep panic — the day before a WSLCB visit, somebody pulls every camera’s retention setting + checks a span of footage. That’s the worst possible time to discover a gap.
Check retention on a schedule, and write the check down
Stop tracking retention by memory. Check every camera’s retention window on a fixed cadence — nightly is the right cadence for a rule measured in days — against the regulator’s minimum and your own safety margin. A camera below the line is an incident, not a note: it gets a record, an owner and a close date. Record the check even when everything is fine, because the record of a clean check is what an inspector asks to see.
Link the moment to the footage when it happens
Surveillance review used to be: variance at 6:42pm Tuesday, manager opens the camera system at 9am Wednesday and scrolls through hours of footage looking for the moment. The fix is to record the timestamp at the moment anything gets flagged — a variance, a void, an override, a failed age check — so the review starts at the right minute. Debrief with the budtender within the hour, while the moment is still fresh.
What NOT to automate
The probe + the bridge automate the work that doesn’t need human judgment. Some things still need the human:
- Don’t auto-classify what the footage shows. Cameras don’t see motive. The platform surfaces the clip; the manager judges what happened.
- Don’t auto-discipline. A flagged transaction is a flag, not a finding. Manager reviews + decides. A documented response is the goal.
- Don’t auto-share with regulators. WSLCB asks → operator pulls + sends. Auto-sharing footage opens a privacy + chain-of-custody can of worms.
- Don’t auto-delete past retention threshold. Some incidents need longer retention than the rule (open arbitration, ongoing investigation). The platform should flag these and refuse the rolling-delete until cleared.
Cannabis-specific gotchas
- WAC 314-55-083 specifics — a minimum of 45 days of retention. That is the rule text, not an interpretation: -083 states "All surveillance recordings must be kept for a minimum of 45 days on the licensee's recording device." Verified against app.leg.wa.gov 2026-09-01.
- Point-of-sale areas — WAC 314-55-083(3)(b) lists all point-of-sale areas among the areas that need camera coverage, and where an online order is handed over is one of them. Know which physical zone that is and confirm a camera covers it.
- Manager-PIN override trail — every override should record who, why and when, and point at the footage for that moment. When an inspector asks why you overrode on March 5 at 9:42pm, the answer is a clip, not a shrug.
- Sale-to-minor incidents — if a budtender attempts to sell to someone with an obviously-fake ID, the register refuses the sale and records the attempt. Footage at the moment of the attempt = the operator’s defense if WSLCB asks. Without it, the sale-to-minor allegation is harder to defend.
- Per-store retention windows — each store has its own recorder, so check each one on its own.
What this replaces
Concretely: a spreadsheet that documents retention windows per camera + a manager who manually scrubs camera footage when something flags. The platform takes those routines off the team’s plate; the team handles judgment + customer-facing follow-up.
Takeaways
- Surveillance is neglected until it is urgent. Move from a spreadsheet updated monthly to a scheduled check that gets written down.
- Check every camera’s retention window on a fixed cadence against the rule and your own margin; a gap is an incident with an owner.
- Record the timestamp the moment anything is flagged, so review starts at the right minute instead of scrolling hours.
- Operator outcome: 4 retention gaps caught before inspection in April / 11 timestamped incidents avg 4-min review at Seattle.
- Don’t auto-classify / auto-discipline / auto-share with regulators / auto-delete past threshold. Automate the work; preserve the judgment.
Frequently asked
- How fast does the WSLCB expect us to produce a specific footage clip in an inspection?
- WSLCB inspections increasingly ask for footage retention in a 30-second turnaround, wanting to see that you can produce a specific date and time clip on demand. In 2026, answering "let me check our spreadsheet" is the wrong answer. The right answer is showing the clip plus the audit row confirming it was retained per policy.
- How long do I need to keep surveillance footage under Washington rules?
- WAC 314-55-083 sets the retention floor and it is not ambiguous: recordings must be kept “for a minimum of 45 days on the licensee’s recording device”, read verbatim at primary source. Operator-side targets usually run 45 to 60 days for a safety margin. Confirm the exact requirement with your LCB liaison and document the answer.
- How can I stop spending hours scrubbing DVR footage every time a transaction gets flagged?
- Use the camera bridge: at the moment of a flag such as a variance over threshold, void, or override, the platform writes the timestamp into the incident row with a clip-fetch URL. The manager opens the incident and clicks Review footage, and a single 30-second clip plays inline with no DVR login or scrolling. That turns a 4-hour scrub into minutes, so the budtender debrief can happen within an hour instead of the next day.
Related guides
Tax + finance deep-dive
IRC 280E for cannabis operators — what it costs you, what 471 + CHAMP buy back
7 min read
Operational deep-dive
Cannabis banking — keeping the account open, not finding one
7 min read
Operational deep-dive
Cannabis customer-acquisition cost — what to spend, what NOT to spend
7 min read
Ready to talk through your migration?
30-minute demo. We end by quoting the cutover from your current setup — fixed scope, no hourly games.