EEO-1 report rescission is not a reason to stop collecting data
The EEOC has proposed ending the EEO-1 filing requirement, but state pay-data rules are expanding, and Title VII recordkeeping survives the report. Here is what people ops should keep intact.
The EEO-1 report rescission proposal is the most consequential federal reporting change HR has seen in years, and it is arriving fast. The EEOC published a proposal to eliminate the EEO-1 requirement, held a public hearing on August 11, 2026, and closed its comment window on August 24. That puts a decision point inside the next few weeks, and it is already prompting a dangerous internal question in HRIS teams: can we finally turn off demographic collection?
What the EEOC has actually proposed
The Commission's proposal would rescind the EEO-1 reporting requirement, the annual workforce demographic filing that has long applied to private employers at a 100-employee threshold and to federal contractors at a lower one. Employers should confirm the current thresholds and any transition language against the EEOC's own instruction booklet and the published notice rather than relying on secondhand summaries, because scope details are where compliance programs usually get tripped up.
Coverage from Epstein Becker Green's Workforce Bulletin and the ABA Banking Journal framed the move as a genuine end to federal EEO reporting rather than a simplification. Federal contractor implications were a central thread at the August 11 hearing, and DirectEmployers Association published a contractor-focused readout on August 18. For contractor-heavy organizations, that is the section of the record worth reading closely.
Nothing is final yet. A proposal plus a closed comment window means a rule could land quickly or could be revised, and litigation over any final action is plausible. The planning posture for HR is therefore conditional: prepare for the filing to disappear, but do not act as though the underlying data no longer matters.
Turning off demographic collection is a one-week HRIS change. Rebuilding a clean data set across a distributed workforce can take a year.
State obligations are moving in the opposite direction
While federal reporting contracts, state reporting expands. Jackson Lewis's July 2026 survey of pay transparency obligations and analyses from Gunderson Dettmer, Hunton and Vorys on California's pay transparency and reporting overhaul effective January 1, 2026 all point the same way: more jurisdictions, more required fields, more frequent filings. GovDocs' tracker has continued to log additions through 2026.
The practical effect is fragmentation rather than relief. An employer that files one federal report today may soon file several state reports on different calendars, with different job-category definitions, different pay-band logic and different demographic groupings. That is more work for people ops, not less, and it is work that depends entirely on the same underlying race, ethnicity, gender and job-classification data the EEO-1 collected.
Multistate employers should map their footprint against current state requirements now, while the federal question is still open. If the EEO-1 goes away and your only demographic pipeline was built to feed it, the first California or Illinois filing after that will be a scramble.
Why the data outlives the report
Title VII recordkeeping obligations do not disappear because a report does. Employers still need to preserve personnel and employment records, and demographic data remains the raw material for defending adverse-impact claims, responding to charges, and answering agency information requests. A company that stops collecting it does not become less exposed. It becomes less able to explain itself.
The internal uses matter just as much. Pay equity audits, promotion-rate analysis, attrition patterns by job family and representation reporting for customer or investor diligence all draw on the same fields. Many commercial contracts and institutional investor questionnaires still ask for workforce composition data, and those requirements are not tied to the EEOC's rulemaking calendar.
There is also a rebuild cost problem. Demographic self-identification data is slow to reacquire once a pipeline goes dark. Turning collection off is a one-week HRIS change; restoring a clean, high-response-rate data set across a distributed workforce can take a year or more.
A practical checklist for people ops teams
Treat any rescission as a filing change, not a data-retention change. Keep collecting race, ethnicity, gender and job-category data, keep the job-category mapping current as roles are created and reorganized, and keep the self-identification workflow in onboarding rather than quietly retiring it. If the report ends, retire the submission step and nothing else.
Run a records retention review in parallel. Confirm how long personnel records are held, who can access demographic fields, and whether retention schedules were written to reference the EEO-1 filing rather than the statutory obligation. Schedules built around a report that no longer exists tend to fail quietly.
Finally, do not read this as an isolated event. The Department of Labor proposed new independent contractor and joint employment rules in 2026 and reopened an expanded PAID self-reporting program for wage-and-hour violations. The federal picture is shifting on several fronts at once, and each shift changes what data you need on hand to answer questions later.
