Compliance Guide

Colorado AI Act Applicability for Companies Headquartered Outside Colorado

Headquarters location is the wrong starting question. Assess applicability system by system and role by role: whether you develop or deploy an AI system, whether it is high-risk, whether it contributes to consequential decisions, and whether those decisions affect Colorado consumers.

Start with triggers, not headquarters

Work through the five questions below for each AI system. Each one tests a separate trigger, and the answers can differ from one system to the next.

Scope analysis path for each AI system
TriggerQuestion to answer
Colorado nexusDoes the business activity connect to Colorado, regardless of headquarters?
RoleIs your organization the developer, the deployer, or both for this system?
High-risk systemDoes the system fall within the statute's high-risk definition?
Consequential decisionDoes its output materially influence a decision of the kind the statute covers?
Colorado consumerAre the people affected Colorado residents as the statute defines them?

Determine your role for each system

Decide whether your organization is the developer, the deployer, or both for each system. Record third-party and foundation model dependencies as part of that role analysis, since they affect who holds which responsibilities.

What to bring to legal counsel

  • A system inventory marking which systems influence decisions about individuals who may be Colorado residents
  • Your role for each system, including third-party and foundation model dependencies
  • Data flows showing how outputs enter a decision process, including agent and tool-call paths
  • Vendor and customer contracts that allocate documentation and notice responsibilities
  • Existing risk assessments, policies, and logging that could serve as compliance evidence
  • Open questions on exemptions, small-deployer carve-outs, effective dates, and rulemaking status

Where runtime governance supports compliance operations

Mapping likely obligation areas to operational controls

Once counsel confirms which systems are in scope, runtime governance can help enforce permissions and keep audit evidence for those systems.

Turn scope findings into enforceable controls

Once counsel confirms which systems are in scope, runtime governance can help enforce permissions and keep audit evidence for those systems.

Explore Runtime Governance