EEOC Proposes Ending EEO-1 Reporting: What the Rescission Means for HR Technology and Compliance Systems

What the EEOC Is Proposing

The NPRM proposes rescinding the requirement for employers covered by Title VII of the Civil Rights Act to file annual reports summarizing aggregate employee data by race and sex. This includes not just the EEO-1 report for private employers with 100 or more employees (and federal contractors with 50 or more), but also the EEO-2 through EEO-6 reports covering apprenticeship committees, local unions, state and local governments, and school systems and colleges — although the EEOC notes it has not actually collected the EEO-2 or EEO-6 since 1981 and 1993, respectively.

According to the EEOC's press release, the Commission determined that:

• The EEO Data Reports are inconsistent with equal employment opportunity law and may raise constitutional concerns
• The reports collect data that is not narrowly tailored or necessary to enforce anti-discrimination statutes
• The current reporting requirement imposes costs of approximately $275 million annually on employers, plus nearly $4 million on the EEOC itself
• Employers must submit reports annually without any specific indication of a potential violation, which the Commission views as inconsistent with Title VII's colorblind mandate

EEOC Chair Andrea Lucas stated that the proposed rescission "reaffirms the founding principle that every individual is created equal and therefore is entitled to equal treatment under the law," while emphasizing that the Commission's authority to request specific records during charge investigations remains unchanged.

The Rulemaking Timeline

Understanding the timeline is critical for HR technology planning:

Comments were submitted through regulations.gov under docket EEOC-2026-0034. Until a final rule takes effect, 29 CFR 1602.7 remains in force — but note that the regulation's default September 30 filing date has not governed recent collections. The EEOC sets each year's deadline through its instruction booklet (the 2024 cycle closed in June 2025), and its data-collections page currently says only that updates on the 2025 collection "will be posted to this page as they become available."

Why HR Technology Teams Cannot Simply "Turn Off" EEO Reporting

The instinct for some organizations may be to begin decommissioning EEO-1 reporting modules in their HRIS and compliance platforms. This would be premature for several reasons.

Federal Obligations Remain Active

The proposed rule is exactly that — a proposal. The Administrative Procedure Act requires the EEOC to review all public comments before issuing a final rule, and legal challenges could further delay or block implementation. Employers who dismantle demographic data collection before a final rule takes effect risk being unable to comply if the EEOC opens the 2025 collection under the existing regulations.

State Reporting Requirements Are Expanding

Even if federal EEO-1 reporting is eliminated, a growing patchwork of state-level demographic and pay data reporting requirements will keep compliance technology busy. The most significant state mandates include:

California requires private employers with 100 or more employees to file annual pay data reports with the Civil Rights Department. For 2026, California expanded these requirements under SB 464 to include mandatory civil penalties ($100 per employee for a first violation, $200 for subsequent violations), separate storage of demographic data from personnel files, and preparation for a transition from EEO-1 job categories to 23 SOC-based categories in 2027.

Illinois requires businesses with 100 or more employees in Illinois to obtain an Equal Pay Registration Certificate (EPRC) from the Illinois Department of Labor and recertify every two years, submitting wage records broken out by gender, race, and ethnicity. Penalties can reach $10,000 per violation.

Federal Contractor Obligations Are Narrowing, Not Disappearing

For federal contractors, the picture changed in two steps. Executive Order 11246 — the basis for the 50-employee contractor EEO-1 filing threshold and race/sex affirmative action plans — was revoked in January 2025, and on August 21, 2026 the Department of Labor published a final rule removing its implementing regulations at 41 CFR parts 60-1 through 60-50 effective October 26, 2026. DOL states that "OFCCP no longer has any use for EEO-1 data."

What remains: OFCCP continues to enforce Section 503 of the Rehabilitation Act and the Vietnam Era Veterans' Readjustment Assistance Act (VEVRAA), whose revised regulations took effect September 21, 2026 and still require affirmative action programs, data collection, and audit readiness for individuals with disabilities and protected veterans. As DirectEmployers notes, those obligations are separate from EEO-1 reporting and are unaffected by the EEOC's proposal.

Litigation Defense Requires Data

Employers who face discrimination claims or class action lawsuits often rely on workforce demographic data to demonstrate compliance and non-discriminatory patterns. Discontinuing data collection could leave organizations without the evidence they need for legal defense.

How to Prepare Your Compliance Technology Stack

Rather than waiting for a final rule, HR technology teams should begin planning for a more complex — not simpler — compliance data environment. Here is a practical framework for preparing your systems.

1. Audit Your Current Data Pipelines

Map every system that collects, processes, stores, or transmits employee demographic data — HRIS platforms, payroll systems that use EEO-1 job categories, compliance reporting modules, internal analytics dashboards, and third-party vendors who handle submissions. Understanding your data architecture is the first step toward making targeted changes rather than sweeping — and potentially harmful — deactivations.

2. Build a Jurisdiction-Level Compliance Matrix

Create a matrix that maps each reporting obligation to its authorizing jurisdiction (federal, state, or local), deadline, data elements required, and the technology module responsible for generating the report. This matrix becomes your decision framework when federal requirements change.

For organizations operating in multiple states, a compliance technology platform that can manage jurisdiction-specific reporting rules is no longer a convenience — it is a necessity.

3. Modularize, Don't Delete

Configure your systems so that federal EEO-1 reporting can be deactivated as a module without disrupting the underlying data collection that supports state reporting, internal analytics, and litigation readiness. Key principles include:

• Separate the data collection layer from the reporting layer — demographic data intake should continue regardless of which specific reports are generated
• Use configurable rule engines that can enable or disable specific reporting workflows by jurisdiction
• Maintain historical data for all past EEO-1 submissions, which may be needed for audits, litigation, or regulatory lookback periods

4. Prepare for State Reporting Divergence

With states increasingly diverging from federal reporting categories, compliance platforms need to support multiple classification systems simultaneously. California's forthcoming transition from EEO-1 job categories to 23 SOC-based job categories in 2027 is a leading example. Organizations should:

• Begin dual-coding employees under both EEO-1 and SOC classification systems now
• Validate that their HRIS can support multiple concurrent job classification taxonomies
• Plan data migration timelines for the 2027 transition

5. Engage Stakeholders Beyond HR

The EEO-1 rescission affects more than HR operations. Legal, compliance, DEI, and executive leadership teams all have a stake in how demographic data is managed. Convene a cross-functional working group to assess the organization's continued need for workforce demographic data, decide whether internal pay equity audits will continue, and evaluate the impact on diversity reporting commitments to boards, investors, or clients.

The Broader Technology Trend: Compliance Complexity Is Increasing

The EEOC's proposed rescission may seem like a simplification on the surface, but the reality for HR technology teams is the opposite. As federal requirements potentially recede, state-level obligations are intensifying with greater specificity, stricter penalties, and more granular data requirements.

This trend reinforces the growing strategic importance of compliance automation platforms that can monitor regulatory changes across jurisdictions in real time and adapt reporting workflows accordingly. Organizations that rely on manual processes or single-jurisdiction compliance tools are likely to face escalating risk as the regulatory landscape fragments.

BlueHive's 2026 Workplace Compliance Outlook describes the same dynamic: employers must maintain readiness for existing federal requirements while building capacity for expanding state mandates — a challenge that fundamentally depends on flexible compliance technology infrastructure.

What Employers Should Do Now

1. Keep your 2025 EEO-1 data ready and monitor the EEOC's data-collections page. The agency has not opened the 2025 collection or set a deadline, but the regulation remains in force until a final rule says otherwise.
2. Do not deactivate demographic data collection in your HRIS or payroll systems. State-level obligations, Title VII recordkeeping, Section 503/VEVRAA requirements, and litigation defense all require this data.
3. Review state reporting obligations in every jurisdiction where you have employees. Build or update a compliance matrix that tracks each requirement independently of federal rules.
4. Assess your compliance technology's flexibility — can it deactivate specific federal reporting modules while maintaining state-level capabilities? If not, plan for system upgrades or vendor conversations.
5. Federal contractors: map which data flows supported E.O. 11246 obligations (ending October 26, 2026) versus Section 503/VEVRAA obligations (continuing), and reconfigure accordingly.
6. Brief leadership teams on the distinction between reduced federal reporting and continued state/internal data obligations, so that budget and technology decisions are not made on the assumption that demographic data management is going away.

The EEOC's proposal to end EEO-1 reporting marks a significant inflection point for HR compliance technology. But the right response is not to dismantle data capabilities — it is to make them more adaptable. The organizations best positioned for this shift are those whose technology stacks were already built for regulatory agility rather than single-mandate compliance.

Sources

• EEOC Proposes Rescission of Annual Race and Sex Reporting Requirements — EEOC Press Release
• Removal of Reporting Requirements — Federal Register NPRM (July 23, 2026, 91 FR 46332)
• Commission Votes: July 2026 — EEOC
• EEO Data Collections — EEOC
• Rescission of Executive Order 11246 Implementing Regulations — DOL Final Rule (Aug. 21, 2026, 91 FR 54444)
• EEOC-2026-0034 — Proposed Rule and Public Comment Portal on Regulations.gov
• EEOC Signals End to Key Federal EEO Reporting Mandates — Jackson Lewis
• EEOC Puts EEO-1 Rescission in Writing: Formal Notice of Proposed Rulemaking — DirectEmployers
• EEOC Proposes Rescission of Annual Reporting Requirement — Seyfarth Shaw
• With the EEOC Poised to End EEO-1 Reporting, What's Next for Employers — Foley & Lardner
• California Pay Data Reporting — California Civil Rights Department
• 820 ILCS 112/11 — Equal Pay Registration Certificate Requirements (Illinois General Assembly)
• California Expands Pay Data Reporting Obligations Under SB 464 — Payne & Fears
• California's 2026 Pay Data Reporting Rules Add New Compliance Pressures — Thomson Reuters
• Compliance Tech Is Becoming a Strategic Priority, as AI Expands in HR — HR Executive
• The 2026 Workplace Compliance Outlook — BlueHive