Cannabis Facility Security and Evidence Planning
Build a security design from the licensed operation, jurisdiction-specific requirements and real inventory workflows—not a generic camera count.
Select the complete system, not one headline feature
Match devices, software, licensing, infrastructure, retention, integrations and support to the operating requirement before finalizing the design.
Operating zones, people and risk
Confirm the license type, approved premises, state and local rules, regulator interpretations and operating procedures before design. Map people and inventory from receiving through cultivation or production, storage, retail, waste and transfer. Requirements differ substantially by jurisdiction and license, so public guidance must not claim a universal retention period or camera layout.
Name the people behind each zone as well: who holds keys and credentials, who witnesses waste handling, who runs the security software day to day, and who fields a regulator request. Where license wording is ambiguous about coverage or retention, settle it with the license holder in writing before layout begins.
- License/premises/jurisdiction
- Inventory and people workflows
- State/local rule review
- Incident and outage procedures
Layered security and response design
Layer credentials, visitor control, video, intrusion, duress and door hardware around policy and regulatory zones. Design camera purpose, field of view, lighting, frame rate, resolution, retention and export from the applicable requirement and investigation need. Protect recording, network, power and time sources and limit administrative and evidence privileges.
Retention length drives more than the recorder model: it sets storage capacity and the rack and power load that follows, while channel counts drive licensing. Cultivation and extraction rooms add humidity, dust and washdown exposure that decide housings, cable and mounting, and camera models should be confirmed against the recorder software version before anything is ordered.
- Zone-based access and visitor control
- Requirement-driven video design
- Protected storage/network/time
- Restricted evidence privileges
| Control layer | Design question | Acceptance evidence |
|---|---|---|
| Licensed activity | Cultivation, manufacturing, storage, testing, retail or delivery functions and approved premises. | Premises/workflow map |
| Controlled inventory | Receiving, vault/storage, processing, waste, sales, returns and transfer points. | Coverage and role tests |
| Regulatory evidence | Camera placement, image quality, retention, export, timestamps, access logs and alarm records as required. | Compliance evidence sample |
| Operations and exceptions | Employees, visitors, vendors, emergencies, outages, maintenance and incident preservation. | Scenario and exception log |
Commissioning with real operating scenarios
Test employee and visitor access, deliveries, inventory transfers, controlled storage, after-hours alarms, duress, video search/export, timestamp, audit trail and approved power/network interruption. Verify the required views under day, night and grow-light or reflective conditions. Document blind spots or rule conflicts for licensed management and regulator resolution.
Export rights deserve tighter control than viewing rights, because a video clip handed to a regulator or an investigator becomes a record of the licensee. Name the people who can pull footage, log every export, and schedule firmware work for hours when transfers and deliveries are not running, with a way back if a recorder loses its configuration.
- Inventory and access scenarios
- Day/night/special-light views
- Search/export/audit evidence
- Power/network recovery
Governance, records and lifecycle
Deliver premises zones, camera purpose/views, access roles, alarm points, retention calculations, storage health, time synchronization, tests, evidence procedure and exceptions. Assign regulatory change review, credential lifecycle, daily or periodic system checks, export authorization, incident hold, firmware and recovery. Keep precise security details restricted.
Acceptance for a licensed premises should end with proof, not assurances: a dated retention check on stored footage, a completed export walked through end to end, an audit report showing who did it, and a copy of the alarm notification that reached the responsible manager. Store that package where an inspector can be shown it quickly.
- Premises/view/role records
- Retention and health evidence
- Regulatory-change owner
- Incident hold and lifecycle
How we plan and deliver the work
The final design depends on site conditions, existing systems, client policies and the selected manufacturer or platform.
Map licensed areas
Walk cultivation, processing, vault and retail spaces and mark where regulators expect camera coverage and restricted access.
Confirm jurisdiction rules
Read the state and local license conditions on retention, coverage and recordkeeping, then write them into the design basis.
Install and aim
Place cameras, readers and alarm points for the actual lighting, product-handling positions and transfer points rather than a plan grid.
Test evidence export
Run identification, weigh-in and transfer scenarios, then verify that exported video and audit logs match the license conditions.
Information to gather before design
Cannabis license conditions drive camera placement, retention and access records, so the design has to start from the permit and the way product actually moves.
- License type and permitted activities
- State and local retention requirements
- Vault, weigh and transfer point locations
- Grow-room lighting and camera positions
- Staff roles allowed in restricted rooms
Frequently asked questions
These are common planning questions. A site-specific answer should be confirmed during discovery and design.
Is there one national cannabis camera-retention rule?
No. Verify the current state, local and license-specific requirements for each premises.
Can an installer certify regulatory compliance?
The licensee and its qualified advisors retain compliance responsibility; installation evidence supports their review.
Why test under grow lights or display reflections?
Unusual lighting can reduce usable identification or activity detail.
Who should export incident video?
Named, trained users following the licensee’s authorization, preservation and disclosure procedure.
Manufacturer software, firmware and technical files remain on the manufacturer’s official website. We do not mirror firmware files locally.
Plan security for your licensed cannabis facility
Describe your license type, room layout, vault and transfer points, and the retention rules your jurisdiction applies. Floor plans and current camera locations let us check coverage against how product actually moves through the building.