16.5 Statutory Workforce Reporting: EEO-4, Recordkeeping, & Compliance Data Requests

16.5 Statutory Workforce Reporting: EEO-4, Recordkeeping, & Compliance Data Requests

PSHRA names this domain "Public Sector HRIS Data Analysis and Reporting." The reporting half is not an afterthought: a public jurisdiction is a reporting entity in a way a private employer is not. It answers to the EEOC, to state civil service commissions and oversight boards, to auditors, to the legislature that appropriates its payroll, and to any member of the public with a records request. Dashboards are discretionary. Statutory reports are not, and the senior HR leader signs them.

The unifying insight for this section: every statutory report is a query against the HRIS. If the underlying data model cannot produce the report cleanly, the jurisdiction is not merely inefficient — it is out of compliance, and the defect surfaces on a two-year cycle in front of a federal agency.

---

1. The EEO-4: The Defining Public Sector Report

The State and Local Government Information Report, EEO-4, is the public-sector counterpart to the private sector's EEO-1. It is administered by the EEOC under section 709(c) of Title VII, 42 U.S.C. § 2000e-8(c), and implemented at 29 CFR 1602.30 through 1602.37.

The two thresholds candidates confuse

This is the most commonly missed distinction in the entire reporting area, because the recordkeeping duty is far broader than the filing duty:

A 40-employee special district files nothing but must still be able to produce EEO-4-equivalent data on demand. A director who tells the governing body "we're under 100, so this doesn't apply to us" is wrong about the half that matters most in an investigation.

Filing mechanics

• Frequency: Biennial, in odd-numbered years (29 CFR 1602.32).
• Data reported: Workforce counts broken out by job category, salary band, sex, and race/ethnicity, aggregated by function.
• Retention of the report itself: A copy of the most recently filed EEO-4 must be retained at the central office of the political jurisdiction for 3 years and produced if requested by the Commission under section 710.
• Agency-level detail: Although data are aggregated by function for reporting, separate data for each agency must be maintained, either by the agency itself or by the central office responsible for preparing the form.
• Confidentiality: Section 709(e) of Title VII restricts release of individually identifiable information.

Job categories

The EEO-4 uses eight job categories, which are not the EEO-1 categories:

1. Officials and Administrators
2. Professionals
3. Technicians
4. Protective Service Workers
5. Paraprofessionals
6. Administrative Support
7. Skilled Craft Workers
8. Service-Maintenance

[!IMPORTANT] Read the current instruction booklet, not a memorized list. The EEOC has revised the collection over successive cycles — recent collections distinguish sworn from non-sworn protective service workers — and the exact salary bands are set by the instruction booklet issued for each cycle. 29 CFR 1602.30 expressly incorporates the instructions by reference and gives them "the same force and effect as other sections of this part." Never map a jurisdiction's classification plan to the EEO-4 from memory or from a prior cycle's crosswalk.

---

2. Records Preservation: 29 CFR 1602.31

Separate from the report, political jurisdictions must preserve personnel and employment records for 2 years from the date the record was made or the date of the personnel action, whichever occurs later. The regulation names the covered record types expressly — requests for reasonable accommodation, application forms, and records concerning hiring, promotion, demotion, transfer, layoff, termination, rates of pay and other compensation terms, and selection for training or apprenticeship.

Two rules on top of the baseline:

• Involuntary terminations: the terminated individual's personnel records must be kept for 2 years from the date of termination.
• The litigation hold overrides the schedule. Where a charge of discrimination has been filed, or the Attorney General brings an action under Title VII, the ADA, or GINA, the jurisdiction must preserve all personnel records relevant to the charge until final disposition. "Relevant" is defined broadly: records of the aggrieved person and of all other employees holding similar positions, plus application forms and test papers of the unsuccessful applicant and of all other candidates for the same position.

The operational failure mode is entirely predictable: an automated HRIS or applicant-tracking purge job runs on a 2-year rule and deletes comparator records the day after a charge is filed. A public agency's retention automation must be interruptible by a legal hold, and the hold must reach the ATS, the HRIS, email, and shared drives — not just the paper file. This is a data-governance control, not a legal-department problem.

---

3. The Wider Public Reporting Stack

The EEO-4 is the anchor, but a senior public HR leader is accountable for a recurring reporting calendar that touches several regimes:

Note the different natures of these obligations. UGESP requires you to be able to prove something about a process you already ran. GASB requires actuarially usable census data, and a census data error is an audit finding against the jurisdiction's financial statements, not against HR. Transparency portals publish unaggregated individual records to the world, which raises the cost of a position-control or payroll data error from an internal annoyance to a public correction.

---

4. Building an HRIS That Can Actually Report

Reporting failures are almost never caused by the report. They are caused by four data-model defects:

1. No maintained crosswalk. The jurisdiction's classification plan must map to EEO-4 job categories through a stored, versioned crosswalk attached to the class specification, refreshed each cycle against the current instruction booklet. Reconstructing the mapping by hand every two years guarantees inconsistency across cycles — and inconsistency across cycles is exactly what an investigator notices.
2. Multiple conflicting demographic fields. Race/ethnicity and sex must live in one authoritative self-identification field of record, with a documented policy on non-disclosure and on visual identification. Recruiting-system demographics, benefits-system demographics, and HRIS demographics diverging is a reporting defect waiting to surface.
3. No governed snapshot date. Every statutory report is a point-in-time extract. The snapshot date, the extract logic, and the resulting file should be archived together so the exact number filed can be reproduced years later when a charge is investigated.
4. No attestation trail. Someone signs the report. Record who certified it, against which extract, reviewed by whom, and on what date. In a public agency this is an accountability record, and its absence converts an ordinary data error into an apparent concealment.

[!NOTE] The reconciliation discipline. Before filing, reconcile the report's total headcount to the payroll register and to position control for the same snapshot date, and document any variance. Three systems that disagree about how many people the jurisdiction employs is the single most common finding in a public HR data audit, and the reconciliation memo is what turns a variance into a documented, defensible difference.

---

5. Reporting as Strategy, Not Just Compliance

The senior-level move is to treat the statutory extract as a free strategic dataset. The EEO-4 crosswalk gives the jurisdiction a standardized occupational structure and salary-band distribution across the entire workforce — which is precisely the frame needed for utilization analysis, pay-band compression review, and DEIA progress measurement. An agency that builds the EEO-4 as a rushed biennial fire drill spends the effort and gets only a filing. An agency that maintains the crosswalk continuously can run the same analysis any month, brief the governing body with it, and detect an adverse-impact trend two years before the next federal filing would have exposed it.