14 September 2026 EN ES
Employment Bench

Workplace law for the people who have to apply it on Monday

Illustration: Even Without EEO-1, Keep a Defensible Workforce-Data File
Policy

Even Without EEO-1, Keep a Defensible Workforce-Data File

If federal demographic reporting shrinks, your workforce-data file still has to answer pay-equity and discrimination questions without a scramble.

Federal reporting changes do not erase the data problem

Your workforce-reporting calendar may need a new line item. The EEOC proposed rescinding the annual EEO-1 through EEO-6 workforce demographic reporting and related recordkeeping rules on July 23, 2026. The agency had voted 2-1 on July 21, 2026, to propose ending employer demographic data reporting. The proposal would eliminate EEO-1, EEO-2, EEO-3, EEO-4, and EEO-5 reporting requirements. Before the public proposal, the Office of Information and Regulatory Affairs received an EEOC proposal on May 14, 2026 whose title called for rescinding EEO-1 through EEO-5 and reporting requirements under Title VII, the ADA, GINA, and the PWFA.

For an HR lead, the practical question is not whether the federal form disappears. It is whether your files can still answer a pay-equity question, a contractor audit, or a discrimination claim. Federal law may require fewer filings. It does not require you to stop documenting why pay, promotion, and selection decisions were made.

State and local rules can still demand data. A local pay-data law can require annual reporting even when federal forms shrink, so the data behind the old federal form may still be useful. Federal contractor rules can change too. Those changes alter the filing calendar, not the need for a clean record.

Three buckets keep the file from becoming a paper pile

Keep a single file, not several. The buckets are a way to decide what belongs in the file and who owns it. Each item below should be testable: can you point to it, open it, and say what it means?

  • Legally required filings: confirm whether EEO-1 is still due this cycle, because current regulations set the completion date at September 30 of each year.
  • Legally required filings: if you are a private employer with at least 200 employees in New York City, calendar the annual pay-data report required by the city's December 4, 2025 pay-data law, based on the former EEO-1 Component 2 pay-band model.
  • Legally required filings: if you are a federal contractor, note the OFCCP final rule that removes the disability self-identification requirement and the 7% utilization goal.
  • Pay-equity benchmarking data: keep job families, pay bands, salary ranges, and the date each range was reviewed.
  • Pay-equity benchmarking data: keep promotion, transfer, and bonus criteria tied to the same job families.
  • Discrimination-defense records: keep selection notes, interview scores, rejection reasons, and the decision-maker for each hire or promotion.
  • Discrimination-defense records: keep complaint files, investigation summaries, and corrective actions together.

Filing items set the legal floor. They tell you what a regulator or court may ask for first. Benchmarking and defense items are good practice, not current federal filings. Benchmarking items let you compare pay across groups without rebuilding the dataset after a claim. Defense items show that a decision had a stated reason rather than a reconstructed one.

The file should be small enough that a new HR lead can find it after a turnover. A single folder or shared drive works if it has a consistent name, a date stamp, and a note on who approved the data. Build it as a file that can be produced without a long search, not a data warehouse.

Make the file usable before a dispute starts

Treat the workforce-data file as a working record, not a display piece. If a manager asks why employees in the same job family have different pay, the file should answer with the range, the review date, and the decision notes. If a plaintiff asks why a candidate was selected, the file should show the criteria, the scores, and the person who made the call.

A clean file also helps with internal reviews. It gives managers a shared reference point when pay bands change, when a role is reclassified, or when a promotion is questioned. That keeps the conversation focused on the decision, not on reconstructing it.

Do not wait for a dispute to assemble it. Assign a single owner, usually the HR lead who already owns reporting. Set a regular review that checks whether the filing calendar, the pay-equity data, and the decision records are current. Keep the file narrow enough to maintain and broad enough to defend. When reporting changes, update the owner and the calendar promptly.

Advertisement