EEO-1 Reporting

What is the current EEO-1 reporting status?

Reporting year, filing window, and announced deadlines

As of November 7, 2026, the EEOC labels the 2024 EEO-1 collection closed and says it will post updates for 2025 when available. The page does not announce an open 2025 or 2026 filing window, so there is no verified current deadline to carry forward. Check the EEOC’s EEO data collections page before treating a portal or submission date as available.

Three dates need to be kept separate:

• Reporting year: the year to which the workforce snapshot belongs.
• Submission year: the calendar year in which the employer submits the report.
• Collection window and deadline: the period announced by the EEOC for that reporting year.

The authority behind that process also has separate layers. Title VII § 709(c) authorizes the EEOC to prescribe relevant reports and records through regulation or order after the required public hearing, subject to the provision’s limits. See the current statutory text. The implementing rule, 29 CFR 1602.7, identifies EEO-1 as revised Standard Form 100, also called the Employer Information Report EEO-1, and directs users to the form’s instructions.

Under the Paperwork Reduction Act (PRA), agency information collection requires the prescribed review, approval and control-number process. The EEOC’s July 2026 proposal explains that EEO reports require clearance from the Office of Management and Budget (OMB) under the PRA, while footnote 16 attributes the referenced approval to reporting years 2022–2024 and gives November 30, 2026 as its expiration. The official OMB instrument record links SF 100 to EEO-1 Component 1. The approval record displays the May 12, 2025 approval and November 30, 2026 expiration.

Those layers answer different questions. The statute supplies reporting authority, the regulation identifies the implementing report and Standard Form 100, and PRA clearance authorizes the information collection. Clearance or a displayed expiration date does not itself announce a filing window, authorize an unverified reporting year or repeal the regulation. It also should not be treated as an automatic three-year employer filing interval.

The completed 2024 cycle illustrates the distinction: employers reported 2024 workforce data in 2025. The EEOC opened that collection on May 20, 2025, and stated a June 24, 2025 deadline without granting an extension. Those dates belong to the closed 2024 cycle; they do not establish the next window. See the EEOC’s historical announcement for the 2024 collection.

While the collection is closed, an employer can still preserve the workforce records, category mappings, establishment assignments and reporting rationale needed for a possible future cycle. That preparation does not establish that a portal is open or that a certified filing has been completed. Monitor the EEOC’s collection notices for a new window and review any accompanying instructions before reusing the 2024 workflow.

A proposed repeal is different from a final rule

The EEOC’s July 23, 2026 proposed rule starts the rulemaking process; it does not itself repeal the reporting regulation. As of November 7, 2026, no final EEOC rescission had been identified in the reviewed Federal Register records, and 29 CFR 1602.7 still appeared in the current eCFR. Check the operative regulation and later EEOC rulemaking before relying on this dated status check.

A proposed rule, review of the proposal, and a final rule are separate stages. A press release cannot replace the operative regulation, and a closed collection cannot establish that the underlying duty has ended. The relevant legal status turns on whether a final rule has been issued and when it becomes effective—not on when the proposal was published or whether a portal is open.

The Department of Labor’s action is separate. Its August 21, 2026 final rule rescinded Executive Order 11246 implementing regulations, effective October 26, 2026. Footnote 11 expressly distinguishes that action from EEOC action concerning EEO-1 reporting. Rescinding the Labor Department’s contractor regulations therefore did not, by itself, repeal the EEOC’s Title VII reporting rule.

A federal contractor must examine both paths. A company with 130 workers may independently meet the current 100-employee Title VII reporting test. A 75-worker contractor requires a separate review of the authority and agency guidance applicable after the contractor-rule change. One announcement does not resolve both questions.

Caption: U.S.; checked November 7, 2026. EEOC rescission remains proposed in the reviewed record; 2024 collection is closed. State requirements need separate assessment; this is not an employer eligibility verdict. EEOC: collection status · EEOC: proposed rescission · eCFR: 29 CFR 1602.7 · Massachusetts: workforce FAQ

Which employers and workers fall within EEO-1 reporting?

Private employers, affiliated companies, and exclusions

A private employer subject to Title VII with 100 or more employees falls within the current EEO-1 reporting test. The employee count is an enterprise-level question for some organizations, not simply a total that can be checked separately for each legal entity. The current regulation at 29 CFR 1602.7 states the 100-employee threshold.

The 2024 EEOC instructions also require an affiliated-company review. Organizations associated through common ownership or centralized management may form a single or integrated enterprise for reporting purposes. Two separately incorporated entities that each employ fewer than 100 people are therefore not automatically outside EEO-1.

The EEOC’s own example combines 30 employees at a parent company with 35 employees at each of two subsidiaries, producing an enterprise total of 100. A hypothetical with two affiliated companies employing 60 and 40 people illustrates the same issue: each is below the threshold when viewed alone, but their combined workforce reaches 100. The exact aggregation conclusion depends on the entities’ ownership, control, management and other facts.

EEO-1 eligibility is also narrower than general coverage under Title VII. Title VII’s general private-employer coverage uses a 15-employees-and-20-weeks test, subject to specified exclusions. An employer can therefore fall within Title VII’s anti-discrimination provisions without meeting the EEO-1 reporting threshold. Failing to file EEO-1 does not itself remove an employer’s Title VII obligations.

Federal, state and local government employers and certain other organizations do not simply file the private-employer EEO-1. The EEOC’s collections page lists EEO-3 for local referral unions, EEO-4 for state and local governments, and EEO-5 for public elementary and secondary schools. A nonprofit, school or foreign-owned company is not automatically excluded. Those descriptions do not, by themselves, decide either EEO-1 eligibility or the organization’s separate responsibilities.

Federal contractors and the changing contractor rules

A federal contract does not settle EEO-1 coverage by itself. The employer must check both its employee count under the EEOC’s Title VII rule and any separate contractor-specific authority that remains in force.

For the completed 2024 cycle, the EEOC instructions described a contractor route based on 50 or more employees plus either:

• a qualifying prime or first-tier subcontractor relationship with a federal contract, subcontract or purchase order worth at least $50,000; or
• the separate route for qualifying federal-depository or savings-bond institutions, which was not a $50,000 bank-deposit threshold.

The historical instructions also contained exemptions and a construction-related proviso. Those conditions matter; “we have a government contract” is not a sufficient test on its own.

That 2024 test cannot safely be treated as a universal current rule. The EEOC’s collection page still repeats the historical 50-employee contractor language and cites the now-rescinded Executive Order 11246 regulations. Meanwhile, the current text of 29 CFR 1602.7 states that employers subject to Title VII with 100 or more employees fall within its reporting provision.

The Department of Labor’s August 2026 final rule rescinded the EO 11246 implementing regulations effective October 26, 2026. Footnote 11 expressly distinguishes that action from the EEOC’s EEO-1 rules. It therefore does not establish either that all contractor reporting ended or that every historical contractor threshold survives.

Consider two hypothetical employers:

• A 75-worker contractor needs current confirmation from the EEOC or counsel about the authority governing its case. The available sources do not establish a universal “must file” or “exempt” outcome for every contractor with 50–99 workers.
• A 130-worker contractor can independently satisfy the current 100-employee Title VII route, subject to the other requirements of the regulation.

“Contractor” also has two different meanings here. A business may contract with the federal government while its individual workers remain employees, independent contractors, or workers supplied by another employer. EEO-1’s coverage test does not determine that worker-status question.

VETS-4212, Section 503 and affirmative-action requirements are separate compliance programs. Their thresholds, contracts and consequences should not be imported into the EEO-1 filing analysis.

Employees, independent contractors, staffing firms, and PEOs

Under the 2024 instructions, the EEO-1 reporting population included full-time and part-time employees employed during the selected snapshot. Genuine nonemployee independent contractors are not employee headcount. An employed apprentice remains subject to the employee and snapshot rules, but the 2024 instructions do not support treating every trainee as an employee.

A payroll code, job title or contractor label cannot decide legal worker status by itself. The distinction between an employee and an independent contractor requires a separate factual and legal analysis, as explained in 4dev.com’s employee glossary entry. Before exporting an HRIS roster for EEO-1, the employer should verify which people meet the applicable reporting definitions rather than assume that everyone appearing in payroll belongs in the report.

Staffing and leasing arrangements require a separate reporting-allocation decision. The 2024 reporting definition excludes ordinary agency-payroll referrals working on another employer’s premises under that employer’s direction and control, with an exception for defined leased employees. A “leased employee” is a permanent employee supplied by an employment agency for a fee to an outside company, with the agency handling all personnel tasks. The leasing agency includes workers who meet that definition in its EEO-1 report; the client does not add them to its own headcount. This is a reporting allocation question; it is not a general conclusion about the legal status of the worker.

An employer should therefore test the actual arrangement instead of relying on a payroll code, the worker’s title or the provider’s EIN. The review needs to establish whether the agency supplied a permanent employee, whether it did so for a fee, and whether it handled all personnel tasks. A worker appearing in the client’s operational roster does not, by that fact alone, become client headcount.

This population rule differs from PEO reporting. A PEO may administer payroll and provide services for client employees, but those employees remain subject to the client employer’s reporting and certification. Under the 2024 PEO, HRO and ASO instructions, an eligible client has its own registration, EIN and complete report set. A provider may prepare or file the client’s data, but the client employer must designate one of its own employees as the certifying official. A provider employee cannot certify the client’s report.

For a mixed team, the practical control is a population review before data extraction:

1. Identify the full- and part-time employees employed during the applicable snapshot.
2. Identify agency-supplied workers and apply the ordinary exclusion and leased-employee exception to their actual arrangement.
3. Exclude genuine nonemployees and ordinary agency workers from client employee headcount.
4. Document unresolved classifications rather than silently including or omitting people.

A provider’s HRIS export or payroll file may help gather data, but it is not a reporting decision or a certified filing. A government-contractor business status likewise does not determine whether an individual worker is an employee, a leased employee or an independent contractor. Using a PEO does not combine all clients into the provider’s establishments or transfer the client’s filing responsibility to the provider. The employer should identify who supplies workforce data, who resolves reporting questions, and which employer employee performs the final certification.

What information goes into an EEO-1 report?

The workforce snapshot and fluctuating headcount

The 2024 EEO-1 report used an employer-selected pay period between October 1 and December 31 of the reporting year. It counted full- and part-time employees employed at any point during that period, rather than all people hired during the year, an annual-average full-time-equivalent figure, or the roster on the submission date.

An employee who left after the selected pay period remained part of the 2024 snapshot. Removing that person merely because they resigned before filing would produce an incomplete workforce count. Each employee is counted once.

The snapshot cannot be selected as an avoidance device. Suppose an employer employs 102 people in November but only 96 during its chosen December pay period. The 2024 instructions prohibit choosing that lower-count period in an effort to avoid reporting when the employer reached the reporting threshold at any time in Q4. The employer must review coverage rather than treat the December count as an automatic exemption.

These rules describe the completed 2024 cycle. Before using them for another reporting year, the employer should check the instructions issued for that cycle.

Caption: U.S. 2024 mechanics: include full- and part-time employees. Selecting a lower-count period in an effort to avoid reporting is prohibited if the threshold was reached in Q4. Later departures remain in the snapshot. EEOC: 2024 instruction booklet

Race, ethnicity, sex, and voluntary self-identification

The 2024 EEO-1 form counted employees in seven race or ethnicity reporting groups:

1. Hispanic or Latino
2. White
3. Black or African American
4. Native Hawaiian or Other Pacific Islander
5. Asian
6. American Indian or Alaska Native
7. Two or More Races

The six groups following Hispanic or Latino in this list are for non-Hispanic employees. “Hispanic or Latino” is reported regardless of race, so a Hispanic employee is not also counted in a non-Hispanic race cell. “Two or More Races” means a selection from more than one of the five non-Hispanic race groups; it does not mean Hispanic plus another race.

An employee is counted once. If someone identifies as Hispanic and Asian, for example, that person belongs in the Hispanic or Latino cell, not both that cell and the non-Hispanic Asian cell. The report’s demographic matrix then combines that single race or ethnicity placement with the employee’s sex and job category.

Employee participation in race and ethnicity self-identification is voluntary, but declining does not remove the person from the workforce count. The 2024 instructions direct employers to offer self-identification. If an employee declines, the employer may use employment records or observer identification. The employer must not invent an “unknown” demographic category or silently omit the worker. Identification records should also be kept separately from the basic personnel file and personnel-decision records.

An HR system’s identity fields do not automatically match the EEO-1 reporting fields. The employer must map the underlying information to the categories on the form for the applicable cycle. If the available information cannot be mapped cleanly, the issue should be resolved under the cycle instructions rather than by deciding that the employee is outside the report.

The 2024 instructions provided male and female sex-reporting options. An employee whose internal identity record does not map automatically to one of those options still requires a documented reporting decision; the employee cannot simply be dropped from the workforce count. The 2024 form also contained no separate Middle East or North Africa reporting category. A general federal statistical revision or an MENA field in another system does not change the EEO-1 form unless the applicable reporting instructions adopt it.

The ten job categories and role mapping

EEO-1 job classification follows the work an employee actually performs, the skills it requires and the responsibilities assigned—not the words in a job title alone. The 2024 instructions list these ten categories. The table pairs them with the standard row codes shown in the EEOC’s historical sample; confirm any cycle-specific submission schema before using the codes in a file:

Code	EEO-1 category	Illustrative work
1.1	Executive/Senior Level Officials and Managers	Chief executive officer or another official responsible for overall strategy and direction
1.2	First/Mid-Level Officials and Managers	Branch or team manager who implements management policies and directs day-to-day operations
2	Professionals	Engineer, accountant or another role requiring advanced professional knowledge and skills
3	Technicians	Drafter or chemical technician applying technical knowledge and skills to established processes
4	Sales Workers	Cashier or sales representative whose principal work involves sales
5	Administrative Support Workers	Bookkeeper or administrative specialist supporting routine office and administrative work
6	Craft Workers	Electrician or another skilled craftsperson
7	Operatives	Machine operator or other worker operating equipment or production processes
8	Laborers and Helpers	Freight or material mover performing laboring and material-handling duties
9	Service Workers	Cook, cleaner or another worker in food, cleaning and other service occupations

The two management categories depend on the level of organizational responsibility. Category 1.1 covers executive or senior officials responsible for overall direction and strategy. Category 1.2 covers officials and managers who implement policies and direct particular units or teams. The difference is responsibility, not whether the words “senior” or “manager” appear in a title.

Professional and technician classifications also turn on the work and its required knowledge. A chemical engineer and a chemical technician may work in the same industry, yet their responsibilities and qualifications can place them in different categories. A senior engineer remains a professional if the position does not carry the management responsibilities associated with category 1.1 or 1.2.

Someone who performs several jobs is reported once, in the job taking most of the employee’s time. The employer should document that decision and the underlying duties rather than create duplicate headcount.

EEO-1 classification must remain separate from FLSA exempt-status analysis. A category may appear convenient for payroll coding, but the Department of Labor’s overtime-exemption test uses its own duties-and-pay requirements. Copying an FLSA designation into the EEO-1 category without reviewing actual job functions can produce the wrong classification.

Component 1, historical Component 2, and pay information

Component 1 is the demographic headcount report: it counts employees by job category, race or ethnicity, and sex. It does not ask for each employee’s salary, earnings or hours worked.

Component 2 was a separate historical collection. For reporting years 2017 and 2018, it used W-2 earnings and pay-band information, together with hours worked, to examine compensation patterns. The EEOC’s historical announcement describes that pay-and-hours collection.

The current EEOC collections page describes Component 1 and does not announce a new Component 2 pay collection. That means an employer should not treat ordinary Component 1 reporting as a request for payroll data, or predict that Component 2 will return in a later year.

A payroll export may still be a useful source for reconciling the employee population, job categories or establishment assignments. That does not turn Component 1 into a payroll return. EEO-1 is also separate from Form W-2 filing and from state pay-data reports, each of which has its own authority, covered population and reporting period.

How are locations and establishment reports organized?

Single-establishment and multi-establishment employers

An establishment is a physical operating location; it is not necessarily a separate legal entity. Under the 2024 framework, an employer with one establishment files one single-establishment report. A multi-establishment employer uses a three-part structure:

• a headquarters report for headquarters employees;
• an establishment-level report for each covered non-headquarters location; and
• a consolidated report combining the workforce across headquarters and the other establishments.

The small size of an office does not remove it from the report set. The 2024 instructions replaced the older size-based Type 4, Type 6 and Type 8 framework, regardless of site size. There is no separate 50-worker threshold for a location within an otherwise covered employer. A site with no employees during the snapshot does not require an establishment report, while the instructions address combining records with the same address, EIN and NAICS code.

The 2024 portal workflow generated the consolidated report, but it could not discover a location the employer omitted. Headquarters and establishment totals must reconcile to the consolidated total, and every employee must appear once across the location reports. A company with a headquarters and two small offices therefore cannot place the whole workforce in the headquarters report and ignore the offices.

The geographical scope is also narrower than the employer’s global footprint. The 2024 instructions covered establishments in the 50 states and Washington, D.C.; they excluded Puerto Rico, the U.S. Virgin Islands and other protectorates. A foreign-based or foreign-owned company may have covered U.S. establishments, but overseas employees do not enter the report merely because the parent company is American or because the company operates in the United Kingdom or Germany.

Caption: Hypothetical U.S. 2024 report set: 40 + 35 + 25 = 100. Arrows show components, not a filing sequence. Small covered sites still need reports. This is a reconciliation example, not an eligibility determination. EEOC: 2024 instruction booklet

Remote workers, client sites, and organizational changes

Under the 2024 instructions, a remote employee was assigned to the establishment to which the employee reported—not automatically to a new establishment at the employee’s home address. If the employee does not report to an establishment but the employee’s manager does, use the manager’s establishment. If neither the employee nor the employee’s manager reports to a site, the 2024 instructions direct the employer to use headquarters. An employer with an entirely remote workforce uses its registered address. Ordinary telework or a temporary closure does not itself create an establishment, while a closure or reassignment can change the location to which an employee belongs.

Client-site workers follow a separate 2024 rule. The instructions allowed an employer to report these workers either at the client-site address or at an employer establishment. Each worker must still be counted once. The booklet’s discussion of a proposed 2025 change was intended guidance, not an adopted rule, and neither option should be assumed for a later cycle without checking its instructions.

Merger and acquisition timing also affects the report set. The 2024 instructions distinguish transactions completed before or during the Q4 snapshot from those completed after Q4. For example, an eligible acquirer completing an acquisition during Q4 would need to assess the acquired workforce as part of its snapshot. Post-Q4 treatment depends on issues such as which company held the relevant data and could require comments about missing information. A spinoff, closure or ownership change should therefore trigger a review of company identifiers, establishment records and access to workforce data, rather than reliance on a dated portal procedure.

Caption: U.S. 2024 instructions: test permanent assignment/reporting, not home address. If neither employee nor manager reports to a site, use HQ. An entirely remote employer uses its registered address. Client-site rules differ. EEOC: 2024 instruction booklet

How does an employer prepare and complete a filing?

Assign an owner and verify the company account

Assign one employer owner responsibility for the filing before gathering the data. The 2024 EEOC instructions distinguish an individual user account, a company profile and the employer’s OFS Company ID. The Company ID is not the IRS Employer Identification Number (EIN).

Registration also depends on the filer’s history:

• A new filer must establish the appropriate company profile and user access.
• A returning filer must recover or maintain access to the existing company profile.
• An employer whose former filer has left must update its account contacts and access arrangements rather than wait for a filing window to begin.

A shared group or headquarters profile should be used only as the applicable instructions permit. The company structure still needs to be reconciled with the reports and establishments the employer must submit.

The operational handoff should make four responsibilities explicit:

1. HR or workforce data: determine the reporting population, collect voluntary self-identification information and maintain establishment assignments.
2. Payroll or HRIS reconciliation: confirm employee counts, locations and the source of missing or conflicting records.
3. Compliance or legal review: resolve questions about coverage, worker inclusion and job classification.
4. Employer certification: have the designated certifying official review and certify the report.

This division of work is practical control design, not a list of legally prescribed job titles. Software, a consultant or a PEO can support collection, preparation or filing, but a vendor dashboard does not prove that the employer certified the report or that the EEOC received it.

Under the 2024 instructions, the certifying official had to be an employee of the employer filing the report. For PEO, HRO and ASO arrangements, a provider’s employee could prepare or submit the report but could not sign as the client’s certifying official. A supported filing therefore requires a clear handoff to the client employer’s authorized employee. The 4dev.com HR compliance guide provides a broader framework for assigning control owners and retaining review evidence.

Collect identifiers, validate totals, and choose an upload method

A raw HR export is only a source file. Before submission, the employer must confirm that it contains the right workforce, maps each worker once to the applicable job category and establishment, and uses the identifiers required by the current cycle.

The 2024 instructions separated several identifiers and reporting details:

• Company and establishment names and addresses identify the reporting organizations and locations.
• IRS EIN identifies the tax entity.
• NAICS code identifies the business activity. The 2024 instructions used the 2022 NAICS edition, rather than whichever edition was newest.
• OFS Company ID identifies the company profile in the reporting portal.
• Snapshot pay-period dates identify the period used to select the reported workforce. The file owner should carry the selected dates into the report and check the extracted population against that period.
• UEI replaced DUNS in the contractor-related workflow. Its applicability after the 2026 contractor-rule changes must be checked against the instructions for the applicable cycle; it should neither be imposed on every employer nor assumed to have been removed.

The data review should reconcile the selected employee population against the HRIS and payroll records, investigate missing or unknown values, document job-category and establishment mappings, and test that no employee appears twice. The demographic cells for each location should sum to that location’s workforce count.

A simple hypothetical reconciliation illustrates the control:

Report component	Employees
Headquarters report	40
Establishment report A	35
Establishment report B	25
Consolidated total	100

The arithmetic works only if the employer includes both establishments and counts each employee once. An automatically generated consolidated total cannot reveal a forgotten site.

The 2024 workflow allowed manual data entry through the portal or a file upload. Both routes still required the subsequent certification process. “Manual” meant portal entry, not the filing of a paper return, and an uploaded CSV or Excel file had to follow the cycle’s published specifications. The sample PDF demonstrated the report layout and information requirements; it was not a submission route.

No operative 2025 or 2026 upload specification was verified for this article. The employer should therefore avoid assuming that a 2024 column order, file format, validator or optional field remains current. It should wait for the specifications attached to an announced collection and use them when preparing the file.

Certify, save confirmation, and resolve errors

Submitting data is not the same as completing an EEO-1 filing. Under the 2024 instructions, a report remained incomplete without final certification, even if every row and column had been entered or the file had uploaded successfully. A successful upload therefore does not prove that the employer fulfilled the filing requirement.

The employer’s designated employee had to perform the final certification. The 2024 workflow then provided a certification email and allowed the employer to save a certified-report PDF. The owner should retain both the certified report and evidence of the filing status rather than relying on a vendor’s upload message. These mechanics describe the 2024 cycle; they do not establish what the currently closed portal permits.

If the employer finds an error, it should flag it promptly and check the support and correction procedure for the relevant collection. The 2024 cycle included processes for eligibility screening, correcting contact or company-profile information, and addressing ceased operations. It did not allow workforce-data corrections after that collection closed. The employer should not assume that a later collection reopened the earlier report, that a Message Center is currently available, or that a new correction route exists.

Timing also affects the options. Under the 2024 instructions, an employer could not simply submit a missing earlier-year return during a later collection. The EEOC also rejected extending that cycle beyond June 24, 2025. These historical facts do not create a universal grace period or predict a future deadline; they show why “the portal is closed,” “we missed the old deadline” and “a later collection is open” must be treated as separate questions.

A missed filing, a correction and a knowingly false statement are also different matters. The employer should preserve the source data, review results, certification evidence and support correspondence so that the final record shows what was reported, who certified it and how any error was addressed.

Caption: U.S. 2024 mechanics, not a live filing route. Data entry or upload alone is incomplete. A designated employee of the employer certifies; a PEO employee cannot certify for its client. Save the certified report and confirmation. EEOC: 2024 instruction booklet

What does an EEO-1 filing change—and what remains separate?

Enforcement, retention, and other record duties

An EEO-1 filing does not create one universal penalty for every late, missing or incorrect report. Under 29 CFR 1602.9, an employer that fails or refuses to file when required may be compelled to comply by order of a U.S. District Court. Knowingly and willfully false statements present a separate issue. The regulation does not support claiming that every late or innocent error automatically produces a fixed fine, imprisonment, contract termination or debarment.

Record duties also need to be separated by type. The current reporting rule at 29 CFR 1602.7 requires the employer to retain its most recent unit report. That is different from retaining the underlying workforce, personnel and decision records used to prepare the report.

29 CFR 1602.14 addresses relevant personnel and charge-related records separately. Relevant personnel records are generally retained for one year from the later of the record’s creation or the personnel action involved. Relevant charge or action records must be retained until final disposition. The one-year rule applies only to the relevant records covered by that provision; it is not a universal destruction date for every personnel record. Other statutes, employment policies, litigation holds and jurisdictional rules may require longer retention.

The July 2026 proposed rescission did not erase every preservation duty. Footnote 5 of the EEOC proposal distinguished report-specific requirements proposed for removal from the general record-preservation provisions identified in the proposal.

A delayed portal or a future repeal is therefore not a reason to destroy records. The employer should identify each record category, determine its applicable authority and check for an active investigation, charge or litigation hold. The 4dev.com HR compliance guide offers a broader control framework for classifying records and assigning review responsibilities.

Data uses, confidentiality, and limits of interpretation

EEO-1 data can support civil-rights enforcement and aggregate analysis of workforce patterns. An employer can also use the data internally to review category mapping and investigate possible disparities. These uses still require a lawful, proportionate process: the snapshot is a starting point for inquiry, not a substitute for examining the relevant hiring pool, roles, time periods and decision records.

An employer or researcher can compare workforce composition with aggregate data for a relevant industry, labor pool or geographic area to identify patterns worth examining. Such benchmarks support a limited comparison: job categories, available labor pools, geography and the period represented should be comparable. A difference from a broad benchmark does not by itself show that the employer’s decisions caused the difference or that any particular comparator should determine the employer’s workforce.

The report cannot establish why a difference exists. If management composition differs from the workforce overall, the employer should identify possible explanations and examine the underlying selection and development practices. The snapshot does not contain the information needed to determine whether a particular hiring or promotion decision was discriminatory. It also does not establish pay equality: ordinary Component 1 reporting contains demographic headcount rather than individual compensation or hours-worked data.

A demographic imbalance also does not establish a lawful numerical target. Any numerical goal or employment-practice measure requires its own legal analysis; it cannot be derived from an EEO-1 snapshot alone.

Confidentiality needs similar precision. An identifiable submission is different from the aggregate datasets that the EEOC publishes for research and public analysis, and both differ from information that the employer voluntarily discloses. Title VII § 709(e) restricts public disclosure of identifiable EEOC material before the relevant proceedings described in the statute. See the EEOC’s account of data use and public reporting.

Title VII § 709(d) provides a separate, limited government-access route. On request and without cost, the EEOC must furnish information obtained under § 709(c) to a state or local agency administering a fair-employment-practice law when the reporting employer falls within that agency’s jurisdiction. The recipient must not make the information public before a proceeding under the state or local law involving the information begins. If the recipient breaks that condition, the EEOC may decline later requests under the subsection. The start of a proceeding should not be read as unrestricted permission to publish the information. These conditions are set out in the current statutory text.

That route is different from an employer’s state filing duty. It describes a restricted transfer from the EEOC to a qualifying state or local agency; it does not create a state-only EEO-1 form, a universal sharing arrangement or permission for any agency to receive all employer information.

The statutory restrictions should not be converted into an absolute promise that no agency or Freedom of Information request can ever disclose information. The 2024 instructions also noted historically separate public-disclosure treatment for contractor information held by the former contractor compliance agency. The practical control is to limit identifiable working data to people with a legitimate reporting or review need, use the applicable legal access rules and avoid assuming that every submission is confidential in every context.

An employer that publishes its own figures makes a separate voluntary disclosure. It should verify the aggregation and context rather than presenting a snapshot as conclusive proof of discrimination, fairness, pay equality or a required quota.

State workforce and pay-data reporting

A closed or repealed federal collection does not answer whether a state reporting duty applies. State regimes may reuse a federal EEO-1 report, require a different workforce dataset, request pay information, or operate on a separate threshold and calendar.

Massachusetts uses the most direct reuse example. Covered employers are those with at least 100 employees in the Commonwealth at any time during the prior calendar year. They must provide a copy of their most recent EEO report on the state’s own annual calendar, with February 1 as the stated deadline and the next business day if needed. A change to the federal deadline does not automatically move the Massachusetts deadline, and the state does not require employers to create a new state-only EEO-1 for this purpose. The Massachusetts workforce reporting FAQ explains the covered-employer and report-version rules. The FAQ does not resolve every possible consequence of a permanent federal repeal.

California and Illinois operate separate programs rather than reuse Component 1 counts as a complete answer:

• California’s pay-data reporting program requires covered employers to submit annual pay, demographic and workforce data for specified payroll and labor-contractor populations.
• Illinois’s Equal Pay Reporting and Compliance program asks covered private businesses with at least 100 Illinois employees for demographic, wage and other data, with certification every two years.

These examples have different covered populations, data fields and reporting schedules. An employer must assess each regime against its own scope rather than import a universal 100-employee rule or treat an EEO-1 headcount as satisfying a state pay-data report.

Colorado provides a more precise preservation mechanism. The enacted HB26-1207 adds EEO-1 data to covered entities’ periodic reports beginning July 1, 2027. It expressly provides that the duty survives federal repeal or discontinuation and uses the federal EEO-1 form as it existed on March 1, 2026.

Colorado’s coverage is narrower than “every company with 100 workers in Colorado.” It applies to a private entity doing business in the state that has at least 100 workers and was required to submit EEO-1 as of March 1, 2026. The statute also excludes specified government, public-education and quasi-government entities.

The law is a future state reporting requirement, not a 2026 filing deadline. The reviewed evidence did not establish an implemented Colorado portal, submission format or detailed administrative procedure, so an employer should check the state’s implementation before filing. The practical consequence comes earlier: a federal change does not justify abandoning the demographic-data and job-category mapping workflow when a state statute expressly preserves the need for it.

Caption: Colorado HB26-1207; checked Nov 7, 2026. Listed government, public-education and quasi-government exclusions apply. Reports begin July 1, 2027; the duty survives federal repeal. No implemented portal or 2026 filing is asserted. Colorado: signed HB26-1207