Risk Operations
Cannabis dispensary incident log workflow
DispensaryVA Editorial TeamPublished
incident managementriskoperations
Powered by StealthAgents
Powered by StealthAgents
Risk Operations
An incident log should preserve what was observed and what was done. It is not a place to assign blame or turn an assumption into a fact.
Record date, time, location, reporter, observable description, affected process, immediate control, people notified, evidence location, and next review. The compliance evidence index helps link supporting records. Use the business continuity test for planned resilience exercises.
Separate facts from hypotheses. Restrict sensitive personal information to the approved system and route legal, safety, privacy, or regulatory questions to the accountable owner.
FEMA’s incident management guidance provides general terminology and coordination context.
Close it when required notifications, corrective actions, evidence, and owner review are complete. If a question remains open, keep it active with a next date.