EEOC Proposes Eliminating EEO-1 Reporting: What Government Contractors Need to Know

For decades, EEO reporting has been a familiar part of the compliance landscape for many employers and government contractors. That landscape could soon change.

On July 21, 2026, the U.S. Equal Employment Opportunity Commission (EEOC) announced a proposal to eliminate its EEO Data Reports, including the EEO-1 report used by private employers and certain federal contractors. The proposed rule was subsequently published in the Federal Register on July 23, 2026.

For GovCon HR and recruiting leaders, the most important word is proposed.

The reporting requirements have not simply disappeared. The EEOC is going through the federal rulemaking process, including a public comment period and public hearing, before making a final determination. In the meantime, government contractors should understand what the agency is proposing and avoid interpreting the announcement as a reason to abandon disciplined recruiting documentation and compliance practices.

What Is the EEOC Proposing?

The EEOC's proposed rule would rescind requirements for filing six categories of EEO Data Reports: EEO-1, EEO-2, EEO-3, EEO-4, EEO-5, and EEO-6. It would also eliminate the recordkeeping and record-preservation requirements specifically associated with those reports under 29 CFR Part 1602.

For private-sector employers and government contractors, the EEO-1 proposal is particularly significant.

The EEO-1 reporting framework dates to 1966. Historically, covered employers have reported workforce demographic information organized by categories including race/ethnicity, sex, and job category. The EEO-1 was originally adopted for joint use by the EEOC and the Office of Federal Contract Compliance Programs (OFCCP).

The EEOC now says the reports should be eliminated.

According to the agency, the current EEO data collection requirements impose almost $275 million in annual costs on employers, along with nearly $4 million in annual administrative costs for the EEOC. The Commission has preliminarily concluded that the reports are not narrowly tailored or necessary for enforcing federal anti-discrimination laws and that their limited value is outweighed by the burden of requiring organizations to report the information routinely.

The proposal also raises legal and constitutional arguments concerning government-mandated classifications based on race and sex. These are the EEOC's stated rationales in the proposed rule; at this stage, they remain part of a rulemaking proposal rather than a final regulatory determination.

What the Proposal Does NOT Mean

One of the most important distinctions for employers is that the proposal concerns routine EEO Data Reports and the recordkeeping requirements specifically associated with those reports.

It does not eliminate the EEOC's ability to investigate employment discrimination.

The proposed rule expressly states that the Commission's authority to request relevant records from a particular employer during an investigation of a discrimination charge would remain unchanged. The EEOC distinguishes those targeted requests from the routine collection of demographic information from covered organizations regardless of whether a discrimination allegation exists.

That distinction matters.

A reduction in one reporting requirement should not be confused with the disappearance of the need for reliable hiring records, consistent processes, or the ability to understand what happened during a recruiting decision.

What This Means for Government Contractors

For GovCon organizations, compliance has never been simply a matter of producing one annual report.

Recruiting can involve contract-specific positions, security clearance requirements, multiple recruiters and hiring managers, subcontracting partners, candidate dispositions, and large volumes of outreach to both applicants and passive candidates.

That complexity makes a reliable system of record valuable even when an individual reporting requirement changes.

AgileATS was designed around this reality. The platform's compliance capabilities have historically included EEO, OFCCP, and AAP reporting alongside structured candidate and recruiting data. More broadly, AgileATS is built around GovCon-specific workflows, including contract-to-job relationships, candidate history, clearance information, hiring workflows, analytics, and compliance functionality.

The regulatory environment may evolve. The operational need to know who entered your recruiting process, what happened, why decisions were made, and where supporting information resides does not disappear with a proposed change to one reporting framework.

Don't Let Less Reporting Become Less Discipline

There is a broader lesson here for recruiting organizations.

Good documentation should not exist only because someone has to produce a report at the end of the year. A mature recruiting organization documents activity because the information makes the organization better.

“If it’s not in your ATS, it never happened.”

Recruiters should have a centralized history of candidate interactions, notes, communications, applications, workflow activity, and follow-ups. Leadership should be able to understand where candidates are in the hiring process and identify bottlenecks before those bottlenecks cost the company a hire.

That same structured data creates visibility and accountability across recruiters, hiring managers, program managers, HR teams, and executives. AgileATS's visual Hiring Board and analytics are designed to give those stakeholders a common view of the hiring process instead of forcing teams to reconstruct activity across email, spreadsheets, and disconnected systems.

In other words, compliance-ready recruiting and high-performance recruiting are not competing objectives.

The same discipline that makes records easier to retrieve can also help teams identify stalled candidates, improve follow-up, measure recruiter activity, understand time in stage, and make better hiring decisions.

Compliance Technology Needs to Adapt With Regulation

The EEOC proposal is also a reminder of why GovCon companies should evaluate recruiting technology differently from organizations operating in less regulated environments.

Government contractors shouldn't have to redesign their entire recruiting operation every time a regulation changes.

Instead, the ATS should serve as the system of record: capturing structured information during the normal recruiting workflow so organizations have reliable data available for whatever reporting and documentation requirements apply.

That's part of the philosophy behind AgileATS's compliance-first approach. Rather than treating compliance as a year-end spreadsheet exercise, AgileATS is designed to capture recruiting activity and documentation throughout the workflow.

And compliance is only one piece of the platform. AgileATS combines that approach with a GovCon-focused ATS, visual Hiring Board, contract management, candidate repository, Partners Portal for subcontractors and staffing partners, automation, outreach, and recruiting analytics.

The goal is not simply to generate a report.

It's to create a faster, more visible, more accountable recruiting operation—and maintain the information necessary to respond as requirements evolve.

What Happens Next?

As of this writing, this is still a proposed rule.

The Federal Register notice states that comments on the proposal are due August 24, 2026, and the EEOC has scheduled a public hearing for August 11, 2026. The Commission has said it will consider public comments and relevant data before making a final determination.

GovCon organizations should therefore monitor the rulemaking process and work with their legal and compliance advisors before changing established reporting or recordkeeping practices.

But there is also a larger takeaway for recruiting leaders:

Regulations change. Your recruiting data shouldn't become chaos when they do.

This article is provided for general informational purposes and is not legal advice. Organizations should consult qualified legal or compliance professionals regarding how proposed or final regulatory changes affect their specific obligations.