Preparing for a Site Visit or Surprise Regulatory Inspection

 

Most cannabis operators know they should be "inspection ready" year-round. But knowing that in theory and actually being ready when an inspector walks through the door unannounced are two very different things. A scheduled audit gives you time to prepare - you know the date, you can pull documentation in advance, and you can walk your team through what to expect. A surprise inspection offers none of that. There's no warning, no prep window, and no do-over if the first few minutes go poorly.

And those first few minutes matter more than most operators realize. Inspectors are trained to read a facility quickly, how staff respond, whether documentation is accessible, whether the team seems rehearsed or rattled. A calm, organized response in the opening moments often shapes how thoroughly the rest of the visit is scrutinized.

This isn't about building a long-term audit program - we've covered that in a separate post. This is the tactical, day-of playbook: what your team actually does the moment an inspector arrives, unannounced, on an otherwise ordinary Tuesday.

 

 

Before It Happens: The Groundwork That Makes the Day-Of Manageable

You can't prepare for a surprise visit on the day it happens. By definition, there's no lead time which means everything that makes a surprise inspection go smoothly has to already be built into how your facility operates on a normal day. This is less about a single checklist and more about a standing operational habit: documentation that's always current, a team that always knows its role, and a chain of communication that doesn't depend on any one person being present.

The gap most operators run into isn't a lack of documentation - it's that the documentation exists somewhere, just not in a form anyone can produce quickly under pressure. The goal here is to close that gap before it's ever tested.

• Designate a point person (and a backup). Every shift should know exactly who greets an inspector and takes the lead. If that person is out, there needs to be a clear second-in-command - not a scramble to figure out who's "in charge" while an inspector waits at the front desk.
• Keep a "go bag" of core documents accessible. Current licenses, SOPs, recent inventory reconciliation reports, employee training logs, and security footage retention confirmation should be retrievable in minutes, not hours. If it takes a phone call to corporate to locate a license, that delay gets noticed.
• Brief your team regularly, not just once. Staff turnover means the "what to do if an inspector shows up" conversation needs to be a recurring part of onboarding and refreshers - not a one-time memo from two years ago that half your current staff never saw.

The Moment an Inspector Arrives

However well-prepared your documentation is, the human response in the first few minutes sets the tone for everything that follows. This is the moment where nerves tend to show and where a team that's actually practiced this scenario looks noticeably different from one that hasn't. The goal isn't to perform confidence; it's to have a clear, repeatable sequence of actions so nobody has to improvise under pressure.

• Verify credentials first. Confirm the inspector's identity and agency before anything else. This is standard practice, not a sign of distrust legitimate inspectors expect it and it costs you nothing to ask.
• Notify your point person and leadership immediately. Even if you're mid-shift and the point person is busy, someone needs to alert them and ownership or compliance leadership right away. Delayed notification often means leadership finds out about the visit after it's already over.
• Stay calm and professional. Tone matters more than most staff expect. An anxious, defensive, or visibly unprepared team can turn what would have been a routine walk-through into a more detailed, more skeptical review.

Walking the Inspector Through Your Facility

Once the inspection is underway, how your team moves through the facility with the inspector matters almost as much as the documentation itself. This is where a lot of operators either build credibility or accidentally undermine it not through anything dishonest, but through disorganization, over-explaining, or staff who aren't sure who's supposed to be answering questions.

• Escort, don't wander. Someone from your team should accompany the inspector at all times not to obstruct or hover, but to answer questions accurately and know exactly what's being observed at each stage of the visit.
• Answer only what's asked. Volunteering unprompted information or guessing at answers you're unsure about creates more problems than it solves. If you don't know something, it's always better to say so and follow up with the correct information than to speculate.
• Take your own notes. Document what areas were reviewed, what questions were asked, and what if anything the inspector flagged along the way. This matters later if there's a follow-up report to compare against, or if details get fuzzy after the fact.

Documentation: What to Have Ready to Hand Over

Even a well-trained team can lose credibility fast if the paperwork doesn't back up what they're saying. Inspectors expect operators to be able to produce core documentation without delay and the speed and organization with which you do so is, itself, a signal of how seriously compliance is treated day to day. This is where your "go bag" groundwork from earlier pays off directly.

• Current state license(s) and any required postings
• Seed-to-sale/track-and-trace system access and recent reconciliation records
• Employee training and certification logs
• Security system documentation (camera coverage, retention window, access logs)
• Most recent internal audit or self-assessment, if available

Having these organized in advance- physically in a binder, digitally in a shared folder, or both signals a well-run operation before the inspector even asks a single question.

After the Inspector Leaves

The visit itself isn't the end of the process what happens in the hours and days afterward often determines whether a surprise inspection becomes a minor footnote or a recurring problem. Treat the immediate aftermath as its own phase, not an afterthought.

• Debrief immediately while details are fresh. Gather your team and document exactly what was reviewed, discussed, and any concerns raised, verbal or written. Memory fades fast, and a same-day debrief captures details a next-week recap will miss.
• Address flagged issues without delay. If anything was noted as a concern, start correcting it the same day if possible. Waiting signals a lack of urgency both to regulators on a follow-up visit and to your own team's compliance culture.
• Update your SOPs if a gap was exposed. A surprise inspection is often the clearest, most honest signal of where your documentation or training has a blind spot. Treat it as free diagnostic information rather than something to move past quickly.

How ICS Consulting Helps

Being truly inspection-ready isn't a document you write once and file away - it's a standard your team practices continuously, until the right response becomes second nature rather than something to look up in the moment. ICS Consulting helps operators build that muscle through Compliance Audits & Gap Assessments and hands-on Compliance Operations Training, so your team knows exactly what to do long before an inspector ever arrives unannounced.

ICS Consulting specializes in Compliance based services, such as Third-Party State Regulatory Audits, State and Local License Application Support, Technical Writing, Standard Operating Procedures Development, Worker Safety, QMS, OSHA Compliance, Metrc Seed-to-Sale Support, Compliance Operations Training, Employee Retention Solutions, and Employee Onboarding.

Learn more about ICS Consulting or book a call with Jenny Germano for additional resources and industry insights.