If EEO-1 disappears, keep the data that lets you defend pay and promotion decisions

A memo may tell you the EEO-1 filing is ending. The EEOC has proposed ending the report that asks employers for employee information by race, ethnicity, sex, and job title. The useful question is which internal records will let you answer a pay or promotion challenge.

The filing is a compliance task; the internal file is a management tool. Once the report stops, the second one still has to work.

The report helps the agency find cases

Experts and former EEOC employees say the agency would have a harder time identifying widespread discrimination in hiring and promotions without the EEO-1 demographic data. It also surfaces the share of women in senior executive roles and the racial composition of the lowest-paid employees. Those numbers show where pay and promotion decisions may need explanation.

Each year, the agency receives roughly 90,000 discrimination complaints. It cannot investigate all of them. The EEO-1 data is among the first tools investigators use to choose which matters to pursue with limited enforcement resources and low staffing. A case may still arise even if your company is not in the report, but the data you keep will shape how quickly you can answer.

Your records are the defense file

If a complaint is not settled and the agency sues, the EEO-1 data can support the case in court. In the Central Transport case, the agency used EEO-1 data to show a steady statistical gap between female truck drivers hired and female applicants. A company without clean job-level data has a harder time explaining a pattern.

Pay equity and disparate impact cases often turn on what the employer knew and what it could show. A promotion pattern that looks uneven should be answered with a dataset, not a narrative. A pay band that looks skewed should be answered with a comparison by job level, not a promise of fairness.

Counsel can argue intent, but a pattern question is usually answered with numbers. The numbers should be tied to job level, not to a vague category like leadership or technical staff. A changed job title needs a mapping.

The legal requirement is narrower than the operational one. You need to be able to explain decisions under challenge. Good practice is to keep the data in a form that can be produced without reconstructing it from memory.

Preserve the data before deletion

Before any system is cleaned, archived, or handed to a vendor, build a preservation file that can stand up to a request from counsel or a regulator. The list below is the minimum.

• Job-level headcount by race, ethnicity, sex, and pay band.
• Promotion dates, job-level changes, and role history for each position.
• Applicant flow data: source, stage, outcome, and reason for non-selection.
• Vendor data requests and retention instructions for the systems that hold the records.

Do not preserve everything. Preserve the fields that let you compare like with like. A file that mixes job families, pay bands, and promotion dates without a key will be hard to use on a narrow question.

Keep the data in a form that can be joined. Headcount needs pay bands, promotion logs need job levels, and vendor exports need retention instructions before use. Aim for a file that lets counsel answer a specific question in a reasonable time.

The file should be complete, dated, and usable before a reviewer asks for it.