The federal report is on its way out. Massachusetts still wants it, Colorado has frozen the form into law, California is switching code sets and New York City wants the pay-band version. The schema your HRIS vendor maintained for everyone is about to become yours to maintain.
The EEO-1 has not been abolished yet. On 21 July the Equal Employment Opportunity Commission voted 2–1 to propose rescinding it, together with the other federal EEO reports and the recordkeeping requirements that support them. The comment period closed on 24 August with around 3,000 submissions. No final rule has been published, the portal for the 2025 data collection has not opened, and employment lawyers are advising employers to stay ready to file.
Most commentary has focused on that timing question. For the people who run HR systems, a different question matters more. The EEO-1 was never just a report. It was a shared data standard that every US employer with 100 or more staff had to meet, and that every HRIS and payroll vendor therefore maintained on their behalf. When the federal requirement goes, the standard does not disappear. It fragments.
What the report was quietly holding together
Filing the EEO-1 was a once-a-year task. Being able to file it required infrastructure that ran all year: voluntary self-identification captured at onboarding, every job code mapped to one of ten federal job categories, a snapshot pay period, and a reconciliation between the HRIS headcount and the number that went to Washington.
The job-category mapping is the piece that matters here. It sits in a field most people never look at, it is usually maintained by whoever administers the HRIS, and it gets checked properly once a year, in the weeks before the filing deadline. The annual filing was the quality control. Take the filing away and, in many organisations, nothing else would notice if the mapping drifted.
The states are keeping copies of the form
Several state and local laws either rely on EEO-1 data or were written around its structure, and they are not waiting for the federal outcome.
Figure 1
Jurisdiction | Who is covered | What it relies on | What that means for the data |
|---|---|---|---|
Massachusetts | 100+ employees in the state, subject to federal EEO-1 | EEO-1 data, filed by 1 February; continues even if the federal report is revoked | The federal format survives as a state filing |
Colorado | 100+ employees, federal EEO-1 filers as of 1 March 2026 | A workforce report on the EEO-1 form as it existed on that date | A frozen version of the federal form, preserved in state law |
Illinois | 100+ employees in the state, including remote | Equal Pay Registration Certificate plus demographic data substantially similar to EEO-1 | EEO-1 categories plus pay and county detail |
California | 100+ employees, at least one in California | Annual pay data report; moving to standard occupational classification groupings from 2027 | A second, different job taxonomy |
New York City | 200+ employees | Pay and hours by demographic group, modelled on the former Component 2 format; latest start December 2028 | Pay-band reporting the federal form stopped collecting |
One federal standard becomes at least three. Summarised from employment-law guidance published in September 2026. Thresholds, deadlines and effective dates should be confirmed against each statute and agency guidance before filing.
Read down the right-hand column and the pattern is clear. The federal form becomes a historical artefact that some states keep alive. California moves to a different occupational taxonomy. New York City revives pay-band reporting the EEOC abandoned years ago. A multi-state employer that mapped its jobs once, to one federal scheme, now needs its job architecture to map cleanly to at least two classification systems, with different thresholds and calendars.
The federal report went away. The obligation to classify every job correctly did not; it just lost the single standard that made it routine.
The vendor incentive changes too
HRIS and payroll vendors kept EEO-1 mapping tools and export files current because every mid-sized and large US customer needed them. If the federal filing ends, that becomes a feature serving a handful of state requirements, each slightly different. Some vendors will build and maintain a proper multi-jurisdiction reporting layer. Others will let the federal export age in place and leave customers to adapt it. It is worth asking your vendor which of those it intends to do before the renewal conversation, not after the first state deadline under the new arrangement.
Where self-identification gets switched off, and why it shouldn't
There will be a temptation, once the federal requirement lapses, to stop collecting demographic self-identification altogether. The argument has some surface appeal: less sensitive data held means less privacy risk, and data minimisation is a real principle.
The problem is that the legal exposure the data helped manage has not moved. Disparate impact claims remain available under federal and state law. Pay equity analysis depends on demographic data. So do the bias audits New York City requires for automated employment decision tools, which report results in race, ethnicity and sex categories. An organisation that stops collecting now will have a gap in its history exactly when it needs to show how a hiring algorithm or a pay decision affected different groups over time.
Five checks for the HRIS owner this quarter
Name an owner for the job-category mapping.Someone in HRIS or people analytics, with employment counsel signing off changes. Until now it has usually belonged to whoever ran the filing.
Version the mapping.Colorado refers to the form as it stood on a specific date. Keep a dated record of your mapping so that you can show which version any report used.
Add the second taxonomy now.If you employ anyone in California, map job codes to standard occupational groupings ahead of the 2027 report rather than during it.
Keep self-identification switched on.If the collection design is changing, make that a documented decision with legal input, not a side effect of a form redesign.
Ask the vendor a direct question.Will it maintain state-specific reporting outputs, and which states, on what timetable?
None of this needs the final rule to be published. Whichever way the EEOC's rulemaking goes, the states have already decided that the data will keep being reported. What is still open is whether the classification behind it stays accurate once the one annual check that kept it accurate has gone.
Sources and notes. The EEOC voted 2–1 on 21 July 2026 to propose rescinding the EEO-1 and other EEO reports and related recordkeeping requirements; the proposal was published in the Federal Register on 23 July 2026 with a 30-day comment period that closed on 24 August, reportedly drawing around 3,000 comments. As of publication no final rule has been issued and the collection portal for 2025 data has not opened. State and local requirements are summarised from employment-law guidance published in September 2026 (including Nilan Johnson Lewis, Littler and HR Daily Advisor). New York City's bias-audit requirement for automated employment decision tools is referenced as context. Coverage thresholds, deadlines and effective dates, particularly for Colorado and New York City, should be verified against the statutes and agency guidance; they are summarised here from secondary sources. US-specific. Journalism, not legal advice. Corrections welcome.
