State Pay Data and Workforce Reporting
Five states now require some form of pay or workforce data reporting, and no two of them are the same obligation. They differ in what triggers coverage, what data is collected, who it goes to, and how often.
The common error is treating them as variations on California's pay data report. Only one of them actually is.
The comparison
| State | What it is | Threshold | Frequency | Data |
|---|---|---|---|---|
| California | Pay data report | 100+ employees with ≥1 in CA; separate 100+ labor contractor test | Annual, second Wednesday of May | Aggregated pay bands, hours, mean and median hourly rate by group |
| Illinois | Equal Pay Registration Certificate | 100+ employees in Illinois | Every 2 years | Individual-level wage, hours and demographic records |
| Massachusetts | Wage data report | 100+ employees in the Commonwealth, federal EEO filers | Annual, February 1 | A copy of the federal EEO report |
| Minnesota | Equal Pay Certificate | 40+ full-time, and a covered contract | Every 4 years | Compensation methodology, not data |
| Colorado | Demographic workforce data (from July 2027) | 100+ workers | With the periodic corporate report | Federal EEO-1 demographic data - not pay |
What actually distinguishes them
California is the only one collecting compensation data at scale. Pay bands, total hours worked, and mean and median hourly rate - computed within every combination of establishment, job category, pay band, race or ethnicity and sex.
Illinois is the most invasive. It collects individual records for every employee - wages, hours including paid time off, start date, county, collective bargaining status. California aggregates; Illinois does not.
Massachusetts collects nothing new. You file a copy of a report you already produced federally.
Minnesota asks a different question entirely. Not what you paid, but how you decide what to pay. And it's triggered by winning a contract, not by operating in the state.
Colorado isn't a pay report at all. It's demographic data attached to a corporate filing.
Two structural risks worth planning around
Massachusetts and Colorado both depend on the federal EEO-1. Massachusetts requires a copy of the federal report; Colorado requires the data from it. In July 2026 the federal agency proposed rescinding the EEO-1 entirely.
Colorado wrote around this - its statute requires the data even if the federal requirement is repealed. Massachusetts did not, and it isn't obvious what Massachusetts employers would file.
The practical implication: don't stop collecting EEO-1-format demographic data on the assumption that the federal requirement is going away. At least one state has already made that data mandatory independent of federal law, and more may follow.
California's job categories change. For the reporting year filed in May 2027, California moves from 10 job categories to 23 occupational major groups. That means re-mapping every job in your workforce, and the work has to start well before the filing window opens.
What a multi-state employer actually faces
Operating in all five states means:
- Five different thresholds - 40, 100 (in-state), 100 (in-state), 100 (total with one in-state), and 100 workers
- Four different frequencies - annual, biennial, quadrennial, and tied to a corporate filing cycle
- Four different data models - aggregated pay bands, individual records, a copied federal form, and a methodology narrative
- Four different recipients - a civil rights department, a labour department, a Secretary of State, and a human rights department
There is no single dataset that satisfies all of them. What is common is the underlying source: headcount, demographics, hours and compensation from the same systems, sliced differently.
What to build once
The filings differ; the source data doesn't. A workforce dataset that carries the following will feed all five:
- Employee-level demographics, with the categories each state uses
- Work location, to establishment and county level
- Job classification, mapped to both the 10 federal categories and the 23 occupational major groups
- Total annual earnings, and the ability to derive an hourly rate for salaried employees
- Hours worked including paid time off
- Employment type, exemption status and collective bargaining status
- Start and end dates
- Remote work status
Every one of those appears in at least two of the five filings. Building it once and slicing it five ways is the only version of this that scales.
Frequently asked questions
Which states require pay data reporting?
California, Illinois, Massachusetts, Minnesota and Colorado - though only California collects pay data in the fullest sense.
Are they the same filing in different states?
No. They differ in trigger, data, frequency and recipient.
Which is the most demanding?
Illinois, for data - individual records for every employee. California, for complexity - aggregation across many dimensions plus mean and median rates.
Which is the easiest?
Massachusetts. You file a copy of your federal EEO report.
Do we need a Minnesota certificate if we don't bid on contracts?
No. It's a contractor prequalification.
What happens if the federal EEO-1 is eliminated?
Colorado's requirement continues by statute. Massachusetts is unresolved.
What's changing in California?
Job categories go from 10 to 23 for the report due in May 2027.
This guide is general information about reporting requirements, not legal advice. Verify current deadlines, thresholds and penalty amounts against the issuing agency before you file.