OLD GUARD
Decision framework / Facility startup

Cannabis facility readiness assessment

A building can be finished and still be months away from controlled production. This framework tests the eight operating systems that have to work together before launch.

Reviewed August 4, 2026 · By Alex Marzec

The assessment is not another construction punch list. A punch list asks whether components were installed. Readiness asks whether trained people can use those components, under approved procedures, with traceable records, without creating uncontrolled safety, quality, or schedule risk.

If a launch requirement cannot be demonstrated with a document, test result, approval, trained operator, or controlled trial, treat it as open.

The eight launch gates

1. Licensing and authority approvals

Map every license, inspection, certificate, occupancy condition, and local approval to its owner and required evidence. Do not use a submitted application as a substitute for an approval.

Evidence: approval register, conditions log, inspection closeouts

2. Facility and utility performance

Verify that HVAC, electrical, water, drainage, compressed gases, fire protection, security, and environmental controls perform under expected operating load—not only while the building is empty.

Evidence: balancing reports, alarm tests, trends, load verification

3. Process equipment acceptance

Confirm installation, utilities, guarding, controls, recipes, cleaning access, spare parts, calibration needs, and vendor support. Close the gap between factory capability and the actual product, room, and crew.

Evidence: FAT/SAT records, manuals, punch list, calibration status

4. Safety and emergency controls

Review job hazards, chemical information, ventilation, hazardous-location documentation where applicable, lockout needs, PPE, emergency shutdowns, spill response, and incident escalation with qualified specialists and the authority having jurisdiction.

Evidence: hazard assessments, drills, inspection records, training

5. Quality system and controlled documents

Make sure current SOPs, specifications, forms, batch records, deviations, corrective actions, sanitation, change control, and release authority are usable on the floor. The document system has to survive a real shift.

Evidence: approved master documents, completed mock records, review workflow

6. People and competency

Fill critical roles, define decision rights, and verify competency through observed execution—not attendance sheets alone. Include backup coverage for quality, maintenance, security, and production leadership.

Evidence: staffing matrix, training records, competency checks

7. Materials, inventory, and data flow

Trace inputs, labels, packaging, work in process, samples, waste, finished goods, and required track-and-trace events through a dry run. Reconcile physical movement with the records it creates.

Evidence: mock batch genealogy, label reconciliation, inventory test

8. Integrated operational trial

Run a controlled rehearsal that crosses departments: receiving, production, sanitation, quality review, packaging, inventory, deviation handling, and shift handoff. Record failures and repeat the test after critical corrections.

Evidence: trial protocol, exceptions, owners, retest results

How to score readiness

Use four statuses instead of a misleading percentage:

  • Blocked: a critical requirement has no viable path or owner.
  • Open: the path exists, but evidence is incomplete.
  • Conditional: the gate passed with a defined operating limitation or follow-up.
  • Ready: the requirement was demonstrated and the evidence is controlled.

A facility is not ready because most tasks are green. It is ready when every critical gate is closed or an accountable decision-maker has accepted a clearly documented residual risk.

What a useful assessment should deliver

  • A launch-gate register with evidence, owners, deadlines, and dependencies.
  • A risk-ranked gap list separating launch blockers from post-launch improvements.
  • A single integrated schedule connecting construction, licensing, staffing, procedures, equipment, and commissioning.
  • A 30-day closeout plan and a defined go/no-go review.
  • A record of assumptions that must be revalidated when the design, product mix, or regulatory conditions change.

Quick answers

When should the assessment start?

Start before major equipment and layout decisions are irreversible, then repeat the review at design freeze, pre-installation, pre-inspection, and before the first controlled batch.

When is a cannabis facility ready to launch?

A facility is ready when its critical launch gates are closed with evidence: required approvals are in hand, utilities and equipment have passed documented tests, trained staff can execute approved procedures, material and data flows work, and deviations can be contained without improvisation.

Does readiness mean regulatory compliance?

No. Readiness work supports compliance and execution, but applicable requirements depend on the jurisdiction, product, process, building, and authority having jurisdiction. Legal, engineering, fire-code, and industrial-hygiene determinations belong with qualified professionals.

What usually becomes the critical path?

The slowest unresolved dependency: an approval, utility, long-lead component, safety control, trained role, validated record flow, or failed integrated test. See why cannabis facility launches get delayed.

Primary references

These sources inform the framework; they do not determine which requirements apply to a specific facility.

Before the date becomes a promise

Turn “almost ready” into a defensible launch decision.

Request an assessment