Anonymize EEO-1 report source data for internal auditing – CCPA/HIPAA-compliant de-identification per 29 CFR §1602
EEO-1 reports aggregate workforce demographics by race, ethnicity, sex, and job category under EEOC record-keeping rules at 29 CFR §1602. The underlying source data links demographic attributes to individual employees. anonym.legal pseudonymizes those linkages so HR analytics teams can audit pay-equity and workforce-composition trends without exposing individual identity-and-demographic pairings. An EEO-1 report is a mandatory annual compliance survey requiring covered private employers to report workforce demographics to the EEOC. The underlying analysis often applies the four-fifths rule from the EEOC's 1978 Uniform Guidelines on Employee Selection Procedures, under which a selection rate below 80% of the highest-selection-rate group can signal adverse impact traceable to Title VII of the Civil Rights Act of 1964.
When this applies
Apply this workflow before sharing EEO-1 source datasets with external diversity consultants, internal analytics teams, or litigation-support vendors where the task is workforce-composition analysis rather than individual-employee review, including four-fifths-rule adverse-impact screens under the 1978 Uniform Guidelines.
How anonym.legal handles it
- Upload the EEO-1 source file (CSV, XLSX, or structured export) to anonym.legal.
- The engine maps each row's employee identifier fields — name, employee ID, SSN fragment — against the EEOC's 29 CFR §1602 data-element taxonomy.
- Each employee record is assigned a consistent pseudonymous identifier that persists across the dataset, preserving the statistical linkage between job category and demographic data.
- Direct identifiers (names, partial SSNs, home addresses) are replaced while protected-class fields (race, ethnicity, sex, job category code) are retained for analysis.
- The output dataset is exported in the same structured format as the source file for seamless import into analytics tools.
- A reversible mapping key is stored encrypted for re-identification if individual follow-up is required.
What you provide
- EEO-1 source data file in CSV, XLSX, or structured HR-system export format
- Field mapping confirming which columns represent direct identifiers vs. demographic attributes
- Scope definition: single establishment or multi-establishment consolidated report
Limitations & cautions
- anonym.legal does not prepare or submit the EEO-1 report itself; the tool processes source data only.
- Demographic fields are retained, not anonymized, because removing them defeats the purpose of equity analysis; re-identification risk from demographic combinations should be assessed separately.
- State EEO reporting requirements may differ from federal EEO-1 requirements and are not addressed by this workflow.
- Small demographic cells (fewer than 5 individuals per category) may still carry re-identification risk despite pseudonymization; statistical disclosure-limitation techniques should be applied separately.
- The four-fifths (80%) rule is a rule of thumb, not a safe harbor; a ratio at or above 80% does not foreclose a disparate-impact finding under Title VII of 1964, and this workflow does not perform that legal analysis.
FAQ
Does this workflow cover both Type 1 and Type 2 EEO-1 consolidated reports?
Yes. The tool processes the underlying source dataset regardless of whether you are preparing a single-establishment or multi-establishment consolidated report. The pseudonymization applies at the individual-employee row level across all establishment units, consistent with recordkeeping rules that trace to Title VII of 1964.
Will pseudonymizing the source data affect the accuracy of the final EEO-1 submission?
No. The pseudonymized dataset is for internal analysis only. The final EEO-1 submission is prepared from your authoritative HR system; you re-identify the records using the stored mapping key before any submission to the EEOC, whose 1978 Uniform Guidelines govern the underlying selection-rate analysis.
Can this workflow help with pay-equity analysis beyond the EEO-1 report?
Yes. The pseudonymized dataset can be enriched with additional compensation fields before sharing with consultants, enabling pay-equity regression analysis without disclosing individual employee identities, including analysis framed around the Equal Pay Act of 1963.