By Victoria Ungvary
BLOG OVERVIEW: Colorado's new HB26-1207 requires private employers with 100 or more employees doing business in the state to file EEO-1-style demographic data, including race/ethnicity, sex, and job category information, with the Secretary of State, and the requirement explicitly continues even if the federal EEO-1 requirement is eliminated. Colorado joins a growing patchwork of state and local workforce data reporting laws, including those in California, Illinois, Massachusetts, Minnesota, New Jersey, and New York City, that are increasingly diverging from one another and from the federal framework. Several trends stand out: state-driven data collection, rising multi-state complexity, analysis-ready data structures, and continued expansion to new jurisdictions.
As the Equal Employment Opportunity Commission (EEOC) moves to try to remove federal workforce demographic reporting requirements, states are building their own reporting infrastructure. Within weeks of a proposal from EEOC to eliminate EEO-1 reporting requirements, the state of Colorado signed HB26-1207 – Disclosure of Demographic Workforce Data into law. This new law in Colorado explicitly states its requirements apply “even if the federal government repeals or discontinues the federal requirement”
Colorado now joins California, Illinois, Massachusetts, Minnesota, and New Jersey in building a state-level reporting infrastructure that increasingly operates independent of federal action. For multi-state employers, demographic data reporting is no longer just a federal compliance issue, as this complex and growing patchwork of state obligations shows no signs of slowing down.
Overview of Colorado’s New Law
Colorado’s law, which was signed June 4, 2026 and takes effect July 1, 2027, introduces a new workforce demographic reporting requirement, the details of which are below:
Who is covered: The law applies to private employers with 100 or more employees that conduct business in Colorado and were required to submit EEO‑1 data as of March 1, 2026.
What must be reported: Covered employers must submit workforce demographic data aligned to an EEO‑1–style format, including race or ethnicity, sex, and job category.
Where and how reporting occurs: The data will be submitted as part of periodic business filings with the Colorado Secretary of State rather than through a standalone reporting system.
Key differentiator: The law explicitly requires reporting even if federal EEO‑1 reporting is eliminated. This is a significant shift and reflects a move away from reliance on federal data collection and toward state-controlled oversight of workforce demographics.
Additional considerations: Key implementation details are still evolving. It remains unclear whether reporting will cover only Colorado-based employees or an employer's entire workforce, and the scope of public access to submitted data has not yet been determined. These elements will likely be addressed through future guidance.
Colorado in Context: Part of a Broader State-Level Trend
Colorado is the latest addition to a growing group of jurisdictions building their own workforce data reporting frameworks, but the landscape is neither uniform nor finished. California requires annual pay data reporting that includes workforce demographics and compensation. Illinois requires demographic and pay data for its Equal Pay Registration Certificate and mandates demographic workforce data through corporate business reporting. Massachusetts requires submission of prior-year EEO-1 filings. Minnesota and New Jersey both require state contractors to regularly report employee demographics. At the local level, New York City will require large employers to submit pay data reports by race, ethnicity, and sex.
These frameworks share a common foundation but are not aligned. Some states are building directly on the EEO-1 structure; others are modifying it; others are moving away from it entirely. Colorado's decision to anchor its requirements to a fixed version of the EEO-1 framework rather than tracking future federal changes adds yet another variation. Differing state contractor reporting requirements, such as those in Minnesota and New Jersey, add further complexity. The result is a collection of parallel obligations that will continue to diverge, particularly if EEO-1 Reporting is eliminated. For many employers, the main challenge is building the flexibility to manage continued change.
The Bigger Picture: Emerging Trends in Workforce Data Reporting
The expansion of these laws highlights several clear trends. First, there is a continued shift toward state-driven data collection. In some cases, states are building on the EEO‑1 model. In others, they are modifying or replacing it. The common theme is that workforce data oversight is no longer anchored at the federal level.
Second, complexity for multi-state employers is increasing. Requirements vary across jurisdictions and include differences in coverage thresholds, required data elements, and reporting timelines. Employers are managing similar but not identical datasets across multiple systems.
Third, these frameworks are being designed for analysis. Standardized data structures make it easier for state agencies to evaluate workforce composition and identify potential disparities, as was the original intent of EEO-1 data collection. Structured reporting supports more consistent statistical analysis and, in turn, more scalable enforcement.
Finally, while the federal government is taking a step back, as anticipated, states are stepping up. Employers should be prepared for continued expansion of reporting requirements. New York State, Washington, and Oregon are likely candidates for the next wave of requirements, along with a potential expansion in New Jersey to cover all employers in the state. For the time being, employers should be prepared for an increase in reporting obligations rather than stabilization.
What Employers Should Be Doing Now
The most immediate priority is data readiness. Many employers already collect EEO-1-level demographic data, but the consistency and quality of that data across systems is rarely tested until a filing deadline forces the issue. Now is the time to assess gaps, not after a state requirement takes effect.
Job architecture should also be evaluated. Aligning to EEO‑1 categories remains important, but as states diverge in their classification systems, employers need the flexibility to map the same underlying data to multiple frameworks without rebuilding the process each time.
Neither of those steps are sustainable without a shift in overall strategy. A reactive, state-by-state approach worked when requirements were limited but becomes increasingly costly and risky as obligations multiply. Employers that invest now in centralized, scalable reporting infrastructure will reduce duplication, improve consistency, and be far better positioned when the next state acts.
Stronger governance is also necessary. Data privacy practices, access controls, and documentation of collection and reporting decisions need to be reviewed and tightened. As more jurisdictions collect and analyze workforce data, accuracy and defensibility become compliance requirements in their own right.
Finally, employers should operate with the assumption that workforce data will become more visible over time, whether through public dashboards, aggregated state reporting, or corporate disclosure filings. That makes it worth reviewing submitted data not only for accuracy, but because it is likely to be read by regulators, employees, and the public. Many employers are already developing internal reporting practices to identify gaps before a filing requires them to. That approach is increasingly prudent and becomes more valuable as reporting increases and scrutiny grows.
Key Takeaways
Colorado's law is not a standalone development; state and local jurisdictions all over the nation are building independent data collection systems, expanding transparency requirements, and setting new compliance expectations, with or without federal alignment.
The primary risk for employers is treating each new obligation as an isolated requirement as the more important dynamic is the system taking shape beneath them. Workforce data reporting is becoming a multi-jurisdictional, state-driven compliance function and employers who build for that reality now rather than responding to each new law as it arrives will be better positioned to manage both compliance and the scrutiny that comes with it.
DCI will continue monitoring state and local workforce data reporting requirements and provide updates as they occur.