Workflow requirements
Map the staff, decisions, data, records, approvals, exceptions, reports, and regulator requests the system must support.
ILC helps operators evaluate document, training, POS, inventory, Metrc, delivery, security, camera, alarm, and other compliance-related systems before selection or during implementation.

ILC knows the systems and the operational questions to ask, but the recommendation is driven by fit for the operator—not by which vendor offers the best referral arrangement.
Requirements based on real workflows
Better vendor questions and demonstrations
Integration and permission gaps identified earlier
A practical implementation and ownership plan
The exact engagement depends on your license, locations, stage, and internal capacity.
Map the staff, decisions, data, records, approvals, exceptions, reports, and regulator requests the system must support.
Turn the workflow into specific questions and test cases instead of relying on a generic feature tour.
Check data ownership, exports, APIs, timing, permissions, audit history, retention, alerts, backups, vendor access, and failure modes.
Assign configuration, content, migration, testing, training, support, review, and the human work that remains outside the tool.
Most problems show up when what staff do, what the system records, and what the written procedure says no longer match.
The happy path looks clean while corrections, outages, returns, investigations, exports, and regulator requests remain untested.
No one owns timing differences, failed syncs, duplicate entry, field mapping, reconciliation, or access to history.
Permissions and notifications are configured before roles, reviews, decisions, and escalation are clear.