On July 21, 2026, the EEOC voted to propose rescinding EEO-1 reporting requirements, along with the related EEO-2 through EEO-6 demographic reports and their recordkeeping rules. The public comment period on that proposal has now closed.
Federal reporting may be going away. Retention obligations aren’t. State requirements stay in place. Years of workforce records are still your best defense if a discrimination claim or audit shows up later.
Key Takeaways on the EEO-1 Reporting Requirements
- The EEOC’s proposal is not yet final and has no confirmed effective date.
- State and local EEO-1 reporting requirements in California, Minnesota, and Colorado continue regardless of the federal outcome.
- Retention of underlying workforce data and documents remains the primary defense in a discrimination claim or audit, independent of any federal filing requirement.
What Changes Under the EEO-1 Reporting Requirements Proposal
The proposal would eliminate the annual demographic reporting requirement for private employers with 100 or more employees. Federal contractors, unions, state and local governments, school systems, and colleges file similar reports, and those would end too.
The EEOC’s stated reasoning: the data collection is costly to administer and imposes an estimated $275 million a year in employer burden. The commission also argues that collecting this data without a specific discrimination charge raises legal questions.
A vote to propose a rule is not the same as a final rule. The EEOC still must review comments before issuing anything final. The timeline remains unsettled, including whether the rule would apply to the current reporting cycle or a future one. Legal challenges are also a real possibility given how significant this rollback would be. Every major employment law firm tracking this proposal is telling clients the same thing. Keep collecting and preserving workforce demographic data until a final rule says otherwise.
State EEO-1 Reporting Requirements Aren’t Going Away
Even if the federal EEO-1 requirement disappears entirely, state and local reporting obligations don’t move with it.
California tightened its pay data reporting rules effective January 1, 2026. Employers now have to store demographic data separately from personnel records. Penalties for missed filings are mandatory: $100 per employee for a first violation, $200 per employee after that.
Minnesota requires government contractors and public subdivisions with 40 or more employees to a Workforce Certificate and an Equal Pay Certificate. Both certificates depend on demographic and pay data broken out by gender, race, and ethnicity.
Colorado has gone further in the opposite direction of the federal proposal. Starting July 1, 2027, covered employers will have to submit EEO-1-style data to the state. The format follows what existed as of March 1, 2026. The law says this obligation stands even if the federal requirement goes away.
Multi-state employers are most exposed. A single federal rule change doesn’t simplify a compliance footprint that already spans a dozen or more state frameworks. Each one has its own definitions, thresholds, and formats.
Records Are Where the Real Exposure Sits
Federal reporting was a snapshot: a form filed once a year based on a point-in-time count. The underlying data and documents behind that snapshot carry the real weight: hiring records, promotion and termination decisions, pay history, job classifications. They’re what gets pulled years later, not the form.
If a discrimination claim surfaces two or three years from now. A state agency might open a pay equity audit even later. Either way, the question won’t be whether you filed an EEO-1 report that year. It will be whether you can produce accurate, complete workforce records for that period. Lookback windows on those requests keep extending too, a trend we break down in why extended lookbacks are increasing. Fewer federal reporting requirements doesn’t reduce that exposure. It means employers are relying more heavily on their own retention discipline instead of a standardized federal form.
That shift puts more weight on how you store the underlying records. Data scattered across old HRIS exports, payroll system backups, and departed vendors’ file formats is hard to trust. It’s also hard to pull quickly when you need it.
What to Do Now
These steps address EEO-1 specifically:
- Keep collecting and retaining demographic and workforce data at your current standard, regardless of what happens with the federal rule.
- Confirm which EEO-1 reporting requirements still apply to you at the state level.
- Set retention windows to the longest applicable requirement, whether federal, state, or litigation-hold, not the shortest.
- Confirm you can retrieve historical HR and payroll data and documents quickly, not just locate them.
The Records Still Have to Hold Up
Less federal reporting doesn’t mean less risk. It moves where the risk sits, from an annual filing to records you can produce when someone asks for them.
ResNav helps HR and payroll teams keep historical workforce data and documents organized, retrievable, and audit-ready, no matter how the reporting rules shift underneath them. Let’s connect to discuss your historical workforce data requirements.
Frequently Asked Questions
No. The proposal isn’t final yet. State and local reporting requirements stay in place regardless of what happens federally, and years of workforce records remain your primary defense in a discrimination claim or audit.
There is no confirmed date. The EEOC must review public comments before issuing a final rule. It hasn’t set a timeline yet, including which reporting cycle the rule would first apply to.
No. States including California, Minnesota, and Colorado have their own independent reporting and recordkeeping requirements that continue regardless of the federal outcome.
Continue your current data collection and retention practices, and confirm your state-level obligations. Store historical workforce data and documents in a format you can retrieve quickly.